From owner-freebsd-questions@FreeBSD.ORG Mon Apr 10 05:28:12 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5536A16A402 for ; Mon, 10 Apr 2006 05:28:12 +0000 (UTC) (envelope-from duane@greenmeadow.ca) Received: from smtpout.eastlink.ca (smtpout.eastlink.ca [24.222.0.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8098F43D7B for ; Mon, 10 Apr 2006 05:28:11 +0000 (GMT) (envelope-from duane@greenmeadow.ca) Received: from ip03.eastlink.ca ([24.222.10.15]) by mta01.eastlink.ca (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0IXH00MT5R755NW0@mta01.eastlink.ca> for freebsd-questions@freebsd.org; Mon, 10 Apr 2006 02:28:17 -0300 (ADT) Received: from blk-224-199-230.eastlink.ca (HELO [192.168.0.103]) ([24.224.199.230]) by ip03.eastlink.ca with ESMTP; Mon, 10 Apr 2006 02:28:10 -0300 Date: Mon, 10 Apr 2006 02:27:19 -0300 From: Duane Whitty In-reply-to: <20060410040401.79401.qmail@web51901.mail.yahoo.com> To: eol1@yahoo.com Message-id: <4439ECB7.6090803@greenmeadow.ca> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAQAAA+k= References: <20060410040401.79401.qmail@web51901.mail.yahoo.com> User-Agent: Thunderbird 1.5 (X11/20060309) Cc: Chris , freebsd-questions@freebsd.org, Kris Kennaway Subject: Re: Hard crash on 6.x -- reproducible, multiple people affected X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2006 05:28:12 -0000 Peter Thoenen wrote: > --- Kris Kennaway wrote: > >> On Sun, Apr 02, 2006 at 04:09:30PM -0400, Anish Mistry wrote: >> >>>> It's not clear what he means by "hard crash", but he also says >>>> power off", which is the part that is most confusing to me. >>>> >>> Hmmm...I missed that part. Yeah, if it powers off then I'm not >>> >> sure what you can do to debug it. >> > > By hard crash I mean the box just instantly powers off. No shutdown > syncs, no error, panic's, or dump generated, nothing logged in syslog, > and I have a serial cable hooked up to another another dumb terminal > hoping to maybe catch a panic or some debug message dumped out over > serial as it goes down but nothing there also. It just stops. > > Also note that this didn't happen on 5.x. And when not running those > particular ports the box stays up just fine for weeks on end. Just > tried again with 6.1 PRERELEASE and same issue. > > >> About all I can think of is to try to reproduce the problem with >> enough logging enabled (e.g. running the binary under ktrace), with >> sync-mounted filesystem, and hope that the last few entries give the >> software developer enough of a clue what the process was doing at the >> time of shutdown (the operation itself probably will not be logged) >> that he can focus the investigation further. >> > > Want to walk me through this and will do. As I said, reproducible. > > NOTE: I doubt it a linux syscall issue as i2p / freenet / and tor are > all build on FBSD, not linux binaries. Freenet and I2P do use > linux-java (as the new diablo ones aren't avaiable for amd64) BUT tor > does not. Its all C. Also as noted, other people (using i386, not > just amd64) have emailed me (as the tor maintainer) with the exact same > problem on entirely different hardware (different nics, motherboards, > proc's etc etc). Somebody suggested maybe a ACPI issue but I just > don't see how that could me it. > > _______________________________________________ > > Anyone got a hardware debugger (breakout box) they know how to use? I don't hear much about them anymore but I think this is the kind of problem they were useful for helping with. Maybe I'm thinking of something else, its been a long time. Duane -- duane@greenmeadow.ca