From owner-freebsd-stable@FreeBSD.ORG  Thu Sep 23 02:15:19 2004
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 EAB0316A4D0
	for <stable@freebsd.org>; Thu, 23 Sep 2004 02:15:19 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CB52743D41
	for <stable@freebsd.org>; Thu, 23 Sep 2004 02:15:19 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id C25E272DD4; Wed, 22 Sep 2004 19:15:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP id C125372DCB;
	Wed, 22 Sep 2004 19:15:19 -0700 (PDT)
Date: Wed, 22 Sep 2004 19:15:19 -0700 (PDT)
From: Doug White <dwhite@gumbysoft.com>
To: Eirik Oeverby <ltning@anduin.net>
In-Reply-To: <41519A92.3070503@anduin.net>
Message-ID: <20040922191436.A36124@carver.gumbysoft.com>
References: <41519A92.3070503@anduin.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: stable@freebsd.org
Subject: Re: Obscure errors in dmsg, system instability
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, 23 Sep 2004 02:15:20 -0000

On Wed, 22 Sep 2004, Eirik Oeverby wrote:

> for some time I have been experiencing weird hangs on one of my servers.
> When it happens, I can still ping it, but I cannot make any connections
> or type anything on existing ssh connections. Serial console is also
> dead, however I can enter the kernel debugger and call cpu_reset() to
> reboot. Upon reboot all is fine again.
>
> Now I discover that my dmsg output contains a few of these:
>
> ahc0: PCI error Interrupt at seqaddr = 0x9
> ahc0: Data Parity Error Detected during address or write data phase
>
> and
>
> ahc0: PCI error Interrupt at seqaddr = 0x8
> ahc0: Data Parity Error Detected during address or write data phase
>
> Thing is - there's nothing connected to the Adaptec. It is enabled, but
> not used.

Is something sharing an interrupt with that device?

PCI bus errors are generally Bad News .. either some device or the mobo is
inroducing errors.

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