From owner-freebsd-stable@FreeBSD.ORG Sun Oct 19 03:28:51 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 BC1BC16A4B3 for ; Sun, 19 Oct 2003 03:28:51 -0700 (PDT) Received: from i.dtl.net (ns1.dtl.net [66.181.4.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id D46E743F3F for ; Sun, 19 Oct 2003 03:28:50 -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 h9JASlgV047330 for ; Sun, 19 Oct 2003 03:28:47 -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 h9JASlbG094267 for ; Sun, 19 Oct 2003 03:28:47 -0700 (PDT) (envelope-from ebay@on-air.net) Message-Id: <200310191028.h9JASlbG094267@space.lan> From: "Serious Signal" To: Date: Sun, 19 Oct 2003 03:28:36 -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 Thread-Index: AcOWK8EVN//mOWdLSdWpcJOpmQ1oyA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: 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 10:28:51 -0000 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.