From owner-freebsd-current@FreeBSD.ORG Fri Jul 27 07:48:38 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 71B1A16A41A for ; Fri, 27 Jul 2007 07:48:38 +0000 (UTC) (envelope-from mv@rulez.sk) Received: from mail.rulez.sk (DaEmoN.RuLeZ.sK [84.16.32.226]) by mx1.freebsd.org (Postfix) with ESMTP id 39AFB13C45E for ; Fri, 27 Jul 2007 07:48:38 +0000 (UTC) (envelope-from mv@rulez.sk) Received: from localhost (localhost [127.0.0.1]) by mail.rulez.sk (Postfix) with ESMTP id 2E5795C39; Fri, 27 Jul 2007 09:48:36 +0200 (CEST) X-Virus-Scanned: by amavisd-new at mail.rulez.sk Received: by mail.rulez.sk (Postfix, from userid 1020) id 448B35C34; Fri, 27 Jul 2007 09:48:32 +0200 (CEST) Date: Fri, 27 Jul 2007 09:48:32 +0200 From: Milos Vyletel To: Peter Wemm Message-ID: <20070727074832.GA69608@rulez.sk> References: <20070721174631.S561@10.0.0.1> <20070722114846.GA97996@rulez.sk> <20070722121631.GA8336@rulez.sk> <200707261806.20554.peter@wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200707261806.20554.peter@wemm.org> User-Agent: Mutt/1.4.2.2i Cc: current@freebsd.org 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 07:48:38 -0000 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. Thanks