That is a failure to route the interrupts and is possibly an issue with the kernel and the hardware, and not the driver directly (since there is an expectation that request_irq will connect the interrupt to the interrupt service routine). Judith reported success in the past with this patch on her hardware, perhaps the motherboard on your system has some odd BIOS setup of the hardware that is giving acpi or the apic some headaches? Can you check out success or failure on other motherboards? Please try the suggestions from the driver (safe flags)? Sincerely -- Mark Salyzyn > -----Original Message----- > From: Vivek Goyal [mailto:vgoyal@xxxxxxxxxx] > Sent: Monday, April 23, 2007 12:12 PM > To: Salyzyn, Mark > Cc: linux-scsi@xxxxxxxxxxxxxxx; James Bottomley; Kexec > Mailing List; Judith Lebzelter > Subject: Re: [PATCH] aacraid: fails to initialize after a > kexec operation > > > On Mon, Apr 23, 2007 at 09:38:43AM -0400, Salyzyn, Mark wrote: > > Missing portion of the kexec changes to the aacraid driver. > The platform > > functions were not initialized when the restart function is > activated > > resulting in a panic when these platform functions are > called. Please > > note that it is NOT a mistake that the disable interrupt > handler is used > > as the initial value of the enable interrupt platform > function, it will > > be set up correctly once the adapter is discovered and initialized. > > > > Please note that aacraid_kexec_5.patch contains this fix, since an > > earlier aacraid_kexec patch was applied to the tree and > appears to have > > propagated, this is meant to supersede the earlier patch > and bring it up > > to date with aacraid_kexec_5.patch, but expected to break when the > > aacraid_kexec_5.patch propagates... James, can you sort out > this mess > > (either by stopping aacraid_kexec_5.patch, or by letting > this enclosed > > patch move with some level of priority)? > > > > ObligatoryDisclaimer: Please accept my condolences > regarding Outlook's > > handling of patches. > > > > This attached patch is against current scsi-misc-2.6. Also > expect this > > patch can be applied to 2.6.21-rc6-mm1 > > > > Signed-off-by: Mark Salyzyn <aacraid@xxxxxxxxxxx> > > > > --- > > > > Thanks Mark, > > I applied this patch but it still does not work. Now oops is gone but > I get following while aacraid is trying to initialize. > > Adaptec aacraid driver (1.1-5[2437]-mh4) > ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 25 (level, low) -> IRQ 25 > aacraid: aac_fib_send: first asynchronous command timed out. > Usually a result of a PCI interrupt routing problem; > update mother board BIOS or consider utilizing one of > the SAFE mode kernel options (acpi, apic etc) > aac_fib_free, XferState != 0, fibptr = 0xffff810104140000, > XferState = 0x810ad > ACPI: PCI interrupt for device 0000:01:02.0 disabled > aacraid: probe of 0000:01:02.0 failed with error -110 > > > Thanks > Vivek > > - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
