Red Hat Bugzilla – Bug 55476
Kernel 2.4.9-7 crashes Dell PE2500 with aacraid on startup
Last modified: 2007-04-18 12:37:55 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.6 [en] (Win95; U)
Description of problem:
Both smp and up versions of newly distributed 2.4.9-7 crash on startup...
aacraid:0 ABORT/ interrupt_status = 0 ( <--- ten times)
itnerrrupt_status = 0
Code: 0f 0b 59 5b 89 7c 24 04 b8 03 00 00 00
<0> Kernel panic: Aiee, killing interrupt handler.
In interrupt handler - not syncing
Reboot from linux.bak or linux-smp.bak works fine (kernel 2.4.7-10 smp or up of 7.2 release)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. see above
Red Hat Folks,
This is a duplicate of 54021, which you claimed was fixed and which you
apparently closed without testing or waiting for user feedback. I commented on
10/11/2001 that this still did not work and should be reopened but apparently,
fixing this bug so that PERC RAID users can upgrade to a kernel that doesn't
have the recent kernel vulnerabilities is not a priority with Red Hat.
I know that getting an updated kernel out is a priority and that holding up the
release for a show stopping bug that affects only Dell PowerEdge servers with
PERC RAID controllers isn't a good thing but you have known about this bug for
over a month, you closed the bug without verifying that it was fixed, and I'm
stuck with a vulnerable kernel, which all leave me a little frustrated with your
All our aacraid machines work with the new kernel. That makes me think something
else is wrong here; are you booting the SMP kernel ?
I've experienced the same problem when attempting to run the 2.4.9-7enterprise
kernel and had to revert to the stock 7.2 kernel.
for a far better description and solution than I could ever come up with.
I am booting the SMP kernel - there are no uniprocessor kernels on this machine.
I installed 2.4.7-10smp and run fine on a dell 2500.. Upgraded to kernel 2.4.9-
13smp and it wouldn't boot in that kernel. Produced error (AAC:
NMI_DMA_0_ERROR) on bootup.
I wonder if this has anything to do with the Interrupt Requests problem.
and see what the aacraid driver is doing (if you get your box up).
Alan Cox rewrote the aacraid driver for 2.4.9-21, does it work with that ?