lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 29 Nov 2009 11:12:13 +0100 From: Ferenc Wagner <wferi@...f.hu> To: "Rafael J. Wysocki" <rjw@...k.pl> Cc: linux-pm@...ts.linux-foundation.org, Andrew Morton <akpm@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org>, linux-netdev@...r.kernel.org Subject: Re: [linux-pm] intermittent suspend problem again "Rafael J. Wysocki" <rjw@...k.pl> writes: > On Saturday 28 November 2009, Ferenc Wagner wrote: >> "Rafael J. Wysocki" <rjw@...k.pl> writes: >> >>> On Wednesday 18 November 2009, Ferenc Wagner wrote: >>> >>>> Ferenc Wagner <wferi@...f.hu> writes: >>>> >>>>> Since I've instrumented s2disk and the hibernation path, no freeze >>>>> happened during hibernating the machine. >>>> >>>> Not until I removed the delays from hibernation_platform_enter(), which >>>> were put there previously to get step-by-step feedback. Removing them >>>> again resulted in a freeze in short course, maybe just two hibernations >>>> later. The instrumentation shows it stuck in dpm_suspend_start(PMSG_HIBERNATE). >>>> Does it mean that some device driver is at fault? >>> >>> A driver or one of the platform hooks. >>> >>>> I'll check if it always fails at the same point (although tracing into >>>> dpm_suspend_start isn't pure fun because of the multitude of devices it >>>> loops over). Is there any way to get printk output from that phase? >>> >>> Compile with CONFIG_PM_VERBOSE (it does mean exactly that). >> >> The last message now was: >> >> e100: 0000:02:08.0: hibernate, may wakeup >> >> Looks like hibernating the e100 driver is unstable. > > Can you verify that by trying to hibernate without the e100 driver? Not really, as I still can't reliable reproduce the issue. Since I'm running with suspend loglevel = 8, it's happened only twice (in a row), with seemingly exact same console output. Some earlier freezes also happened in dpm_suspend_start, at least. However, I can certainly add e100 to SUSPEND_MODULES under /etc/pm/config.d, and continue running with that. Or I can try stress-testing the module, but not sure, how. Interestingly, git log v2.6.31.. -- e100.c is tiny, but 8fbd962e affects the suspend/resume routines through e100_up. This could explain the timing-sensitive nature of the issue. I took the liberty to change the Cc list, maybe linux-netdev can lend us a hand. -- Regards, Feri. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists