From owner-freebsd-current Mon Aug 21 11:02:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id LAA03287 for current-outgoing; Mon, 21 Aug 1995 11:02:03 -0700 Received: from kaiwan.kaiwan.com (kaiwan.kaiwan.com [198.178.203.2]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id LAA03281 for ; Mon, 21 Aug 1995 11:02:01 -0700 Received: from exit.com (uucp@localhost) by kaiwan.kaiwan.com (8.6.12/8.6.12) with UUCP id LAA06459; Mon, 21 Aug 1995 11:01:24 -0700 *** KAIWAN Internet Access *** Received: (from frank@localhost) by exit.com (8.6.11/8.6.6) id LAA03399; Mon, 21 Aug 1995 11:03:02 -0700 From: Frank Mayhar Message-Id: <199508211803.LAA03399@exit.com> Subject: Re: Show-stopper crashes on 2.1-STABLE and 2.1.0-072695-SNAP. To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 21 Aug 1995 11:03:01 -0700 (PDT) Cc: current@freebsd.org, fmayhar@locus.com In-Reply-To: <199508211000.MAA26738@bonnie.tcd-dresden.de> from "J Wunsch" at Aug 21, 95 12:00:48 pm X-Mailer: ELM [version 2.4 PL24 ME5a] Content-Type: text Content-Length: 778 Sender: current-owner@freebsd.org Precedence: bulk Joerg wrote: > Since Frank has apparently email problems, and i'm not sure if this > report appeared in the lists, is it a known problem? Thanks, Joerg, but the problem appears to be hardware. I finally yanked the pipeline burst cache module, and haven't had a single crash in almost 24 hours of continuous news unbatching (I had a _lot_ of backed up news batches). I'm sending the module back today, and should have a new one by Wednesday. (The alternative is that it's a problem in the cache circuitry of the motherboard itself, but that will only become apparent if the system fails in the same way with the new PB module. I'm keeping my fingers crossed that it's the module itself.) Oh, and the email problems have been fixed. Thanks. -- Frank Mayhar frank@exit.com