On Saturday, January 22, 2011, Jeff Chua wrote: > On Sat, Jan 22, 2011 at 1:54 PM, Jeff Chua <jeff.chua.linux@xxxxxxxxx> wrote: > > 2011/1/22 Rafael J. Wysocki <rjw@xxxxxxx>: > >> On Friday, January 21, 2011, Jeff Chua wrote: > >>> 2011/1/21 Rafael J. Wysocki <rjw@xxxxxxx>: > >>> > Thanks, but unfortunately this wasn't conclusive. Please apply the patch below > >>> > instead of the previous one (on top of [1/11] - [11/11]) and collect dmesg > >> So, below is a replacement for [11/11]. Please test it on top of > >> [1/11] - [10/11] (the current Linus' tree already contains [1/11] and [2/11]) > >> and let me know if it works for you (in either case, please attach dmesg > >> output containing a suspend attempt). > >> > >> If it works, I'll remove the diagnostic messages and submit along with the > >> rest of the patchset. > > > > Rafael, > > > > dmesg attached. This time, it worked! > > > > I discovered CONFIG_THINKPAD_ACPI caused suspend-to-disk to hang. I > > need the Thinkpad ACPI to control the fan and bluetooth. It looks like > > the thinkpad acpi is trying acquire locks while suspending. Disabling > > cmos, light, led and hotkeys makes suspend-to-disk works again. > > Here's the dmesg. Thanks! Well, and this: Brought up 4 CPUs 2011-01-22T11:32:56.424328+08:00 boston kernel: Total of 4 processors activated (17023.83 BogoMIPS). 2011-01-22T11:32:56.424329+08:00 boston kernel: PM: Registering ACPI NVS region at bb371000 (528384 bytes) 2011-01-22T11:32:56.424332+08:00 boston kernel: PM: Registering ACPI NVS region at bb668000 (524288 bytes) 2011-01-22T11:32:56.424334+08:00 boston kernel: PM: Registering ACPI NVS region at bb76b000 (49152 bytes) 2011-01-22T11:32:56.424335+08:00 boston kernel: PM: Registering ACPI NVS region at bb77a000 (28672 bytes) 2011-01-22T11:32:56.424337+08:00 boston kernel: PM: Registering ACPI NVS region at bb782000 (36864 bytes) 2011-01-22T11:32:56.424338+08:00 boston kernel: PM: Registering ACPI NVS region at bb78c000 (77824 bytes) 2011-01-22T11:32:56.424339+08:00 boston kernel: NET: Registered protocol family 16 means that my patch [11/11] _and_ the replacement are totally wrong, because you have _multiple_ NVS regions. That really helped, thanks a lot. Rafael _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
