Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 80315

Summary: (SCSI QLOGIC_ISP) insmod qlogicisp = immediate kernel dump on all > 2.4.18-14 (intel & athlon)
Product: [Retired] Red Hat Linux Reporter: Jez Tucker <jez>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: high    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-09-30 15:40:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Jez Tucker 2002-12-24 11:22:30 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
Any kernel released by RedHat more recent than the 'default' supplied 2.4.18-14
revision causes an immediate kernel dump as part of the boot process when the
required qlogicisp module is loaded via insmod.

This results in an unusable machine.  

Currently, the user has to remain with the outdated & **insecure** 2.4.18-14 kernel.

Currently affects (to my knowledge): 2.4.18-17.x, 2.4.18-18.x, 2.4.18-19.x

This problem has been reproduced on two separate machines, with two different
(though the identical model) SCSI cards.  One machine is Athlon based and one
machine is Intel based.

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

How reproducible:

Steps to Reproduce:
1. Install RedHat supplied kernel more recent than 2.4.18-14
2. Reboot machine.
3. Boot with newly installed kernel. 

Actual Results:  1. Boot process attempts insmod qlogicisp
2. Machine crashes and dumps kernel.  keyboard caps & scroll lights flash.

Expected Results:  1. Kernel insmod qlogicisp module succeeds.
2. Machine continues booting.

Additional info:

Incidentally the qlogicisp module was not detected during the installation
process and had to be manually selected. At that point installation was 100% ok
and no parameters were required in addition.

Qlogic ISP 1020 module appears to support Qlogic ISP 1040 based cards 100% under
kernel 2.4.18-14.

A strange insmod message occurs on all kernel revisions:

(the following is from 2.4.18-14 dmesg)

SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
PCI: Found IRQ 11 for device 00:08.0
qlogicisp : new 1020 revision ID (5)
scsi0: Qlogic ISP1020 SCSI on PCI bus 00 device 40 irq 11 MEM base 0xf0856000

Again, this problem occurs on multiple architectures (though I believe you
compile your Athlon kernel with ARCH=i686) and with two different instances of
the same card.

Any user experiencing this problem CANNOT upgrade kernels. This creates knock on
effects.  I.E. I cannot upgrade to a later NVIDIA driver as I require a newer
kernel (etc.).

I suggest that the qlogicisp code from 2.4.18-14 is ported to the newer kernels.

Please contact if more information is required.  I could possibly capture kernel
dump via console.

Comment 1 Jez Tucker 2002-12-24 11:24:54 UTC
The card I'm using is a Qlogic 1040 SE SCSI PCI host adapter.

Info at:

Comment 2 David Hekimian 2003-06-05 02:46:27 UTC
I also have the same issue.

I have the qlogic 1040 card. This is on an Intel PII.

I had to select the driver (qlogicisp) at install time as it was not detected.

RH 9 w/ Kernel-2.4.20-8 works OK.

RH 9 w/ Kernel-2.4.20-13.9 kernel panics on boot.
RH 9 w/ Kernel-2.4.20-18.9 kernel panics on boot.

Is there a workaround or proposed fix?

Comment 3 Bugzilla owner 2004-09-30 15:40:19 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 ( maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: