Date: Thu, 29 Jun 2006 02:15:09 +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: <20060629021509.13ff7341@localhost> In-Reply-To: <20060628230255.M78211@fledge.watson.org> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060628235258.3414b074@localhost> <20060628230255.M78211@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Robert Watson <rwatson@FreeBSD.org> wrote: > On Wed, 28 Jun 2006, Fabian Keil wrote: > > > Robert Watson <rwatson@FreeBSD.org> wrote: > > > >> - Are there any warnings on the console from WITNESS or other > >> debugging options? > > > > I just got: > > > > Jun 28 23:01:19 tor kernel: lock order reversal: > > Jun 28 23:01:19 tor kernel: 1st 0xc3795000 kqueue (kqueue) > > Looks similar to <http://sources.zabbadoz.net/freebsd/lor.html#185>. > > Could you run "vmstat -z", "netstat -m", and "vmstat -m" please? I wish I could. The machine died before I read your message. I was logged in on the serial console running tail -f /var/log/messages. Last messages were: Jun 29 00:42:20 tor kernel: Memory modified after free 0xc4275000(2048) val=a020c0de @ 0xc4275000 Jun 29 00:42:20 tor kernel: Memory modified after free 0xc4055800(2048) val=a020c0de @ 0xc4055800 Jun 29 00:42:20 tor kernel: Memory modified after free 0xc4ca0000(2048) val=a020c0de @ 0xc4ca0000 Jun 29 00:42:20 tor kernel: Memory modified after free 0xc39ef000(2048) val=a020c0de @ 0xc39ef000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc4bd7000(2048) val=a020c0de @ 0xc4bd7000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc3c8a000(2048) val=a020c0de @ 0xc3c8a000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc33bd000(2048) val=a020c0de @ 0xc33bd000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc3f1d000(2048) val=a020c0de @ 0xc3f1d000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc45dc800(2048) val=a020c0de @ 0xc45dc800 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc429e000(2048) val=a020c0de @ 0xc429e000 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc3aef800(2048) val=a020c0de @ 0xc3aef800 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc432a000(2048) val=a020c0de @ 0xc432a000 Jun 29 00:42:24 tor kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=34263674 Jun 29 00:42:24 tor kernel: Memory modified after free 0xc3dff800(2048) val=a020c0d Ctrl+Alt+ESC didn't trigger any reaction, so I caused a reset through the ISP's webinterface. Now the system appears to be hosed, at least FreeBSD never reaches the login: 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 [nothing] Probably something which would be easy to resolve with keyboard access and a screen, but I think I'm forced to use the "RecoveryManager". Unfortunately "recovery" means reinstalling the preconfigured GNU/Linux which I than can replace with FreeBSD again. If there ever was a core dump it will be gone, and so will be kernel.debug. On the bright side you can chose the OS to go with. Should I use Current to see if the problem still exists? Fabian -- http://www.fabiankeil.de/ [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEoxuajV8GA4rMKUQRAt9OAJ9uga9zr6O0YvKWrDoZ0UNgcVNHOwCgrT/h XwUib09g4H8a7UjnVSD/0qg= =OOCb -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060629021509.13ff7341>