Bug 58140 - (SCSI GDTH)gdth driver causes kernel panic after halt and ctrl-alt-del
Summary: (SCSI GDTH)gdth driver causes kernel panic after halt and ctrl-alt-del
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-01-09 21:02 UTC by Chetan Bhargava
Modified: 2008-08-01 16:22 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-09-30 15:39:20 UTC
Embargoed:


Attachments (Terms of Use)

Description Chetan Bhargava 2002-01-09 21:02:41 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461)

Description of problem:
Kernel panic occurs when the system is halted and after that ctrl-alt-del is 
pressed. The error is <0>Kernel panic: scsi_unjam_host: Miscount of number of 
failed commands.



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.halt
2.after the system is halted
3.press ctrl-alt-delete
	

Actual Results:  md: stopping all md devices
GDT: flushing all host drives ..  <0>Kernel panic: scsi_unjam_host: Miscount of 
number of failed commands.

Expected Results:  the machine should have rebooted

Additional info:

hardware: Intel server board scb2, 2GB SDRAM, Intel SR2200 Chasis
RAID adapter: ICP-Vortex (Intel) GDT8523RZ with BIOS Rev 6.05B dated Nov 7, 2001
Drives: 2 host drives (mirrored). OS is on the mirrored disks

Have tried kernel 2.4.9-13 but it gives same result.

Comment 1 Chetan Bhargava 2002-01-10 00:54:22 UTC
SCB2 BIOS details:
SCB20.86B.0011.P01.0109121047
SCB2 Production BIOS Version 1.00
BIOS Build 0011

Comment 2 Bugzilla owner 2004-09-30 15:39:20 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/



Note You need to log in before you can comment on or make changes to this bug.