From owner-freebsd-current@FreeBSD.ORG  Sat Dec  7 19:33:03 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 8B83A712
 for <current@freebsd.org>; Sat,  7 Dec 2013 19:33:03 +0000 (UTC)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
 by mx1.freebsd.org (Postfix) with ESMTP id 526451423
 for <current@freebsd.org>; Sat,  7 Dec 2013 19:33:03 +0000 (UTC)
Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3])
 by phk.freebsd.dk (Postfix) with ESMTP id 7FF043EB51
 for <current@freebsd.org>; Sat,  7 Dec 2013 19:32:56 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
 by critter.freebsd.dk (8.14.7/8.14.7) with ESMTP id rB7JWuR7027326
 for <current@freebsd.org>; Sat, 7 Dec 2013 19:32:56 GMT
 (envelope-from phk@phk.freebsd.dk)
To: current@freebsd.org
Subject: r259072 is not a happy camper...
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Content-Type: text/plain; charset=ISO-8859-1
Date: Sat, 07 Dec 2013 19:32:56 +0000
Message-ID: <27325.1386444776@critter.freebsd.dk>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Dec 2013 19:33:03 -0000


I updated my "canary" machine to -current today and it's not a happy
camper.  Trying to run a buildworld on it I get the follwing reproducible
panic:

FreeBSD/amd64 (ni.freebsd.dk) (cuau0)

login: lock order reversal:
 1st 0xfffff8011641a9a0 ufs (ufs) @ /freebsd/head/sys/kern/vfs_lookup.c:518
 2nd 0xfffffe00e7858790 bufwait (bufwait) @ /freebsd/head/sys/ufs/ffs/ffs_vnops
.c:262
 3rd 0xfffff800b40ad5f0 ufs (ufs) @ /freebsd/head/sys/kern/vfs_subr.c:2101
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0111361da0
kdb_backtrace() at kdb_backtrace+0x39/frampanic: bad stray interrupt
cpuid = 2
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe011120e9e0
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe011120ea90
vpanic() at vpanic+0x126/frame 0xfffffe011120ead0
kassert_panic() at kassert_panic+0x136/frame 0xfffffe011120eb40
intr_event_handle() at intr_event_handle+0x11d/frame 0xfffffe011120eb90
intr_execute_handlers() at intr_execute_handlers+0x48/frame 0xfffffe011120ebc0
lapic_handle_intr() at lapic_handle_intr+0x73/frame 0xfffffe011120ebf0
Xapic_isr1() at Xapic_isr1+0xa4/frame 0xfffffe011120ebf0
--- interrupt, rip = 0x11f7b11, rsp = 0x7fffffff8b50, rbp = 0x7fffffff8b80 ---
KDB: enter: panic
[ thread pid 72149 tid 100102 ]
Stopped at      kdb_enter+0x3e: movq    $0,kdb_why
db> 

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.