From owner-freebsd-stable@FreeBSD.ORG Sun Aug 12 16:42:47 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8B8CB106566C for ; Sun, 12 Aug 2012 16:42:47 +0000 (UTC) (envelope-from wajih.ahmed@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0AEEB8FC08 for ; Sun, 12 Aug 2012 16:42:46 +0000 (UTC) Received: by bkcje9 with SMTP id je9so1162553bkc.13 for ; Sun, 12 Aug 2012 09:42:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mUXAAGQIGGXVsU93MuAd3+PcTO0J+PXCWNqg0o2H/3A=; b=Y2YXTcsqb6Y3xq1EBEZkbMKjFMyOANLsj0gDKU4f41frllRxOLRKyQCHz2SyEfx5XY 2rszqTH/faGPcg9uIaE+Nh/I7URwxOjxuf+K+7qOBeak4ZoeCpH/t/DiDvmylJuDTNE3 lSSD8TENfZ3k8WDofJkM5srd0He+mzVbGONFxgW7u6nwCAmYTz/ieoU6iA3GmrAPwPPe qxihw2Bly3k5W7CEj08Vv7sVkoBTJovehNi0hf5kFsItLJAIX6305kW4NfBTo99mOWDf prIaV3VvRy2eJzKtbV4viy7lWP0/nUPWx76BLOi6W+ZE7hchKPSG14lzKRI0d6YNMlUY nL7A== MIME-Version: 1.0 Received: by 10.204.157.22 with SMTP id z22mr3240420bkw.4.1344789765666; Sun, 12 Aug 2012 09:42:45 -0700 (PDT) Received: by 10.204.38.141 with HTTP; Sun, 12 Aug 2012 09:42:45 -0700 (PDT) In-Reply-To: References: <1344786355.1186.32.camel@revolution.hippie.lan> Date: Sun, 12 Aug 2012 12:42:45 -0400 Message-ID: From: Wajih Ahmed To: Ian Lepore Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 9.0 and (Kingspec) PATA drive ATA status errors. Drive unusable. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 12 Aug 2012 16:42:47 -0000 Ok at the boot loader prompt i did as you suggested set hint.ata.0.mode="UDMA33" And that change did take effect as evedint by ada0: 33.300MB/s transfers (UDMA2, PIO 512bytes) Unfortunately i still get the error .....ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT) Regards, On Sun, Aug 12, 2012 at 12:29 PM, Wajih Ahmed wrote: > Thank you. I'll try it out. One question though. How do i modify the > loader.conf on the usb image from which i am booting? Is there somethign i > can change in the boot loader? If this is RTFM kindly point me to it. > > > > > On Sun, Aug 12, 2012 at 11:45 AM, Ian Lepore < > freebsd@damnhippie.dyndns.org> wrote: > >> On Sun, 2012-08-12 at 10:57 -0400, Wajih Ahmed wrote: >> > I have a Dell D420 laptop with the ZIF interface and uses a 1.8" PATA >> > drive. I purchased a Kingspec 16GB SSD and installed it. The BIOS >> > recogonizes the drive. I am using the USB image to boot in verbose >> mode. >> > Upon boot the disk is recognized by FreeBSD 9.0 as follows (sorry for >> any >> > typos as i am reading this off the console): >> > >> > ada0 at ata0 bus 0 scbus0 target 0 lun 0 >> > ada0: ATA-7 device >> > ada0: Serial number... >> > ada0: 100.0000MB/s transfers (UDMA5, PIO 512bytes) >> > >> > Then i see these errors >> > >> > (ada0:ata0:0:0:0): ATA status error >> > .....READ_DMA. ACB: c8 .... >> > .....CAM status: ATA status error >> > .....ATA status: 51 (DRDY SERV ERR), error: 84 (ICRC ABRT) >> > .....RES: 51 ..... >> > >> > >> > As a result the disk is rendered unusable and i cannot write >> (partition) to >> > it. I did test the drive with a linux boot disk and i was able to >> format >> > it. >> > >> > So my question is how can i make this drive work? Do i need to pass >> > something to the kernel at boot to lower the speed of the drive. Maybe >> to >> > UDMA66? Any help will be really appreciated. >> >> Whenever I've seen ICRC errors, it has been caused by using a 40-wire >> cable at speeds faster than UDMA33 [1]. A potential fix is to force the >> mode in loader.conf: >> >> hint.ata.0.mode="UDMA33" >> >> [1] I've also seen ICRC errors when there was no cable involved at all, >> such as with a surface-mount compact flash socket on a circuit board >> that has 50 pins spaced even closer together than a standard ata cable. >> I have no real proof that such closely-spaced pins cause the same kind >> of signal crosstalk as a 40-wire cable (they're close, but the length of >> the parallel wires is just a couple millimeters), but forcing the driver >> to UDMA33 or less always seems to fix the problem. >> >> -- Ian >> >> >> >