Re: aacraid driver

Using the patches to 2.6.4 to update the aacraid driver to the latest
adaptec 1.1.5 driver, the kernel does not boot, hanging at:

Red Hat/Adaptec aacraid driver (1.1-5[9999])
ACPI: No IRQ known for interrupt pin D of device 0000:00:07.2 - using
IRQ 255
AAC0: kernel 4.0-0 build 6011
AAC0: monitor 4.0-0 build 6011
AAC0: bios 4.0-0 build 6011
AAC0: serial b73c5a
AAC0: Non-DASD support enabled
AAC0: 64 Bit DAC enabled
scsi0 : aacraid

The patches I used are at:

http://linux.mainstreetsoftworks.com/0290_aacraid_1.1.5.patch
http://linux.mainstreetsoftworks.com/0291_aacraid_1.1.5_2.6.4.patch

  Aman Gupta

On Tue, 2004-03-16 at 14:28, Aman Gupta wrote:
> I am using 2.6.4 on a dual opteron 246 box with 8GB ram and a Adaptec
> 2200S scsi raid card setup to use 6 scsi drives in a raid10 config. The
> box is running Gentoo AMD64 with 64bit kernel/applications. 
> 
> I keep getting the following panic, sometimes happens during boot, and
> at other times up to half an hour after the bootup.
> 
> Unable to handle kernel paging request at 00000000101f007c RIP:
> <ffffffff802c1cad>{aac_command_normal+109}PML4 1fd036067 PGD 1fd076067
> PMD 0
> Oops: 0002 [1] SMP
> CPU 0
> Pid: 0, comm: swapper Not tainted
> RIP: 0010:[<ffffffff802c1cad>]
> <ffffffff802c1cad>{aac_command_normal+109}
> RSP: 0018:ffffffff80494448  EFLAGS: 00010002
> RAX: 0000010000048018 RBX: 0000010000048000 RCX: 0000000000000008
> RDX: 00000000101f007c RSI: 00000100101f0000 RDI: 00000100f7e1d2e8
> RBP: 00000100f7e1d2e8 R08: ffffffff80498000 R09: ffffffff805054a0
> R10: 0000000000000000 R11: 0000000000000000 R12: 00000100101f0000
> R13: 00000100101f007c R14: 0000000000000000 R15: 0000000000000000
> FS:  0000002a95bcf060(0000) GS:ffffffff804901c0(0000)
> knlGS:0000000000000000
> CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> CR2: 00000000101f007c CR3: 0000000000101000 CR4: 00000000000006e0
> Process swapper (pid: 0, stackpage=ffffffff803d83a0)
> Stack: 0000010000049080 0000000000000086 00000101ffff1000
> 0000000000000006
>        ffffffff80494488 ffffffff8012eece 00000100100048c0
> 000001001007d120
>        ffffffff804944c8 0000000000000082
> Call Trace:<IRQ> <ffffffff8012eece>{recalc_task_prio+430}
> <ffffffff8013daec>{update_wall_time+12}
>        <ffffffff802c1e21>{aac_rx_intr+97}
> <ffffffff8011190f>{handle_IRQ_event+47}
>        <ffffffff80111b61>{do_IRQ+193} <ffffffff8010cc60>{default_idle+0}
>        <ffffffff8010f1fd>{ret_from_intr+0}  <EOI>
> <ffffffff80131600>{thread_return+0}
>        <ffffffff8010cc84>{default_idle+36}
> <ffffffff8010cd0a>{cpu_idle+26}
>        <ffffffff8049d84d>{start_kernel+397}
>                                                                                                                        
> Code: 89 02 31 d2 e8 2a f7 ff ff ba 01 00 00 00 be 01 00 00 00 49
> RIP <ffffffff802c1cad>{aac_command_normal+109} RSP <ffffffff80494448>
> CR2: 00000000101f007c
>  <0>Kernel panic: Aiee, killing interrupt handler!
> In interrupt handler - not syncing
>  <0>Rebooting in 2 seconds..
> 
> 
> I also got the panic message:
> 
> Kernel panic: Attempted to kill the idle task!
> In idle task - not syncing
> 
> earlier today, but I think that is a BIOS bug that can be fixed with the
> kernel option 'idle=poll'
> 
> Also, I don't have any swap space setup on the box - should I just
> disable swap in the kernel so swapper isn't running? Will this actually
> stop the panic, or just cause another process to die?
> 
> Thanks,
>   Aman Gupta
> 

_______________________________________________
Linux-aacraid-devel mailing list
[email protected]
http://lists.us.dell.com/mailman/listinfo/linux-aacraid-devel
Please read the FAQ at http://lists.us.dell.com/faq or search the list archives at http://lists.us.dell.com/htdig/