[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48DA64FC.4020706@gmail.com>
Date: Wed, 24 Sep 2008 18:04:12 +0200
From: Jiri Slaby <jirislaby@...il.com>
To: Alan Stern <stern@...land.harvard.edu>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux-pm mailing list <linux-pm@...ts.linux-foundation.org>,
USB list <linux-usb@...r.kernel.org>
Subject: Re: suspend (uhci_hcd) defunct in mmotm 2008-09-13-03-09
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists