Date: Sun, 19 Sep 2004 13:58:29 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: NetAdmin <daemon@foxchat.net> Cc: freebsd-questions@freebsd.org Subject: Re: panic: rtqkill route really not free Message-ID: <20040919125829.GI51161@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <1095572412.59753.18.camel@foxdaemon.com> References: <1095572412.59753.18.camel@foxdaemon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--zgY/UHCnsaNnNXRx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Sep 19, 2004 at 01:40:12AM -0400, NetAdmin wrote:
> I'm running FreeBSD 4.10-RELEASE-p2 and today was the second time in 3
> days that my box has rebooted with (panic: rtqkill route really not
> free). I've looked on the web but can't find anything relevant. Has
> anyone else run across this? If so, could you point me to some help in
> trying to figure out how to correct it?
Take a look at=20
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ke=
rneldebug.html
If you can configure your system to preserve a crash dump and extract
from it a backtrace which you then use send-pr(1) to send in, you
should find a developer willing to help you.
See also Michael Lucas' Big Scary Daemon articles:
http://www.oreillynet.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html
http://www.oreillynet.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html
However, crash bugs like this do not appear spontaneously: something
in your environment changed to cause the problem. A prime suspect
would be hardware failure -- if you have the resources to do so, try
swapping out components to see if you can isolate the problem. Don't
forget to swap out the simplest parts, like network cables. Another
prime suspect would be recent changes made to the configuration of
your system or the network it is attached to. Given the nature of the
panic, changes to the way routing is done would be a good place to
start investigating. (Nb. if it turns out to be a change that someone
else made on a machine elsewhere on your network, then reporting the
problem to the FreeBSD developers would become imperative: remote
crash bugs are very bad news indeed)
This topic is best dealt with on the freebsd-stable@... list -- please
post any follow up there. (Reply-to: set appropriately).
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--zgY/UHCnsaNnNXRx
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)
iD8DBQFBTYJ1iD657aJF7eIRAuoHAJ41JdFWZ9wwRJ6NNMA5cZdDGFePwQCgsS75
+QhMCddVR/wX2gHPod0oqyc=
=b5Vs
-----END PGP SIGNATURE-----
--zgY/UHCnsaNnNXRx--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040919125829.GI51161>