From owner-freebsd-isdn Tue Nov 30 14:47:45 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from devil.intervisors.nl (office.intervisors.nl [194.109.13.117]) by hub.freebsd.org (Postfix) with ESMTP id 8297115821 for ; Tue, 30 Nov 1999 14:47:42 -0800 (PST) (envelope-from luke@roberts.nl) Received: from roberts4 (roberts4.intranet.iv [192.168.0.8]) by devil.intervisors.nl (8.9.3/8.9.3) with ESMTP id XAA00310; Tue, 30 Nov 1999 23:41:50 +0100 (CET) (envelope-from luke@roberts.nl) Message-Id: <4.2.2.19991130233731.00ade6b0@pop.roberts.nl> X-Sender: luke@pop.roberts.nl X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 30 Nov 1999 23:44:44 +0100 To: Gerald Heinig , isdn@FreeBSD.ORG From: Luke Roberts Subject: Re: Black tuesday :-( In-Reply-To: <38444FEE.977FC696@hdz-ima.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Gerald, >I ifconfig=B4ed up isp0, did a fetchmail and got the BIOS message. In >other words: fetchmail... 3 seconds...blank screen...BIOS startup >message. I remember having this problem on a black Sunday and the cause, which had=20 nothing to do with the machine or software, was very simple: a very short power failure, aka a brownout, but enough to quickly power=20 down and reboot the machine. Of course your power supply could be faulty in= =20 stead. >Also, I=B4d like a few tips on how to go about preparing for a repeat. I >assume this bug (if indeed it is a bug!) is *very* rare, since, give or >take a protocol message or two in earlier versions, I haven=B4t heard so >much as a squeak from my setup for several months. The solution was very simple: A UPS batterypack hooked up to the FreeBSD=20 machine. Hope this helps, Luke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message