Date: Wed, 13 Apr 2005 12:51:15 +0200 From: Jeremie Le Hen <jeremie@le-hen.org> To: Eirik =?iso-8859-1?Q?=D8verby?= <ltning@anduin.net> Cc: "current@freebsd.org" <current@freebsd.org> Subject: Re: Panic after "in_cksum_skip: out of data by 260" Message-ID: <20050413105115.GG63229@obiwan.tataz.chchile.org> In-Reply-To: <20050413094338.GE63229@obiwan.tataz.chchile.org> References: <BE8297B3.116B1%ltning@anduin.net> <20050413094338.GE63229@obiwan.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I have no idea about what could have caused this, but in this case, it > would be useful to have a crashdump and its associated kernel.debug file, > or at least a backtrace (but you must have enabled the break to debugger > on panic). I guess you could also use addr2line(1) to determine which > function caused the panic from the instruction pointer, but it's likely > not enough to help understanding the problem. Since it's a NULL pointer derefence, mux@ told me the addr2line(1) result could be relevant, assuming you have a debug kernel compiled. Could you give back the result of the following command please : addr2line -e kernel.debug 0xc066ec33 Once addr2line(1) gave you the file and the line, it is also important to tell us the revision of the file. If you don't have a debug kernel, and you *absolutely* change neither the sources from which you compiled it nor the kernel configuration file, you should be able to rebuild it. -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050413105115.GG63229>