Date: Fri, 7 Jul 2006 14:34:36 +0200 From: Fabian Keil <freebsd-listen@fabiankeil.de> To: freebsd-stable@freebsd.org Cc: Peter Thoenen <peter.thoenen@yahoo.com>, Robert Watson <rwatson@FreeBSD.org> Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) Message-ID: <20060707143436.3716f63c@localhost> In-Reply-To: <20060703112705.0da6a071@localhost> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060702173338.00a5ed44@localhost> <20060702170843.C67344@fledge.watson.org> <20060702190520.3b344c83@localhost> <20060702182302.H80381@fledge.watson.org> <20060702212335.0bf121be@localhost> <20060703112705.0da6a071@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_rOmSZeS.=Tok48PT5q5OvEt Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Fabian Keil <freebsd-listen@fabiankeil.de> wrote: > Fabian Keil <freebsd-listen@fabiankeil.de> wrote: >=20 > > Robert Watson <rwatson@FreeBSD.org> wrote: >=20 > > > 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: > > >=20 > > > # 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 > >=20 > > It took me several attempts to get the character sequence right, > > but yes, this one works. Thanks. >=20 > Unfortunately it didn't work while the system was hanging > this morning. Since then I got one or two hangs a day and entering the debugger never worked out, even if my console connection was opened a few minutes before the hang. I no longer think it has anything to do with the terminal server, but assume the hang takes the console with it. sio0 is running on acpi0, so I tried to disable acpi to see if it changes anything, but the only change I got was that fxp0 stopped working (it is up but only produces timeout warnings). I tried to partly disable acpi subsystems like described in acpi(4), but either I got the syntax wrong, or it just isn't working. Can someone on this list confirm or deny if something like debug.acpi.disabled=3Disa in /boot/loader.conf makes sense? That's how I understand the man page, but I don't see any reaction. I also tried /etc/sysctl.conf (which probably is parsed too late anyway) but I just got a message that the sysctl does not exists. sysctl debug.acpi indeed only shows: debug.acpi.do_powerstate: 1 debug.acpi.acpi_ca_version: 0x20041119 debug.acpi.semaphore_debug: 0 so maybe I need some special acpi options or it just doesn't work if acpi is loaded as a module, but as least the man page has no such hints. Fabian --=20 http://www.fabiankeil.de/ --Sig_rOmSZeS.=Tok48PT5q5OvEt Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFErlTjjV8GA4rMKUQRApNNAJsH09z9tikl6IUiGrRinlnBq7MsBgCcDTVB zGUFzqf/s1gt2Laewkkc1cc= =n6nj -----END PGP SIGNATURE----- --Sig_rOmSZeS.=Tok48PT5q5OvEt--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060707143436.3716f63c>