From owner-freebsd-current@FreeBSD.ORG Wed Sep 12 15:48:47 2012 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 F2242106566C for ; Wed, 12 Sep 2012 15:48:46 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id AF33B8FC08 for ; Wed, 12 Sep 2012 15:48:46 +0000 (UTC) Received: by vcbfw7 with SMTP id fw7so2872813vcb.13 for ; Wed, 12 Sep 2012 08:48:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=p4kdcKrRy2LqAkgBQvGsCmx6Lx++nv8a8sRiusX500M=; b=E4G23Md+x+PaA0oGsuo1qMdArDDkILp7EJTY9xWGtmALWa8h9k6ZobYHi7nt+wm8Ef yHEn2qLCqKejf3QbSPPxV9XIShsvOS49z081bj3YAshAQxa3QZfzYu6/GB1m3htu92FW 0ahyXTaOGhXt7zOqwXD4y2ldH0raw1aDxPyXuAsa9fHxvLPtktxqHuRRmmWPfFYudb13 9cj062t/h6rvH6srLM9AswCywCM/aqlB07RDQZsvC2RfBjGGGIZhM1V6kGTaCcpcyQtY pnc0KPMh+FfVIgdNtTHXRRkkUY8zgmS4KH/lzWNTMgKe+xqVZTc5YEa0sEUhQ6oaliNa VgJA== MIME-Version: 1.0 Received: by 10.52.28.113 with SMTP id a17mr23309300vdh.47.1347464925944; Wed, 12 Sep 2012 08:48:45 -0700 (PDT) Received: by 10.58.26.129 with HTTP; Wed, 12 Sep 2012 08:48:45 -0700 (PDT) Date: Wed, 12 Sep 2012 11:48:45 -0400 Message-ID: From: Kim Culhan To: freebsd-current@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: recently updated -current fatal trap at boot 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: Wed, 12 Sep 2012 15:48:47 -0000 FreeBSD -current r240360 has a fatal trap at boot. This has been noted on two machines running -current which were updated using the recommended buildworld update procedure. Booting in single-user mode is possible and booting with the previous kernel, r240327M from ~ 09-10-12, is also possible and appears to run well. On the console the moment of failure is just after the config data for the last network device is displayed, where normally on the console is: add net default: gateway: 1.2.3.4 When pflog was enabled, pflog was the last item displayed, disabling pf and pflog has no effect. A serial console is not available so a picture of the console after the fatal trap is: https://picasaweb.google.com/lh/photo/vFCZkxwtD1iTis5FEFZPN3l5YW7gL02s7FRYfqxWRYs?feat=directlink Any recommendations toward finding the cause would be greatly appreciated. thanks -kim