Date: Mon, 11 Oct 2004 17:08:41 +0200 From: Max Laier <max@love2party.net> To: freebsd-current@freebsd.org Cc: Volker <volker@vwsoft.com> Subject: Re: beta6/7 machine freeze Message-ID: <200410111708.48663.max@love2party.net> In-Reply-To: <416A97E1.70603@vwsoft.com> References: <416A97E1.70603@vwsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart4127795.dkvV9YoiCe Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 11 October 2004 16:25, Volker wrote: > 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. Guess at large, are you using any IPFW uid/gid/jail rules or PF user/group= =20 rules? If so, you must deactivate debug.mpsafenet (=3D0) in the loader. Thi= s is=20 something you can try in any case. > When the machine locks up, there's no console or network response from > the machine. The only way out is the reset switch. You might want to build a custom kernel with WITNESS turned on and KDB, DDB= =20 built in. That way you will get warnings for lock order reversals, that can= =20 be the source of a hard lockup. > 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 =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart4127795.dkvV9YoiCe Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBaqIAXyyEoT62BG0RAutTAJ44Yv03UQhDvybKrHaxCvYDV18NdwCfXerX HmEOt6EnPy7y2oLVqnShRtY= =s4pv -----END PGP SIGNATURE----- --nextPart4127795.dkvV9YoiCe--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410111708.48663.max>