Date: Fri, 27 Jul 2007 09:26:40 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Milos Vyletel <mv@rulez.sk> Cc: current@freebsd.org, Peter Wemm <peter@wemm.org> Subject: Re: ULE status, invalid load, buildkernel times. Message-ID: <20070727132640.GA6877@rot26.obsecurity.org> In-Reply-To: <20070727074832.GA69608@rulez.sk> References: <20070721174631.S561@10.0.0.1> <20070722114846.GA97996@rulez.sk> <20070722121631.GA8336@rulez.sk> <200707261806.20554.peter@wemm.org> <20070727074832.GA69608@rulez.sk>
index | next in thread | previous in thread | raw e-mail
On Fri, Jul 27, 2007 at 09:48:32AM +0200, Milos Vyletel wrote:
> On Thu, Jul 26, 2007 at 06:06:20PM -0700, Peter Wemm wrote:
> > The other option is to find the kernel.debug for this crash, and do
> > this:
> > kgdb kernel.debug
> > gdb> l *0xffffffff8033953c
> > This will tell us the file and line number that the crash happened in.
> > There is no need to reboot for this unless you no longer have a
> > crashing kernel.
>
> I've played with this a little while, and after turning INVARIANTS on, it
> paniced in lapic_ipi_raw() on the
> KASSERT(lapic != NULL, ("%s called too early", __func__));
>
> so I assume, that this function was called before lapic_init(), where lapic is initialized, which is wrong.
>
> It was clean current kernel with no other patches, now I don't have local
> access to that machine so I can test it in few days.
>
> btw. how can one get trace in text form, I mean syslog stop after panic and all
> I got logged is that it paniced. Anything I type in db> is lost. I know that
> this can be done by remote gdb, but unfortunatelly this isn't possible.
If you trigger a dump (call doadump) then some amount of the DDB
session will usually be saved with the dump and displayed by kgdb.
Kris
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070727132640.GA6877>