Bug 97956 - (SCSI 3WXXXX) Kernel 2.4.20-18.7smp panic in 3w-xxxx module
Summary: (SCSI 3WXXXX) Kernel 2.4.20-18.7smp panic in 3w-xxxx module
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
(Show other bugs)
Version: 7.2
Hardware: i686 Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL: http://www.slac.stanford.edu/~bhimji/...
Depends On:
TreeView+ depends on / blocked
Reported: 2003-06-24 16:04 UTC by Wahid Bhimji
Modified: 2007-04-18 16:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-30 15:41:11 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Console Output (9.38 KB, text/plain)
2003-06-24 16:06 UTC, Wahid Bhimji
no flags Details

Description Wahid Bhimji 2003-06-24 16:04:58 UTC
From Bugzilla Helper:
User-Agent: Opera/6.11 (Linux 2.4.20acpi i686; U)  [en]

Description of problem:
Upgraded to 2.4.20-18 kernel. On boot there is a kernel panic which 
from the output appears to be related to the 3w-xxxx module.

A similar kernel panic is also seen when the previous Red Hat 2.4.20 
kernel was tried. System works with 2.4.18-18.7 kernel.

We are using a 3Ware Esplanade 6400.

Console output enclosed.

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

How reproducible:

Steps to Reproduce:
1.Select 2.4.20-18.7 kernel at boot time

Actual Results:  kernel Oops

Expected Results:  normal boot up 

Additional info:

Comment 1 Wahid Bhimji 2003-06-24 16:06:15 UTC
Created attachment 92589 [details]
Console Output

Comment 2 Bugzilla owner 2004-09-30 15:41:11 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

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.