Date: Sun, 3 Aug 2003 19:07:33 +0200 (CEST) From: Soeren Schmidt <sos@spider.deepcore.dk> To: ryan chris <hospital@sdf.lonestar.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: dma error Message-ID: <200308031707.h73H7Y3E079957@spider.deepcore.dk> In-Reply-To: <Pine.NEB.4.33.0308031644190.14796-100000@sdf.lonestar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
It seems ryan chris wrote: > versions this happened on: 4.8-release, 5.1-release, 5.1-current > > with dma enabled, panics with anic errors occur left and right during > intensive hdd i/o... examples are during a non-minimal sysinstall, and > during a tar -xvf of the entire ports collection > > this is on an asus a7v-ve ( > http://www.hp.com/cposupport/personal_computing/support_doc/bph07371.html > ) > > -bash-2.05b$ dmesg|grep atapci > atapci0: <VIA 82C686B UDMA100 controller> port 0xd800-0xd80f at device 7.1 > on pci0 > atapci0: Correcting VIA config for southbridge data corruption bug > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > atapci0: <VIA 82C686B UDMA100 controller> port 0xd800-0xd80f at device 7.1 > on pci0 > atapci0: Correcting VIA config for southbridge data corruption bug > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > > disabling dma seemed to fix the problem You have one of the bug ridden VIA 82c686B southbridges, and the normal procedure for fixing this problem is to get a new BIOS that programs the chipset correctly.. -Søren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200308031707.h73H7Y3E079957>