Bug#677472: [3.1->3.2 regression] Immediate wake on suspend, associated with OHCI on MCP51
- To: Octavio Alvarez <alvarezp@alvarezp.com>
- Cc: Lan Tianyu <tianyu.lan@intel.com>, Frank Schäfer <fschaefer.oss@googlemail.com>, Lan Tianyu <lantianyu1986@gmail.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, <677472@bugs.debian.org>, Ben Hutchings <ben@decadent.org.uk>, <linux-usb@vger.kernel.org>, Frank Schäfer <schaefer.frank@gmx.net>
- Subject: Bug#677472: [3.1->3.2 regression] Immediate wake on suspend, associated with OHCI on MCP51
- From: Alan Stern <stern@rowland.harvard.edu>
- Date: Wed, 19 Dec 2012 13:19:00 -0500 (EST)
- Message-id: <[🔎] Pine.LNX.4.44L0.1212191314390.1580-100000@iolanthe.rowland.org>
- Reply-to: Alan Stern <stern@rowland.harvard.edu>, 677472@bugs.debian.org
- In-reply-to: <[🔎] op.wpkpriue6g6bxc@alvarezp-samsung>
On Wed, 19 Dec 2012, Octavio Alvarez wrote:
> On Wed, 19 Dec 2012 08:57:00 -0800, Alan Stern <stern@rowland.harvard.edu>
> wrote:
>
> > You, the stupid end-user, would not see this message at all under
> > normal circumstances. It uses the ohci_dbg macro and therefore will
> > not appear unless your kernel is built with CONFIG_USB_DEBUG enabled.
>
> Shouldn't it be exposed to dmesg?
None of the other quirk messages are. On the other hand, they don't
affect the behavior as much as this quirk does.
Still, if we do produce a message about it, I don't feel it is
necessary to try and explain the whole situation. Something as simple
as "Buggy wakeup support, disabling" should be enough for an end-user
who wants to know why typing on the USB keyboard doesn't wake up a
suspended system.
Alan Stern
Reply to: