linux-kernel - Re: debugging oops after disconnecting Nexio USB touchscreen

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.0912080958050.3046-100000@iolanthe.rowland.org>
Date:	Tue, 8 Dec 2009 10:03:58 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Ondrej Zary <linux@...nbow-software.org>
cc:	linux-usb@...r.kernel.org, <linux-kernel@...r.kernel.org>
Subject: Re: debugging oops after disconnecting Nexio USB touchscreen

On Tue, 8 Dec 2009, Ondrej Zary wrote:

> > You don't have to compile either driver into the kernel.  Try doing
> > this:
> >
> > 	rmmod ehci-hcd
> >
> > 	dmesg -c >/dev/null (clear the log buffer)
> >
> > 	Start up usbmon on the 0u file
> >
> > 	Plug in the hub, which attaches to UHCI
> >
> > 	modprobe ehci-hcd
> > 	At this point the hub should switch over to EHCI
> >
> > It will make things easier to understand if you unplug all other USB
> > devices first.  Let's see what that shows, both in usbmon and in dmesg.
> >
> > It would be nice if the EHCI controller turned out to be at fault.
> > Then we could blame this entire problem on the controller hardware.  :-)
> 
> OK, all USB devices disconnected, except for that mass storage card reader
> which is built-in.
> 
> Strange, it worked fine:

...

> Tried multiple times with different devices (except the Nexio) connected and it
> always worked. Everything reconnected to ehci after loading the moduled.

Then you should try again in the original configuration to see if it 
still happens.  If it all works right, forget about it and let's move 
on.

To start, you could modify those debugging lines I had you put in.  As 
well as printing out qh->qh_next, also print ((unsigned long) 
qh->hw_next) with a %lx format specifier.

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/