After upgrading from 4.4.0 to 4.15.0 system doesn't boot - ACPI issue

[santicor]

I'm using Xubuntu in an old system, I'm concerned because other users looking for a light OS for their old PC wouldn't be able to install or boot the 18.04 version and above.

With kernel 4.4.0 the system boots without problem (xubuntu 16.04), after upgrading to kernel 4.15 the system doesn't boot anymore (18.04). This issue was present when testing kernel 4.13 too.

The install crashes with an error: BIOS bug:8254 timer not connected to io-apic error on.

Adding any of these commands to the boot allows the system to load properly:

-acpi=off
-pci=noacpi
-acpi=noirq

I attach the info related.

Ubuntu 4.15.0-32.35-generic 4.15.18
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: 1509 F.... pulseaudio
 /dev/snd/controlC1: 1509 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ed42d246-f10a-403e-a009-8c6428ce1a88
InstallationDate: Installed on 2018-06-12 (70 days ago)
InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
Lsusb:
 Bus 001 Device 002: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 248a:00da
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Inc Dimension C521
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=467ee8bd-241d-4d11-95d9-6d9268a1dca6 ro quiet splash pci=noacpi vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-32-generic N/A
 linux-backports-modules-4.15.0-32-generic N/A
 linux-firmware 1.173.1
RfKill:

Tags: bionic
Uname: Linux 4.15.0-32-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-08-17 (5 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1788387

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[santicor (scor)]

apport information

[santicor (scor)]

apport information

[santicor (scor)]

apport information

[santicor (scor)]

apport information

[santicor (scor)]

apport information

[santicor (scor)]

apport information

[santicor (scor)]

apport information

[santicor (scor)]

apport information

[santicor (scor)]

apport information

[santicor (scor)]

apport information

[santicor (scor)]

apport information

[santicor (scor)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18.3

[santicor (scor)]

I've tested the kernel 4.18.3

The headers file installed with errors:

/etc/kernel/header_postinst.d/dkms:
ERROR (dkms apport): kernel package linux-headers-4.18.3-041803-generic is not supported
Error! Bad return status for module build on kernel: 4.18.3-041803-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.48/build/make.log for more information.
ERROR (dkms apport): binary package for rtl8192eu: 1.0 not found
Error! Bad return status for module build on kernel: 4.18.3-041803-generic (x86_64)
Consult /var/lib/dkms/rtl8192eu/1.0/build/make.log for more information.

The kernel installed too, with these errors:

/etc/kernel/header_postinst.d/dkms:
ERROR (dkms apport): kernel package linux-headers-4.18.3-041803-generic is not supported
Error! Bad return status for module build on kernel: 4.18.3-041803-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.48/build/make.log for more information.
ERROR (dkms apport): binary package for rtl8192eu: 1.0 not found
Error! Bad return status for module build on kernel: 4.18.0-041800-generic (x86_64)
Consult /var/lib/dkms/rtl8192eu/1.0/build/make.log for more information.

The kernel didn't booted, it was necessary to add pci=noacpi to boot, after loging the network icon got cloned in the bar (two icons).

I attach the make.log files for nvidia and the wifi network driver.

[Kai-Heng Feng (kaihengfeng)]

Would it be possible for you to do a kernel bisection?

First, find the last good -rc kernel and the first bad -rc kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you found)
$ git bisect bad $(the bad version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression.

[santicor (scor)]

Hi, yes I can try.

The last good one is 4.4.154 and the first bad kernel is 4.13.0 (4.15 and 4.18 are confirmed problematic), I see the range between kernels is wide. How would I proceed to test?

Bye

[zunda (zundan+launchpad)]

I have seemingly similar problem on Intel NUC DE3815TYKHE (ntel Atom CPU E3815). On 4.15.*, it takes more than 5 minutes to unpack the initramfs (below is an example on 4.15.0-36). With the acpi=noirq, the kernel boots as usual.

$ dmesg | head -2; dmesg | grep -A1 initramfs
[ 0.000000] Linux version 4.15.0-36-generic (buildd@lgw01-amd64-031) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 (Ubuntu 4.15.0-36.39-generic 4.15.18)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a6268849-42cb-4d0e-80f3-eb2704407c01 ro vga=normal
[ 1.613146] Unpacking initramfs...
[ 350.054603] perf: interrupt took too long (2503 > 2500), lowering kernel.perf_event_max_sample_rate to 79750

[Kai-Heng Feng (kaihengfeng)]

Find the first bad/good -rc kernel to minimize the bisect range.