From: Jiri Slaby <jirislaby@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: suspend (uhci_hcd) defunct in mmotm 2008-09-13-03-09
Date: Wed, 24 Sep 2008 18:04:12 +0200 [thread overview]
Message-ID: <48DA64FC.4020706@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0809241047500.2650-100000@iolanthe.rowland.org>
On 09/24/2008 04:49 PM, Alan Stern wrote:
> On Wed, 24 Sep 2008, Jiri Slaby wrote:
>
>>>> pm_op(): pci_pm_suspend+0x0/0xd0 returns -16
>>>> PM: Device 0000:00:1d.0 failed to suspend: error -16
>>>> PM: Some devices failed to suspend
>>> The reason for this error is that the root hub wasn't already
>>> suspended. Was there a USB device plugged into that controller?
>> No:
>
>>> If you still run into problems, post more of the dmesg log (with
>>> CONFIG_USB_DEBUG enabled, of course!).
>> Hm, it doesn't work. 2 dmesgs from mmotm 2008-09-10-19-39 (without usb debug)
>> [ok] and -rc6+gkh-all (with usb debug) [fail]:
>> http://decibel.fi.muni.cz/~xslaby/dmesg_fail.hcd
>> http://decibel.fi.muni.cz/~xslaby/dmesg_ok.hcd
>
> In fact neither of those logs includes USB debugging messages. Maybe
> you omitted a mkinitrd step.
I don't think so. I don't use neither vanilla nor initrd so this must be the
kernel. Anyway I recompiled with .config linked in and did
# dmesg >dmesg_config.hcd
# zcat /proc/config.gz >>dmesg_config.hcd
in the built kernel. The file is here:
http://decibel.fi.muni.cz/~xslaby/dmesg_config.hcd
next prev parent reply other threads:[~2008-09-24 16:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 14:00 hda_intel (sigmatel) defunct in mmotm 2008-09-13-03-09 Jiri Slaby
2008-09-15 14:16 ` Matthew Ranostay
2008-09-15 14:16 ` Matthew Ranostay
2008-09-16 14:43 ` Matthew Ranostay
2008-09-17 8:58 ` Jiri Slaby
2008-09-17 14:09 ` Matthew Ranostay
2008-09-24 9:42 ` Jiri Slaby
2008-09-17 16:46 ` suspend (uhci_hcd) " Jiri Slaby
2008-09-18 21:14 ` Alan Stern
2008-09-18 21:14 ` Alan Stern
2008-09-24 10:55 ` Jiri Slaby
2008-09-24 14:49 ` Alan Stern
2008-09-24 16:04 ` Jiri Slaby
2008-09-24 16:04 ` Jiri Slaby [this message]
2008-09-24 16:38 ` Alan Stern
2008-09-24 16:38 ` Alan Stern
2008-09-24 18:14 ` Greg KH
2008-09-24 18:14 ` Greg KH
2008-09-24 18:19 ` Jiri Slaby
2008-09-24 18:19 ` Jiri Slaby
2008-09-24 18:54 ` Jiri Slaby
2008-09-24 21:29 ` Alan Stern
2008-09-24 21:29 ` Alan Stern
2008-09-25 20:51 ` Jiri Slaby
2008-09-25 20:51 ` Jiri Slaby
2008-09-25 21:07 ` [PATCH] PM: use pm_op methods for device types Alan Stern
2008-09-25 21:27 ` Rafael J. Wysocki
2008-09-25 21:27 ` Rafael J. Wysocki
2008-09-25 22:06 ` Greg KH
2008-09-26 13:56 ` Alan Stern
2008-09-26 17:59 ` Greg KH
2008-09-26 17:59 ` Greg KH
2008-10-06 15:11 ` Pavel Machek
2008-10-06 15:11 ` Pavel Machek
2008-09-26 13:56 ` Alan Stern
2008-09-25 22:06 ` Greg KH
2008-09-25 21:07 ` Alan Stern
2008-09-24 18:54 ` suspend (uhci_hcd) defunct in mmotm 2008-09-13-03-09 Jiri Slaby
2008-09-24 14:49 ` Alan Stern
2008-09-24 10:55 ` Jiri Slaby
2008-09-17 16:46 ` Jiri Slaby
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=48DA64FC.4020706@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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.