From owner-freebsd-sparc64@FreeBSD.ORG Fri Feb 6 23:27:57 2004 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 0226216A4CE for ; Fri, 6 Feb 2004 23:27:57 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDAD943D39 for ; Fri, 6 Feb 2004 23:27:56 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id D089072DC7; Fri, 6 Feb 2004 23:27:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id CEF1672DBF; Fri, 6 Feb 2004 23:27:56 -0800 (PST) Date: Fri, 6 Feb 2004 23:27:56 -0800 (PST) From: Doug White To: Phillip Walters In-Reply-To: <40214B33.7030005@linkline.com> Message-ID: <20040206232333.V20729@carver.gumbysoft.com> References: <40214B33.7030005@linkline.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "'freebsd-sparc64@freebsd.org'" Subject: Re: Watchdog Reset 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: Sat, 07 Feb 2004 07:27:57 -0000 On Wed, 4 Feb 2004, Phillip Walters wrote: > Hi All, > > I've got FreeBSD 5.2 installed on a SunFire v100. After a seemingly > random period of time, I always get the following: > > Watchdog Reset > Externally Initiated Reset This generally means there is a hardware problem with the system. Sun suggests running this at the ok prompt immediately following the failure to extract any messages (this may not work right with bsd): f8002010 wector p You may want to set the watchdog-reset? OBP variable to false so you can capture these better. Now this could be a bug in FreeBSD; the doc (InfoDoc 11371) mentions that these types of resets can happen if the CPU gets a trap when traps have been disabled. But my experience with sun hardware leans toward this being a hardware fault. > After this, I'm dropped to the 'ok' prompt where I can boot the machine > back up. Anyone have any clue what's going on here? You might try running max diagnostics, or put Solaris on the system and bang on it. If you can get Solaris to croak, that would tend to point at more of a hardware issue. > warning: no time-of-day clock registered, system time will not be set > accurately This is a wierd one. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org