From: Gabriel Paubert <paubert@iram.es>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Jamie Lokier <jamie@shareable.org>, Andi Kleen <ak@suse.de>,
joe briggs <jbriggs@briggsmedia.com>,
linux-kernel@vger.kernel.org
Subject: Re: software reset
Date: Wed, 30 Apr 2003 18:15:25 +0200 [thread overview]
Message-ID: <20030430161525.GA3834@iram.es> (raw)
In-Reply-To: <m1llxsfdpg.fsf@frodo.biederman.org>
On Wed, Apr 30, 2003 at 05:04:59AM -0600, Eric W. Biederman wrote:
>
> And as an interesting data point all a triple fault does on a modern
> system is to put the cpu in a weird stopped state. Some hardware
> usually the southbridge then detects this and if properly configured
> will trigger the reset line.
>
> I believe this may actually go back into history as far as the 486 but
> I have not done the researched to see how far back this behavior goes.
Try 286. It was the fastest (actually only) way to make a 286 switch back
from protected to real mode.
Gabriel
next prev parent reply other threads:[~2003-04-30 16:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200304291037.13598.jbriggs@briggsmedia.com.suse.lists.linux.kernel>
2003-04-29 15:19 ` software reset Andi Kleen
2003-04-30 7:50 ` Jamie Lokier
2003-04-30 11:04 ` Eric W. Biederman
2003-04-30 16:15 ` Gabriel Paubert [this message]
2003-04-30 17:02 ` Eric W. Biederman
2003-04-30 17:19 ` Gabriel Paubert
2003-04-30 19:31 ` Jamie Lokier
2003-04-30 23:00 ` Rafael Santos
2003-04-30 23:14 ` Andi Kleen
2003-04-30 23:20 ` H. Peter Anvin
2003-05-07 6:55 Perez-Gonzalez, Inaky
-- strict thread matches above, loose matches on Subject: below --
2003-04-29 14:37 joe briggs
2003-04-30 23:12 ` James Stevenson
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=20030430161525.GA3834@iram.es \
--to=paubert@iram.es \
--cc=ak@suse.de \
--cc=ebiederm@xmission.com \
--cc=jamie@shareable.org \
--cc=jbriggs@briggsmedia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.