From owner-freebsd-questions@FreeBSD.ORG Sun Apr 2 19:43:33 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 81B0A16A437 for ; Sun, 2 Apr 2006 19:43:33 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id B83D643D46 for ; Sun, 2 Apr 2006 19:43:06 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.4) with ESMTP id k32Jvu77066979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 2 Apr 2006 15:58:01 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-questions@freebsd.org Date: Sun, 2 Apr 2006 15:43:01 -0400 User-Agent: KMail/1.9.1 References: <5F1267A9-EAC2-4E6B-9F17-13827E40ADD4@shire.net> <20060331042659.45161.qmail@web51901.mail.yahoo.com> <3aaaa3a0604021222h663124f0t130a45ab2d395f65@mail.gmail.com> In-Reply-To: <3aaaa3a0604021222h663124f0t130a45ab2d395f65@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5943302.6OXTtWR4BT"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604021543.02376.mistry.7@osu.edu> X-Spam-Status: No, score=-5.1 required=5.0 tests=ALL_TRUSTED,BAYES_40, J_CHICKENPOX_23,MYFREEBSD2 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88/1367/Sun Apr 2 06:40:41 2006 on mail.united-ware.com X-Virus-Status: Clean Cc: Chris , eol1@yahoo.com 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: Sun, 02 Apr 2006 19:43:34 -0000 --nextPart5943302.6OXTtWR4BT Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 02 April 2006 15:22, Chris wrote: > On 31/03/06, Peter Thoenen wrote: > > Hallo everybody. Will prob end up PR'ing this but want to post > > to the list first and get some feelers. At first I thought it > > was just me but as the port maintainer for tor-devel I have had a > > couple other folk email me with the exact same problem (believing > > tor to be the cause). Its not. > > > > Problem: When tor (running in server mode), i2p, or freenet is > > ran (all high bandwidth, high number of concurrent tcp / udp / ip > > connections, maybe 2000+ sim connects @ a constant 4 mb) between > > the 2 and 4 hour mark a system running FBSD 6 will hard crash and > > power off. This is reproducible (though not on demand, just on > > arbitrary time between 2 and 4 hours). > > > > Troubleshooting so far: > > > > - It is NOT an issue on 5.x. It is an issue on both 6.0 and > > 6.1BETA4. > > > > > > - It is not easy to reproduce. I assume a couple hundred people > > use these ports and I have only had a dozen or so report this > > problem to me. All of the people suffering from this though CAN > > reproduce this crash on demand. I have to assume though the > > other 99% of users though do not see this error for unknown > > reasons. > > > > - It is not a port issue (as tor/i2p/freenet all can cause it).=20 > > It is not a java issue (was another early worry of mine but tor > > is written in C). > > > > - The hard crash does NOT generate a dump or panic for anybody I > > have spoken with. /var/crash comes up empty every time. Ok, so the machines hard lock and require power cycling them? I'd=20 advise throwing in a firewire card into one of these systems and=20 setup remote debugging. There should be some info on the web for=20 getting this setup. With the firewire debugging you should be able=20 to access the systems memory space remotely even if there is a hard=20 lock and the OS is not responding. I haven't setup this last part=20 myself, but I'm pretty sure I read it was possible. =2D-=20 Anish Mistry --nextPart5943302.6OXTtWR4BT Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEMClGxqA5ziudZT0RAhp9AJ9yAjOsLwnTL+UHrVhVcIq9jto/ZACfbQA8 wtAZXiUeA4IfhTphcyqwnio= =3Mu6 -----END PGP SIGNATURE----- --nextPart5943302.6OXTtWR4BT--