Date: Sun, 2 Jul 2006 19:05:20 +0200 From: Fabian Keil <freebsd-listen@fabiankeil.de> To: Robert Watson <rwatson@FreeBSD.org> Cc: Peter Thoenen <peter.thoenen@yahoo.com>, freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_8.6DL+reQjOqcr=ZPMylzXF Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Robert Watson <rwatson@FreeBSD.org> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060702190520.3b344c83>