From owner-freebsd-stable@FreeBSD.ORG  Thu Mar 10 07:40:24 2005
Return-Path: <owner-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 D6F8416A4CE
	for <freebsd-stable@freebsd.org>;
	Thu, 10 Mar 2005 07:40:24 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A7B9743D2D
	for <freebsd-stable@freebsd.org>;
	Thu, 10 Mar 2005 07:40:24 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 9D59372DD4; Wed,  9 Mar 2005 23:40:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP id 9830972DCB;
	Wed,  9 Mar 2005 23:40:24 -0800 (PST)
Date: Wed, 9 Mar 2005 23:40:24 -0800 (PST)
From: Doug White <dwhite@gumbysoft.com>
To: "Jim C. Nasby" <decibel@decibel.org>
In-Reply-To: <20050309075111.GA528@decibel.org>
Message-ID: <20050309233948.L53915@carver.gumbysoft.com>
References: <20050309075111.GA528@decibel.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-stable@freebsd.org
Subject: Re: ad0 errors on FBSD 4.11-RELEASE
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Mar 2005 07:40:25 -0000

On Wed, 9 Mar 2005, Jim C. Nasby wrote:

> Since moving my machine, I've been having all kinds of issues with ad0.
> Here's one example:
>
> Mar  9 06:26:23 flake /kernel: ad0: READ command timeout tag=0 serv=1 - resetting
> Mar  9 06:26:23 flake /kernel: ad0: invalidating queued requests
> Mar  9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests
> Mar  9 06:26:23 flake /kernel: done
> Mar  9 06:26:23 flake /kernel: ad0: timeout waiting for READY
> Mar  9 06:26:23 flake /kernel: ad0: invalidating queued requests
> Mar  9 06:26:23 flake /kernel: ad0: timeout sending command=00 s=d0 e=04
> Mar  9 06:26:23 flake /kernel: ad0: flush queue failed
> Mar  9 06:26:23 flake /kernel: - resetting
> Mar  9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests
> Mar  9 06:26:23 flake /kernel: done
> Mar  9 06:26:23 flake /kernel: ad0: READ command timeout tag=0 serv=1 - resetting
> Mar  9 06:26:23 flake /kernel: ad0: invalidating queued requests
> Mar  9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests
> Mar  9 06:26:23 flake /kernel: done
> Mar  9 06:26:23 flake /kernel: ad0: WRITE command timeout tag=1 serv=0 - resetting
> Mar  9 06:26:23 flake /kernel: ad0: invalidating queued requests
> Mar  9 06:26:23 flake /kernel: ad0: timeout waiting for READY
> Mar  9 06:26:23 flake /kernel: ad0: invalidating queued requests
> Mar  9 06:26:23 flake /kernel: - resetting
> Mar  9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests
> Mar  9 06:26:23 flake /kernel: done
> Mar  9 06:26:23 flake /kernel: ata0: resetting devices .. ad0: invalidating queued requests
> Mar  9 06:26:23 flake /kernel: done
>
> These issues have been resulting in spontaneous reboots; presumably from
> kernel panics.

FreeBSD version in use and ATA hardware description would be nice. If this
is 4.x it looks like you have tagged queueing on; try turning it off.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org