From owner-freebsd-current@FreeBSD.ORG Sun Dec 23 09:44:56 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 0805ED61; Sun, 23 Dec 2012 09:44:56 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.c2i.net [212.247.154.194]) by mx1.freebsd.org (Postfix) with ESMTP id 2E4098FC0C; Sun, 23 Dec 2012 09:44:55 +0000 (UTC) X-T2-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED Received: from [176.74.213.204] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe07.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 360502604; Sun, 23 Dec 2012 10:39:46 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Subject: Re: double fault [Was: clang compiled kernel panic when mounting zfs root on i386] Date: Sun, 23 Dec 2012 10:41:21 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.8.4; amd64; ; ) References: <50b37d46.8584440a.735c.ffffb4e6@mx.google.com> <50D5954D.5090509@FreeBSD.org> <50D5AE9F.10801@FreeBSD.org> In-Reply-To: <50D5AE9F.10801@FreeBSD.org> X-Face: 'mmZ:T{)),Oru^0c+/}w'`gU1$ubmG?lp!=R4Wy\ELYo2)@'UZ24N@d2+AyewRX}mAm; Yp |U[@, _z/([?1bCfM{_"B<.J>mICJCHAzzGHI{y7{%JVz%R~yJHIji`y>Y}k1C4TfysrsUI -%GU9V5]iUZF&nRn9mJ'?&>O MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201212231041.21789.hselasky@c2i.net> Cc: Dimitry Andric , Andriy Gapon 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: Sun, 23 Dec 2012 09:44:56 -0000 On Saturday 22 December 2012 13:59:11 Dimitry Andric wrote: > 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. Hi, It was due to running out of stack. I've fixed it in -current. --HPS