linux-kernel - Re: [linux-usb-devel] 2.6.24-rc3-mm1: usb mouse doesn't work

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.0712311605170.10555-100000@iolanthe.rowland.org>
Date:	Mon, 31 Dec 2007 16:06:25 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	"Kirill A. Shutemov" <k.shutemov@...esys.com>
cc:	Marin Mitov <mitov@...p.bas.bg>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB development list <linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] 2.6.24-rc3-mm1: usb mouse doesn't work

On Fri, 23 Nov 2007, Kirill A. Shutemov wrote:

> On [Thu, 22.11.2007 21:51], Alan Stern wrote:
> > On Thu, 22 Nov 2007, Marin Mitov wrote:
> > 
> > > > > > I've had some strangenesses with USB lately.  Sometimes running `lsusb'
> > > > > > makes the USB system notice a newly attached device.
> > > > >
> > > > > No. But I have new messages in dmesg:
> > > > >
> > > > > uhci_hcd 0000:00:1d.3: FGR not stopped yet!
> > > > > uhci_hcd 0000:00:1d.2: FGR not stopped yet!
> > > > > uhci_hcd 0000:00:1d.1: FGR not stopped yet!
> > > > > uhci_hcd 0000:00:1d.0: FGR not stopped yet!
> > > > >
> > > > > > Is that "FGR not stopped yet!" messgae new behaviour?
> > > > >
> > > > > It is a new message since 2.6.24-rc3. I have never try -mm tree before.
> > > >
> > > > These messages could indicate a timing problem.  You can see the code
> > > > that writes the messages near the end of wakeup_rh() in
> > > > drivers/usb/host/uhci-hcd.c.
> > > >
> > > > The message gets written if the controller hardware hasn't turned off a
> > > > particular bit after a 4-us delay.  If the udelay() function wasn't
> > > > working right, it could cause this problem.
> > > 
> > > udelay() _is_ OK for 2.6.24-rc3, so it is not the cause of the problem
> > 
> > But is it OK for 2.6.24-rc3-mm1?  Kirill said specifically that 
> > 2.6.24-rc3 does not display the message but 2.6.24-rc3-mm1 does.
> 
> How can I test it?

Any progress?  How about more recent kernels?

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/