From owner-freebsd-stable@FreeBSD.ORG Mon Jul 23 03:24:44 2007 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 E1B5A16A417 for ; Mon, 23 Jul 2007 03:24:44 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id 94ADA13C458 for ; Mon, 23 Jul 2007 03:24:44 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id l6N3Oh0G055234; Sun, 22 Jul 2007 23:24:43 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id l6N3Oht7042841 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 22 Jul 2007 23:24:43 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200707230324.l6N3Oht7042841@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 22 Jul 2007 23:24:32 -0400 To: Dmitry Morozovsky From: Mike Tancsa In-Reply-To: <20070723005933.Y51455@woozle.rinet.ru> References: <46A35EE6.6030902@incunabulum.net> <200707221437.l6MEbCCP039856@lava.sentex.ca> <20070723005933.Y51455@woozle.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: Help! My laptop drive may be dying. 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, 23 Jul 2007 03:24:45 -0000 At 04:59 PM 7/22/2007, Dmitry Morozovsky wrote: >On Sun, 22 Jul 2007, Mike Tancsa wrote: >OK) >MT> remind me of a bad cable/connector. Have you tried a new cable ? > >Hmm, in a laptop? ;) Details :) Dirty or weak connection point ? If the controller was working well up until this point, it doesnt sound like a driver bug. ---Mike