mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: poweroff problem
Date: 06 Apr 2003 19:26:19 +0100	[thread overview]
Message-ID: <1049653578.1600.2.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <3E906FF5.202@gmx.net>

On Sul, 2003-04-06 at 19:20, Carl-Daniel Hailfinger wrote:
> > I can't find any specific A7V workarounds in 2.5.66 ACPI code, so I guess
> > the ACPI code in 2.4 isn't up-to-date.
> > 
> > The original poster's problem is then probably indeed related to a buggy BIOS
> > if it doesn't even powerdown with APM.
> 
> The original poster said his kernel was 2.4.2-2, which looks like a 
> RedHat one and could have contained ACPI...

No Red Hat production kernel so far contains ACPI. As the reliability improves
and the quality of BIOS ACPI code rises that may change.

2.4.2 is also obsolete, and about five erratas back including security
ones.


  reply	other threads:[~2003-04-06 19:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-05  6:08 Anant Aneja
2003-04-05 16:47 ` Alan Cox
2003-04-05 18:31   ` Michael Buesch
2003-04-05 18:41 ` Willy Tarreau
2003-04-05 19:44 ` James Watkins-Harvey
2003-04-06 13:33 ` Stephen Rothwell
2003-04-06 13:58   ` Udo A. Steinberg
2003-04-06 14:27     ` Stephen Rothwell
2003-04-06 15:46       ` Udo A. Steinberg
2003-04-06 14:24         ` Alan Cox
2003-04-06 16:37           ` Udo A. Steinberg
2003-04-06 15:14             ` Alan Cox
2003-04-06 18:04               ` Udo A. Steinberg
2003-04-06 18:20                 ` Carl-Daniel Hailfinger
2003-04-06 18:26                   ` Alan Cox [this message]
2003-04-06 16:37             ` Petr Vandrovec

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=1049653578.1600.2.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=c-d.hailfinger.kernel.2003@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=us15@os.inf.tu-dresden.de \
    /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®