Date: Wed, 10 Apr 2002 21:31:12 +0200 (CEST) From: Nick Hibma <n_hibma@van-laarhoven.org> To: Tomas Pluskal <plusik@pohoda.cz> Cc: "freebsd-scsi@freebsd.org" <freebsd-scsi@freebsd.org>, "freebsd-hardware@freebsd.org" <freebsd-hardware@freebsd.org> Subject: Re: umass0: BBB reset failed, TIMEOUT Message-ID: <20020410212511.K27956-100000@heather.van-laarhoven.org> In-Reply-To: <20020405104357.K305-100000@s096-n062.tele2.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
For the record: The problem is the fact that the device gets confused when a command is sent to it on the control pipe while at the same time it is working on a BBB command that came in on the bulk pipe earlier. This happens during attach. The solution is to postpone the inquiry command that CAM sends until attach has finished completely (including sending the attach event to userland (it requests string descriptors from the device after umass_attach has finished)). The change I committed earlier today doesn't work as CAM does XPT actions synchroneously. I expected them to be asynchroneous, especially when a SCSI_BUSY error is returned. Nevertheless that change is a correct one as we do not want anything to happen until we are completely finished with initialising the device. Tomas is testing changes I proposed at the moment. Nick On Fri, 5 Apr 2002, Tomas Pluskal wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Hello, > > I am trying to connect a nikon 775 camera via USB. When I plug it in > BEFORE I boot the kernel, it works ok (it detects da0 and I can mount it). > When I plug it when system is already up, it doesn't work. It detects > umass0 (umass0: NIKON NIKON DSC E775, rev 1.10/1.00, addr 2), but it > doesn't attach it to da0 and in dmesg I see: > umass0: BBB reset failed, TIMEOUT > umass0: BBB bulk-in clear stall failed, IOERROR > umass0: BBB bulk-out clear stall failed, IOERROR > about 10 times... > > I have all drivers compiled in kernel (no modules), > > I've been searching throught lists, but I found only similar problem > reports (with different USB devices), but no solution. Is there any ? > > Thanks > > Tomas Pluskal > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (FreeBSD) > Comment: For info see http://www.gnupg.org > > iD8DBQE8rWWkqlO9Q2aZisoRAr1tAJ9DyAw2eaYP+7390ALLSZpW062DEACfTIwf > GLZu0RxwOFE5KcELlKlLelg= > =3hJh > -----END PGP SIGNATURE----- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > -- n_hibma@van-laarhoven.org http://www.van-laarhoven.org/ n_hibma@FreeBSD.org http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020410212511.K27956-100000>