http://bugzilla.kernel.org/show_bug.cgi?id=13903 Summary: Hibernation failure on dual core Athlon 64 (64-bit) Product: Power Management Version: 2.5 Kernel Version: 2.6.31-rc2 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: cpufreq AssignedTo: cpufreq@xxxxxxxxxxxxxxx ReportedBy: rjw@xxxxxxx Blocks: 7216,13615 Regression: Yes Created an attachment (id=22595) --> (http://bugzilla.kernel.org/attachment.cgi?id=22595) dmesg output from the affected machine My test machine based on Athlon 64 X2 3800+ and a NVidia chipset suffers from hibernation regression where the second attempt to hibernate in a row hangs it right before the creation of the image. Since the issue is 100% reproducible, I was able to bisect it and that turned up the following commit: commit 3f4a782b5ce2698b1870b5a7b573cd721d4fce33 Author: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx> Date: Fri Jul 3 11:25:16 2009 -0400 [CPUFREQ] fix (utter) cpufreq_add_dev mess OK, I've tried to clean it up the best I could, but please test this with concurrent cpu hotplug and cpufreq add/remove in loops. I'm sure we will make other interesting findings. This is step one of fixing the overall locking dependency mess in cpufreq. Signed-off-by: Dave Jones <davej@xxxxxxxxxx> First-Bad-Commit : 3f4a782b5ce2698b1870b5a7b573cd721d4fce33 -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
