Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Feb 1996 03:17:03 -0800 (PST)
From:      "Brian Litzinger" <brian@easy1.mediacity.com>
To:        freebsd-questions@freebsd.org
Subject:   My NCR810 nolonger dies on -stable, -current or 2.1.0-RELEASE
Message-ID:  <199602271117.DAA04842@MediaCity.com>

next in thread | raw e-mail | index | archive | help
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 -----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602271117.DAA04842>