From owner-freebsd-questions Tue Feb 27 03:13:02 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA04288 for questions-outgoing; Tue, 27 Feb 1996 03:13:02 -0800 (PST) Received: from MediaCity.com (root@easy1.mediacity.com [205.216.172.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA04278 for ; Tue, 27 Feb 1996 03:12:59 -0800 (PST) Received: (from brian@localhost) by MediaCity.com (8.6.11/8.6.9) id DAA04842 for freebsd-questions@freebsd.org; Tue, 27 Feb 1996 03:17:03 -0800 Message-Id: <199602271117.DAA04842@MediaCity.com> Subject: My NCR810 nolonger dies on -stable, -current or 2.1.0-RELEASE To: freebsd-questions@freebsd.org Date: Tue, 27 Feb 1996 03:17:03 -0800 (PST) From: "Brian Litzinger" X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org Precedence: bulk Well, I upgraded my motherboard from a neptune to a triton chipset. (Actually an ASUS P54 somethingorother) And all the problems went away. The system now boots on -stable, -current, and 2.1.0-RELEASE. Brian Litzinger brian@mediacity.com ----- Quoted message from Brian Litzinger ----- Earlier I reported that my NCR 810 PCI controllers was locking up after the 'changing root device to sd0a'. I happened to wait for about 30 seconds with the system stuck and got this message: changing root device to sd0a [about 30 second delay] ncr0: aborting job ... ncr0:1: ERROR (90:0) (8-0-0) (0/13) @ (c84:50000000). script cmd = 740a8700 reg: de 00 00 13 47 00 06 1f 35 08 00 00 90 00 0f 02. ncr0: restart (fatal error) sd0(ncr0:0:0) COMMAND FAILED (9 ff) @f0a21800. sd0(ncr0:0:0) FAST SCSI-2 100ns (10 Mb/sec) offset 8. panic: cannot mount root That basic problem is that things work fine with 2.1.0-RELEASE, and the above happens with -stable and -current. ----- End of quoted message from Brian Litzinger -----