From owner-freebsd-stable@FreeBSD.ORG Wed Mar 9 07:51:15 2005 Return-Path: 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 92DC216A4CE for ; Wed, 9 Mar 2005 07:51:15 +0000 (GMT) Received: from flake.decibel.org (flake.decibel.org [67.100.216.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B3A443D31 for ; Wed, 9 Mar 2005 07:51:15 +0000 (GMT) (envelope-from decibel@decibel.org) Received: by flake.decibel.org (Postfix, from userid 1001) id 517011C91C; Wed, 9 Mar 2005 07:51:11 +0000 (GMT) Date: Wed, 9 Mar 2005 01:51:11 -0600 From: "Jim C. Nasby" To: freebsd-stable@freebsd.org Message-ID: <20050309075111.GA528@decibel.org> Mail-Followup-To: "Jim C. Nasby" , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 4.11-RELEASE i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.6i Subject: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2005 07:51:15 -0000 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. Any ideas what could be causing this? I'm running vinum, if that matters. I guess if I need to I can run both drives off the second IDE controller... is there any magic I'd need to do in vinum to accomplish that? -- Jim C. Nasby, Database Consultant decibel@decibel.org Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"