From owner-freebsd-sparc64@FreeBSD.ORG Wed Sep 3 09:55:30 2003 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D13F16A4BF for ; Wed, 3 Sep 2003 09:55:30 -0700 (PDT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 09D7D43FAF for ; Wed, 3 Sep 2003 09:55:27 -0700 (PDT) (envelope-from tmoestl@gmx.net) Received: (qmail 21863 invoked by uid 65534); 3 Sep 2003 16:55:25 -0000 Received: from p508E7DCD.dip.t-dialin.net (EHLO timesink.dyndns.org) (80.142.125.205) by mail.gmx.net (mp002) with SMTP; 03 Sep 2003 18:55:25 +0200 Received: by galatea (Postfix, from userid 1001) id CB4BECD; Wed, 3 Sep 2003 18:55:49 +0200 (CEST) Date: Wed, 3 Sep 2003 18:55:49 +0200 From: Thomas Moestl To: Chris Jackman , freebsd-sparc64@freebsd.org Message-ID: <20030903165549.GA20825@timesink.dyndns.org> Mail-Followup-To: Chris Jackman , freebsd-sparc64@freebsd.org References: <20030721194436.GA42900@collab.or8.net> <20030721224708.GB768@crow.dom2ip.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030721224708.GB768@crow.dom2ip.de> User-Agent: Mutt/1.4.1i Subject: Re: correctable DMA error AFAR X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2003 16:55:30 -0000 On Tue, 2003/07/22 at 00:47:08 +0200, Thomas Moestl wrote: > On Mon, 2003/07/21 at 15:44:36 -0400, Chris Jackman wrote: > > My e250 has locked up twice in the last few weeks with these > > error messages. The error gets repeated over and over > > again on the serial console, and I can't do anything to the > > box except power cycle it. > > This interrupt is informational only, and the documentation states > that no further cleanup is required. We should probably clear the > error bits in the status register however, since this looks like the > interrupt being triggered again and again when any bits are still > set. The manual is a bit ambiguous on that point, but clearing the > bits is desirable anyway since it improves error reporting. > > The attached patch implements this; can you please try it and report > how well it behaved on the next ECC error? So, did you see such errors again, and if so, did the patch fix the lockups? Thanks, - Thomas -- Thomas Moestl http://www.tu-bs.de/~y0015675/ http://people.FreeBSD.org/~tmm/ PGP fingerprint: 1C97 A604 2BD0 E492 51D0 9C0F 1FE6 4F1D 419C 776C