Re: s2ram slow (radeon) / failing (usb)

Previous thread: Tracing of power:power_start events doesn't work by Ronny Tschüter on Monday, May 3, 2010 - 6:19 am. (12 messages)

Next thread: PPC: Problems at early stage after starting from U-Boot by Dunda, Matthias on Monday, May 3, 2010 - 7:51 am. (1 message)
From: Alan Stern
Date: Monday, May 3, 2010 - 6:57 am

Did you boot with "no_console_suspend"?  Are you using a VT console
instead of X (a serial console may or may not work as well)?

You might also want to #define VERBOSE_DEBUG at the start of 
drivers/usb/core/driver.c, before the first #include.

Alan Stern

--

From: Bruno Prémont
Date: Monday, May 3, 2010 - 7:48 am

Yes, I'm booting with no_console_suspend and console=ttyS0. On that
system there is no X. Multiple ttys are showing up on display with
KMS or VGA text mode (just the getty, all kernel and init output goes to
serial console as expected)

As noted in first e-mail, I disabled SERIAL_8250_PNP as that one

--

From: Bruno Prémont
Date: Monday, May 3, 2010 - 12:46 pm

Still no difference... (will retry with own printk's in ohci's suspend
code as suggested in other mail)

Suspend output as it goes:
[  240.799757] PM: Syncing filesystems ... done.
[  240.836295] PM: Preparing system for mem sleep
[  240.841226] PM: Adding info for No Bus:vcs63
[  240.841295] PM: Adding info for No Bus:vcsa63
[  240.856296] Freezing user space processes ... (elapsed 0.02 seconds) done.
[  240.885352] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[  240.912898] PM: Entering mem sleep
[  240.916676] pci 0000:00:00.0: preparing suspend
[  240.921565] pci 0000:00:00.0: __pm_runtime_resume()!
[  240.922690] pci 0000:00:00.0: __pm_runtime_resume() returns -11!
[  240.933301] pci 0000:00:01.0: preparing suspend
[  240.938169] pci 0000:00:01.0: __pm_runtime_resume()!
[  240.943294] pci 0000:00:01.0: __pm_runtime_resume() returns -11!
[  240.949932] pcieport 0000:00:04.0: preparing suspend
[  240.955269] pcieport 0000:00:04.0: __pm_runtime_resume()!
[  240.961075] pcieport 0000:00:04.0: __pm_runtime_resume() returns -11!
[  240.967976] pcieport 0000:00:05.0: preparing suspend
[  240.973321] pcieport 0000:00:05.0: __pm_runtime_resume()!
[  240.979144] pcieport 0000:00:05.0: __pm_runtime_resume() returns -11!
[  240.986044] pcieport 0000:00:06.0: preparing suspend
[  240.991390] pcieport 0000:00:06.0: __pm_runtime_resume()!
[  240.996038] pcieport 0000:00:06.0: __pm_runtime_resume() returns -11!
[  241.004046] ahci 0000:00:12.0: preparing suspend
[  241.009011] ahci 0000:00:12.0: __pm_runtime_resume()!
[  241.012784] ahci 0000:00:12.0: __pm_runtime_resume() returns -11!
[  241.020884] ohci_hcd 0000:00:13.0: preparing suspend
[  241.026113] ohci_hcd 0000:00:13.0: __pm_runtime_resume()!
[  241.031739] ohci_hcd 0000:00:13.0: __pm_runtime_resume() returns -11!
[  241.038545] ohci_hcd 0000:00:13.1: preparing suspend
[  241.043779] ohci_hcd 0000:00:13.1: __pm_runtime_resume()!
[  241.049429] ohci_hcd 0000:00:13.1: __pm_runtime_resume() returns -11!
[  ...
Previous thread: Tracing of power:power_start events doesn't work by Ronny Tschüter on Monday, May 3, 2010 - 6:19 am. (12 messages)

Next thread: PPC: Problems at early stage after starting from U-Boot by Dunda, Matthias on Monday, May 3, 2010 - 7:51 am. (1 message)