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@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - A squeegee, by any other name, wouldn't sound as funny. - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
