From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de, rjw@sisk.pl
Subject: Re: [BISECTED] Suspend regression in v2.6.31 with Lenovo 3000 v200
Date: Tue, 22 Jun 2010 19:53:08 +0300 [thread overview]
Message-ID: <4C20EA74.6090109@pardus.org.tr> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1006221039530.1631-100000@iolanthe.rowland.org>
Alan Stern wrote:
> Okay, the bus is usb2, the device attached to port 5 is a USB camera,
> and it uses the Ali m5602 driver. I have seen similar reports before,
> but they involved a webcam using the uvcvideo driver.
>
> Anyway, the problem is that the camera sends a wakeup request, which
> causes the suspend to be aborted. I can't imagine why a camera would
> want to send a wakeup request -- probably it's a bug in the firmware.
> You can work around it by manually (or in a udev script) disabling
> wakeup on the camera:
>
> echo disabled >/sys/bus/usb/devices/2-5/power/wakeup
>
> Or you can back-port the patch that fixed the problem, commit
> 7aba8d014341341590ecb64050b7a026642a62eb (USB: don't enable remote
> wakeup by default).
>
> Alan Stern
Thank you very much for your help but it seems that core/hub.c in 2.6.31.13
doesn't even include device_set_wakeup_enable() call that the commit you've
mentioned removes. There are 2 calls in core/hcd.c and 1 in core/hcd-pci.c
which at a quick glance still exists in the current master.
Should I disable the the remote wakeup in somewhere else or does that commit
doesn't really fix the issue?
Regards,
Ozan Caglayan
next prev parent reply other threads:[~2010-06-22 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 7:22 [BISECTED] Suspend regression in v2.6.31 with Lenovo 3000 v200 Ozan Çağlayan
2010-06-21 10:31 ` Ozan Çağlayan
2010-06-21 16:25 ` Alan Stern
2010-06-22 9:09 ` Ozan Çağlayan
2010-06-22 14:49 ` Alan Stern
2010-06-22 16:53 ` Ozan Çağlayan [this message]
2010-06-22 17:47 ` Alan Stern
2010-06-24 7:01 ` Ozan Çağlayan
2010-06-24 14:10 ` Alan Stern
2010-06-24 15:40 ` Ozan Çağlayan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C20EA74.6090109@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox