Bug 513203 - system fails to go into s4
Summary: system fails to go into s4
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.4
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: John Feeney
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-22 14:16 UTC by Adam Stokes
Modified: 2018-10-27 14:57 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-30 07:21:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
suspend log (11.30 KB, text/x-log)
2009-07-22 14:16 UTC, Adam Stokes
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0178 0 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 5.5 kernel security and bug fix update 2010-03-29 12:18:21 UTC

Description Adam Stokes 2009-07-22 14:16:16 UTC
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

Comment 4 Denise Dumas 2009-07-23 13:05:21 UTC
Adam, this is IA64, correct?

Comment 6 David Aquilina 2009-07-23 14:52:00 UTC
(In reply to comment #4)
> Adam, this is IA64, correct?  

HP reported this on the xw9400 workstation - AMD x86_64.

Comment 12 Denise Dumas 2009-11-03 15:01:38 UTC
David, Adam, ping?  Comment 3 and 5 - any update?

Comment 16 Jiri Skala 2009-11-05 12:18:55 UTC
Tests point to kernel issue -> changed component

Comment 17 Matthew Garrett 2009-12-21 21:32:21 UTC
Does shutdown -h power the system down?

Comment 18 Peter Martuccelli 2009-12-22 15:08:56 UTC
The kernel team is investigating this issue.  We will target this for rc not Beta 1.

Comment 19 Matthew Garrett 2009-12-22 16:01:38 UTC
I'm seeing the -128 kernel fail to power off on S4. Could you please confirm the configuration of the working setup?

Comment 20 Matthew Garrett 2009-12-22 21:11:38 UTC
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.

Comment 21 David Aquilina 2009-12-22 22:07:13 UTC
(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

Comment 23 Matthew Garrett 2009-12-22 22:21:06 UTC
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.

Comment 25 Matthew Garrett 2010-01-06 18:06:49 UTC
Kernel is hanging at pci_set_power_state in the nv_shutdown code - I'm trying to work out why at the moment.

Comment 27 Jarod Wilson 2010-02-23 20:05:03 UTC
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.

Comment 35 errata-xmlrpc 2010-03-30 07:21:50 UTC
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


Note You need to log in before you can comment on or make changes to this bug.