From owner-freebsd-questions@FreeBSD.ORG Tue May 27 03:53:32 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B3C437B401 for ; Tue, 27 May 2003 03:53:32 -0700 (PDT) Received: from msr28.hinet.net (msr28.hinet.net [168.95.4.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF64443F93 for ; Tue, 27 May 2003 03:53:30 -0700 (PDT) (envelope-from y2kbug@ms25.hinet.net) Received: from pro.utopia.com (61-227-219-79.HINET-IP.hinet.net [61.227.219.79]) by msr28.hinet.net (8.9.3/8.9.3) with ESMTP id SAA27045 for ; Tue, 27 May 2003 18:54:00 +0800 (CST) Content-Type: text/plain; charset="iso-8859-1" From: Robert Storey To: freebsd-questions@freebsd.org Date: Tue, 27 May 2003 18:53:10 +0800 User-Agent: KMail/1.4.3 References: <200305242016.21540.y2kbug@ms25.hinet.net> <20030524122713.GA29846@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <20030524122713.GA29846@happy-idiot-talk.infracaninophile.co.uk> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200305271853.10173.y2kbug@ms25.hinet.net> Subject: Re: bad kernel fried motherboard??? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 May 2003 10:53:32 -0000 On Saturday 24 May 2003 20:27, Matthew Seaman wrote: > On Sat, May 24, 2003 at 08:16:21PM +0800, Robert Storey wrote: > > My question - is there any possibility that a misconfigured kernel co= uld > > harm the hardware? Or is it just a strange coincidence that "kernel > > panic" was followed by real hardware failure? > It's highly unlikely that booting up a FreeBSD or Linux kernel will > lead to hardware failure due to bad or malicious coding --- the core It turns out that the reset switch went bad - it was not the motherboard = as I=20 thought. The kernel panic was indeed a misconfigured kernel - I hit the r= eset=20 switch after I got the kernel panic message and the switch remained stuck= =20 permanently in the reset position. A weird chain of events! Maybe no one = is=20 interested, but remember, it could happen to you too. regards, Robert