From owner-freebsd-hackers Mon Jan 9 05:06:41 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id FAA25069 for hackers-outgoing; Mon, 9 Jan 1995 05:06:41 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id FAA25063 for ; Mon, 9 Jan 1995 05:06:33 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA14221; Tue, 10 Jan 1995 00:04:21 +1100 Date: Tue, 10 Jan 1995 00:04:21 +1100 From: Bruce Evans Message-Id: <199501091304.AAA14221@godzilla.zeta.org.au> To: jaitken@csugrad.cs.vt.edu, wollman@halloran-eldar.lcs.mit.edu Subject: Re: Machine state after reboot? Cc: hackers@FreeBSD.org, root@io.cts.com Sender: hackers-owner@FreeBSD.org Precedence: bulk >Quite a lot. The BIOS traps C-A-D and then sends a signal to the >keyboard controller, which uses a spare line on one of its I/O ports >to pull down the hardware reset line, which (depending on the design >of the system) may or may not get propagated to the ISA bus reset >line. Pushing the power button actually kills the power to The standard keyboard reset never resets the ISA bus. It was originally a kludge for switching 80286's back to real mode. Some software depends on switching modes without losing much of the software state, let alone the hardware state, so the behaviour of only resetting the cpu has to be preserved for compatibility. >were, the CPU triple-faults and resets itself. This does not perform >a reset of any of the hardware in the machine, which doing it Actually the cpu triple-faults and shuts down. "Compatible" motherboards detect the shutdown and turn it into a reset. >``properly'' might or might not do. Unfortunately, the keyboard >controller hack doesn't work on all machines (although it is supposed >to), and so WFJ (yes, this is his doing) went this route instead. I think it does work on all machines, but it is tricky to program. Bruce