Date: Sun, 2 Jul 2006 18:24:47 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Fabian Keil <freebsd-listen@fabiankeil.de> Cc: Peter Thoenen <peter.thoenen@yahoo.com>, freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) Message-ID: <20060702182302.H80381@fledge.watson.org> In-Reply-To: <20060702190520.3b344c83@localhost> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060702173338.00a5ed44@localhost> <20060702170843.C67344@fledge.watson.org> <20060702190520.3b344c83@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2 Jul 2006, Fabian Keil wrote: > 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? >> >> 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. You probably need to find out in order to find out what break sequence to send. Alternatively, you can use ALT_BREAK_TO_DEBUGGER, which defines an alternative break sequence without relying on a serial break (which is an out-of-band break signal). >> 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 > | It sounds like your serial console server may not know how to map SSH break signals into remote serial break signals. Try ALT_BREAK_TO_DEBUGGER. Here's the description from NOTES: # Solaris implements a new BREAK which is initiated by a character # sequence CR ~ ^b which is similar to a familiar pattern used on # Sun servers by the Remote Console. options ALT_BREAK_TO_DEBUGGER Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060702182302.H80381>