From owner-freebsd-stable@FreeBSD.ORG Sat May 28 12:30:42 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A02A116A421 for ; Sat, 28 May 2005 12:30:42 +0000 (GMT) (envelope-from robbak@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49FA543D49 for ; Sat, 28 May 2005 12:30:42 +0000 (GMT) (envelope-from robbak@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so1878250wri for ; Sat, 28 May 2005 05:30:41 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gLnRwFUXppHnyWmk8JxKGW9bpY46bUrc16JX5cscc08fHMziXxL4AUfTKJHDy9xCmL1EgU5g0gjS1DYT3coEc1tQcWg2IIEcjNFRcXDWyCujLXl94r1310zzv7ZRoTG2BGap3J8uHpfLO+A4DxzP+3TfGbJ5kbs2h1f5m34HpNY= Received: by 10.54.49.26 with SMTP id w26mr3388644wrw; Sat, 28 May 2005 05:30:41 -0700 (PDT) Received: by 10.54.130.5 with HTTP; Sat, 28 May 2005 05:30:41 -0700 (PDT) Message-ID: Date: Sat, 28 May 2005 22:30:41 +1000 From: Robert Backhaus To: Tony Byrne In-Reply-To: <1936063736.20050526220424@byrnehq.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1936063736.20050526220424@byrnehq.com> Cc: freebsd-stable@freebsd.org Subject: Re: ATA Timeouts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robert Backhaus List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 May 2005 12:30:42 -0000 > I temporarily moved the disk to a recent 5.4 desktop machine equipped > with the same chipset and the timeouts stopped, so it appears that the > problem is not with the disk. So the problem exists on 5.S and not on 5.4-RELEASE? or is it vice versa?