I then tested this more completely by using the stock 2.2.1 IBM SCSI driver
with only one change, I removed the spin_lock_irqsave/spin_lock_irqrestore
from the do_interrupt_hanlder routine. With this minor change I no longer
loose serial interrupts.
The most information I could find about this change was in Linus' comments
about the 2.1.95 patch, and by my limited interpretation the changes were
mainly for SMP. So, my big question then is this, is it really neccessary
to do spin_locks on SCSI interrupt handlers even on UP machines? So far
I've noticed no ill effects with my change.
The problem with this seems to occur on machines other than mine. I
received several emails from other users who were experiencing similar
trouble with the Seagte scsi driver.
I'd like to hear some other comments on this. Perhaps there are better ways
to handle this such as trimming down the interrupt handler and moving some
portions to another routine that will funtion with interrupts enabled.
Any help would be greatly appreciated.
Later,
Tom
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/