From owner-freebsd-current@FreeBSD.ORG Sat Dec 22 12:59:06 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 85FC5CC7; Sat, 22 Dec 2012 12:59:06 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 42C6D8FC12; Sat, 22 Dec 2012 12:59:06 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:84e5:2627:88f9:e626] (unknown [IPv6:2001:7b8:3a7:0:84e5:2627:88f9:e626]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 9B7165C5A; Sat, 22 Dec 2012 13:59:05 +0100 (CET) Message-ID: <50D5AE9F.10801@FreeBSD.org> Date: Sat, 22 Dec 2012 13:59:11 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20121128 Thunderbird/18.0 MIME-Version: 1.0 To: Andriy Gapon Subject: Re: 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> <50D5954D.5090509@FreeBSD.org> In-Reply-To: <50D5954D.5090509@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, Hans Petter Selasky 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 12:59:06 -0000 On 2012-12-22 12:11, Andriy Gapon wrote: > 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. Specifically interesting are the stack frame addresses, which Kostik has added recently. From these, you can easily see whether the double fault is due to stack exhaustion (which seems unlikely with such a small call stack), or to something else.