[lkml]   [2011]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Regression between 2.6.35 and 2.6.38 (freeze at resume)
At Tue, 20 Sep 2011 22:06:35 +0200,
Éric Brunet wrote:
> I reported a bug three days ago about my computer occasionaly not waking up
> (see below) and I have since compiled several kernels to see when the bug
> arrived.
> Till now, I have seen the bug trigger on a vanilla 2.6.39-rc3. (Only once, in
> about ten suspend/resume) and I haven't seen it trigger in 2.6.38 nor 2.6.39-
> rc1. I am now running 2.6.39-rc1 to see if the bug will eventualy trigger or
> not.
> The WARNING with call trace on the fedora kernel that I reported in my
> previous message (see below) also happened in the vanilla kernel in exactly
> the same way. After that initial WARNING, I had four more WARNINGS and one BUG
> in rapid succession, and one final BUG 14 seconds later.
> I'd like to know what I can do to help nail this annoying bug. I am not sure
> if I can git bisect it; it is hard to tell offhand if a kernel is good; it may
> resume correctly many times before crashing.

Did you try the recent 3.1-rc? There have been a few commits relevant
with battery module and PM after 3.0, and I guess this will be the fix
for your case, too.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2011-09-21 14:31    [W:0.055 / U:34.292 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site