From owner-freebsd-stable@FreeBSD.ORG Tue Aug 23 21:08:33 2011 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9F94106564A for ; Tue, 23 Aug 2011 21:08:32 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 201A08FC14 for ; Tue, 23 Aug 2011 21:08:31 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA03177; Wed, 24 Aug 2011 00:08:24 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QvyCt-0007nW-RS; Wed, 24 Aug 2011 00:08:23 +0300 Message-ID: <4E5416C4.8090207@FreeBSD.org> Date: Wed, 24 Aug 2011 00:08:20 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0) Gecko/20110819 Thunderbird/6.0 MIME-Version: 1.0 To: Aragon Gouveia References: <4E540817.4080102@phat.za.net> In-Reply-To: <4E540817.4080102@phat.za.net> X-Enigmail-Version: undefined Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: reproducible panic on 8.2-RELEASE, but no core file X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Aug 2011 21:08:33 -0000 on 23/08/2011 23:05 Aragon Gouveia said the following: > Hi, > > I'm experiencing a reproducible kernel panic that would be really nice to debug, > but unfortunately no core file is getting generated. I don't have console > access either. All I can get so far is this, from syslog: > > Aug 23 19:51:38 estranged kernel: > Aug 23 19:51:38 estranged kernel: Fatal double fault: > Aug 23 19:51:38 estranged kernel: eip = 0xc0593b2e > Aug 23 19:51:38 estranged kernel: esp = 0xe5583fe4 > Aug 23 19:51:38 estranged kernel: ebp = 0xe5584010 > Aug 23 19:51:38 estranged kernel: cpuid = 0; apic id = 00 > Aug 23 19:51:38 estranged kernel: panic: double fault > Aug 23 19:51:38 estranged kernel: cpuid = 0 > Aug 23 19:51:38 estranged kernel: panic: 0xc4263b40 must be migratable > Aug 23 19:51:38 estranged kernel: cpuid = 0 > Aug 23 19:51:38 estranged kernel: panic: 0xc4263b40 must be migratable > Aug 23 19:51:38 estranged kernel: cpuid = 0 > [SNIP - above two lines repeated alot] > Aug 23 19:51:38 estranged kernel: cpuid = 0kernel trap 12 with > interrupts disabled > Aug 23 19:51:38 estranged kernel: panic: > Aug 23 19:51:38 estranged kernel: 0xc4263b40 must be > migratablekernel trap 12 with interrupts disabled > Aug 23 19:51:38 estranged kernel: kernel trap 12 with interrupts > disabled > Aug 23 19:51:38 estranged kernel: cpuid = 0 > Aug 23 19:51:38 estranged kernel: kernel trap 12 with interrupts > disabled > Aug 23 19:51:38 estranged kernel: panic: > > My dumpdev is set: > > $ ls -l /dev/dumpdev > lrwxr-xr-x 1 root wheel 11 Aug 23 19:56 /dev/dumpdev@ -> /dev/ad4s1b > > But savecore reports: > > Aug 23 19:56:34 estranged kernel: No core dumps found. > > Any advice for getting a core file? :) Not sure about the core file - I think that we do not attempt to do a dump when we get a doublefault which is what you have, but not sure about this. Also, those secondary panics might be coming from the sched_bind() call at the start of boot() function in sys/kern/kern_shutdown.c. For a start you can try adding DDB to your kernel config and capturing a stack trace of the panic from the ddb prompt. -- Andriy Gapon