Re: bug in NCR5380.c scsi driver - no sti() :)

Alan Cox (alan@lxorguk.ukuu.org.uk)
Wed, 31 Mar 1999 13:34:33 +0100 (BST)


> Comparing code from 2.0.33 and 2.2.4 I see that sti()
> became restore_flags() and hence the interrupts are _never_ enabled inside
> NCR5380_main() 8-|

Thats not the case.

> It means that despite all tricks with USLEEP the system is paralized while
> accessing scsi. Even the date does not advance :)

The delay loops do

spin_unlock_irq(&io_request_lock)

blah

spin_lock_irq(&io_request_lock)

which means interrupts are running during the delays. It still cripples the
machine because its a polled 8 bit device that demands continual CPU
attention.

Alan

-
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/