Date: Wed, 30 Mar 2005 14:36:11 +0200 From: Bernd Walter <ticso@cicely12.cicely.de> To: Alexandre Jouravlev <bofh@mail.ru> Cc: freebsd-usb@freebsd.org Subject: Re: Ezload problems. Message-ID: <20050330123610.GP33677@cicely12.cicely.de> In-Reply-To: <548e4b9dbf2553ebdc2584bee71441a5@mail.ru> References: <d6c9e248f5b46757d8083af2d48db088@mail.ru> <20050330104411.GL33677@cicely12.cicely.de> <dd8d511271eeba61ce9b9b25c8d4e123@mail.ru> <20050330110436.GM33677@cicely12.cicely.de> <6ea402e33ab5f4d1a9e66c51c5ddc78a@mail.ru> <20050330115629.GO33677@cicely12.cicely.de> <548e4b9dbf2553ebdc2584bee71441a5@mail.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 30, 2005 at 04:11:27PM +0400, Alexandre Jouravlev wrote: > > > >Try setting hw.usb.uhub.debug=20 befor testing. > >Would be interesting to see why you see a disconnect event, > >but no connect. > > > > > As I am not skilled usb developer (this is my first usb project ever) I > don't understand much in this output. > Here is the output of debug session from plugging the device to what > happens next: > > ugen0: Device (no firmware), rev 1.00/1.00, addr 2 > uhub_intr: sc=0xc288d790 > uhub_explore dev=0xc2af4380 addr=1 > uhub_explore: uhub0 port 1 status 0x0100 0x0000 This is a root hub - things might be different if you use another host controller type or an external hub between. Neverthelesse there is a problem to fix somewhere. > uhub_explore: port=1 !C_CONNECT_STATUS > uhub_explore: uhub0 port 2 status 0x0100 0x0003 > uhub_explore: C_PORT_ENABLED 0x3 > uhub_explore: status change hub=1 port=2 > uhub_explore: device addr=2 disappeared on port 2 > ugen0: at uhub0 port 2 (addr 2) disconnected > ugen0: detached > uhub_explore: port=2 !CURRENT_CONNECT_STATUS > uhub_intr: sc=0xc288d790 > uhub_explore dev=0xc2af4380 addr=1 > uhub_explore: uhub0 port 1 status 0x0100 0x0000 > uhub_explore: port=1 !C_CONNECT_STATUS > uhub_explore: uhub0 port 2 status 0x0101 0x0001 > uhub_explore: status change hub=1 port=2 > uhub_intr: sc=0xc288d790 > uhub_explore dev=0xc2af4380 addr=1 > uhub_explore: uhub0 port 1 status 0x0100 0x0010 > uhub_explore: port=1 !C_CONNECT_STATUS > uhub_explore: uhub0 port 2 status 0x0100 0x0011 > uhub_explore: status change hub=1 port=2 > uhub_explore: port=2 !CURRENT_CONNECT_STATUS > uhub_intr: sc=0xc288d790 I asume the messages don't have much time in between? > And next the following repeated at rate about 2 messages per second: > > uhub_intr: sc=0xc288d790 > uhub_explore dev=0xc2af4380 addr=1 > uhub_explore: uhub0 port 1 status 0x0100 0x0010 > uhub_explore: port=1 !C_CONNECT_STATUS > uhub_explore: uhub0 port 2 status 0x0101 0x0011 > uhub_explore: status change hub=1 port=2 Will have to check the meaning of those states in USB specs. Looks like we ignore it for whatever reason. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050330123610.GP33677>