Date: Wed, 3 Sep 2008 21:11:27 GMT From: gavin@FreeBSD.org To: i.angelov@developers.bg, gavin@FreeBSD.org, freebsd-bugs@FreeBSD.org, gavin@FreeBSD.org Subject: Re: kern/126997: [panic] Kernel panic Message-ID: <200809032111.m83LBRGr052668@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
Synopsis: [panic] Kernel panic
State-Changed-From-To: open->feedback
State-Changed-By: gavin
State-Changed-When: Wed Sep 3 20:59:12 UTC 2008
State-Changed-Why:
To submitter: Sadly, because you have recompiled your kernel, the core
dumps are very hard to analyse anywhere but on your own system.
However, it's not hard for you to get the basic information we will
need:
- Make sure you have the same sources in /usr/src as the kernel was
compiled with (recompile if necessary)
- Make sure the kernel was compiled with "makeoptions DEBUG=-g" in
the kernel config file (I believe it's default)
- Make sure you are running with the above kernel, and wait for a
panic
- On the core dump produced, run:
kgdb /usr/obj/usr/src/sys/GENERIC/kernel.debug /var/crash/vmcore.X
(replacing GENERIC with the name of your kernel, and vmcore.X with
the most recent core dump)
- When in kgdb, run "bt", and reply-all to this email with the backtrrace
Finally: FreeBSD PRs are public, and kernel core dumps may well contain
sensitive information such as passwords etc, as they are a full dump
of the computer's memory at the time it crashed. Therefore it's
probably a good idea for you to remove the core files you've made
accessible. If a FreeBSD developer needs them, you can share them
privately.
Responsible-Changed-From-To: freebsd-bugs->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Wed Sep 3 20:59:12 UTC 2008
Responsible-Changed-Why:
Track
http://www.freebsd.org/cgi/query-pr.cgi?pr=126997
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200809032111.m83LBRGr052668>