From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Matt Mackall <mpm@selenic.com>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: 2.6.21-mm2: ACPI exception on resume
Date: Wed, 23 May 2007 10:57:47 +0200 [thread overview]
Message-ID: <200705231057.48320.rjw@sisk.pl> (raw)
In-Reply-To: <20070523014825.GX11115@waste.org>
On Wednesday, 23 May 2007 03:48, Matt Mackall wrote:
> On Tue, May 22, 2007 at 09:19:43PM -0300, Henrique de Moraes Holschuh wrote:
> > On Tue, 22 May 2007, Matt Mackall wrote:
> > > On Mon, May 21, 2007 at 08:03:49PM -0300, Henrique de Moraes Holschuh wrote:
> > > > On Mon, 21 May 2007, Matt Mackall wrote:
> > > > > BIOS Information
> > > > > Vendor: IBM
> > > > > Version: 1RETDHWW (3.13 )
> > > > > Release Date: 10/29/2004
> > > > >
> > > > > No sign of any EC version in the output.
> > > >
> > > > This is a buggy, ancient version of the BIOS, which probably means you have
> > > > an old and slightly buggy EC firmware. I recommend you to upgrade to BIOS
> > > > 3.21 and EC 3.04. See http://thinkwiki.org/wiki/BIOS_Upgrade for more
> > > > details.
> > >
> > > Really, I'd much prefer my kernel not regress instead. Updating
> > > firmware is just introducing more potential instability and ignoring
> > > the problem.
> >
> > We can't very much know if the kernel is really buggy, then.
>
> Whether the 'bug' is in the firmware or the kernel, it is the kernel
> that has regressed. Suspend worked fine for 2+ years before this.
>
> Breaking working systems, either software or hardware, is a bad idea.
> I shouldn't have to upgrade my BIOS to work with a new kernel any more
> than I should have to upgrade my browser.
While I agree with that, it would really be helpful if you tested the latest -rc
kernel and saw if the bug was present in there.
If the bug is not present in the latest -rc, it'll be possible to identify the
patch that causes it to appear in -mm and find the reason of the breakage.
Greetings,
Rafael
next prev parent reply other threads:[~2007-05-23 8:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 16:57 2.6.21-mm2: ACPI exception on resume Matt Mackall
2007-05-19 18:24 ` Rafael J. Wysocki
2007-05-19 22:40 ` Matt Mackall
2007-05-19 23:05 ` Rafael J. Wysocki
2007-05-19 20:45 ` Henrique de Moraes Holschuh
2007-05-19 22:38 ` Matt Mackall
2007-05-20 3:52 ` Henrique de Moraes Holschuh
2007-05-21 22:23 ` Matt Mackall
2007-05-21 23:03 ` Henrique de Moraes Holschuh
2007-05-22 22:45 ` Matt Mackall
2007-05-23 0:19 ` Henrique de Moraes Holschuh
2007-05-23 1:48 ` Matt Mackall
2007-05-23 4:19 ` Henrique de Moraes Holschuh
2007-05-23 4:41 ` Ray Lee
2007-05-23 12:51 ` Henrique de Moraes Holschuh
2007-05-23 22:50 ` Ray Lee
2007-05-24 0:28 ` Henrique de Moraes Holschuh
2007-05-24 1:37 ` Ray Lee
2007-05-27 21:02 ` Pavel Machek
2007-05-23 8:57 ` Rafael J. Wysocki [this message]
2007-05-23 17:13 ` Henrique de Moraes Holschuh
2007-05-23 17:48 ` Matt Mackall
2007-05-23 20:56 ` Rafael J. Wysocki
2007-05-23 21:15 ` Matt Mackall
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=200705231057.48320.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=hmh@hmh.eng.br \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/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