Bug 26562 - [aic7xxx] kernel crashes when loading aic7xxx module
Summary: [aic7xxx] kernel crashes when loading aic7xxx module
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Doug Ledford
QA Contact: Brock Organ
URL:
Whiteboard: Florence RC-1
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-07 22:45 UTC by Steve Dum
Modified: 2007-04-18 16:31 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-02-09 11:16:40 UTC
Embargoed:


Attachments (Terms of Use)

Description Steve Dum 2001-02-07 22:45:59 UTC
On a Kayak xu with 2 333 Mhz processors, AIC-7880, and Adaptec Array 1000CA
right after loading the aic7xxx module the kernel gets a oops 0000.  Lat
message is
Kernel panic ahc_pci:0:8:0 missing case in ahc_handle_scsiint
status 8

Redhat 7.0 loads just fine on same machine.

Comment 1 Sammy 2001-02-08 02:11:56 UTC
I have the same problem with aic7xxx....kernel PANIC etc.etc. Whatever that
new driver is does not work for me. Going back to the old driver works.

An additional note: I also built and used 2.4.0 with Alan Cox patches and
today built 2.4.1 with patch ac3 --- ac3 also patches/updates aic7xxx and
I had the same kernel PANIC....I took out all the aic7xxx patches from ac3
and the version that comes with 2.4.1 works just fine.

Comment 2 Glen Foster 2001-02-08 23:33:22 UTC
We (Red Hat) should really try to resolve this before next release.

Comment 3 Doug Ledford 2001-02-09 11:16:36 UTC
The aic7xxx driver has been reverted to a previous version so the 6.0.8BETA
driver that caused the initial oops won't be a problem.

The aic7xxx updated in 2.4.1-ac3 didn't work properly, but all reports are that
the on in 2.4.1-ac6 and later does indeed work for more people than before. 
That's the driver currently slated for release in Florence, and it doesn't yet
have any known bugs against it.  Our kernel build 2.4.1-0.1 or later will have
it in there.

Comment 4 Steve Dum 2001-02-26 17:18:40 UTC
This failure has been resolved in the wolverine release


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