From owner-freebsd-current Tue Nov 24 01:58:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00623 for freebsd-current-outgoing; Tue, 24 Nov 1998 01:58:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00608 for ; Tue, 24 Nov 1998 01:57:38 -0800 (PST) (envelope-from romanp@wuppy.rcs.ru) Received: from room101.wuppy.rcs.ru (peer cross-checked as room101.wuppy.rcs.ru [194.84.206.44]) by room101.wuppy.rcs.ru with ESMTP id MAA02676; Tue, 24 Nov 1998 12:54:35 +0300 (MSK) (envelope-from romanp@wuppy.rcs.ru) Date: Tue, 24 Nov 1998 12:54:35 +0300 (MSK) From: "Roman V. Palagin" To: Karl Pielorz cc: current@FreeBSD.ORG Subject: Re: Random craches under heavy(?) disk activity In-Reply-To: <365A7F6A.3ED8A6D6@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Nov 1998, Karl Pielorz wrote: > > I thought this had been fixed a while ago? - my system (current as of > Thu/19/11/98) doesn't show any symptoms (it's an SMP P-Pro 200), even when > busy (14 drives across 5 controllers) - it certainly makes it past the usual > 2am cron-job's, and backups etc. It was fixed by McKusick 17/11/98. But it's very interesting: I've current as of 23/11/98 and kernel crashes without disabling 'realloc' code, maximum uptime about 5-6 hours. Previous kernel was as of about 20/11/98 and works without any problems 8-) It's looks like something changed in src/sys tree. ------------------------------------------------------------------------- Roman V. Palagin | RVP1-6BONE | Just because you're paranoid Network Administrator | RP40-RIPE | doesn't mean they AREN'T after you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message