From owner-freebsd-hardware@FreeBSD.ORG Mon Nov 3 08:14:49 2003 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3BF416A4CF for ; Mon, 3 Nov 2003 08:14:49 -0800 (PST) Received: from reaktorn.org (reaktorn.org [195.84.133.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D60843F75 for ; Mon, 3 Nov 2003 08:14:48 -0800 (PST) (envelope-from tjyv@reaktorn.org) Received: from as1-6-1.kpr.ks.bonet.se ([217.215.116.95] helo=elite) by reaktorn.org with asmtp (Exim 4.22) id 1AGhLs-000EbL-P3 for freebsd-hardware@freebsd.org; Mon, 03 Nov 2003 17:14:48 +0100 Message-ID: <002201c3a225$c46d8f70$0100a8c0@elite> From: "Tomas Nyman" To: Date: Mon, 3 Nov 2003 17:15:58 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: UDMA ICRC Error X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 16:14:49 -0000 Hi! I have a serious problem with 3 of my harddrives, the fail to enter DMA = mode on boot, I can force them into udma5 using atacontrol but after a = few reads I will get the same error and they will fall back into PIO4 = mode. The 3 disks are in a Vinum array consisting of 6 drives, the other 3 are = working fine. I have tried 2 different ata controller cards in 2 different PCI slots = and 3 different ide cables, I still get the same error. I have ran fsck 4 times on the array and the output is always looking = good, no errors found: ** /dev/vinum/MyVol ** Last Mounted on /projects ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 39454 files, 546808950 used, 78086290 free (3682 frags, 9760326 blocks, = 0.0% fragmentation) Sometimes when I try to boot I get this error: Fatal trap 12: page fault while in kernel mode fault code =3D supervisor read, page not present I have not been able to catch the complete error message on a file since = the machine is far from home and I just had my friend reboot the machine = when I got that error, but it made me think it might have something to = do with this: = http://lists.freebsd.org/pipermail/freebsd-current/2003-July/007155.html I know that is a 5.1 error and I=B4m running 4.9 but could applying the = patch that is posted a few messages later help me? I don=B4t know what to do really, I am OK with doing NEWFS on the array = if it would fix the disks, but since fsck shows no error I think it=B4s = something else, I appreciate any help. Tomas DMESG: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD 4.9-RELEASE #1: Thu Oct 30 19:09:30 CET 2003 root@Tanhauser:/usr/obj/usr/src/sys/SOPP Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 701593772 Hz CPU: Intel Pentium III (701.59-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x683 Stepping =3D 3 = Features=3D0x387f9ff real memory =3D 671088640 (655360K bytes) avail memory =3D 648806400 (633600K bytes) Preloaded elf kernel "kernel" at 0xc032f000. ccd0-8: Concatenated disk drivers Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 9 entries at 0xc00fde70 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem = 0xd0000000-0xd3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on = pci0 pci1: on pcib1 pci1: at 0.0 irq 10 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 = on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 irq 7 chip0: port 0x5000-0x500f at = device 7.3 on pci0 atapci1: port = 0xa400-0xa40f,0xa000-0xa003,0x9c00-0x9c07,0x9800-0x9803,0x9400-0x9407 = mem 0xdb000000-0xdb003fff irq 7 at device 11.0 on pci0 ata2: at 0x9400 on atapci1 ata3: at 0x9c00 on atapci1 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xa800-0xa87f mem = 0xdb00c000-0xdb00c07f irq 11 at device 13.0 on pci0 xl0: Ethernet address: 00:04:76:1b:ea:73 miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci2: port = 0xbc00-0xbc0f,0xb800-0xb803,0xb400-0xb407,0xb000-0xb003,0xac00-0xac07 = mem 0xdb004000-0xdb007fff irq 5 at device 15.0 on pci0 ata4: at 0xac00 on atapci2 ata5: at 0xb400 on atapci2 atapci3: port = 0xd000-0xd00f,0xcc00-0xcc03,0xc800-0xc807,0xc400-0xc403,0xc000-0xc007 = mem 0xdb008000-0xdb00bfff irq 10 at device 17.0 on pci0 ata6: at 0xc000 on atapci3 ata7: at 0xc800 on atapci3 atapci4: port = 0xdc00-0xdcff,0xd800-0xd803,0xd400-0xd407 irq 11 at device 19.0 on pci0 ata8: at 0xd400 on atapci4 atapci5: port = 0xe800-0xe8ff,0xe400-0xe403,0xe000-0xe007 irq 11 at device 19.1 on pci0 ata9: at 0xe000 on atapci5 orm0: