From owner-freebsd-stable@FreeBSD.ORG Sun Jul 2 17:05:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C04616A403 for ; Sun, 2 Jul 2006 17:05:32 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FAC444555 for ; Sun, 2 Jul 2006 17:05:31 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 19200 invoked from network); 2 Jul 2006 17:05:29 -0000 Received: from unknown (HELO localhost) (775067@[217.50.151.147]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 2 Jul 2006 17:05:29 -0000 Date: Sun, 2 Jul 2006 19:05:20 +0200 From: Fabian Keil To: Robert Watson Message-ID: <20060702190520.3b344c83@localhost> In-Reply-To: <20060702170843.C67344@fledge.watson.org> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060702173338.00a5ed44@localhost> <20060702170843.C67344@fledge.watson.org> X-Mailer: Sylpheed-Claws 2.2.3 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_8.6DL+reQjOqcr=ZPMylzXF"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Peter Thoenen , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 17:05:32 -0000 --Sig_8.6DL+reQjOqcr=ZPMylzXF Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Robert Watson wrote: > On Sun, 2 Jul 2006, Fabian Keil wrote: > > After manually triggering a test panic through debug.kdb.enter I > > could enter ddb and everything seemed to be working. > > > > However today I got another hang and couldn't enter the debugger by > > sending BREAK. It is the same BREAK ssh sends with ~B, right? > > > > Even after rebooting, sending break didn't trigger a panic, so > > either I'm sending the wrong BREAK, or my console settings are > > still messed up. Any ideas? >=20 > What serial software are you using to reach the console? I use ssh to log in to a console server, hit enter and am connected to the console. I have no idea what kind of software is used between console server and console. > Do you have options BREAK_TO_DEBUGGER compiled into your kernel? Yes, together with the other options you suggested: makeoptions DEBUG=3D-g options DDB #options KDB_UNATTENDED options KDB options BREAK_TO_DEBUGGER options WITNESS options WITNESS_SKIPSPIN options INVARIANTS options INVARIANT_SUPPORT > The delivery mechanism for the break will depend on the software > you're using... The ssh man page offers: |~B Send a BREAK to the remote system (only useful for SSH protocol | version 2 and if the peer supports it). I am using ssh 2, but the only reaction I get is a new line. |FreeBSD/i386 (tor.fabiankeil.de) (ttyd0) | |login: ~B | Maybe machdep.enable_panic_key would be another solution? The description says "Enable panic via keypress specified in kbdmap(5)", I'm just not sure if console input qualifies as "keypress". Fabian --=20 http://www.fabiankeil.de/ --Sig_8.6DL+reQjOqcr=ZPMylzXF Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEp/zWjV8GA4rMKUQRAj1aAKDpYy4TQaaNZKqbyU7czMvH60btmACg4RvR N0xpH+pDPZhKI48eL7uNHW4= =dA7g -----END PGP SIGNATURE----- --Sig_8.6DL+reQjOqcr=ZPMylzXF--