-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 20 May 2001, David Brownell wrote:
> > > How about the "printer-0519.patch" ... did that resolve, by itself,
> > > the problems in the printer driver? Specifically: the looping you
> > > observed with the previous printer patch, caused by the fact that
> > > usblp_write didn't drop the semaphore so usblp_disconnect could
> > > never do its job. If that's fixed, then the oops-on-rmmod paths
> > > will be very hard to trigger from usermode.
> >
> > The printer-0519 patch gives a flood of:
> >
> > printer.c: usblp0: error -110 reading printer status
>
> Previously you'd said it looped forever there. What I'd expect to
> see is a "flood" of such messages (processes using the device will
> notice it's gone before khbud can) and then it should stop. Did
> this flood not stop? What happens if you add a wait_ms(10) call
> at about line 416, right after up (&usblp->sem) gets called?
Without the wait_ms call, the flood continued long enough that I could go
out and brew myself a nice big can of coffee. And a bit later, with the
wait_ms call, the flood didn't stop while I poured myself a cup, put in a
bit of milk, and had a few sips :-).
Sincerely, Anders
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (SunOS)
Comment: For info see http://www.gnupg.org
iD8DBQE7CDbsWyfD6jrb5n4RAs5xAJ9Uk0lv9cCLJyhYqvd7w1oHod0iWwCg2hIy
k54p/j1pk7nY0uXZw3AG7mI=
=VDHj
-----END PGP SIGNATURE-----
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
