linux-kernel - Re: [linux-usb-devel] 2.6.17: dmesg flooded with "ohci

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.0609221648330.8223-100000@iolanthe.rowland.org>
Date:	Fri, 22 Sep 2006 16:52:23 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Andrey Borzenkov <arvidjaar@...l.ru>
cc:	David Brownell <david-b@...bell.net>,
	<linux-usb-devel@...ts.sourceforge.net>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [linux-usb-devel] 2.6.17: dmesg flooded with "ohci_hcd 0000:00:02.0:
 wakeup"

On Fri, 22 Sep 2006, Andrey Borzenkov wrote:

> > It's the usual case of fixing one bug triggering another, in your case
> > because the fix ran into a previously unseen hardware bug.  One other
> > way to work around that bug would be disabling CONFIG_PM, but I suspect
> > you don't want to go that route...
> >
> > > Here you are. I am still puzzled where all these "suspends" come from - I
> > > did not try any suspend in the meantime ...
> >
> > It's the driver putting the controller into a low power state.  Your
> > hardware seems to have a bug whereby that doesn't work correctly,
> > making it immediately leave that state.  (And the driver messaging is
> > fine for what should be an uncommon event; plus it highlighted your
> > hardware bug.)  Notice the "initreset quirk" message -- another bug
> > in that hardware.  Workarounds in both cases are simple.
> >
> > When I get a moment, I'll have a patch for you to try.  Meanwhile,
> > either workaround I showed above should prevent the attempt to enter
> > that low power mode.
> >
> 
> 
> I updated to 2.6.18 and got the same issue; any patch to try?

> > > ohci_hcd 0000:00:02.0: suspend root hub
> > > hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000, resume root
> > > hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000
> > > ohci_hcd 0000:00:02.0: suspend root hub
> > > hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000, resume root
> > > hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000
> > > ohci_hcd 0000:00:02.0: suspend root hub
> > > hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000, resume root
> > > hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0000
> > > ohci_hcd 0000:00:02.0: suspend root hub
> >
> > .... etc

I had to add special code in uhci-hcd for controllers where the 
resume-detect mechanism was broken.  When the root hub on one of those 
bad machines is suspended, the driver uses polling instead of interrupts 
to detect port status changes.

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/