Created attachment 354695 [details] suspend log Description of problem: pm-suspend does not properly put system in suspend-to-disk. system will halt but not fully power down. rebooting does bring the system back to previous state. Version-Release number of selected component (if applicable): pm-utils-0.99.3-10.el5 How reproducible: 100% Steps to Reproduce: 1. boot system into runlevel 3 2. pm-suspend 3. Actual results: system halts, but does not power down. Expected results: system powers down Additional info: this happens in both runlevel 3/5
Adam, this is IA64, correct?
(In reply to comment #4) > Adam, this is IA64, correct? HP reported this on the xw9400 workstation - AMD x86_64.
David, Adam, ping? Comment 3 and 5 - any update?
Tests point to kernel issue -> changed component
Does shutdown -h power the system down?
The kernel team is investigating this issue. We will target this for rc not Beta 1.
I'm seeing the -128 kernel fail to power off on S4. Could you please confirm the configuration of the working setup?
This appears to be caused by 21a5fdb51145795d7cc0e5be38a148321d19e3f4 . If I make the shutdown return immediately, I get identical behaviour between the 5.3 and 5.4 kernels.
(In reply to comment #19) > I'm seeing the -128 kernel fail to power off on S4. Could you please confirm > the configuration of the working setup? -182 was able to power off the system with 'shutdown -h' When manually invoking pm-hibernate, here's the output I get. This is on hp-xw9400-02.rhts.bos.redhat.com : [root@hp-xw9400-02 ~]# pm-hibernate Disabling non-boot CPUs ... CPU 1 is now offline CPU1 is down CPU 2 is now offline CPU2 is down CPU 3 is now offline CPU3 is down Breaking affinity for irq 4 Breaking affinity for irq 50 CPU 4 is now offline CPU4 is down CPU 5 is now offline CPU5 is down Breaking affinity for irq 225 CPU 6 is now offline CPU6 is down CPU 7 is now offline CPU7 is down Breaking affinity for irq 14 CPU 8 is now offline CPU8 is down CPU 9 is now offline CPU9 is down Breaking affinity for irq 90 CPU 10 is now offline CPU10 is down CPU 11 is now offline CPU11 is down Stopping tasks: =========================================================================================== stopping tasks timed out after 120 seconds (1 tasks remaining): khungtaskd Restarting tasks...<6> Strange, khungtaskd not stopped done Enabling non-boot CPUs ... Initializing CPU#1 Six-Core AMD Opteron(tm) Processor 2427 stepping 00 CPU1 is up Initializing CPU#2 Six-Core AMD Opteron(tm) Processor 2427 stepping 00 CPU2 is up Initializing CPU#3 Six-Core AMD Opteron(tm) Processor 2427 stepping 00 CPU3 is up Initializing CPU#4 Six-Core AMD Opteron(tm) Processor 2427 stepping 00 CPU4 is up Initializing CPU#5 Six-Core AMD Opteron(tm) Processor 2427 stepping 00 CPU5 is up Initializing CPU#6 Six-Core AMD Opteron(tm) Processor 2427 stepping 00 CPU6 is up Initializing CPU#7 Six-Core AMD Opteron(tm) Processor 2427 stepping 00 CPU7 is up Initializing CPU#8 Six-Core AMD Opteron(tm) Processor 2427 stepping 00 CPU8 is up Initializing CPU#9 Six-Core AMD Opteron(tm) Processor 2427 stepping 00 CPU9 is up Initializing CPU#10 Six-Core AMD Opteron(tm) Processor 2427 stepping 00 CPU10 is up Initializing CPU#11 Six-Core AMD Opteron(tm) Processor 2427 stepping 00 CPU11 is up
The kungtaskd error is an additional bug that masks the one that's in 5.4. The forcedeth update seems to be responsible for the 5.4 failure, and I've identified the patch that's responsible for the khungtaskd error.
Kernel is hanging at pci_set_power_state in the nv_shutdown code - I'm trying to work out why at the moment.
in kernel-2.6.18-190.el5 You can download this test kernel from http://people.redhat.com/jwilson/el5 Please update the appropriate value in the Verified field (cf_verified) to indicate this fix has been successfully verified. Include a comment with verification details.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0178.html