From owner-freebsd-bugs Sat Jan 6 12:10: 6 2001 From owner-freebsd-bugs@FreeBSD.ORG Sat Jan 6 12:10:05 2001 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7B67337B400 for ; Sat, 6 Jan 2001 12:10:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f06KA4S39567; Sat, 6 Jan 2001 12:10:04 -0800 (PST) (envelope-from gnats) Date: Sat, 6 Jan 2001 12:10:04 -0800 (PST) Message-Id: <200101062010.f06KA4S39567@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Martin Birgmeier Subject: Re: kern/24092: Disk data corruption using FreeBSD_4_2_0_RELEASE Reply-To: Martin Birgmeier Sender: gnats@FreeBSD.org Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/24092; it has been noted by GNATS. From: Martin Birgmeier To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/24092: Disk data corruption using FreeBSD_4_2_0_RELEASE Date: Sat, 06 Jan 2001 21:05:24 +0100 Quite (or not so?) unbelievably, upgrading the motherboard's BIOS seems to do the trick: From a7v1004c.zip to a7v1005a.zip. I'll watch it some more and post a final note when everything seems indeed doing well again. I guess that now some chipset registers are initialized `more correctly'. Would be nice if FreeBSD could do that instead of relying on the BIOS, but I understand the task involved. -- Martin Birgmeier Vienna Austria To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message