Bug 151358

Summary: Linux hangs when shutdown or reboot
Product: Red Hat Enterprise Linux 3 Reporter: Michael Schuster <michael.schuster>
Component: kernelAssignee: Doug Ledford <dledford>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: coughlan, jbaron, petrides, riel
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
URL: GDT: Flushing all host drives
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 19:06:10 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:

Description Michael Schuster 2005-03-17 09:59:31 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

Description of problem:
After reboot or shutdown the linux hangs with the message:

...
...
Please stand by while rebooting the system...
md: stopping all md devices.
flushing ide devices: hdc
GDT: Fllushing all host drives .. Starting timer : 0 0

--------------------------------------------------------------
RAID Controller:

GDT: Storage RAID Controller Driver. Version: 2.05

Version-Release number of selected component (if applicable):
2.4.21-27.0.2.ELsmp

How reproducible:
Always

Steps to Reproduce:
1.reboot
2.or shutdown
3.
  

Additional info:

Comment 1 RHEL Program Management 2007-10-19 19:06:10 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.