From owner-freebsd-current@FreeBSD.ORG Thu Dec 18 07:03:15 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E91516A4CE for ; Thu, 18 Dec 2003 07:03:15 -0800 (PST) Received: from rdsnet.ro (smtp.rdsnet.ro [62.231.74.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77C1343D3F for ; Thu, 18 Dec 2003 07:03:13 -0800 (PST) (envelope-from itetcu@apropo.ro) Received: (qmail 8042 invoked from network); 18 Dec 2003 15:03:10 -0000 Received: from unknown (HELO it.buh.cameradicommercio.ro) (81.196.25.19) by mail.rdsnet.ro with SMTP; 18 Dec 2003 15:03:10 -0000 Date: Thu, 18 Dec 2003 17:03:43 +0200 From: Ion-Mihai Tetcu To: Soren Schmidt Message-Id: <20031218170343.5753eb06.itetcu@apropo.ro> In-Reply-To: <200312181159.hBIBxZUM069241@spider.deepcore.dk> References: <20031218135627.0229225b.itetcu@apropo.ro> <200312181159.hBIBxZUM069241@spider.deepcore.dk> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: 5.2RC1 Read+Write data corruption (with SeagateBarracuda ATA V 120G (ST3120023A) + VIA 8237) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Dec 2003 15:03:15 -0000 On Thu, 18 Dec 2003 12:59:35 +0100 (CET) Soren Schmidt wrote: > It seems Ion-Mihai Tetcu wrote: > > On Thu, 18 Dec 2003 12:36:44 +0100 (CET) > > Soren Schmidt wrote: > > > > > It seems Ion-Mihai Tetcu wrote: > > > > atapci0: port 0xd000-0xd00f at device 7.1 on pci0 > > > > atapci0: Correcting VIA config for southbridge data corruption bug > > > > > > This piece of bugridden silicon might very well be the cause of all > > > your problems... > > > > I know that mainboard is a crap and that is the reason it is used for > > our secretary solitaire and stuff like that :). > > > > But then why does it happend on my Gigabyte MB ? It is an outher cipset. > > Hmm, there has been some trouble with a certain model of Seagate 40G > drives (bad firmware) so that might be something you could look into, > otherwise I have no idea... I have the feeling that the drive is not addresed properly; this seems to be partition size dependent and / or place from the begining of the disk where the partition is. Supposing I want to debug this problem, could you sugest some place to start ? Thanks. -- IOnut Unregistered ;) FreeBSD user