From owner-freebsd-questions Mon Apr 27 07:04:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17075 for freebsd-questions-outgoing; Mon, 27 Apr 1998 07:04:11 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from att.com (cagw1.att.com [192.128.52.89]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA17065 for ; Mon, 27 Apr 1998 07:04:06 -0700 (PDT) (envelope-from jwb@homer.att.com) Received: by cagw1.att.com; Mon Apr 27 09:56 EDT 1998 Received: from ulysses.homer.att.com (ulysses.homer.att.com [135.205.212.4]) by caig1.att.att.com (AT&T/GW-1.0) with ESMTP id KAA12761 for ; Mon, 27 Apr 1998 10:03:35 -0400 (EDT) Received: from akiva.homer.att.com (akiva.homer.att.com [135.205.213.77]) by ulysses.homer.att.com (8.8.8/8.8.8) with SMTP id JAA03420 for ; Mon, 27 Apr 1998 09:58:45 -0400 (EDT) Received: by akiva.homer.att.com (4.1) id AA20496; Mon, 27 Apr 98 10:03:11 EDT Message-Id: <9804271403.AA20496@akiva.homer.att.com> Received: from localhost.homer.att.com [127.0.0.1] by akiva; Mon Apr 27 10:03:10 EDT 1998 X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-questions@FreeBSD.ORG Subject: freebsd hardware early warning system??? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Apr 1998 10:03:09 -0400 From: "J. W. Ballantine" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I have a strange question about freebsd and potential "almost-broken" hardware. I have a NCR630 with an Adaptec AHA2490 and a 3COM etherlink III. I'm running NT and did have current on it. The other day I tried to reboot FreeBSD-current and the FB boot process hung, first before the disk checks and then after the disk checks with the SCSI disk light locked on. (Did this a few times.) I then decided to load 980311-SNAP and the system would hang when it tried to establish the default route to the router. (several times) At this point I rebooted the system to NT, and lo and behold the network card wasn't working. After a couple of reboots, it started working again and I had conductivity again. Anyway, wondering if the SNAP was a problem, I tried to load 2.2.6-RELEASE, and this load hung when it was trying to start the emergency shell. Also, the boot manager (osbsbeta) would stop working, and after I check on it, and found it ok, it would work again. So anyway my question is FreeBSD stressing something on the system that would detect "early" hardware problems that aren't found under NT?? And could the "locked" disk cause the network board to lock up and/or cause the bootmanager problem? Any insight is appreciated. Thanks Jim Ballantine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message