Re: Soft lockup during suspend since ~2.6.36

[Thilo-Alexander Ginkel]

On Sun, Apr 3, 2011 at 08:18, Mike Galbraith <efault@xxxxxx> wrote:
> Adds CC to author of fingered commit.
>
> On Sun, 2011-04-03 at 04:03 +0200, Thilo-Alexander Ginkel wrote:
>> recently, I upgraded my Linux kernel (running on an Intel Core 2 Quad)
>> from 2.6.35 to 2.6.38. Unfortunately, I have been experiencing
>> frequent (but sporadic) freezes during suspend (S3) since then, i.e.,
>> the system became completely unresponsive (even MagicSysRq stopped
>> working) after having spun down the hard disks.
>>
>> I performed a bisect, which pointed out the following commit:
>>
>> bd25f4dd6972755579d0ea50d1a5ace2e9b00d1a is the first bad commit
>> commit bd25f4dd6972755579d0ea50d1a5ace2e9b00d1a

A good night of sleep and some Googling later I am under the
impression that this issue was already supposedly fixed by the
following commit a long time ago:
  http://git.kernel.org/?p=linux/kernel/git/jikos/hid.git;a=commitdiff;h=9c9e54a8df0be48aa359744f412377cc55c3b7d2
  http://permalink.gmane.org/gmane.linux.kernel/1024386

This makes some sense as versions closer to 2.6.36 only lock up
sporadically whereas the original bug locks up reliably. I'll try to
get a backtrace for the sporadic bug, but may only be able to do so
using a tainted kernel as my text console does not survive
suspend/resume without proprietary drivers (and the serial console
also breaks during the relevant suspend phase). I hope, this is
acceptable.

Thanks,
Thilo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/