linux-kernel - Re: usb device not showing up

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.0811062223100.26081-100000@netrider.rowland.org>
Date:	Thu, 6 Nov 2008 22:26:55 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Norbert Preining <preining@...ic.at>
cc:	Pete Zaitcev <zaitcev@...hat.com>,
	Mattia Dongili <malattia@...ux.it>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB list <linux-usb@...r.kernel.org>
Subject: Re: usb device not showing up

On Thu, 6 Nov 2008, Norbert Preining wrote:

> 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

Yes, okay.  That's bus 4, address 2.

> > 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. 

I hope it works out.

> > 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.

It must be like Pete said: Some events just got lost because not enough
memory was allocated to usbmon.  Fortunately those missing events had
nothing to do with the hso problem.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/