Bug 55313 - kernel oops with kernel 2.4.9-6
kernel oops with kernel 2.4.9-6
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-10-29 11:34 EST by hjl
Modified: 2007-04-18 12:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-07 15:59:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
kernel oops trace (2.77 KB, text/plain)
2001-10-29 11:35 EST, hjl
no flags Details
lsmod (503 bytes, text/plain)
2001-10-29 11:51 EST, hjl
no flags Details

  None (edit)
Description hjl 2001-10-29 11:34:35 EST
I got an kernel oops over night.
Comment 1 hjl 2001-10-29 11:35:16 EST
Created attachment 35421 [details]
kernel oops trace
Comment 2 Arjan van de Ven 2001-10-29 11:38:11 EST
Seems a device bug; can you attach the output of lsmod so I can narrow the list
of suspects ?
Comment 3 hjl 2001-10-29 11:51:34 EST
Created attachment 35445 [details]
lsmod
Comment 4 Arjan van de Ven 2001-10-30 03:50:04 EST
I think we found the cause; seems there's a nice race in the bdput function
versus opening of a new device.

Side question: is there a specific reason you're using e100 instead of eepro100
?
Comment 5 hjl 2001-10-30 11:17:44 EST
eepro100 doesn't work on my Intel STL2 MB.

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