Date: Wed, 01 Jul 2009 16:25:38 +0200 From: Ian FREISLICH <ianf@clue.co.za> To: Thomas Backman <serenity@exscape.org> Cc: current@freebsd.org Subject: Re: kgdb on an amd64 kernel anyone? Message-ID: <E1MM0kk-0004JU-1X@clue.co.za> In-Reply-To: <3EF4C954-2A84-42BA-B0F5-629B3CCC1578@exscape.org> References: <3EF4C954-2A84-42BA-B0F5-629B3CCC1578@exscape.org> <E1MM0Co-0004BT-Jb@clue.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
Thomas Backman wrote: > On Jul 1, 2009, at 03:50 PM, Ian Freislich wrote: > > > > The last useful crashdump I've had was before February this year. > > Do others share this experience? > > I haven't had any such problems. I do often get a "broken stack?" > following the rest of the BT, but they're generally useful anyway, and > I've never ever seen "Attempt to extract a component of a value that > is not a structure pointer" before. Interesting. So, it's just me then (which is why there haven't been any panic reports from me for a while). There's heavy use of the following modules to the tune of 3*10^9 packets a day peaking at several 1000Mbits/s: Id Refs Address Size Name 1 10 0xffffffff80100000 6f3108 kernel 2 1 0xffffffff80a22000 4986 if_lagg.ko 3 1 0xffffffff80a27000 9f9 pflog.ko 4 1 0xffffffff80a28000 5292 if_bridge.ko 5 1 0xffffffff80a2e000 350f bridgestp.ko I suspect it's blowing up in there somewhere a few times a week. I'll try compiling them into the kernel and see if that yields a useable vmcore. Ian -- Ian Freislich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1MM0kk-0004JU-1X>