Re: Suspend hangs since 2.6.34

[Rafael J. Wysocki]

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/