Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 8 Jan 2002 15:50:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 8 Jan 2002 15:50:16 -0500 Received: from chaos.analogic.com ([204.178.40.224]:30848 "EHLO chaos.analogic.com") by vger.kernel.org with ESMTP id ; Tue, 8 Jan 2002 15:50:10 -0500 Date: Tue, 8 Jan 2002 15:51:24 -0500 (EST) From: "Richard B. Johnson" Reply-To: root@chaos.analogic.com To: Mike Castle cc: Linux Kernel Subject: Re: PROBLEM: "shutdown -r now" (lilo, win98) (fwd) In-Reply-To: <20020108202358.GO22948@thune.mrc-home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 8 Jan 2002, Mike Castle wrote: > On Tue, Jan 08, 2002 at 08:15:07PM +0000, Alan Cox wrote: > > Some windows driver is assuming things that the BIOS has not cleared up > > on reset and whichit probably shouldn't. Its not uncommon to have to > > powercycle a box between OS's. Sometimes you see it with windows hanging > > sometimes with Linux > > I thought that Linux forced a cold-restart upon a reboot to solve this very > issue. At least wrt the BIOS. > > Perhaps a physical component needs that power cycle to do a reset? > You can force a processor-reset in the simplist way, with an Intel paged executive.... make a module that has open() only. Call it a character device with some unused major number. Make a 'device', /dev/reboot with that major number. Install it. When you want to re-boot, execute cat