Bug 69809 - qla2100 Kernel panic: scsi_free:Bad offset
Summary: qla2100 Kernel panic: scsi_free:Bad offset
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
(Show other bugs)
Version: 7.3
Hardware: i686 Linux
medium
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-25 16:35 UTC by Need Real Name
Modified: 2007-04-18 16:44 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-07 18:54:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Need Real Name 2002-07-25 16:35:20 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)

Description of problem:
When using a qla2100 card on redhat 7.3 the following error randomly appears 
and locks the server :

white kernel: qla2x00: Status Entry invalid handle<6>qla2x00: Performing ISP 
error recovery - ha= c14f8084.
kernel: qla2x00: 64 Bit PCI Addressing Enabled
kernel: Kernel panic: scsi_free:Bad offset

Currently using 2.4.18-4 recompiled to have lun probing enabled.
The panic has occured at varios times during the day.

Qlogic has a specific driver for the 2100 but only for rh 6.2  I am relying on 
the kernel driver for support in 7.3.


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


How reproducible:
Always

Steps to Reproduce:
1.install qla2100
2.recompile 2.4.18-4 with lun probing enabled
3. mount san drive, system under normal production.
4. kernel panic after varios times under load
	

Additional info:
Comment 1 Arjan van de Ven 2003-06-07 18:54:13 UTC 
current errata kernels have a much newer qlogic driver with a lot of bugs fixed
Note You need to log in before you can comment on or make changes to this bug.