From: Takashi Iwai <tiwai@suse.de>
To: "Éric Brunet" <Eric.Brunet@lps.ens.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Regression between 2.6.35 and 2.6.38 (freeze at resume)
Date: Wed, 21 Sep 2011 14:29:19 +0200 [thread overview]
Message-ID: <s5hy5xigjts.wl%tiwai@suse.de> (raw)
In-Reply-To: <201109202206.35705.Eric.Brunet@lps.ens.fr>
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.
Takashi
next prev parent reply other threads:[~2011-09-21 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 7:35 Éric Brunet
2011-09-20 20:06 ` Éric Brunet
2011-09-21 12:29 ` Takashi Iwai [this message]
[not found] ` <20110921200939.5898164EE5@quatramaran.ens.fr>
2011-09-22 5:32 ` Takashi Iwai
2011-09-23 9:37 ` Éric Brunet
2011-09-21 20:49 Éric Brunet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hy5xigjts.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Eric.Brunet@lps.ens.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®