Bug 672564 - kacpi_notify is in D-state from boot
Summary: kacpi_notify is in D-state from boot
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 14
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: John Feeney
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-25 15:45 UTC by Kevin Stovall
Modified: 2013-01-10 07:34 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-11 19:52:03 UTC
Type: ---


Attachments (Terms of Use)
The output from alt+sysrq+t. (186.34 KB, text/plain)
2011-01-26 15:56 UTC, Kevin Stovall
no flags Details

Description Kevin Stovall 2011-01-25 15:45:56 UTC
Description of problem:
After booting up system, kacpi_notify is in D-state and stays in that state

$ top -b -n 1 | awk '{if (NR <=7) print; else if ($8 == "D") {print; count++} } END {print "Total status D: "count}'
top - 09:31:00 up 1 min,  2 users,  load average: 2.63, 1.27, 0.48
Tasks: 206 total,   1 running, 205 sleeping,   0 stopped,   0 zombie
Cpu(s): 11.0%us, 14.3%sy,  0.0%ni, 48.5%id, 25.9%wa,  0.0%hi,  0.3%si,  0.0%st
Mem:   3797480k total,   604448k used,  3193032k free,    47000k buffers
Swap:  5898236k total,        0k used,  5898236k free,   220480k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            
   23 root      20   0     0    0    0 D  0.0  0.0   0:00.00 kacpi_notify

Also, unsure if it is related, system randomly hangs during the udev stage on boot. It happens about 1 out of every 5 boots.

Version-Release number of selected component (if applicable):

$ uname -r
2.6.35.10-74.fc14.x86_64

How reproducible:

Every successful boot, kacpi_notify is in this state. The system hanging is somewhat reproducible, but requires a few boots.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

System is HP Pavilion dv4-1275mx

$ cat /proc/cpuinfo 
processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 17
model		: 3
model name	: AMD Turion(tm) X2 Ultra Dual-Core Mobile ZM-80
stepping	: 1
cpu MHz		: 525.000
cache size	: 1024 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch osvw skinit lbrv svm_lock nrip_save
bogomips	: 4200.54
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

processor	: 1
vendor_id	: AuthenticAMD
cpu family	: 17
model		: 3
model name	: AMD Turion(tm) X2 Ultra Dual-Core Mobile ZM-80
stepping	: 1
cpu MHz		: 2100.000
cache size	: 1024 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch osvw skinit lbrv svm_lock nrip_save
bogomips	: 4189.86
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

Comment 1 Chuck Ebbert 2011-01-26 05:57:16 UTC
Can you do this:

  1. Add 'sysrq_always_enabled ignore_loglevel' to the kernel boot options.
  2. Press alt-sysrq-t and capture the output (it should go to the syslog.)
  3. Attach the output to this bug report.

Comment 2 Kevin Stovall 2011-01-26 15:56:27 UTC
Created attachment 475424 [details]
The output from alt+sysrq+t.

Comment 3 Kevin Stovall 2011-02-08 17:46:28 UTC
More information on the system hanging problem. Here is an error message I get if I wait long enough (maybe 5 minutes?) before powering the computer off and on again.

Starting udev: udevd[522]L worker [595] unexpectedly returned with status 0x0100

udevd[522]: worker [595] failed while handling '/devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.3'

udevd[522]: worker [629] unexpectedly returned with status 0x0100

udevd[522]: worker [629] failed while handling '/devices/virtual/wmi/95F24279-4D7B-4334-9387-ACCDC67EF61C'
                                                                                  [   OK   ]
Setting hostname localhost:                                 [   OK   ]

Then it doesn't do anything else.

Comment 4 Chuck Ebbert 2011-02-09 14:00:13 UTC
Does blacklisting the hp-wmi module make any difference?

Comment 5 Kevin Stovall 2011-02-22 03:38:34 UTC
(In reply to comment #4)
> Does blacklisting the hp-wmi module make any difference?

That seems to have taken care of both issues.

Comment 6 Matthew Garrett 2011-02-24 18:43:14 UTC
syslog has helpfully dropped some of the output from alt+sysrq+t. Never mind. Can you install the pmtools package, run acpidump as root and attach the output?


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