From owner-freebsd-questions Wed Oct 17 21:25: 0 2001 Delivered-To: freebsd-questions@freebsd.org Received: from firewall.crimsonwasteland.com (cx154799-b.btnrug1.la.home.com [24.13.195.243]) by hub.freebsd.org (Postfix) with SMTP id 1A65437B403 for ; Wed, 17 Oct 2001 21:24:50 -0700 (PDT) Received: (qmail 559 invoked from network); 18 Oct 2001 04:24:45 -0000 Received: from unknown (HELO travis) (172.16.69.2) by 172.16.69.1 with SMTP; 18 Oct 2001 04:24:45 -0000 From: "Travis Leuthauser" To: Subject: RE: UDMA ICRC error reading fsbn Date: Wed, 17 Oct 2001 23:24:45 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In answer to my own question, had I read my dmesg output a little closer, I would have noticed that my ATA100 controller was sharing an IRQ with my USB controller. After resolving that, my errors have gone away. Sorry to anyone who actually spent time looking at my mindless questions. :) -Travis -----Original Message----- From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Travis Leuthauser Sent: Wednesday, October 17, 2001 9:08 PM To: freebsd-questions@freebsd.org Subject: UDMA ICRC error reading fsbn I have seen a few posts from people who are experiencing the same problem with a workaround disabling dma mode for the suspect drive. Several people have also suggested that it could be failing hardware. The problematic drive is brand new from Western Digital and the Promise controller that it is connected to is also brand new. If I do disable dma mode for the suspect drive, the errors go away. I am of the opinion that I have run into one of those "funky" hardware mixes that causes this problem. I am more looking for other people's opinion on the matter and a fix to keep dma mode would be excellent (not expecting that though). I am including a dmesg output. The drive (ad4) has not even been fdisk'ed or labeled yet. Thanks for any insight that you can provide. Travis dmesg output: Oct 17 20:25:20 firewall /kernel: Copyright (c) 1992-2001 The FreeBSD Project. Oct 17 20:25:20 firewall /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Oct 17 20:25:20 firewall /kernel: The Regents of the University of California. All rights reserved. Oct 17 20:25:20 firewall /kernel: FreeBSD 4.4-STABLE #0: Mon Sep 24 16:00:52 CDT 2001 Oct 17 20:25:20 firewall /kernel: korak@firewall.crimsonwasteland.com:/usr/obj/usr/src/sys/FIREWALL Oct 17 20:25:20 firewall /kernel: Timecounter "i8254" frequency 1193182 Hz Oct 17 20:25:20 firewall /kernel: CPU: Pentium II/Pentium II Xeon/Celeron (267.27-MHz 686-class CPU) Oct 17 20:25:20 firewall /kernel: Origin = "GenuineIntel" Id = 0x633 Stepping = 3 Oct 17 20:25:20 firewall /kernel: Features=0x80f9ff Oct 17 20:25:20 firewall /kernel: real memory = 134217728 (131072K bytes) Oct 17 20:25:20 firewall /kernel: avail memory = 126730240 (123760K bytes) Oct 17 20:25:20 firewall /kernel: Preloaded elf kernel "kernel" at 0xc0382000. Oct 17 20:25:20 firewall /kernel: Preloaded userconfig_script "/boot/kernel.conf" at 0xc038209c. Oct 17 20:25:20 firewall /kernel: Pentium Pro MTRR support enabled Oct 17 20:25:20 firewall /kernel: md0: Malloc disk Oct 17 20:25:20 firewall /kernel: Using $PIR table, 6 entries at 0xc00fdc00 Oct 17 20:25:20 firewall /kernel: npx0: on motherboard Oct 17 20:25:20 firewall /kernel: npx0: INT 16 interface Oct 17 20:25:20 firewall /kernel: pcib0: on motherboard Oct 17 20:25:20 firewall /kernel: pci0: on pcib0 Oct 17 20:25:20 firewall /kernel: pcib1: at device 1.0 on pci0 Oct 17 20:25:20 firewall /kernel: pci1: on pcib1 Oct 17 20:25:20 firewall /kernel: pci1: at 0.0 irq 9 Oct 17 20:25:20 firewall /kernel: isab0: at device 7.0 on pci0 Oct 17 20:25:20 firewall /kernel: isa0: on isab0 Oct 17 20:25:20 firewall /kernel: atapci0: port 0xf000-0xf00f at device 7.1 on pci0 Oct 17 20:25:20 firewall /kernel: ata0: at 0x1f0 irq 14 on atapci0 Oct 17 20:25:20 firewall /kernel: ata1: at 0x170 irq 15 on atapci0 Oct 17 20:25:20 firewall /kernel: uhci0: port 0x6400-0x641f irq 11 at device 7.2 on pci0 Oct 17 20:25:20 firewall /kernel: usb0: on uhci0 Oct 17 20:25:20 firewall /kernel: usb0: USB revision 1.0 Oct 17 20:25:20 firewall /kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Oct 17 20:25:20 firewall /kernel: uhub0: 2 ports with 2 removable, self powered Oct 17 20:25:20 firewall /kernel: chip1: port 0x5f00-0x5f0f at device 7.3 on pci0 Oct 17 20:25:20 firewall /kernel: xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x6500-0x657f mem 0xe4005000-0xe400507f irq 9 at device 9.0 on pci0 Oct 17 20:25:20 firewall /kernel: xl0: Ethernet address: 00:04:76:6f:71:36 Oct 17 20:25:20 firewall /kernel: miibus0: on xl0 Oct 17 20:25:20 firewall /kernel: xlphy0: <3Com internal media interface> on miibus0 Oct 17 20:25:20 firewall /kernel: xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Oct 17 20:25:20 firewall /kernel: xl1: <3Com 3c905B-TX Fast Etherlink XL> port 0x6600-0x667f mem 0xe4004000-0xe400407f irq 12 at device 10.0 on pci0 Oct 17 20:25:20 firewall /kernel: xl1: Ethernet address: 00:04:76:6f:71:4e Oct 17 20:25:20 firewall /kernel: miibus1: on xl1 Oct 17 20:25:20 firewall /kernel: xlphy1: <3Com internal media interface> on miibus1 Oct 17 20:25:20 firewall /kernel: xlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Oct 17 20:25:20 firewall /kernel: atapci1: port 0x6b00-0x6b0f,0x6a00-0x6a03,0x6900-0x6907,0x6800-0x6803,0x6700-0x6707 mem 0xe4000000-0xe4003fff irq 11 at device 12.0 on pci0 Oct 17 20:25:20 firewall /kernel: ata2: at 0x6700 on atapci1 Oct 17 20:25:20 firewall /kernel: ata3: at 0x6900 on atapci1 Oct 17 20:25:20 firewall /kernel: orm0: