Bug 172859 - rmmod aic79xx panics kernel
rmmod aic79xx panics kernel
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.0
All Linux
medium Severity high
: ---
: ---
Assigned To: Tom Coughlan
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-11-10 12:12 EST by Didier
Modified: 2012-06-20 09:30 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 09:30:14 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)
SCSI output (2.60 MB, image/jpeg)
2005-11-10 12:13 EST, Didier
no flags Details
First kernel trace (2.81 MB, image/jpeg)
2005-11-10 12:14 EST, Didier
no flags Details
Second kernel trace (2.90 MB, image/jpeg)
2005-11-10 12:15 EST, Didier
no flags Details

  None (edit)
Description Didier 2005-11-10 12:12:40 EST
Description of problem:
With an attached SCSI device, rmmod'ing the aic79xx module causes kernel panic.


Version-Release number of selected component (if applicable):
kernel-2.6.9-22.0.1.EL

How reproducible:
Always

Steps to Reproduce:
1. attach SCSI device
2. boot
3. 'rmmod aic79xx'
  
Actual results:
Kernel panic (see attached screenshots)

Expected results:
module should be removed.

Additional info:
* See bug #171957 (tested with FC4, appearantly fixed in kernel-2.6.14-1.1636_FC4).

* Reason for rmmod'ing : Attached to SCSI card is a JetStor RAID array. When the
array is expanded, an rmmod is needed to let the kernel recognize the enlarged
disk geometry (the alternative is a reboot, which is not always an option in a
production environment).

* SCSI card is an Adaptec 29320ALP :
'# cat /proc/scsi/aic79xx/0' :

Adaptec AIC79xx driver version: 1.3.11
Adaptec 29320ALP Ultra320 SCSI adapter
aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs
Allocated SCBs: 4, SG List Length: 128

Serial EEPROM:
0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8
0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8
0x09f4 0x0142 0x2807 0x0010 0xffff 0xffff 0xffff 0xffff
0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0430 0xb3f3

Target 0 Negotiation Settings
        User: 320.000MB/s transfers (160.000MHz DT|IU|RTI|QAS, 16bit)
        Goal: 160.000MB/s transfers (80.000MHz DT, 16bit)
        Curr: 160.000MB/s transfers (80.000MHz DT, 16bit)
        Transmission Errors 0
...

* The kernel panic first displays some SCSI output (module is loaded with
parameter aic79xx=verbose) ; after pressing the hosts' power on/off button, I
suppose an ACPI signal is sent, end I get a kernel trace, followed by a second
trace after approx. one second (see attached screenshots ; output is not logged
to /var/log/messages).
Comment 1 Didier 2005-11-10 12:13:53 EST
Created attachment 120888 [details]
SCSI output
Comment 2 Didier 2005-11-10 12:14:50 EST
Created attachment 120889 [details]
First kernel trace
Comment 3 Didier 2005-11-10 12:15:54 EST
Created attachment 120890 [details]
Second kernel trace
Comment 4 Jiri Pallich 2012-06-20 09:30:14 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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