From owner-freebsd-questions@FreeBSD.ORG Sun Jul 19 22:13:50 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B1B41065687 for ; Sun, 19 Jul 2009 22:13:50 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (unknown [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 2388B8FC1D for ; Sun, 19 Jul 2009 22:13:50 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n6JMDn1l030071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 19 Jul 2009 15:13:49 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n6JMDnjQ030070; Sun, 19 Jul 2009 15:13:49 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA03067; Sun, 19 Jul 09 15:07:48 PDT Date: Sun, 19 Jul 2009 15:05:06 -0700 From: perryh@pluto.rain.com To: jwdevel@gmail.com Message-Id: <4a639892./fy8MOPpWFzE9if0%perryh@pluto.rain.com> References: <20090719082502.92d8b144.freebsd@edvax.de> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Strange (repeatable) hang when ripping a CD X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2009 22:13:50 -0000 jw wrote: > On Sat, Jul 18, 2009 at 11:25 PM, Polytropon wrote: > > Maybe wrong cable (40 pin)? The "device detached" message > > doesn't look good. First of all, it shouzld at least be UDMA66. > > Maybe defective drive due to failing TUR taskqueuing? > > Wow, thanks for the 'bad cable' idea. I replaced the (brand new) > cable and it's working, now. Previously, it was the right kind, > it must have just been flakey. You might want to give that brand-new "bad" cable another try before tossing it. It may just not have been plugged in quite all the way at one connector or another (e.g. 39 of 40 pins making contact).