public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ákos Maróy" <akos@maroy.hu>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@suse.de>, USB list <linux-usb@vger.kernel.org>
Subject: Re: pm_op(): usb_dev_suspend+0x0/0x10 returns -2 on USB device 8087:0020
Date: Wed, 24 Feb 2010 23:36:03 +0100	[thread overview]
Message-ID: <4B85A9D3.6060709@maroy.hu> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1002241137030.2436-100000@iolanthe.rowland.org>

Alan,

> You can get more information if you enable CONFIG_USB_DEBUG in your
> kernel configuration.  The most likely explanation is that the suspend
> failed because one of the ports on that root hub issued a wakeup
> request.

I tried, and this is what I seem to be getting now:


Feb 24 23:28:52 tonkachi kernel: [  348.733460] PM: Syncing filesystems ...
Feb 24 23:28:52 tonkachi kernel: [  348.903106] done.
Feb 24 23:28:52 tonkachi kernel: [  348.903123] Freezing user space
processes ... (elapsed 0.00 seconds) done.
Feb 24 23:28:52 tonkachi kernel: [  348.903808] Freezing remaining
freezable tasks ... (elapsed 0.00 seconds) done.
Feb 24 23:28:52 tonkachi kernel: [  348.903952] Suspending console(s)
(use no_console_suspend to debug)
Feb 24 23:28:52 tonkachi kernel: [  348.985903] xhci_hcd 0000:02:00.0:
WARN: short transfer on control ep
Feb 24 23:28:52 tonkachi kernel: [  348.987274] PM: resume devices took
0.060 seconds
Feb 24 23:28:52 tonkachi kernel: [  348.987371] Restarting tasks ...
Feb 24 23:28:52 tonkachi kernel: [  348.988165] done.


though I don't see the pm_op() error log anymore..

would this make sense?

actually, the whole USB susbsystem seems to be very fragile - I plug in
a USB device, and the whole system freezes for about 5 seconds or more.
then the device is registered (for example, a mouse). but I unplug and
re-plug, and the device doesn't work anymore...

or I plug in an external USB DVD drive - but if I unplug it, it is still
listed in lsusb..


Akos


  reply	other threads:[~2010-02-24 22:36 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
2010-02-24 16:40   ` Alan Stern
2010-02-24 22:36     ` Ákos Maróy [this message]
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=4B85A9D3.6060709@maroy.hu \
    --to=akos@maroy.hu \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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