http://bugzilla.kernel.org/show_bug.cgi?id=9169
------- Comment #10 from [EMAIL PROTECTED] 2008-01-09 03:27 ------- Reply-To: [EMAIL PROTECTED] Sent by mail, I hope it will appear on http://bugzilla.kernel.org/show_bug.cgi?id=9169 first of all sorry for not answering via bugzilla, but I am off-line now and I d not know how to use bugzilla via mail. When back to work I will be swamped by real life, so I have used this bit of time to test your patches from http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.24-rc6/patches/ The behaviour of the laptop is quite complex, so I will explain what happened step by step. I have PM debug on, so I will attach the kernel messages of every step. I compiled the kernel with the attached config. After boot, the fan works ok (It goes off when temp is under 49 C, goes on quietly betwenn 52 and somewhere around 70, goes on top speed over that. Temperature will top around 75 C with all two cores at 100% compiling kernels). I hibernated the computer with "shutdown" method. What happened on resume is that the fan stayed everytime on at a quiet level; my suspect is that it is sort-of congealed at the status it had at the moment of hibernation. See syslog-*-shutdown.txt.gz attached. After that, I started again hibernation in platform mode (without rebooting before; I will try next with a reboot and a fresh platform hibernation). Nothing changed. (syslog-*-platform-*). After that, I did a suspend-to-ram cycle (syslog-*-suspend*) and on resume, the fan went off and stayed off, even when temperature reached 80 C. Notice that if I just use suspend to ram from a fresh reboot the fans work perfectly. The behaviour does not change if I use only "platform" hibernate method. The log of this hibrnation cycle after a fresh reboot is in the file syslog-rc6-test-rafael-only-platform.txt.gz. Notice that there is a warning from lockdep: hibernate.sh/7392 is trying to acquire lock: [ 1459.153489] (events){--..}, at: [cleanup_workqueue_thread+16/112] cleanup_workqueue_thread+0x10/0x70 [ 1459.153499] [ 1459.153500] but task is already holding lock: [ 1459.153502] (workqueue_mutex){--..}, at: [workqueue_cpu_callback+235/320] workqueue_cpu_callback+0xeb/0x140 [ 1459.153507] [ 1459.153508] which lock already depends on the new lock. but I do not know if it's relevant. Resuming, on this laptop hibernation is a very dangerous thing to do :-). Thanks again, Romano -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
