Date: Fri, 24 Apr 2009 10:49:00 +0200 From: Gary Jennejohn <gary.jennejohn@freenet.de> To: Pierre Guinoiseau <geekounet@poildetroll.net> Cc: pluknet <pluknet@gmail.com>, Michael Butler <imb@protected-networks.net>, freebsd-current@freebsd.org Subject: Re: 'sysctl -a | less' crashes -current Message-ID: <20090424104900.579dfa41@ernst.jennejohn.org> In-Reply-To: <49F16F9E.40306@poildetroll.net> References: <49F12578.4060609@protected-networks.net> <200904241248.16562.doconnor@gsoft.com.au> <a31046fc0904232211r3a08647dte616b3ca38cf2c2f@mail.gmail.com> <49F16F9E.40306@poildetroll.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 24 Apr 2009 09:51:58 +0200 Pierre Guinoiseau <geekounet@poildetroll.net> wrote: > The same from 18th. > > pluknet wrote: > > 2009/4/24 Daniel O'Connor <doconnor@gsoft.com.au>: > >> On Fri, 24 Apr 2009, Michael Butler wrote: > >>> I can't seem to get a dump from this :-( The noted command either > >>> hangs or reboots a kernel built on April 24th. > >>> > >>> I'll rebuild with KDB to see what else I can find out .. > >> Works OK on mine from 5th Apr. (to give you a bookend if you're binary > >> searching :) > >> > > > > Even one from 16th does okey. > > > [sysctl -a causes a crash dump] I saw this yesterday also. It turned out that I had an old kqemu.ko loaded. Removing it eliminated the crash. If you're using modules, especially from ports, then make sure they're up-to-date with your kernel sources. I got the idea for this from a mail which Robert Watson posted. --- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090424104900.579dfa41>