Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Jul 2007 23:11:33 +0200
From:      "Attilio Rao" <attilio@freebsd.org>
To:        "Peter Wemm" <peter@wemm.org>
Cc:        Milos Vyletel <mv@rulez.sk>, freebsd-current@freebsd.org, current@freebsd.org, Kris Kennaway <kris@obsecurity.org>
Subject:   Re: ULE status, invalid load, buildkernel times.
Message-ID:  <3bbf2fe10707301411u80120ban1bbde128aeb8662b@mail.gmail.com>
In-Reply-To: <200707291552.57528.peter@wemm.org>
References:  <20070721174631.S561@10.0.0.1> <20070727132640.GA6877@rot26.obsecurity.org> <20070727133342.GA12179@rulez.sk> <200707291552.57528.peter@wemm.org>

next in thread | previous in thread | raw e-mail | index | archive | help
2007/7/30, Peter Wemm <peter@wemm.org>:
> On Friday 27 July 2007, Milos Vyletel wrote:
> > On Fri, Jul 27, 2007 at 09:26:40AM -0400, Kris Kennaway wrote:
> > > 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.
> >
> > Yes, I forgot about that. I have zfs swap partition and I can't
> > configure my dumpdev. Have anyone succesfully acomplish this?
>
> Please abandon the original patch and try this one:
>
> http://people.freebsd.org/~peter/topology.diff

Shouldn't you still fix the SI_SUB_CPU family functions order?
Otherwise you will still have apic_init() and cpu_startup() not
ordered... I think the rank I used for the past patch is reasonable
for it.

Thanks,
Attilio


-- 
Peace can only be achieved by understanding - A. Einstein



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3bbf2fe10707301411u80120ban1bbde128aeb8662b>