From owner-freebsd-current@FreeBSD.ORG Sat Dec 22 11:11:16 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 03805452 for ; Sat, 22 Dec 2012 11:11:16 +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 44D788FC0C for ; Sat, 22 Dec 2012 11:11:14 +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 NAA18088; Sat, 22 Dec 2012 13:11:10 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1TmMz0-000E0w-Ir; Sat, 22 Dec 2012 13:11:10 +0200 Message-ID: <50D5954D.5090509@FreeBSD.org> Date: Sat, 22 Dec 2012 13:11:09 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Hans Petter Selasky Subject: double fault [Was: clang compiled kernel panic when mounting zfs root on i386] References: <50b37d46.8584440a.735c.ffffb4e6@mx.google.com> <50CF9AA9.1030808__28729.3355250315$1355782864$gmane$org@FreeBSD.org> <50D2F3FE.1000509@gmail.com> <201212211738.08781.hselasky@c2i.net> In-Reply-To: <201212211738.08781.hselasky@c2i.net> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Sat, 22 Dec 2012 11:11:16 -0000 on 21/12/2012 18:38 Hans Petter Selasky said the following: > I've built a 10-current i386 kernel as of today, and I see double fault when > USB audio is allocating memory. Anyone knows why? > > kdb_enter() > vpanic() > panic() > dblfault_handler() > vm_map_lookup() > vm_fault_hold() > vm_fault() > vm_fault_wire() > vm_map_wire() > kmem_alloc_attr(xxx, 0x4000,2,0,0xffffffff) > bus_dmamem_alloc() > usb_pc_alloc_mem() I suspect that this double fault may have nothing to do with the thread to which you followed up. You need to obtain full debug information to answer your question. -- Andriy Gapon