Bug 233373 - Power off not complete (screen still on)
Summary: Power off not complete (screen still on)
Status: RESOLVED DUPLICATE of bug 221667
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: i686 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-10 21:11 UTC by Vlad Codrea
Modified: 2007-01-12 04:28 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Beginning dmesg (doesn't include anything after shutdown command) (12.37 KB, text/plain)
2007-01-10 21:16 UTC, Vlad Codrea
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vlad Codrea 2007-01-10 21:11:05 UTC
Shutting down the system from the desktop or using "shutdown -h now" stalls after the following lines are printed on the console:

Stopping udev
proc unmounted
The system will be halted immediately

I can hear the fan turning off, but the screen remains on. I have to press the power button to completely turn off the computer. Every distribution I've tried that uses 2.6.* kernels fails to turn off the screen. On the other hand, all 2.4.* kernels I've tried are able to completely turn off the computer.

I am attaching the dmesg below. I'd be happy to provide any other information,
try out patches, or give developers SSH access to the affected computer. Thank
you.
Comment 1 Vlad Codrea 2007-01-10 21:16:30 UTC
Created attachment 112328 [details]
Beginning dmesg (doesn't include anything after shutdown command)

Attached is the beginning portion of the dmesg which doesn't include any messages after running "shutdown -h now". How would I be able to record dmesg messages that happen right before shutdown? Are dmesg messages from previous sessions archived somewhere in OpenSUSE 10.2? (ie. /var/log/ ?)
Comment 2 Greg Kroah-Hartman 2007-01-12 04:28:03 UTC

*** This bug has been marked as a duplicate of bug 221667 ***