From owner-freebsd-stable@FreeBSD.ORG Sun Oct 19 07:03:29 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 AC91B16A4B3 for ; Sun, 19 Oct 2003 07:03:29 -0700 (PDT) Received: from spam2.snu.ac.kr (spam2.snu.ac.kr [147.46.10.68]) by mx1.FreeBSD.org (Postfix) with SMTP id 5071643F75 for ; Sun, 19 Oct 2003 07:03:28 -0700 (PDT) (envelope-from lahaye@users.sourceforge.net) Received: (snipe 2656 invoked by alias); 19 Oct 2003 14:02:38 -0000 Received: from lahaye@users.sourceforge.net with SpamSniper2.76 (Processed in 0.017248 secs); Received: from unknown (HELO sis1.snu.ac.kr) (147.46.10.36) by 0 with SMTP; 19 Oct 2003 14:02:38 -0000 X-RCPTTO: freebsd-stable@freebsd.org,ebay@on-air.net, Received: from users.sourceforge.net ([147.46.44.183]) by sis1.snu.ac.kr (8.12.10/8.12.10) with ESMTP id h9JE1pit287996; Sun, 19 Oct 2003 23:01:52 +0900 Message-ID: <3F9299A8.10401@users.sourceforge.net> Date: Sun, 19 Oct 2003 23:03:20 +0900 From: Rob Lahaye Organization: Seoul National University - South Korea User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4.1) Gecko/20031014 X-Accept-Language: en-us, ko-kr MIME-Version: 1.0 To: Serious Signal , freebsd-stable@freebsd.org References: <200310191028.h9JASlbG094267@space.lan> In-Reply-To: <200310191028.h9JASlbG094267@space.lan> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 14:03:29 -0000 Serious Signal wrote: > 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 Interesting that I get a similar situation, be it with a regular hard disk (no special setups such as vinum). 'dmesg' says: [...] ata1-slave: ATA identify retries exceeded ad0: 76319MB [155061/16/63] at ata0-master UDMA66 acd0: CDROM at ata1-master PIO4 Mounting root from ufs:/dev/ad0s1a ad0s1a: UDMA ICRC error reading fsbn 137023 of 68480-68607 (ad0s1 bn 137023; cn 8 tn 134 sn 61) retrying ad0s1a: UDMA ICRC error reading fsbn 137023 of 68480-68607 (ad0s1 bn 137023; cn 8 tn 134 sn 61) retrying ad0s1a: UDMA ICRC error reading fsbn 137023 of 68480-68607 (ad0s1 bn 137023; cn 8 tn 134 sn 61) retrying ad0s1a: UDMA ICRC error reading fsbn 137023 of 68480-68607 (ad0s1 bn 137023; cn 8 tn 134 sn 61) falling back to PIO mode When I reported this to the STABLE list, my PC was blamed of having some broken communication to my harddisk. Now I wonder if this is indeed the case; or will you also be blamed for having a bad PC :). Regards, Rob.