Red Hat Bugzilla – Bug 30676
[aic7xxx] Kernel panics when booting 'new' aix7xxx module on SMP system
Last modified: 2007-04-18 12:31:58 EDT
From Bugzilla Helper: User-Agent: Mozilla/4.76 [en] (Win98; U) Installed Fisher on dual-processor system (MMX-200 in venerable old Intergraph TD-40); upon reboot, system panics reliably when loading SCSI module - aic7xxxx (TD-40 contains an AIC-7850 on motherboard for SCSI support). Booting the UP kernel succeeds; I'm then able to build an SMP kernel with the 'old' aic7xxx driver. Booting SMP with the old aic7xxx works fine, as far as I can tell. Reproducible: Always Steps to Reproduce: 1. Install Fisher on TD-40 with dual CPU 2. Boot Linux in SMP mode 3. Watch it explode. It blowed up. Actual Results: Systems reliably panics when loading aic7xxx module during boot Expected Results: System should display SCSI probe information and successfully boot up and run.
After a normal install, I can not reproduce this problem with Wolverine; I suspect Wolverine is using the 'old' aic7xxx driver.
Yes Wolverine uses the old module.
I'm closing this bug since it can't be reproduced with the old aic7xxx module and I suspect it won't happen with the latest new aic7xxx module (version 6.1.4 or later) either.
I might not be too familiar with the bugzilla process, but in my kernel development days, we closed bugs as 'resolved' when the reported problem was verified as actually fixed, not when we suspected it would be fixed. In any case, you might want to update the release notes for Fisher (which is still advertised as the 'latest beta' on the RedHat homepage) to include a mention that it will certainly blow up after installation on an SMP box with an Adaptec 7xxx-family adapter, and document the workaround (boot UP). I will look forward to trying the 'new' driver on Wolverine when it is available (perhaps it is already?) and comment this bug with confirmation of resolution. ;-)
Dana, a known bug with this description was fixed between Fisher and Wolverine. Doug said "suspect" in case of the remote possibility that there is a different bug with a similar description.