[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0611121120110.6353-100000@netrider.rowland.org>
Date: Sun, 12 Nov 2006 11:31:24 -0500 (EST)
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.19-rc5 regression: can't disable OHCI
wakeup via sysfs
On Sat, 11 Nov 2006, Andrey Borzenkov wrote:
> On Tuesday 20 June 2006 00:12, David Brownell wrote:
> > > > > > An alternative (but post-boot) workaround _should_ be
> > > > > >
> > > > > > echo disabled > /sys/bus/pci/devices/0000:00:02.0/power/wakeup
> > > >
> > > > Did that work?
> > >
> > > No. But
> > >
> > > echo -n disabled >
> > > /sys/devices/pci0000:00/0000:00:02.0/usb1/power/wakeup
> >
> > That's what I meant ... thanks, and sorry for the confusion.
>
> this does not work anymore in current rc5. After writing
> cat /sys/devices/pci0000:00/0000:00:02.0/usb1/power/wakeup shows "disabled"
> but messages continue to be logged.
>
> Anything I can do to help narrow it down?
Undoubtedly this change in behavior is caused by the "autostop" code I
added to ohci-hcd. It doesn't check the "wakeup" attribute.
Dave, is there any clue about exactly what triggers the immediate wakeup?
If you could tell me what to test for, I could try writing a patch to fix
it. Perhaps the driver needs a "resume_detect_is_broken" quirk.
Andrey, if you aren't using USB at all (you mentioned that no devices were
plugged in), you can simply do "rmmod ohci-hcd" to stop all those log
messages.
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/
Powered by blists - more mailing lists