From owner-freebsd-stable@FreeBSD.ORG Wed Sep 22 15:29:14 2004 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 5542516A4DE for ; Wed, 22 Sep 2004 15:29:14 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DEB843D39 for ; Wed, 22 Sep 2004 15:29:14 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from mailnull by anduin.net with dspam-scanned (Exim 4.42 (FreeBSD)) id 1CA915-0006j6-VI for stable@freebsd.org; Wed, 22 Sep 2004 17:26:47 +0200 Received: from mailnull by anduin.net with spamassassin-scanned (Exim 4.42 (FreeBSD)) id 1CA911-0006ix-1I for stable@freebsd.org; Wed, 22 Sep 2004 17:26:47 +0200 Received: from eirik.unicore.no ([213.225.74.166] helo=[10.0.16.10]) by anduin.net with esmtp (Exim 4.42 (FreeBSD)) id 1CA910-0006iu-VA for stable@freebsd.org; Wed, 22 Sep 2004 17:26:43 +0200 Message-ID: <41519A92.3070503@anduin.net> Date: Wed, 22 Sep 2004 17:30:26 +0200 From: Eirik Oeverby User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040922) X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on anduin.net X-Spam-Level: X-Spam-Status: No, hits=-3.9 required=7.5 tests=AWL,BAYES_00 autolearn=ham version=2.64 Subject: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2004 15:29:14 -0000 Hi all, 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. Can someone in-the-know tell me what exactly these errors mean, and what they might indicate? Ofcourse this MIGHT be the cause of my problems, but I don't know that for sure, and I'd like to know if there are any other plausible explanations for these errors... I will obviously disable the onboard adaptec at the earliest convenience. This is an ASUS P2B-DS board, dual p3 with onboard u2w scsi. Anyone? Thanks, /Eirik