From owner-freebsd-current@FreeBSD.ORG Mon Oct 11 14:25:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57E1E16A4CE for ; Mon, 11 Oct 2004 14:25:45 +0000 (GMT) Received: from mail.vtec.ipme.de (Ad6ac.a.pppool.de [213.6.214.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 083C943D1F for ; Mon, 11 Oct 2004 14:25:42 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from [192.168.16.24] (unknown [192.168.16.24]) by bellona.sz.vwsoft.com (Postfix) with ESMTP id EEFC75CF2 for ; Mon, 11 Oct 2004 16:25:37 +0200 (CEST) Message-ID: <416A97E1.70603@vwsoft.com> Date: Mon, 11 Oct 2004 16:25:37 +0200 From: Volker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040822 Thunderbird/0.7+ Mnenhy/0.6.0.101 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: beta6/7 machine freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2004 14:25:45 -0000 Hi folks! Back from a one week vacation, I immediately updated my machine to BETA 7. Before I left, my machine had panics serveral times a day. Since BETA 6 the panics are gone but the machine locked up a few times (experienced two days before I left for a week). The machine freeze has been mostly while hanging up or shortly after a ppp (userland) connection has been hang up. Now I've updated to BETA 7 and the machine seem to lock up faster. The machine freezes most times while having an established ppp connection to the public internet. The machine is acting as a router, dial-up client, proxy, mailserver, webserver etc. etc. When the machine locks up, there's no console or network response from the machine. The only way out is the reset switch. One of my guesses has been that either i4b or userland ppp is causing the machine freeze. To figure out if that might be the case, I've set up a 2nd machine (releng_4) acting as a dial-up client (i4b/ppp) and router. The 2nd machine is now being used as a default route for the server machine. Since using that test setup the server machine didn't had a lockup. So my guess might be probably right to have a problem somewhere at i4b or user-ppp in releng_5. How does one debug a dead machine? Is there any way to get a backtrace or call the debugger while the machine has been frozen? Thanks, Volker -- GPG/PGP fingerprint: FF93 13A1 2477 B631 E953 06DF 4C49 ADD9 E4BF 79B1