From owner-freebsd-stable@FreeBSD.ORG Mon May 12 05:54:07 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FB22106566C for ; Mon, 12 May 2008 05:54:07 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0B2768FC0C for ; Mon, 12 May 2008 05:54:06 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id EAE9B1CC033; Sun, 11 May 2008 22:54:06 -0700 (PDT) Date: Sun, 11 May 2008 22:54:06 -0700 From: Jeremy Chadwick To: dikshie Message-ID: <20080512055406.GA1333@eos.sc1.parodius.com> References: <910e60e80805112117j1ecb83b4s4cdb62eafbdf748f@mail.gmail.com> <20080512051142.GA99535@eos.sc1.parodius.com> <910e60e80805112214p5a03b6fcn73ea1c5ebf70baab@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <910e60e80805112214p5a03b6fcn73ea1c5ebf70baab@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: any available patches for sata: "ad4: warning - setfeatures set transfer mode taskqueue timeout - completing request directly" 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: Mon, 12 May 2008 05:54:07 -0000 On Mon, May 12, 2008 at 02:14:37PM +0900, dikshie wrote: > On Mon, May 12, 2008 at 2:11 PM, Jeremy Chadwick wrote: > > On Mon, May 12, 2008 at 01:17:16PM +0900, dikshie wrote: > >> and strange output from dmesg: > >> ad4: 305245MB at ata2-master UDMA33 > >> ^^^^^^^^^^^ > >> any available patches ? > > > > What's strange about this? > > i mean for "UDMA33" it should be SATA300 > do have to upgrade BIOS? Your carets are pointing to the drive firmware revision, which is why I was confused. :-) Yes, it should say either SATA150 or SATA300 (more on that in a moment), but based on your dmesg output, it appears your SATA controller does not have an attached driver, thus is operating generically. Andrey recommended showing pciconf -lv output; please do. Your drive is *probably* operating in SATA150/300 mode, despite UDMA33 being printed, however. Assuming you know your disk can push >33MB/sec, you could try some simple read I/O and use gstat to watch the speed. dd if=/dev/ad4 of=/dev/null bs=1m should suffice. Regarding SATA150 vs. SATA300: your drive has a physical jumper, labelled OPT1 in the below photo, which limits the drive to SATA150 capability. You can remove this jumper and get SATA300. This doesn't explain the UDMA33 issue, though. http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1400&p_created=1134597011 Also, please don't remove the mailing list from the CC; others need to know what information you've provided, and future users may find this thread useful. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |