>
>
> I had two problems, which were both (possibly) not the fault of
> the aix7xxx driver:
>
> 1. 2 IO-APIC's. I finally noticed both the discreet "Warning:
> Multiple APIC's not supported" bootup message, and the "Disable
> secondary APIC" option in the BIOS. Both APIC's enabled resulted
> in Linux deciding that the scsi0 device was at an interrupt that
> it wasn't really at. That sort of hung the boot process.
>
> 2. Once I got the APIC problem solved, I found that both my eepro100
> and my scsi1 were sharing the same interrupt. / is on scsi1, so
> that interrupt was causing lots of activity. A kernel complile
> resulted in more "scsi: aborting command due to timeout..."
> messages, which were then followed by messages from the ethernet
> driver about a lost interrupt or something. I moved the eepro100
> to the second PCI bus so that it had its own interrupt, and the
> system seems to be quite stable now. (So, IRQ sharing between
> aic7xxx and eepro100 seems broken!)
>
> Some system info:
> CPU0 CPU1 CPU2 CPU3
> 0: 18424 30176 149440 30416 IO-APIC-edge timer
> 1: 404 759 3781 761 IO-APIC-edge keyboard
> 2: 0 0 0 0 XT-PIC cascade
> 9: 8907 17891 88969 17802 IO-APIC-edge Intel EtherExpress Pro 10/100 Ethernet
> 10: 2284 3206 16302 3345 IO-APIC-edge aic7xxx
> 11: 45 3 3 8 IO-APIC-edge aic7xxx
> 12: 1257 2539 12729 2487 IO-APIC-edge PS/2 Mouse
> 13: 1 0 0 0 XT-PIC fpu
> 14: 3 0 0 0 IO-APIC-edge ide0
> NMI: 0
> IPI: 0
>
> If anyone wants me to test something on here, let me know.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu