From owner-freebsd-current Sat May 15 20:56:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id C771C14C96 for ; Sat, 15 May 1999 20:56:31 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA13745; Sat, 15 May 1999 21:54:01 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id VAA18027; Sat, 15 May 1999 21:54:00 -0600 Date: Sat, 15 May 1999 21:54:00 -0600 Message-Id: <199905160354.VAA18027@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Kevin Day , current@FreeBSD.ORG Subject: Re: -current page fault at 0xdeadc0de In-Reply-To: <199905160318.UAA03441@dingo.cdrom.com> References: <199905130258.VAA11540@home.dragondata.com> <199905160318.UAA03441@dingo.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > One system was running 2.2.8, and my core file presents me with this: ... > Just out of curiosity, are either of these systems running with NCR > controllers? In case you're fishing, I'm running 4 NCR equipped boxes (510 and 575) with FreeBSD 2.2.8-stable right now and have seen *NO* problems whatsoever. I've only *once* had a SCSI error on my system, and that was due to a bug that was somewhere other than the NCR driver. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message