From owner-freebsd-questions Wed Feb 8 10:11:20 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA13940 for questions-outgoing; Wed, 8 Feb 1995 10:11:20 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA13933 for ; Wed, 8 Feb 1995 10:11:16 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA19319; Wed, 8 Feb 95 11:02:48 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9502081802.AA19319@cs.weber.edu> Subject: Re: reboot under 2.X To: wraith@csd.uwm.edu (Robert Michael Gorichanaz) Date: Wed, 8 Feb 95 11:02:47 MST Cc: questions@FreeBSD.org In-Reply-To: <199502081722.LAA06790@alpha2.csd.uwm.edu> from "Robert Michael Gorichanaz" at Feb 8, 95 11:22:05 am X-Mailer: ELM [version 2.4dev PL52] Sender: questions-owner@FreeBSD.org Precedence: bulk > Is the a more effective method of rebooting the CPU, other than invalidating > the entire address space and causing the chip to have a seizure? Force the processer back to real mode and use the keyboard controller to strobe the reset line. Of course getting back to real mode after you have loaded BSD code and data all over low memory is a critical problem. > Reason I ask is that , for some reason, my dx2-66 VLB system locks up hard > when I try to do a software reboot under 2.x. The OS halts properly (no > fsck errors on start-up), but as soon as it attempts to "cycle" the CPU, I > lock up - keyboard too - and hafta hit the reset switch. You could argue that the hardware does not behave correctly, since only about 5% of all hardware will not reset after "chip seizure". 8-). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.