Date: Sun, 2 Jul 2006 17:33:38 +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: <20060702173338.00a5ed44@localhost> In-Reply-To: <20060628101729.J50845@fledge.watson.org> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_wzkp/wo_80Zh=okBSNrSOZJ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Robert Watson <rwatson@FreeBSD.org> wrote: > On Tue, 27 Jun 2006, Fabian Keil wrote: >=20 > > There was a "request" for Tor related problem reports a while ago, > > I couldn't find the message again, but I believe it was posted here. >=20 > I'm very interested in tracking down this problem, but have had a lot > of trouble getting reliable reports of problems -- i.e., ones where I > could get any debugging information. I had a similar conversation on > these lines yeterday with Roger (Tor author) here at the WEIS > conference. If this is easily reproduceable, I would like you to do > the following: > - Does the hang occur? If so, use a serial break to get into DDB, > see the above. I previously had the serial console misconfigured and I'm still not sure if the settings are correct now. So far I put "BOOT_COMCONSOLE_SPEED=3D57600" in /etc/make.conf, "options CONSPEED=3D57600" in the kernel and "console=3Dcomconsole" in /boot/loader.conf. Kernel and bootblock were recompiled and reinstalled. /boot.config contains the line: "-D -h -S57600" (speed setting through make.conf didn't work). The boot process now starts with: PXELINUX 3.11 2005-09-02 Copyright (C) 1994-2005 H. Peter Anvin Booting from local disk... 1 Linux 2 FreeBSD 3 FreeBSD Default: 2=20 /boot.config: -DConsoles: internal video/keyboard serial port =20 BIOS drive C: is disk0 BIOS 639kB/523200kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 [...] 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? Fabian --=20 http://www.fabiankeil.de/ --Sig_wzkp/wo_80Zh=okBSNrSOZJ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEp+dbjV8GA4rMKUQRAkYlAKCyHy/njIji95D/ykRI1C/yps0b9gCeIP/W IDstMpVovLqA6WkSiBXotQk= =oBO1 -----END PGP SIGNATURE----- --Sig_wzkp/wo_80Zh=okBSNrSOZJ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060702173338.00a5ed44>