From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: poweroff problem
Date: 06 Apr 2003 16:14:42 +0100 [thread overview]
Message-ID: <1049642082.1218.3.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030406183713.3435d742.us15@os.inf.tu-dresden.de>
On Sul, 2003-04-06 at 17:37, Udo A. Steinberg wrote:
> On 06 Apr 2003 15:24:55 +0100 Alan Cox (AC) wrote:
>
> AC> We rely on the bios for the power off sequences. Many BIOS vendors do
> AC> set it up to share the bios code it seems
>
> Ok, but this does not explain why things work with 2.5.66 on the exact same
> machine, unless 2.5 had workarounds for BIOS bugs or didn't use the BIOS for
> power off. Board is an Asus A7V, BIOS version 1011.
Different options for reboot (16 v 32) perhaps, might even be something is
random as which way the carry flag is when the bios code is called. If you
want to be sure for the APM case stick a printk just before we drop into
the BIOS and make sure we oops after and not before..
next prev parent reply other threads:[~2003-04-06 16:01 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 [this message]
2003-04-06 18:04 ` Udo A. Steinberg
2003-04-06 18:20 ` Carl-Daniel Hailfinger
2003-04-06 18:26 ` Alan Cox
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=1049642082.1218.3.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--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®