We just test-installed a Promise controller in a machine, and tried to
get it probed. Turns out that crashed the machine.
/root# lspci -v -s 00:09.0
00:09.0 Unknown mass storage controller: Promise Technology, Inc. 20268 (rev 02) (prog-if 85)
Subsystem: Promise Technology, Inc. 20268
Flags: bus master, 66Mhz, slow devsel, latency 32, IRQ 9
I/O ports at e000 [size=8]
I/O ports at d800 [size=4]
I/O ports at d400 [size=8]
I/O ports at d000 [size=4]
I/O ports at c800 [size=16]
Memory at fb000000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at <unassigned> [disabled] [size=16K]
Capabilities:  Power Management version 1
We then went into the bios (install video card, grab a monitor,
etcetc.) and told it to assign interrupts automatically, rather than
IRQ9 for all slots....
So then the VGA card, ethernet card, scsi card all got assigned
different IRQs than 9.
Now when we insmod the IDE, the machine doesn't crash.
Hypothesis: The Promise driver enables IRQs on the chip first, then
grabs its IRQ. This leads to an interrupt storm, provided that any
other device is using that IRQ.
This is on our testing machine:
Pentium PRO 150.
We've got our system running. We only have the hardware for a day, so
we're running our tests, and won't have time to test stuff (like
upgrading the kernel. Sorry)
-- ** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 ** *-- BitWizard writes Linux device drivers for any device you may have! --* * There are old pilots, and there are bold pilots. * There are also old, bald pilots. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jun 30 2002 - 22:00:09 EST