From owner-freebsd-current@FreeBSD.ORG Fri Jul 27 13:26:54 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F1AF16A41F for ; Fri, 27 Jul 2007 13:26:54 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 7BCF513C46C for ; Fri, 27 Jul 2007 13:26:54 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from rot26.obsecurity.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id B9F1A1A4D82; Fri, 27 Jul 2007 06:26:49 -0700 (PDT) Received: by rot26.obsecurity.org (Postfix, from userid 1001) id EF924BB74; Fri, 27 Jul 2007 09:26:40 -0400 (EDT) Date: Fri, 27 Jul 2007 09:26:40 -0400 From: Kris Kennaway To: Milos Vyletel Message-ID: <20070727132640.GA6877@rot26.obsecurity.org> References: <20070721174631.S561@10.0.0.1> <20070722114846.GA97996@rulez.sk> <20070722121631.GA8336@rulez.sk> <200707261806.20554.peter@wemm.org> <20070727074832.GA69608@rulez.sk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070727074832.GA69608@rulez.sk> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org, Peter Wemm Subject: Re: ULE status, invalid load, buildkernel times. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jul 2007 13:26:54 -0000 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