From owner-freebsd-hardware Wed Jun 11 13:54:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA17419 for hardware-outgoing; Wed, 11 Jun 1997 13:54:45 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA17410 for ; Wed, 11 Jun 1997 13:54:42 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-44.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA03928 (5.67b/IDA-1.5 for ); Wed, 11 Jun 1997 22:54:26 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id WAA07053; Wed, 11 Jun 1997 22:54:20 +0200 (CEST) X-Face: " Date: Wed, 11 Jun 1997 22:54:20 +0200 From: Stefan Esser To: alex fuchsstadt Cc: sthaug@nethelp.no, hardware@FreeBSD.ORG Subject: Re: overclocking References: <20071.866011725@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from alex fuchsstadt on Wed, Jun 11, 1997 at 10:11:27AM +0200 Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 11, alex fuchsstadt wrote: > I read all the mails about the overclocking theme and it turned to some > different but interesting ones. > I had a NCR 53C810 too and it died while working with fBSD, I suddenly got > a message like: NCR died ......... Well, there is no test for a "dead" NCR chip in the code, so you can only have received a message from the timeout handler, which warns if no progress has been made for some time. > I bought a new one and run it without any problems. I had a 486 ASUS > motherboard before with one integrated NCR also running without > anyproblems. > Anyone else there having problems with suddenly died NCRs? I have heard of just a few defective NCR chips over the last three years. Symptons were different: From complete failure (system won't start with controller card installed) to a data pattern dependent lockup (one NCR card could not extract some NetBSD distribution file: Writing a certain data pattern lead to a PCI bus error interrupt, and thus one file could not be written to disk; replacing the NCR, card solved that ...) Most of the problems I've heard of should have been covered by the SCSI card's warranty. Regards, STefan