From: Norbert Preining <preining@logic.at>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
Mattia Dongili <malattia@linux.it>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: usb device not showing up
Date: Thu, 6 Nov 2008 23:57:13 +0100 [thread overview]
Message-ID: <20081106225713.GD11406@gamma.logic.tuwien.ac.at> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0811061423510.23473-100000@iolanthe.rowland.org>
Hi Alan,
On Do, 06 Nov 2008, Alan Stern wrote:
> Okay. In the earlier (working) test, the modem showed up on bus 4, not
> bus 2. Not that it matters much -- the modem didn't show up at all in
Sorry, it is always bus 4, i meant interface (or how do you call it) 2,
bus id 004:002
> this test, on any bus. Its USB interface seems to be electrically
> disconnected or turned off.
Right.
> should start working, but I have no idea what that would be. It's not
> a USB issue; as far as USB is concerned the device just isn't there at
Ok, if it is not an usb issue, I guess I have to hope for some fix in
sony-laptop module.
> Interestingly, this trace appears to be missing some events. There's a
> gap between timestamps 4284549076 and 4284645743 (the timestamps are in
> the second column) where we should see the initialization of bus 5 and
> bus 6. Instead there's a 100-ms delay in which nothing happens,
> followed later on by the second initialization phase for those two
> buses.
>
> I have to wonder... Did you remove any part of the trace? Did usbmon
No. I sent you the output as it was saved on my hard disk. No editing
involved.
> malfunction? Did parts of the initialization for those two buses
> really get skipped (I can't imagine how)?
No idea. I can redo any tests you want, but I can guarantee that I
didn't tinker with the usbmon-bad.txt file itself, it was created with
cat .../0u > usbmon-bad.txt
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <preining@logic.at> Vienna University of Technology
Debian Developer <preining@debian.org> Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
Someone down there
is trying to kill us!'
`Terrific,' said Arthur.
`But don't you see what this means?'
`Yes. We are going to die.'
`Yes, but apart from that.'
`APART from that?'
`It means we must be on to something!'
`How soon can we get off it?'
--- Zaphod and Arthur in a certain death situation over
--- Magrathea.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
next prev parent reply other threads:[~2008-11-06 22:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 15:31 Norbert Preining
2008-11-03 19:05 ` Alan Stern
2008-11-04 9:37 ` Norbert Preining
2008-11-04 15:23 ` Alan Stern
2008-11-04 16:17 ` Norbert Preining
2008-11-04 16:36 ` Alan Stern
2008-11-04 21:58 ` Norbert Preining
2008-11-05 16:13 ` Alan Stern
2008-11-06 15:00 ` Norbert Preining
2008-11-06 15:23 ` Alan Stern
2008-11-06 17:19 ` Norbert Preining
2008-11-06 19:34 ` Alan Stern
2008-11-06 22:57 ` Norbert Preining [this message]
2008-11-07 3:26 ` Alan Stern
2008-11-07 1:54 ` Pete Zaitcev
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=20081106225713.GD11406@gamma.logic.tuwien.ac.at \
--to=preining@logic.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=malattia@linux.it \
--cc=stern@rowland.harvard.edu \
--cc=zaitcev@redhat.com \
/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
all inboxes | Powered by JetHome®