Hello,
On 19-10-14 05:29, Yinghai Lu wrote:
Please try to "debug ignore_loglevel no_console_suspend".
Same thing. :-(
[ 72.572354] Restarting tasks ... done.
[ 72.576554] PM: calling nb rcu_pm_notify+0x0/0x60
[ 72.581277] PM: ... nb rcu_pm_notify+0x0/0x60 done
[ 72.586115] PM: calling nb cpu_hotplug_pm_callback+0x0/0x50
[ 72.591692] PM: ... nb cpu_hotplug_pm_callback+0x0/0x50 done
[ 72.597345] PM: calling nb fw_pm_notify+0x0/0x150
[ 72.602047] PM: ... nb fw_pm_notify+0x0/0x150 done
[ 72.606839] PM: calling nb bsp_pm_callback+0x0/0x50
[ 72.611711] PM: ... nb bsp_pm_callback+0x0/0x50 done
[ 73.382175] r8169 0000:07:00.0 eth0: link up
[ 78.857526] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 79.025718] ata3.00: configured for UDMA/133
[ 81.379533] ata4: softreset failed (device not ready)
[ 82.623212] PM: Syncing filesystems ... done.
[ 82.661564] PM: Preparing system for mem sleep
[ 82.669405] Freezing user space processes ... (elapsed 0.001 seconds)
done.
[ 82.677729] Freezing remaining freezable tasks ... (elapsed 0.001
seconds) done.
[ 82.686338] PM: Entering mem sleep
And nothing related to resume. :-(
Is there any point of me retrying with the initcall_debug flag but
without your patch?
Looking at your patch again, it seems pretty mad that this would cause
such a big difference. Overnight I remembered how my machine has TSC
issues at the time this bug shows, so I tried setting hpet as the
clocksource. (hpet=force on the cmdline did not seem to have that effect
so I used sysfs instead) No effect either.
I need to go now, can experiment a little more tonight.
Thanks,
Wilmer v/d Gaast.
--
+-------- .''`. - -- ---+ + - -- --- ---- ----- ------+
| wilmer : :' : gaast.net | | OSS Programmer www.bitlbee.org |
| lintux `. `~' debian.org | | Full-time geek wilmer.gaast.net |
+--- -- - ` ---------------+ +------ ----- ---- --- -- - +
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
