Bug 495355

Summary: machine fails to shutdown
Product: [Fedora] Fedora Reporter: Russell Strong <russell>
Component: distributionAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: low    
Version: rawhideCC: dcantrell, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-14 16:20:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
failed shutdown sequence 1
none
failed shutdown sequence 2
none
failed shutdown sequence 3 none

Description Russell Strong 2009-04-12 10:14:04 UTC
Created attachment 339223 [details]
failed shutdown sequence 1

Description of problem:

Pressed the power button.  When the "shutdown this system now" dialog appeared I selected Shutdown.  The machine started to shutdown, the screen went black, I shut the lid and put the laptop in a bag.  A few hours later when I got it out of the bag, I found that it was EXTREMELY HOT. I opened it up and found that it had gotten stuck during the shutdown, see 1.jpg.  I then hit ctrl+alt+del which then caused the shutdown to continue one more step, but then get stuck again, see 2.jpg.  Again I hit ctrl+alt+del and the shutdown continued, see 3.jpg, and ultimately powered off.

I consider this to be a very serious issue.  It has potential to damage hardware.

Would it be possible to have a kernel based watchdog timer shut the power off if things go wrong?

Comment 1 Russell Strong 2009-04-12 10:14:54 UTC
Created attachment 339224 [details]
failed shutdown sequence 2

Comment 2 Russell Strong 2009-04-12 10:16:03 UTC
Created attachment 339225 [details]
failed shutdown sequence 3

Comment 3 Bill Nottingham 2009-04-14 16:20:42 UTC
I believe this is a duplicate of an already reported bug.

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