From owner-freebsd-hackers Sun Jun 25 12:13:37 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA03211 for hackers-outgoing; Sun, 25 Jun 1995 12:13:37 -0700 Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA03204 for ; Sun, 25 Jun 1995 12:13:34 -0700 Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.11/8.6.9) id PAA07494; Sun, 25 Jun 1995 15:12:59 -0400 From: A boy and his worm gear Message-Id: <199506251912.PAA07494@skynet.ctr.columbia.edu> Subject: Re: 2.05R reboot hangs To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Sun, 25 Jun 1995 15:12:54 -0400 (EDT) Cc: hackers@freebsd.org In-Reply-To: <199506251847.LAA01917@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Jun 25, 95 11:47:21 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2552 Sender: hackers-owner@freebsd.org Precedence: bulk Of all the gin joints in all the world, Rodney W. Grimes had to walk into mine and say: [lots of discussion about failed system resets] > This problem has actually been around for a long time (machines that > would not detect a CPU shutdown cycle have always hung during the > reboot). I don't know if I have made the problem worse or better > though with my keyboard reset, as that now seems to hang machines > that did not hang before. Perhaps I should reverse the logic of > the #ifdef and only use the keyboard reset on machines that have > broken cpu shutdown detection. > > Comments? > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Reliable computers for FreeBSD I have a thought. I may be barking up the wrong tree here, and for all I know this could be impossible, but I suppose it wouldn't hurt to ask. I seem to recall reading somewhere that there's a BIOS routine that can be used for rebooting the system. Now, I know using BIOS calls is a no-no without a VM86 interface of some kind, but what I'm wondering is if it's possible to force the system back into real mode just long enough to call the BIOS reboot routine. I've been reluctant to suggest this since I don't know a) how easy it would be to do a 'quick and dirty' switch back to real mode, b) if it's even _possible_ to switch back to real mode this late in the game, c) whether or not the BIOS reset call exists or if it's just a figment of my imagination or d) if it does exist, does it reset the system correctly (i.e. will it cause all hardware to be reset properly). My reasoning is that the BIOS reset function should be reasonably reliable ("It works in DOS" and all that crap). And since we're about to kill the system anyway, maybe it wouldn't be that hard to jam the system back into real mode for the purpose of this one call (we don't necessarily have to be that neat about it since we don't ever intend to return). So, am I nuts, or am I nuts? -Bill -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Bill Paul (212) 854-6020 | System Manager Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Møøse Illuminati: ignore it and be confused, or join it and be confusing! ~~~~~~ "Welcome to All Things BSDish! If it's not BSDish, it's crap!" ~~~~~~~