Date: Tue, 12 Feb 2008 09:46:51 +0100 From: remco@spacemarines.us (Remco van Bekkum) To: Torfinn Ingolfsen <torfinn.ingolfsen@broadpark.no> Cc: freebsd-stable@freebsd.org Subject: Re: "ad0: TIMEOUT - WRITE_DMA" type errors with 7.0-RC1 Message-ID: <20080212084651.GA7902@marshal.spacemarines.us> In-Reply-To: <20080212010335.190e2771.torfinn.ingolfsen@broadpark.no> References: <479A0731.6020405@skyrush.com> <20080125162940.GA38494@eos.sc1.parodius.com> <479A3764.6050800@skyrush.com> <3803988D-8D18-4E89-92EA-19BF62FD2395@mac.com> <479A4CB0.5080206@skyrush.com> <20080126003845.GA52183@eos.sc1.parodius.com> <20080211120057.GA5821@marshal.spacemarines.us> <20080212010335.190e2771.torfinn.ingolfsen@broadpark.no>
index | next in thread | previous in thread | raw e-mail
On Tue, Feb 12, 2008 at 01:03:35AM +0100, Torfinn Ingolfsen wrote: > On Mon, 11 Feb 2008 13:00:57 +0100 > remco@spacemarines.us (Remco van Bekkum) wrote: > > > here? It's on an amd64, Asus m2a-vm with ati xp600, AMD BE-2350 CPU, > > 2GB 800MHz RAM. > > FWIW, I have the almost the same motherboard (m2a-vm hdmi) with an AMD > Phenom 9500 and 4GB RAM[1]. Different disk, though. The (single) disk > drive has worked without problems so far. I'm using standard ufs2 > filesystems on that disk. I'm running RELENG_7: > tingo@kg-vm$ uname -a > FreeBSD kg-vm.kg4.no 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #6: Sat Jan > 26 20:58:51 CET 2008 > root@kg-vm.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 > root@kg-vm# atacontrol list > ATA channel 0: > Master: acd0 <Optiarc DVD RW AD-5170A/1.12> ATA/ATAPI revision 0 > Slave: no device present > ATA channel 2: > Master: ad4 <SAMSUNG HD501LJ/CR100-12> Serial ATA II > Slave: no device present > ATA channel 3: > Master: no device present > Slave: no device present > ATA channel 4: > Master: no device present > Slave: no device present > ATA channel 5: > Master: no device present > Slave: no device present > > > References: > 1) http://tingox.googlepages.com/asus_m2a-vm_hdmi_freebsd > -- > Regards, > Torfinn Ingolfsen > Thanks, here some more detailed info from me: xaero# dmesg | grep atapci atapci0: <ATI AHCI controller> port 0xfc00-0xfc07,0xf800-0xf803,0xf400-0xf407,0xf000-0xf003,0xec00-0xec0f mem 0xfe02f000-0xfe02f3ff irq 22 at device 18.0 on pci0 atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: <ATA channel 0> on atapci0 ata3: <ATA channel 1> on atapci0 ata4: <ATA channel 2> on atapci0 ata5: <ATA channel 3> on atapci0 atapci1: <ATI IXP600 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe400-0xe40f at device 20.1 on pci0 ata0: <ATA channel 0> on atapci1 xaero# atacontrol list ATA channel 0: Master: no device present Slave: no device present ATA channel 2: Master: ad4 <Hitachi HDP725050GLA360/GM4OA50E> Serial ATA II Slave: no device present ATA channel 3: Master: ad6 <Hitachi HDP725050GLA360/GM4OA50E> Serial ATA II Slave: no device present ATA channel 4: Master: ad8 <Hitachi HDP725050GLA360/GM4OA50E> Serial ATA II Slave: no device present ATA channel 5: Master: ad10 <Hitachi HDP725050GLA360/GM4OA50E> Serial ATA II Slave: no device present xaero# uname -a FreeBSD xaero.spacemarines.us 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Sun Feb 10 16:07:39 CET 2008 root@xaero.spacemarines.us:/usr/obj/usr/src/sys/GENERIC amd64 I'm using bios 1603, and a seasonic 330W PSU. The errors appear to happen at random, heavy I/O doesn't trigger it. I can rebuild world without problems, so I guess the CPU is ok. The memory has been tested and showed no errors. What's left is cables and mainboard. But how error-prone are sata cables? Considering that I've got 50% failing... Okay, maybe that should "prove" that the mainboard is faulty :) -Remcohome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080212084651.GA7902>