My trusty old IBM T30 laptop will no longer boot with the latest kernel-4.7.9-200.fc24.i686 kernel-4.8.4-200.fc24.i686 kernel-PAE-4.8.4-200.fc24.i686 It will still boot kernel-4.7.7-200.fc24.i686
The grub2 menu is displayed, and after selecting the 4.7.7-200 kernel there's a 2-3 sec delay with blinking cursor, then I'm prompted for the encryption passphrase for the /home filesystem. Then the voluminous messages (from removing the rhgb boot option) scroll forth and bootup proceeds normally.
However, If I choose any of the newer kernels, the blinking cursor remains forever; no prompt for the encryption passphrase occurs; the keyboard is totally non-responsive. Power cycling is required to recover.
Things I've tried: - dnf remove <the "bad" kernel>, and reinstall it. - Rebuild initramfs-4.8.4-200.fc24.i686.img with dracut. The new file is only one byte bigger, probably due to a different date, and still won't boot. - Added the secret 'dis_ucode_ldr' boot option, as revealed in https://www.reddit.com/r/Fedora/comments/4qrl1k/kernel_46_wont_boot_how_can_... but this seemed aimed at newer IBM laptops, and indeed, had no effect on my T30. - Updated the BIOS. The T30 has two components: the BIOS and the EC (Embedded Controller). My BIOS was up to date at version 2.10 but the EC was v. 1.03, while v. 1.07 was available. Sadly, updating to EC v. 1.07 did not alleviate the problem.
Any thoughts, shared experience, commiserations, suggestions?
What can be so different about these newer kernels?
On Thu, 10 Nov 2016 16:24:31 -0500 "David A. De Graaf" dad@datix.us wrote:
My trusty old IBM T30 laptop will no longer boot with the latest kernel-4.7.9-200.fc24.i686 kernel-4.8.4-200.fc24.i686 kernel-PAE-4.8.4-200.fc24.i686 It will still boot kernel-4.7.7-200.fc24.i686
The grub2 menu is displayed, and after selecting the 4.7.7-200 kernel there's a 2-3 sec delay with blinking cursor, then I'm prompted for the encryption passphrase for the /home filesystem. Then the voluminous messages (from removing the rhgb boot option) scroll forth and bootup proceeds normally.
However, If I choose any of the newer kernels, the blinking cursor remains forever; no prompt for the encryption passphrase occurs; the keyboard is totally non-responsive. Power cycling is required to recover.
Things I've tried:
- dnf remove <the "bad" kernel>, and reinstall it.
- Rebuild initramfs-4.8.4-200.fc24.i686.img with dracut. The new file is only one byte bigger, probably due to a different date, and
still won't boot.
- Added the secret 'dis_ucode_ldr' boot option, as revealed in
https://www.reddit.com/r/Fedora/comments/4qrl1k/kernel_46_wont_boot_how_can_... but this seemed aimed at newer IBM laptops, and indeed, had no effect on my T30.
- Updated the BIOS. The T30 has two components: the BIOS and the EC (Embedded Controller). My BIOS was up to date at version 2.10 but the EC was v. 1.03, while v. 1.07 was available. Sadly, updating to EC v. 1.07 did not alleviate the problem.
Any thoughts, shared experience, commiserations, suggestions?
What can be so different about these newer kernels?
Between 4.7.7 and 4.7.9, there were some bug fixes. The first two seem unrelated to your problem. I couldn't check the 1352140 ticket because the server had problems, but the I2C leads me to conclude that it probably isn't related either.
Changelog * Thu Oct 20 2016 Justin M. Forbes jforbes@fedoraproject.org - 4.7.9-200 - Linux v4.7.9 - CVE-2016-5195 (rhbz 1384344 1387080)
* Tue Oct 18 2016 Peter Robinson pbrobinson@fedoraproject.org - Build in AXP20X_I2C (should fix rhbz 1352140)
* Mon Oct 17 2016 Laura Abbott labbott@redhat.com - 4.7.8-200 - Linux v4.7.8
My suspicion would be that, since kernel developers use newer hardware to develop and test, they made changes to the kernel that affected you, but that their testing did not catch.
I suggest you open a bugzilla against the kernel, and basically put in the contents of this email message. Are there any kind of log messages? It's very early, so probably not.
You could try compiling a local kernel newer than 4.7.7, to see if compiling in your environment would fix the problem. I think that's a long shot though.
On 11/10/16 21:27, stan wrote:
On Thu, 10 Nov 2016 16:24:31 -0500 "David A. De Graaf" dad@datix.us wrote:
My trusty old IBM T30 laptop will no longer boot with the latest kernel-4.7.9-200.fc24.i686 kernel-4.8.4-200.fc24.i686 kernel-PAE-4.8.4-200.fc24.i686 It will still boot kernel-4.7.7-200.fc24.i686
I suggest you open a bugzilla against the kernel, and basically put in the contents of this email message. Are there any kind of log messages? It's very early, so probably not.
OK, see *Bug 1394353* https://bugzilla.redhat.com/show_bug.cgi?id=1394353 -New kernels won't boot on older IBM T30 laptop
Thanks, Stan.
On 11/10/2016 04:24 PM, David A. De Graaf wrote:
My trusty old IBM T30 laptop will no longer boot with the latest kernel-4.7.9-200.fc24.i686 kernel-4.8.4-200.fc24.i686 kernel-PAE-4.8.4-200.fc24.i686 It will still boot kernel-4.7.7-200.fc24.i686
I too am unable to boot the newer kernels from at least 4.8.4 but I have a different failure than what you are describing. I have a Lenovo T440p and an older desktop machine with an Intel core 2 duo processor, both fail in the same manner.
When the system comes up the system goes into a hibernation mode, if I bring it out of hibernation it'll continue the boot and then go into hibernation again, eventually after 4 or 5 hibernation cycles I can finally get the machine to complete the boot cycle and allow me to log in, at this point the system appears to work properly.
[ 41.661105] nouveau 0000:02:00.0: DRM: resuming kernel object tree... [ 41.704285] nouveau 0000:02:00.0: priv: HUB0: 085014 ffffffff (1870820b) [ 41.704757] nouveau 0000:02:00.0: priv: GPC0: 4188ac 00000001 (1b70822e) [ 41.727714] nouveau 0000:02:00.0: priv: HUB0: 10ecc0 ffffffff (1f70822c) [ 41.748279] nouveau 0000:02:00.0: DRM: resuming client object trees... [ 42.799310] PM: Syncing filesystems ... [ 47.093082] nouveau 0000:02:00.0: DRM: evicting buffers... [ 47.093084] nouveau 0000:02:00.0: DRM: waiting for kernel channels to go idle... [ 47.093110] nouveau 0000:02:00.0: DRM: suspending client object trees... [ 47.094368] nouveau 0000:02:00.0: DRM: suspending kernel object tree... [ 47.585291] ip6_tables: (C) 2000-2006 Netfilter Core Team . . . [ 52.205610] Netfilter messages via NETLINK v0.30. [ 52.220236] ip_set: protocol 6 [ 63.673308] done. [ 63.673312] PM: Preparing system for sleep (mem) [ 63.673734] Freezing user space processes ... (elapsed 0.063 seconds) done. [ 63.737356] Double checking all user space processes after OOM killer disable... (elapsed 0.000 seconds) [ 63.737374] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 63.738490] PM: Suspending system (mem) [ 63.738512] Suspending console(s) (use no_console_suspend to debug) [ 63.861830] sd 0:0:0:0: [sda] Synchronizing SCSI cache
. . . [ 79.503546] device virbr0-nic left promiscuous mode [ 79.503570] virbr0: port 1(virbr0-nic) entered disabled state [ 83.960786] nouveau 0000:02:00.0: DRM: evicting buffers... [ 83.960788] nouveau 0000:02:00.0: DRM: waiting for kernel channels to go idle... [ 83.960823] nouveau 0000:02:00.0: DRM: suspending client object trees... [ 83.962116] nouveau 0000:02:00.0: DRM: suspending kernel object tree... [ 102.929666] nouveau 0000:02:00.0: DRM: resuming kernel object tree... [ 102.972865] nouveau 0000:02:00.0: DRM: resuming client object trees... [ 103.081139] e1000e: enp0s25 NIC Link is Down [ 103.347125] PM: Syncing filesystems ... done. [ 104.362519] PM: Preparing system for sleep (mem) [ 104.362774] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 104.364228] Double checking all user space processes after OOM killer disable... (elapsed 0.000 seconds) [ 104.364286] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 104.365463] PM: Suspending system (mem)
Suggestions?
Jeff
On 11/20/2016 06:43 PM, Jeffrey Ross wrote:
On 11/10/2016 04:24 PM, David A. De Graaf wrote:
My trusty old IBM T30 laptop will no longer boot with the latest kernel-4.7.9-200.fc24.i686 kernel-4.8.4-200.fc24.i686 kernel-PAE-4.8.4-200.fc24.i686 It will still boot kernel-4.7.7-200.fc24.i686
I too am unable to boot the newer kernels from at least 4.8.4 but I have a different failure than what you are describing. I have a Lenovo T440p and an older desktop machine with an Intel core 2 duo processor, both fail in the same manner.
When the system comes up the system goes into a hibernation mode, if I bring it out of hibernation it'll continue the boot and then go into hibernation again, eventually after 4 or 5 hibernation cycles I can finally get the machine to complete the boot cycle and allow me to log in, at this point the system appears to work properly.
I have an HP laptop that wont boot with the 4.8 kernel. Boots fine on 4.7 kernels. Took me a bit to figure out it was a problem with the kernel. Mine just hangs when the kernel should load with a white dot in the upper left-hand corner of the screen.
On 11/20/2016 03:43 PM, Jeffrey Ross wrote:
On 11/10/2016 04:24 PM, David A. De Graaf wrote:
My trusty old IBM T30 laptop will no longer boot with the latest kernel-4.7.9-200.fc24.i686 kernel-4.8.4-200.fc24.i686 kernel-PAE-4.8.4-200.fc24.i686 It will still boot kernel-4.7.7-200.fc24.i686
I too am unable to boot the newer kernels from at least 4.8.4 but I have a different failure than what you are describing. I have a Lenovo T440p and an older desktop machine with an Intel core 2 duo processor, both fail in the same manner.
When the system comes up the system goes into a hibernation mode, if I bring it out of hibernation it'll continue the boot and then go into hibernation again, eventually after 4 or 5 hibernation cycles I can finally get the machine to complete the boot cycle and allow me to log in, at this point the system appears to work properly.
[ 41.661105] nouveau 0000:02:00.0: DRM: resuming kernel object tree... [ 41.704285] nouveau 0000:02:00.0: priv: HUB0: 085014 ffffffff (1870820b) [ 41.704757] nouveau 0000:02:00.0: priv: GPC0: 4188ac 00000001 (1b70822e) [ 41.727714] nouveau 0000:02:00.0: priv: HUB0: 10ecc0 ffffffff (1f70822c) [ 41.748279] nouveau 0000:02:00.0: DRM: resuming client object trees... [ 42.799310] PM: Syncing filesystems ... [ 47.093082] nouveau 0000:02:00.0: DRM: evicting buffers... [ 47.093084] nouveau 0000:02:00.0: DRM: waiting for kernel channels to go idle... [ 47.093110] nouveau 0000:02:00.0: DRM: suspending client object trees... [ 47.094368] nouveau 0000:02:00.0: DRM: suspending kernel object tree... [ 47.585291] ip6_tables: (C) 2000-2006 Netfilter Core Team . . . [ 52.205610] Netfilter messages via NETLINK v0.30. [ 52.220236] ip_set: protocol 6 [ 63.673308] done. [ 63.673312] PM: Preparing system for sleep (mem) [ 63.673734] Freezing user space processes ... (elapsed 0.063 seconds) done. [ 63.737356] Double checking all user space processes after OOM killer disable... (elapsed 0.000 seconds) [ 63.737374] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 63.738490] PM: Suspending system (mem) [ 63.738512] Suspending console(s) (use no_console_suspend to debug) [ 63.861830] sd 0:0:0:0: [sda] Synchronizing SCSI cache
. . . [ 79.503546] device virbr0-nic left promiscuous mode [ 79.503570] virbr0: port 1(virbr0-nic) entered disabled state [ 83.960786] nouveau 0000:02:00.0: DRM: evicting buffers... [ 83.960788] nouveau 0000:02:00.0: DRM: waiting for kernel channels to go idle... [ 83.960823] nouveau 0000:02:00.0: DRM: suspending client object trees... [ 83.962116] nouveau 0000:02:00.0: DRM: suspending kernel object tree... [ 102.929666] nouveau 0000:02:00.0: DRM: resuming kernel object tree... [ 102.972865] nouveau 0000:02:00.0: DRM: resuming client object trees... [ 103.081139] e1000e: enp0s25 NIC Link is Down [ 103.347125] PM: Syncing filesystems ... done. [ 104.362519] PM: Preparing system for sleep (mem) [ 104.362774] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 104.364228] Double checking all user space processes after OOM killer disable... (elapsed 0.000 seconds) [ 104.364286] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 104.365463] PM: Suspending system (mem)
Suggestions?
Obvious question, but have you bugzilla'd this? It sure looks like an issue with the ACPI system considering the power manager is what's shutting it down. You could try booting with "acpi=off" on the command line and see if that'll keep it alive. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - A squeegee, by any other name, wouldn't sound as funny. - ----------------------------------------------------------------------
On 11/21/16 12:16, Rick Stevens wrote:
On 11/20/2016 03:43 PM, Jeffrey Ross wrote:
On 11/10/2016 04:24 PM, David A. De Graaf wrote:
My trusty old IBM T30 laptop will no longer boot with the latest kernel-4.7.9-200.fc24.i686 kernel-4.8.4-200.fc24.i686 kernel-PAE-4.8.4-200.fc24.i686 It will still boot kernel-4.7.7-200.fc24.i686
I too am unable to boot the newer kernels from at least 4.8.4 but I have a different failure than what you are describing. I have a Lenovo T440p and an older desktop machine with an Intel core 2 duo processor, both fail in the same manner.
When the system comes up the system goes into a hibernation mode, if I bring it out of hibernation it'll continue the boot and then go into hibernation again, eventually after 4 or 5 hibernation cycles I can finally get the machine to complete the boot cycle and allow me to log in, at this point the system appears to work properly.
[ 41.661105] nouveau 0000:02:00.0: DRM: resuming kernel object tree... [ 41.704285] nouveau 0000:02:00.0: priv: HUB0: 085014 ffffffff (1870820b) [ 41.704757] nouveau 0000:02:00.0: priv: GPC0: 4188ac 00000001 (1b70822e) [ 41.727714] nouveau 0000:02:00.0: priv: HUB0: 10ecc0 ffffffff (1f70822c) [ 41.748279] nouveau 0000:02:00.0: DRM: resuming client object trees... [ 42.799310] PM: Syncing filesystems ... [ 47.093082] nouveau 0000:02:00.0: DRM: evicting buffers... [ 47.093084] nouveau 0000:02:00.0: DRM: waiting for kernel channels to go idle... [ 47.093110] nouveau 0000:02:00.0: DRM: suspending client object trees... [ 47.094368] nouveau 0000:02:00.0: DRM: suspending kernel object tree... [ 47.585291] ip6_tables: (C) 2000-2006 Netfilter Core Team . . . [ 52.205610] Netfilter messages via NETLINK v0.30. [ 52.220236] ip_set: protocol 6 [ 63.673308] done. [ 63.673312] PM: Preparing system for sleep (mem) [ 63.673734] Freezing user space processes ... (elapsed 0.063 seconds) done. [ 63.737356] Double checking all user space processes after OOM killer disable... (elapsed 0.000 seconds) [ 63.737374] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 63.738490] PM: Suspending system (mem) [ 63.738512] Suspending console(s) (use no_console_suspend to debug) [ 63.861830] sd 0:0:0:0: [sda] Synchronizing SCSI cache
. . . [ 79.503546] device virbr0-nic left promiscuous mode [ 79.503570] virbr0: port 1(virbr0-nic) entered disabled state [ 83.960786] nouveau 0000:02:00.0: DRM: evicting buffers... [ 83.960788] nouveau 0000:02:00.0: DRM: waiting for kernel channels to go idle... [ 83.960823] nouveau 0000:02:00.0: DRM: suspending client object trees... [ 83.962116] nouveau 0000:02:00.0: DRM: suspending kernel object tree... [ 102.929666] nouveau 0000:02:00.0: DRM: resuming kernel object tree... [ 102.972865] nouveau 0000:02:00.0: DRM: resuming client object trees... [ 103.081139] e1000e: enp0s25 NIC Link is Down [ 103.347125] PM: Syncing filesystems ... done. [ 104.362519] PM: Preparing system for sleep (mem) [ 104.362774] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 104.364228] Double checking all user space processes after OOM killer disable... (elapsed 0.000 seconds) [ 104.364286] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 104.365463] PM: Suspending system (mem)
Suggestions?
Obvious question, but have you bugzilla'd this? It sure looks like an issue with the ACPI system considering the power manager is what's shutting it down. You could try booting with "acpi=off" on the command line and see if that'll keep it alive.
- Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
-A squeegee, by any other name, wouldn't sound as funny. -
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
As I have noted in "*Bug 1394353* https://bugzilla.redhat.com/show_bug.cgi?id=1394353 -New kernels won't boot on older IBM T30 laptop", this bug has been squashed by the latest
kernel-4.8.6-201.fc24.i686+PAE kernel-4.8.6-201.fc24.i686
Both of these kernels boot correctly, hence I have not tried Rick Stevens' helpful suggestion.
On 11/20/2016 03:43 PM, Jeffrey Ross wrote:
Suggestions?
Obvious question, but have you bugzilla'd this? It sure looks like an issue with the ACPI system considering the power manager is what's shutting it down. You could try booting with "acpi=off" on the command line and see if that'll keep it alive.
Sorry haven't been able to test in a while, I just tried kernel.x86_64 4.8.14-200.fc24 last night both with and without "acpi=off" and with acpi in the default setting the system would go to sleep but I was able to wake the system up and log in normally. When I set acpi to off the system didn't go to sleep but when the graphics display started up I got a grey screen but never presented with a login prompt.
The other item I noticed is that when the system started it initial boot (file system encryption is enabled) the graphics screen that comes up asking for my password the screen is reduce to about 1/2 the normal size.
Laptop is a T440P the grub line I'm using is -
GRUB_CMDLINE_LINUX=" rd.lvm.lv=fedora_laptop/root rd.luks.uuid=luks-533e7156-775d-48f6-abbd-90f14f31303d rd.lvm.lv=fedora_laptop/swap rhgb quiet i915.enable_rc6=7 i915.enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 acpi=off"
I'm now suspect of the i915 driver but I don't know for sure.
Jeff
On Mon, Dec 19, 2016 at 2:31 PM, Jeffrey Ross jeff@bubble.org wrote:
On 11/20/2016 03:43 PM, Jeffrey Ross wrote:
Suggestions?
Obvious question, but have you bugzilla'd this? It sure looks like an issue with the ACPI system considering the power manager is what's shutting it down. You could try booting with "acpi=off" on the command line and see if that'll keep it alive.
Sorry haven't been able to test in a while, I just tried kernel.x86_64 4.8.14-200.fc24 last night both with and without "acpi=off" and with acpi in the default setting the system would go to sleep but I was able to wake the system up and log in normally. When I set acpi to off the system didn't go to sleep but when the graphics display started up I got a grey screen but never presented with a login prompt.
The other item I noticed is that when the system started it initial boot (file system encryption is enabled) the graphics screen that comes up asking for my password the screen is reduce to about 1/2 the normal size.
Laptop is a T440P the grub line I'm using is -
GRUB_CMDLINE_LINUX=" rd.lvm.lv=fedora_laptop/root rd.luks.uuid=luks-533e7156-775d-48f6-abbd-90f14f31303d rd.lvm.lv=fedora_laptop/swap rhgb quiet i915.enable_rc6=7 i915.enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 acpi=off"
I'm now suspect of the i915 driver but I don't know for sure.
I suggest dropping all the i915 options and go with kernel defaults while troubleshooting this. It might also be useful to add no_console_suspend ignore_loglevel when troubleshooting suspend problems.
-
Chris Murphy -
David A. De Graaf -
Derrik Walker v2.0 -
Jeffrey Ross -
Rick Stevens -
stan