From owner-freebsd-current@FreeBSD.ORG Thu Nov 10 10:32:55 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 451C01065745; Thu, 10 Nov 2011 10:32:55 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id A16768FC17; Thu, 10 Nov 2011 10:32:53 +0000 (UTC) Received: by wwg14 with SMTP id 14so1485608wwg.31 for ; Thu, 10 Nov 2011 02:32:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=rBOtWoZM8udu2H4zBELzlL0sp60ffW8Co6eb2gkTms8=; b=lOQ+q1vqkohFxlTO8N4AYRnNnXSsmLk9P0UB/AK2kuvPSkIEvNJgqdRdU5kNzjKZa2 dtOIBsrtrgozRQr/0KsHqA5Me2zAze7OfOoUaqcHL2yxidNgsOsMlQTkHhmhspeDZa8d vLynbHE84jZdhHqVk8q/qkdL3m/0IdEB1fTf8= MIME-Version: 1.0 Received: by 10.216.176.14 with SMTP id a14mr6106899wem.14.1320921172629; Thu, 10 Nov 2011 02:32:52 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.216.182.3 with HTTP; Thu, 10 Nov 2011 02:32:52 -0800 (PST) In-Reply-To: <4EBB885E.9060908@freebsd.org> References: <4EBB885E.9060908@freebsd.org> Date: Thu, 10 Nov 2011 11:32:52 +0100 X-Google-Sender-Auth: LpC2nxGOiv4PNz1R4BRfEylsqcY Message-ID: From: Attilio Rao To: Stefan Esser Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Current Subject: Re: [amd64] Reproducible cold boot failure (reboot succeeds) in -CURRENT 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: Thu, 10 Nov 2011 10:32:55 -0000 2011/11/10 Stefan Esser : > For a few weeks I have been suffering from a problem that requires manual > intervention to get my home workstation boot -CURRENT. > > The kernel panics at varying places and with different panic messages, e.g. > (hand transcribed since kernel dumps don't work at that stage): > > privileged instruction fault while in kernel mode > > kmem_alloc_nofault +0x37 > kmem_init +0x9e > vm_kmem_init +0x39 > mi_startup +0x77 > btext +0x2c > > > On another cold boot attempt: > > kernel trap 12 with interrupts disabled > Fatal trap 12: page fault while in kernel mode > > elf_relocinternal +0xa8 > link_elf_reloc_local +0x2fe > link_elf_link_preload +0x69d > linker_preload +0x101 > mi_startup +0x77 > btext +0x2c > > > In all the cases observed, the system starts without any problems on second > attempt (pressing RESET or the reboot command in the debugger). > The system is working reliably, once booted. > > This started a few weeks back (after the switch-over to 10-CURRENT, > IIRC), and I did not bother to report it at the time, since I thought it was > caused by a temporary instability in the code base. > > The system is an i2600K on ASUS P8H67-M EVO with 8GB of RAM and an amd64 > kernel booting from ZFS (gptzfsboot). The kernel is a stripped down GENERIC > plus IPFW and ath (but I doubt that the configuration is causing this, since > the failure happens before any devices are probed and the identically > configured kernels used to cold boot just fine for half a year). > > Any hint how to further diagnose this case is welcome (but my spare > time is very limited and I cannot easily bisect to find a revision > that boots, for example). > > I can produce further debug output on demand, but I do not have a serial or > firewire console setup for debugging. > > Is anybody else affected by this boot problem? Can you setup a videocamera or a simple serial console? Did you try to boot with both -s and -v on? Attilio -- Peace can only be achieved by understanding - A. Einstein