Bug 720913

Summary: RHEL6 host reboot failed on Dell OPTIPLEX 990 machine
Product: Red Hat Enterprise Linux 6 Reporter: Mike Cao <bcao>
Component: kernelAssignee: John Feeney <jfeeney>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: high    
Version: 6.2CC: arozansk, bcao, jfeeney, juzhang, michen
Target Milestone: rcKeywords: Reopened
Target Release: 6.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-03 13:48:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mike Cao 2011-07-13 08:33:27 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
uname -r
2.6.32-168.el6

How reproducible:
100%

Steps to Reproduce:
1.install RHEL6 on DELL OPTIPLEX  990 machine
2.reboot

  
Actual results:
host reboot failed .It will stuck at 
"Please stand by while rebooting the system...                                  
Restarting system.   "

Expected results:
host reboot successfully

Additional info:
Comment 2 Matthew Garrett 2011-07-15 17:32:07 UTC 
Is this a regression? Do we have any of these machines in Westford?
Comment 3 Prarit Bhargava 2011-08-08 17:30:40 UTC 
AFAICT this isn't a certified system:

https://hardware.redhat.com/list.cgi?product=Red%20Hat%20Hardware%20Certification&quicksearch=dell&showall=1

P.
Comment 4 Mike Cao 2011-08-18 03:21:24 UTC 
(In reply to comment #3)
> AFAICT this isn't a certified system:
> 
> https://hardware.redhat.com/list.cgi?product=Red%20Hat%20Hardware%20Certification&quicksearch=dell&showall=1
> 
> P.

Reopen this Bug .

the machine was coming to market in March ,2011 ,while the time for RHEL6 coming to market is much more earlier than that .I still prefer to fix it due to it is a testbloker about RHEVM configuration (machine need reboot).
Comment 5 Matthew Garrett 2011-10-03 13:48:36 UTC 

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