mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.de>
To: linux-pm@lists.linux-foundation.org
Cc: "Bruno Prémont" <bonbons@linux-vserver.org>,
	"Jiri Kosina" <jkosina@suse.cz>,
	USB@smtp1.linux-foundation.org, list <linux-usb@vger.kernel.org>,
	"Kernel development list" <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] s2ram slow (radeon) / failing (usb)
Date: Tue, 4 May 2010 08:42:35 +0200	[thread overview]
Message-ID: <201005040842.35260.oneukum@suse.de> (raw)
In-Reply-To: <20100503231154.486c27d6@neptune.home>

Am Montag, 3. Mai 2010 23:11:54 schrieb Bruno Prémont:
> [  477.543304] usb 1-2.1: usb_autosuspend_device: cnt 1 -> 0
> [  477.543316] usbhid 1-2.1:1.1: __pm_runtime_suspend()!
> [  477.543326] usbhid 1-2.1:1.1: __pm_runtime_suspend() returns 0!
> [  477.543380] usbcore: registered new interface driver usbhid
> [  477.549457] usbhid: USB HID core driver
> 
> And suspend is freezing inside of hid_cancel_delayed_stuff(usbhid) call
> from hid_suspend() in drivers/hid/usbhid/hid-core.c ...
> 
> Is it worth continuing iteration and adding further printk's down there?
> Jiri, what's your opinion on this?

Ugh. That looks like a bug in usbhid that I introduced. A fix is not trivial.
In short, I did not think the device could be undergoing a queued resumption
while suspend() is being called. I wonder why this is happening.

	Regards
		Oliver

  reply	other threads:[~2010-05-04  6:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-02 13:56 Bruno Prémont
2010-05-02 15:07 ` Alan Stern
2010-05-02 20:06   ` Bruno Prémont
2010-05-02 20:16     ` Rafael J. Wysocki
2010-05-02 20:56       ` Bruno Prémont
2010-05-02 22:04       ` Alan Stern
2010-05-02 21:59     ` Alan Stern
2010-05-03  6:34       ` Bruno Prémont
2010-05-03 13:57         ` Alan Stern
2010-05-03 14:48           ` Bruno Prémont
2010-05-03 15:04             ` Alan Stern
2010-05-03 19:23               ` Bruno Prémont
2010-05-03 19:39                 ` Alan Stern
2010-05-03 19:46           ` Bruno Prémont
2010-05-03 20:11             ` Alan Stern
2010-05-03 20:57               ` Bruno Prémont
2010-05-03 21:11                 ` Bruno Prémont
2010-05-04  6:42                   ` Oliver Neukum [this message]
2010-05-04  8:37                     ` [linux-pm] " Jiri Kosina
2010-05-04 21:04                       ` Bruno Prémont
2010-05-05 12:58                         ` Jiri Kosina
2010-05-05 19:17                           ` Bruno Prémont
2010-05-05 20:30                       ` Bruno Prémont
2010-05-05 20:53                         ` Bruno Prémont
2010-05-05 20:55                           ` Jiri Kosina
2010-05-05 21:35                             ` Alan Stern
2010-05-06 17:47                               ` Bruno Prémont
2010-05-06 18:40                                 ` Alan Stern
2010-05-06 20:59                                   ` Bruno Prémont
2010-05-07  8:29                                   ` Jiri Kosina
2010-05-07 21:18 ` s2ram slow resume - radeon versus no_console_suspend? Bruno Prémont

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=201005040842.35260.oneukum@suse.de \
    --to=oneukum@suse.de \
    --cc=USB@smtp1.linux-foundation.org \
    --cc=bonbons@linux-vserver.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux-usb@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®