From owner-freebsd-stable@FreeBSD.ORG Sun Oct 19 14:03:50 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1FD716A4B3 for ; Sun, 19 Oct 2003 14:03:50 -0700 (PDT) Received: from i.dtl.net (ns1.dtl.net [66.181.4.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id E351D43FA3 for ; Sun, 19 Oct 2003 14:03:49 -0700 (PDT) (envelope-from ebay@on-air.net) Received: from space.lan (cox-i2b.space.lan [192.168.1.4]) by i.dtl.net (8.12.9/8.12.9) with ESMTP id h9JL3ngV053198; Sun, 19 Oct 2003 14:03:49 -0700 (PDT) (envelope-from ebay@on-air.net) Received: from mars (mars.space.lan [192.168.0.6]) by space.lan (8.12.9/8.12.9) with ESMTP id h9JL3mbG095722; Sun, 19 Oct 2003 14:03:48 -0700 (PDT) (envelope-from ebay@on-air.net) Message-Id: <200310192103.h9JL3mbG095722@space.lan> From: "Serious Signal" To: "'Dmitry Morozovsky'" , "'Rob Lahaye'" Date: Sun, 19 Oct 2003 14:03:35 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5329 In-Reply-To: <20031020003821.C88532@woozle.rinet.ru> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Thread-Index: AcOWgTH78qOqgDyDS2+evvf6mO2bNQAAK3XA cc: freebsd-stable@freebsd.org Subject: RE: Odd IDE / vinum problem on new 4.9-RC3 system X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Oct 2003 21:03:50 -0000 > Well colleagues, but both of you failed to specify your onboard IDE > controlled > dmesg lines! ;-) > > *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** Dmitry, Good catch! atapci0: port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 In my case, the motherboard came in a Shuttle XPC (Flex ATX form factor) barebones model FV24 which uses the VIA VT82C686B chipset. It has the latest available BIOS installed. A friend of mine said, "When UDMA 100 first came out, many of the chipsets were 100 on primary and 66 on secondary. This was not at all uncommon." The specs in the manual say, "PCI Bus Master IDE Controller Onboard -- Two UltraDMA 100/66/33 Bus Master Dual-channel IDE ports provide support to a maximum of four IDE devices. The IDE Bus implements the data transfer speed up to 100/66/33 MB/sec and also supports Enhanced PIO Modes." If my friend is right, it certainly explains what I'm seeing, as UDMA100 works on the primary and only UDMA66 works on the secondary. Can anyone else confirm and specifically with this VIA chipset? --Serious Original posting: All, I'm running 4.9-RC3 on a new installation with three new hard drives that are all Ultra100-compatible. BIOS is set to Auto for IDE drives and correctly reports sizes with UDMA 100 LBA modes. The OS sees: ad0: 76319MB [155061/16/63] at ata0-master UDMA100 ad1: 238475MB [484521/16/63] at ata0-slave UDMA100 ad2: 238475MB [484521/16/63] at ata1-master UDMA100 When I connect the drives to the onboard IDE, only the first IDE channel (ad0 and ad1) works right at UDMA100. On the second channel, with ad2 only, I get errors when writing (reading is not a problem): ad2s1e: UDMA ICRC error writing fsbn 643383313 of 321036265-321036392 (ad2s1 bn 643383313; cn 40048 tn 193 sn 34) retrying ad2s1e: UDMA ICRC error writing fsbn 643383313 of 321036265-321036392 (ad2s1 bn 643383313; cn 40048 tn 193 sn 34) retrying ad2s1e: UDMA ICRC error writing fsbn 643383313 of 321036265-321036392 (ad2s1 bn 643383313; cn 40048 tn 193 sn 34) retrying Occasionally, the retries succeed. But eventually, the OS sets the ATA mode to PIO: ad2s1e: UDMA ICRC error writing fsbn 643383313 of 321036265-321036392 (ad2s1 bn 643383313; cn 40048 tn 193 sn 34) falling back to PIO mode Of course, PIO mode works (albeit slowly). If I manually set the ATA mode with atacontrol to UDMA66, it works fine. Moving the drives to a Promise Ultra100 PCI card works, too, but is not what I want. I've tried two UDMA100 cables with no difference (and they work on the Promise card as a control test, so they're fine). BIOS is set to auto for everything -- CPU, bus, SDRAM frequency -- no over-clocking or any other aggressive settings. I'm accessing a vinum striped and mirrored file system across ad1 and ad2, if that's significant. (But if it were, why would the errors appear only on the ad2 device?). I've run out of ideas. Am I'm missing something? Thanks for your help. --Serious P.S. Please include my address in your reply.