From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <443616ac3c0ca2287124acb19b7bdf3f@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Tue, 12 Feb 2008 19:50:49 -0500
To: 9fans@cse.psu.edu
Subject: Re: [9fans] usbd problem
In-Reply-To: <964c1529df94a5c6ba189fb0520afbc5@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 51afcda0-ead3-11e9-9d60-3106f5b1d025

thanks for the update.  i have switched to a slightly
more agreeable key but i have a new way to fail.  the key
works the first time.  but the second time i connect the same
key, i get

	; usbfat:
	setupreq: write err: No response
	usb/disk: describedevice: error writing usb device request: get device descriptor: No response
	No response
	mount: mount /n/usb: unknown format

initially in this state, i could restart usbd and got this information.

	; usb/usbd -fvD
	usbd: probing usb2/0.1
	usbd: probing usb3/0.1
	usbd: probing usb4/0.1
	usbd: probing usb0/0.1
	out	5	[8] 80 06 00 01 00 00 08 00
	in	5	[8] 12 01 00 02 00 00 00 40
	usb1/0.1 maxpkt: 64
	out	5	[8] 00 05 02 00 00 00 00 00
	describedevice
	out	24	[8] 80 06 00 01 00 00 18 00
	in	24	[18] 12 01 00 02 00 00 00 40 ec 08 08 00 00 01 01 02 03 01
	loadconfig
	out	24	[8] 80 06 00 02 00 00 ff 03
	in	24	[32] 09 02 20 00 01 01 00 80 64 09 04 00 00 02 08 06 50 00 07 05 81 02 40 00 00 07 05 02 02 40 00 00
	out	24	[8] 00 09 01 00 00 00 00 00
	checking usb1/0.1
	...

but two devices (1 and 2) with the identical status files
existed.

i've got things pretty wedged now -- usbd won't start
so it's hard to get much more information. but i did
get two "done > started, 1 0" messages on the console.

sorry for the poor bug report.

- erik