All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Ákos Maróy" <akos@maroy.hu>
Cc: linux-kernel@vger.kernel.org,
	Alan Stern <stern@rowland.harvard.edu>, Greg KH <gregkh@suse.de>,
	linux-usb@vger.kernel.org
Subject: Re: pm_op(): usb_dev_suspend+0x0/0x10 returns -2 on USB device 8087:0020
Date: Tue, 23 Feb 2010 22:17:19 +0100	[thread overview]
Message-ID: <201002232217.19201.rjw@sisk.pl> (raw)
In-Reply-To: <4B839202.8090008@maroy.hu>

On Tuesday 23 February 2010, Ákos Maróy wrote:
> Hi,
> 
> I wonder if this is the write place to post this issue to, but I have a
> proplem when trying go suspend or hibernate my system. after enabling
> pm_trace by:
> 
> echo 1 > /sys/power/pm_trace
> 
> and then issuing pm-suspend, I get the following in dmesg:
> 
> [  685.833275] PM: Entering mem sleep
> [  685.833292] Suspending console(s) (use no_console_suspend to debug)
> [  685.993399] pm_op(): usb_dev_suspend+0x0/0x10 returns -2
> [  685.993404] PM: Device usb2 failed to suspend: error -2
> [  685.993408] PM: Some devices failed to suspend
> [  685.997009] PM: resume devices took 0.000 seconds
> [  685.997169] PM: Finishing wakeup.
> 
> this is on 2.6.32.8, but on 2.6.33-rc8 I get the same results.
> 
> trying to find out what device this is:
> 
> $ lsusb
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 003: ID 0bda:0159 Realtek Semiconductor Corp.
> Bus 001 Device 004: ID 04f2:b16c Chicony Electronics Co., Ltd
> Bus 001 Device 005: ID 03f0:231d Hewlett-Packard
> Bus 001 Device 002: ID 8087:0020
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 
> my persumption is that "Device usb2" would be device 002 on bus 001
> above, that is, 8087:0020. googling for this USB id I found some
> references here: http://forum.notebookreview.com/showthread.php?p=5906076 :
> 
> Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
> 
> 
> I wonder what could be done to make this device not sabotage the suspend
> process?

That's a good question for the USB people (CCed).

Rafael

  reply	other threads:[~2010-02-23 21:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-23  8:29 pm_op(): usb_dev_suspend+0x0/0x10 returns -2 on USB device 8087:0020 Ákos Maróy
2010-02-23 21:17 ` Rafael J. Wysocki [this message]
2010-02-24 16:40   ` Alan Stern
2010-02-24 22:36     ` Ákos Maróy
2010-02-25 15:27       ` Alan Stern
2010-02-25 16:43         ` Ákos Maróy
2010-02-25 17:46           ` Alan Stern
2010-02-25 19:04             ` Sarah Sharp
2010-02-25 19:36               ` Alan Stern
2010-02-25 19:52                 ` Sarah Sharp
2010-02-25 22:37                   ` Ákos Maróy
2010-02-26  0:16                     ` Sarah Sharp
2010-02-26 16:12                       ` Alan Stern
2010-02-26 16:32                         ` Sarah Sharp
2010-02-27  8:02                       ` Ákos Maróy
2010-03-02  0:48                         ` Sarah Sharp
2010-02-25 21:05             ` Ákos Maróy
2010-02-25 22:23               ` Alan Stern
2010-02-25 17:07         ` Ákos Maróy
2010-03-04 13:55         ` Ákos Maróy
2010-02-26  5:21       ` Edward Shao
2010-02-27  8:03         ` Ákos Maróy

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=201002232217.19201.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akos@maroy.hu \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.