linux-kernel - Re: 2.6.18-rc6-mm2 (-mm1): ohci_hcd does not recognize new devices

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]

Date:	Mon, 18 Sep 2006 08:50:43 +0200
From:	Jan De Luyck <ml_linuxkernel_20060528@...re.org>
To:	linux-kernel@...r.kernel.org
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>, Andrew Morton <akpm@...l.org>,
	David Brownell <david-b@...bell.net>,
	USB development list <linux-usb-devel@...ts.sourceforge.net>,
	Greg KH <greg@...ah.com>,
	Alan Stern <stern@...land.harvard.edu>
Subject: Re: 2.6.18-rc6-mm2 (-mm1): ohci_hcd does not recognize new devices

On Monday 18 September 2006 08:27, Rafael J. Wysocki wrote:
> On Saturday, 16 September 2006 10:13, Rafael J. Wysocki wrote:
> > On Saturday, 16 September 2006 00:13, Rafael J. Wysocki wrote:
> > > It looks like the ohci_hcd driver sometimes has problems with the
> > > initialization (eg. USB mouse doesn't work after a fresh boot and
> > > reloading of the driver helps).
> > >
> > > I have observed this on two different x86_64 boxes (HPC 6325, Asus
> > > L5D), but it is not readily reproducible.  Anyway I've got a dmesg
> > > output from a failing case which is attached.
> >
> > Actually, the problem is ohci_hcd doesn't seem to recognize devices
> > plugged into the USB ports.
> >
> > For example, if I unplug and replug a mouse (that worked before
> > unplugging), it doesn't work any more.  I have to reload ohci_hcd to make
> > it work again.
> >
> > This is 100% reproducible and occurs on the two boxes above.

I can confirm this behaviour. I've also seen that sometimes my USB 
keyboard/mouse doesn't work after booting up. Reloading the module solves the 
problem.

This is on an amd64 box, ABIT kn9-sli, nForce 550.

This is with 2.6.17.13.

> I have carried out a binary search and found that the problem is caused by
>
> gregkh-usb-usbcore-remove-usb_suspend_root_hub.patch

Will this work against 2.6.17.13 vanilla?

Thanks,

Jan
-- 
QOTD:
	"If I could walk that way, I wouldn't need the cologne, now would I?"
-
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/