public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Matt Mackall <mpm@selenic.com>
Cc: 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 01:19:58 -0300	[thread overview]
Message-ID: <20070523041958.GA15952@khazad-dum.debian.net> (raw)
In-Reply-To: <20070523014825.GX11115@waste.org>

On Tue, 22 May 2007, Matt Mackall wrote:
> 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.

That means something, but not that much.  The kernel could have been doing
broken things for two years in ACPI that happened to not trigger a bug in
someone's firmware, for example.  And when the kernel was fixed (to, e.g.,
do it right by the spec or unbreak other firmwares that did it by the spec)
and that triggered the bug.

We really need to find the cause of the regression to know.

> Breaking working systems, either software or hardware, is a bad idea.

We shouldn't do it for frivoulous reasons, of course.

> I shouldn't have to upgrade my BIOS to work with a new kernel any more
> than I should have to upgrade my browser.

We don't agree there, as you are not talking about a stable kernel series.

And btw, unless you hunt down someone that also has the bug and uses an
up-to-date BIOS (or something else to give an extra data point that discards
a possible firmware bug in your version of the BIOS), or bissect to pinpoint
what caused the regression, this thread will go nowhere.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2007-05-23  4:20 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 [this message]
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
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=20070523041958.GA15952@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=akpm@linux-foundation.org \
    --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