From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Tino Keitel <tino.keitel+xorg@tikei.de>,
Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel@vger.kernel.org,
"Linux-pm mailing list" <linux-pm@lists.linux-foundation.org>
Subject: Re: Suspend hangs since 2.6.34
Date: Mon, 21 Jun 2010 21:24:08 +0200 [thread overview]
Message-ID: <201006212124.09076.rjw@sisk.pl> (raw)
In-Reply-To: <20100620225601.GA15589@x61.home>
On Monday, June 21, 2010, Tino Keitel wrote:
> Hi,
>
> this nasty bug did not appear after I enabled suspend debugging first,
> but now it did:
>
> 2010-06-20_22:40:31.22927 kern.info: usbcore: deregistering interface driver dvb_usb_vp7045
> 2010-06-20_22:40:31.24960 kern.debug: usb 1-6: __pm_runtime_resume()!
> 2010-06-20_22:40:31.24968 kern.debug: usb 1-6: __pm_runtime_resume() returns 1!
> 2010-06-20_22:40:31.24969 kern.debug: PM: Removing info for No Bus:dvb0.frontend0
> 2010-06-20_22:40:31.24971 kern.debug: PM: Removing info for No Bus:dvb0.net0
> 2010-06-20_22:40:31.24972 kern.debug: PM: Removing info for No Bus:dvb0.demux0
> 2010-06-20_22:40:31.24973 kern.debug: PM: Removing info for No Bus:dvb0.dvr0
> 2010-06-20_22:40:31.24974 kern.info: dvb-usb: Twinhan USB2.0 DVB-T receiver (TwinhanDTV Alpha/MagicBox II) successfully deinitialized and disconnected.
> 2010-06-20_22:40:32.26675 kern.info: PM: Syncing filesystems ... done.
> 2010-06-20_22:40:32.39011 kern.debug: PM: Preparing system for mem sleep
>
> When I killed the suspend script which hung at the echo mem >
> /sys/power/state line, the computer suspended. After wakeup, the kernel
> log lines after the line above look like this:
>
> 2010-06-20_22:49:10.28745 kern.warn: Freezing user space processes ... (elapsed 0.02 seconds) done.
> 2010-06-20_22:49:10.28748 kern.warn: Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
> 2010-06-20_22:49:10.28748 kern.debug: PM: Entering mem sleep
> 2010-06-20_22:49:10.28749 kern.warn: Suspending console(s) (use no_console_suspend to debug)
>
> I also attached the full kernel log since the boot.
Hmm. It looks like a USB problem, then.
Alan, can you have a look at this, please?
Rafael
next prev parent reply other threads:[~2010-06-21 19:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 17:53 Tino Keitel
2010-06-09 23:42 ` Rafael J. Wysocki
2010-06-10 6:05 ` Michael Tokarev
2010-06-10 6:07 ` Tino Keitel
2010-06-10 15:41 ` Rafael J. Wysocki
2010-06-10 21:14 ` Bill Davidsen
2010-06-13 11:00 ` Rafael J. Wysocki
2010-06-20 22:56 ` Tino Keitel
2010-06-21 19:24 ` Rafael J. Wysocki [this message]
2010-06-21 21:32 ` Tino Keitel
2010-06-21 22:27 ` Tino Keitel
2010-06-21 22:31 ` Alan Stern
2010-06-23 20:32 ` Tino Keitel
2010-06-23 21:22 ` Rafael J. Wysocki
2010-06-14 14:42 ` Maciej Rutecki
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=201006212124.09076.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stern@rowland.harvard.edu \
--cc=tino.keitel+xorg@tikei.de \
/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
Powered by JetHome