Red Hat Bugzilla – Bug 485016
HP6510b close lid cause system crash
Last modified: 2013-01-10 02:11:42 EST
Description of problem: When I close lid of my HP6510b system crashes
no ssh reaction after system hangup
Version-Release number of selected component (if applicable):
Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
Core 2 Duo x86_64
Steps to Reproduce:
1.start system and close lid no matter if X is running
when I change flag in /proc/acpi/video/C098/DOS from 0 to 1 it starts to behave normally but I cannot return from suspend
when the flag is set to 0 I can suspend/resume normally
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
I changed /proc/acpi/video/*/DOS from 0 to 1 and now everything (suspend/resume, lid close) works fine..
maybe bad component?
This is fundamentally a BIOS bug, but it may be possible to work around it. I'll backport a patch and we can see if it helps.
Created attachment 362946 [details]
Run ACPI workqueues on CPU 0
This patch should deal with the issue.
I'm doing a brew build at https://brewweb.devel.redhat.com/taskinfo?taskID=2014046 .
Vladimir, can you test the kernel in the above brew build?
You can download this test kernel from http://people.redhat.com/dzickus/el5
Please do NOT transition this bugzilla state to VERIFIED until our QE team
has sent specific instructions indicating when to do so. However feel free
to provide a comment indicating that this fix has been verified.
the behavior is better but hang up still occasionally occurs :( testing 189 kernel
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.