Bug 105032 - gdth causes OOPS on /proc read and on shutdown
Summary: gdth causes OOPS on /proc read and on shutdown
Status: CLOSED DUPLICATE of bug 104520
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Doug Ledford
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-09-24 20:08 UTC by Keldon Jones
Modified: 2007-11-30 22:06 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-02-21 18:58:43 UTC


Attachments (Terms of Use)
OOPS from gdth driver (1.72 KB, text/plain)
2003-09-24 20:10 UTC, Keldon Jones
no flags Details

Description Keldon Jones 2003-09-24 20:08:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030908
Debian/1.4-4

Description of problem:
On a system with an Intel RAID Controller SRCZCR installed, the "gdth" driver
that controls the card issues an OOPS on a /proc read.  It will also OOPS on
system shutdown.  The OOPS message is attached.

Version-Release number of selected component (if applicable):
kernel-2.4.21-1.1931.2.399.ent

How reproducible:
Always

Steps to Reproduce:
1. Install Intel RAID card.
2. Boot system.
3. Shutdown.
    

Additional info:

Comment 1 Keldon Jones 2003-09-24 20:10:20 UTC
Created attachment 94692 [details]
OOPS from gdth driver

Comment 2 Arjan van de Ven 2003-09-24 20:12:42 UTC
we know this; it's supposed to be better in later kernels (available via RHN)

Comment 3 Matt Wilson 2003-09-25 23:13:59 UTC
to be clear, please re-test with 3.EL kernel


Comment 4 Jason Sauve 2003-10-31 02:27:48 UTC
There is a bugfix available, see Buzilla Bug #104520. It was never fixed in 
later taroon beta kernels and it seems the bug got carried into the gold 
release.

Comment 5 Ernie Petrides 2004-04-08 20:30:18 UTC

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

Comment 6 Red Hat Bugzilla 2006-02-21 18:58:43 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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