Date: Sat, 22 Dec 2012 13:59:11 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Andriy Gapon <avg@FreeBSD.org> Cc: freebsd-current@FreeBSD.org, Hans Petter Selasky <hselasky@c2i.net> Subject: Re: double fault [Was: clang compiled kernel panic when mounting zfs root on i386] Message-ID: <50D5AE9F.10801@FreeBSD.org> In-Reply-To: <50D5954D.5090509@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50D5AE9F.10801>