Re: 2.6.24-rc3-mm1: usb mouse doesn't work

Alan Stern <[email protected]>
Newsgroups gmane.linux.usb.devel,gmane.linux.kernel
Message-ID <[email protected]>
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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.