From owner-freebsd-current@FreeBSD.ORG Wed Nov 7 16:14:47 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D180416A419; Wed, 7 Nov 2007 16:14:47 +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 DE83513C4B7; Wed, 7 Nov 2007 16:14:46 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 964D91CC07A; Wed, 7 Nov 2007 08:14:34 -0800 (PST) Date: Wed, 7 Nov 2007 08:14:34 -0800 From: Jeremy Chadwick To: "Aryeh M. Friedman" Message-ID: <20071107161434.GA32044@eos.sc1.parodius.com> References: <20071106153509.GB91218@eos.sc1.parodius.com> <47308E19.70507@samsco.org> <47315094.6080405@yandex.ru> <47315158.5090304@gmail.com> <4731A755.7060701@yandex.ru> <4731AEE8.70606@gmail.com> <4731AFA5.9090104@gmail.com> <20071107160212.GA31717@eos.sc1.parodius.com> <4731E269.6000701@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4731E269.6000701@gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: d@delphij.net, Justin Hibbits , freebsd-current@freebsd.org, "Andrey V. Elsukov" , "Sean C. Farley" , S?ren Schmidt Subject: Re: [ANNOUNCEMENT] Wiki for discussing P35/IHC9(R)/SATA issues set up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2007 16:14:47 -0000 On Wed, Nov 07, 2007 at 11:06:01AM -0500, Aryeh M. Friedman wrote: > Jeremy Chadwick wrote: > > This is a separate issue, and as I mentioned somewhere else in the > > thread, happens on numerous hardwares of all kinds. > As I remember correctly you mentioned it as a annonyance for > cluttering up the log files not in the context of complete > impossibility to r/w anything from acd0 due to timeouts... namely you > got errornous error messages that had no real effect on actual > functionality; the issue I was confirming prevents any use of acd0 > (or even booting if there is a cd in the drive) What I said was two lines: "The SATA ATAPI errors you see are something I can't really help with, many see these kinds of messages on all sorts of hardware." Although I am curious to know what happens if you take that SATA ATAPI drive and replace it with another SATA ATAPI drive of a different brand, such as Plextor or Pioneer. Most of the ATAPI errors I've seen have been caused by ATAPI devices which simply don't implement specific ATAPI commands. FreeBSD is fairly verbose about reporting such. -- | 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 |