linux-kernel - Re: [PATCH] OHCI: disallow autostop when wakeup is not available

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.0701021013470.4122-100000@iolanthe.rowland.org>
Date:	Tue, 2 Jan 2007 10:16:21 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Andrey Borzenkov <arvidjaar@...l.ru>
cc:	Greg KH <greg@...ah.com>,
	USB development list <linux-usb-devel@...ts.sourceforge.net>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] OHCI: disallow autostop when wakeup is not available

On Mon, 1 Jan 2007, Andrey Borzenkov wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Wednesday 15 November 2006 00:28, Alan Stern wrote:
> > This patch (as822) prevents the OHCI autostop mechanism from kicking in
> > if the root hub is not able or not allowed to issue wakeup requests.
> >
> > Signed-off-by: Alan Stern <stern@...land.harvard.edu>
> >
> > ---
> >
> > Greg:
> >
> > This patch should go into 2.6.19-rc ASAP.  It does solve a real problem.
> > The larger-scale changes Dave and I have been discussing will be submitted
> > separately, for inclusion in 2.6.20.
> >
> 
> Is the original problem (OHCI constantly attempting and failing to suspend 
> root hub) supposed to be fixed in 2.6.20?

No.  It can't be fixed in the kernel because it is a hardware bug.

>  Currently in rc3 I have
...
> ohci_hcd 0000:00:02.0: auto-stop root hub
> ohci_hcd 0000:00:02.0: auto-wakeup root hub
> ohci_hcd 0000:00:02.0: auto-stop root hub
> ohci_hcd 0000:00:02.0: auto-wakeup root hub
> ...
> 
> and it goes on and on until I stop it manually by usual method:
> 
> usb usb1: remote wakeup needed for autosuspend

The patch mentioned above allows the manual method to work.  Without the 
patch you would not be able to stop these messages at all, as you already 
have seen.

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/