-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 20 May 2001, David Brownell wrote:
> > > Bogus kernel config, those drivers didn't get rebuilt -- sorry. This
> > > one should be OK ("dev" --> "usb_dev").
> >
> > Hi Dave,
> >
> > Thanks for the update! Now things compile, but the oopses come back
> > to back :-(.
>
> OK, so that "usbcore-0519.patch" won't behave. There are even more
> nonsensical things going on in the device-to-bus binding than that first
> issue I noticed ... ignore that patch. Most drivers can't trigger the code
> paths that was trying to fix, anyway.
>
> 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
rmmod usb-ohci stops the flood and produces the usual oops.
Still, adding the line "case -ETIMEDOUT:" to printer-0518 does cure the
problem (but I have no idea what other diseases this may cause).
Sincerely, Anders
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.5 (SunOS)
Comment: For info see http://www.gnupg.org
iD8DBQE7B/aWWyfD6jrb5n4RAsWJAKCzbvQLp4/rJT4A4QmGjofZyIC7lgCgqfAr
QmBo6evHwGX+vmii/dpsek4=
=GgOx
-----END PGP SIGNATURE-----
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
