mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Éric Brunet" <Eric.Brunet@lps.ens.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: Regression between 2.6.35 and 2.6.38 (freeze at resume)
Date: Wed, 21 Sep 2011 22:49:46 +0200	[thread overview]
Message-ID: <20110921204946.GA4304@lps.ens.fr> (raw)

In-Reply-To: <s5hy5xigjts.wl%tiwai@suse.de>
References: <201109170935.17777.Eric.Brunet@lps.ens.fr> <201109202206.35705.Eric.Brunet@lps.ens.fr> <s5hy5xigjts.wl%tiwai@suse.de>

>> 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.

I did try 3.0.4 and it crashed the same way. I'll try 3.1-rc as you
suggest.

The point is that it worked very well in F14 with 2.6.35 kernels. I was
trying to find out in which kernel exactly the problems began. I couldn't
crash 2.6.36, 2.6.37 and 2.6.38 but, today, 2.6.39-rc1 crashed on me. I
suspect (because there is a small change of behaviour) that the problem
appears in 2.6.38 even though I haven't crashed it yet. Were there some
changes in battery and PM around 2.6.38 ?

Anyway, I start now to compile 3.1.

Thanks,

        Éric Brunet

             reply	other threads:[~2011-09-21 21:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 20:49 Éric Brunet [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-09-17  7:35 Éric Brunet
2011-09-20 20:06 ` Éric Brunet
2011-09-21 12:29   ` Takashi Iwai
     [not found]     ` <20110921200939.5898164EE5@quatramaran.ens.fr>
2011-09-22  5:32       ` Takashi Iwai
2011-09-23  9:37         ` É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=20110921204946.GA4304@lps.ens.fr \
    --to=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®