From owner-freebsd-current Thu Nov 26 02:09:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15136 for freebsd-current-outgoing; Thu, 26 Nov 1998 02:09:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freesbee.t.dk (freesbee.t.dk [193.163.159.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA15129 for ; Thu, 26 Nov 1998 02:09:08 -0800 (PST) (envelope-from jesper@freesbee.t.dk) Received: (qmail 15396 invoked by uid 1001); 26 Nov 1998 10:09:03 -0000 Date: Thu, 26 Nov 1998 11:09:02 +0100 From: Jesper Skriver To: David Greenman Cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity Message-ID: <19981126110902.C15228@skriver.dk> References: <19981126091330.C14233@skriver.dk> <199811260907.BAA14375@root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: <199811260907.BAA14375@root.com>; from David Greenman on Thu, Nov 26, 1998 at 01:07:10AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 26, 1998 at 01:07:10AM -0800, David Greenman wrote: > >> This appears to be different and unrelated as well and probably indicates > >> a hardware problem. > > > >Have you got any idea which HW, I've got a ethernet card that logs > >"Recieve CRC error" all the time, I'm working on getting it replaced, > >but as the security people here require static MAC addresses in the > >routers, it's a but of a hassle to swap it ... sigh ... > > Memory, cache, CPU, or motherboard. I finally got the old lance ethernet replaced with a 3c905B card, and now it hasn't crashed yet, even a "make buildworld" and running X at the same time hasn't crashed the box ... /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message