Messages in this thread | | | Date | Mon, 10 Dec 2001 12:44:40 -0500 (EST) | From | "Richard B. Johnson" <> | Subject | Re: 2.4.16: scsi "PCI error Interrupt"?! |
| |
On Mon, 10 Dec 2001, Keith Warno wrote: [Snipped...]
> > Any ideas? I really don't like the SCSI controller sharing an interrupt > with anyone but I can't seem to force it to be in its own land. >
If the controller is a separate board, not built onto the motherboard, move it to a different slot! There is only one interrupt line going to each PCI slot. This should move the IRQ to something else.
In the same manner, if a board-mounted device is sharing an IRQ with some slot device, move the slot device to another slot or swap it with something that isn't using an interrupt.
Also, if your BIOS has an Y/N entry for (PnP OS), say "N". This will force the BIOS to more-properly allocate resources. This gives Linux at least a "correct" set-up to start with when it configures the PCI interface.
Cheers, Dick Johnson
Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
I was going to compile a list of innovations that could be attributed to Microsoft. Once I realized that Ctrl-Alt-Del was handled in the BIOS, I found that there aren't any.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |