From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] usbd problem
Date: Tue, 12 Feb 2008 19:50:49 -0500 [thread overview]
Message-ID: <443616ac3c0ca2287124acb19b7bdf3f@quanstro.net> (raw)
In-Reply-To: <964c1529df94a5c6ba189fb0520afbc5@plan9.bell-labs.com>
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
next prev parent reply other threads:[~2008-02-13 0:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 1:36 erik quanstrom
2008-02-12 8:20 ` Richard Miller
2008-02-12 13:59 ` Sape Mullender
2008-02-12 14:13 ` erik quanstrom
2008-02-12 14:35 ` Sape Mullender
2008-02-12 14:42 ` Fco. J. Ballesteros
2008-02-13 0:50 ` erik quanstrom [this message]
2008-02-13 14:32 ` Richard Miller
2008-02-13 14:45 ` erik quanstrom
2008-02-13 14:52 ` Richard Miller
2008-02-13 15:04 ` erik quanstrom
2008-02-13 16:18 ` Sape Mullender
2008-02-13 16:37 ` erik quanstrom
2008-02-13 17:09 ` Sape Mullender
2008-02-12 8:21 Richard Miller
2008-02-12 13:21 ` erik quanstrom
2008-02-12 21:24 ` Richard Miller
2008-02-12 21:28 ` geoff
2008-02-12 21:33 ` Richard Miller
2008-02-12 21:37 ` erik quanstrom
2008-02-12 22:18 ` Richard Miller
2008-02-12 23:05 ` geoff
2008-02-13 6:31 ` arisawa
2008-02-13 8:25 ` Richard Miller
2008-02-13 8:54 ` arisawa
2008-02-13 10:58 ` Richard Miller
2008-02-13 14:13 ` Richard Miller
2008-02-13 18:49 ` geoff
2008-02-13 15:54 ` Richard Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=443616ac3c0ca2287124acb19b7bdf3f@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).