From owner-freebsd-current@FreeBSD.ORG Mon Nov 22 19:14:25 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21FE510656A5 for ; Mon, 22 Nov 2010 19:14:25 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id D85098FC1C for ; Mon, 22 Nov 2010 19:14:24 +0000 (UTC) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.4/8.14.4) with ESMTP id oAMJEO23090848; Mon, 22 Nov 2010 11:14:24 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.4/8.14.4/Submit) id oAMJEOIo090847; Mon, 22 Nov 2010 11:14:24 -0800 (PST) (envelope-from obrien) Date: Mon, 22 Nov 2010 11:14:24 -0800 From: "David O'Brien" To: Pyun YongHyeon Message-ID: <20101122191424.GB60518@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Pyun YongHyeon , freebsd-current@freebsd.org References: <20101111003254.GA7139@dragon.NUXI.org> <20101111223059.GK17566@michelle.cdnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101111223059.GK17566@michelle.cdnetworks.com> X-Operating-System: FreeBSD 9.0-CURRENT X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: Non-sleepable locks PANIC in sf(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Nov 2010 19:14:25 -0000 On Thu, Nov 11, 2010 at 02:30:59PM -0800, Pyun YongHyeon wrote: > On Wed, Nov 10, 2010 at 04:32:54PM -0800, David O'Brien wrote: > > Kernel page fault with the following non-sleepable locks held: > > exclusive sleep mutex sf0 (network driver) r = 0 (0xc722b584) locked @ /usr/obj/4kib/modules/sf/../../dev/sf/if_sf.c:1862 > > KDB: stack backtrace: > > db_trace_self_wrapper(c08870ef,c6be8a80,4,c0a83ba0,c704164c,...) at 0xc04ed726 = db_trace_self_wrapper+0x26 > > kdb_backtrace(746,0,ffffffff,c0a83b94,daaa2ac0,...) at 0xc061152a = kdb_backtrace+0x2a > > _witness_debugger(c08898ba,daaa2ad4,4,1,0,...) at 0xc0626256 = _witness_debugger+0x26 > > witness_warn(5,0,c08b2265,246,c70415a0,...) at 0xc062776d = witness_warn+0x1fd > > trap(daaa2bac) at 0xc08214bd = trap+0x2ad > > calltrap() at 0xc080b93c = calltrap+0x6 > > --- trap 0xc, eip = 0xc08077c4, esp = 0xdaaa2bec, ebp = 0xdaaa2c00 --- > > _bus_dmamap_sync(c6cbac80,c724a000,2,daaa2c28,daaa2c30,...) at 0xc08077c4 = _bus_dmamap_sync+0x54 > > sf_newbuf(c722b584,4,c7223bbd,603,c06051d5,...) at 0xc7220173 = sf_newbuf+0xf3 > > sf_intr(c722a000,c0947ec0,4,c0882361,c65d4238,...) at 0xc7221c48 = sf_intr+0x248 > > intr_event_execute_handlers(c658f7f8,c65d4200,c087ef80,533,c65d4270,...) at 0xc05b47b5 = intr_event_execute_handlers+0x125 > > ithread_loop(c65dd830,daaa2d28,c087ed0e,33b,c658f7f8,...) at 0xc05b55ac = ithread_loop+0xac [..] > > > > thoughts? > > Does sf(4) use shared interrupt? Yes. sf0: port 0x8800-0x88ff mem 0xfa480000-0xfa4fffff irq 26 at device 4.0 on pci3 sf1: port 0x8400-0x84ff mem 0xfa380000-0xfa3fffff irq 27 at device 5.0 on pci3 em0: port 0x9880-0x98bf mem 0xfa5c0000-0xfa5dffff irq 27 at device 8.0 on pci2 sf2: port 0x8000-0x80ff mem 0xfa300000-0xfa37ffff irq 24 at device 6.0 on pci3 bge0: mem 0xfa5b0000-0xfa5bffff irq 24 at device 9.0 on pci2 em1: port 0x9c00-0x9c3f mem 0xfa5e0000-0xfa5fffff irq 24 at device 8.1 on pci2 sf3: port 0x7800-0x78ff mem 0xfa200000-0xfa27ffff irq 25 at device 7.0 on pci3 -- -- David (obrien@FreeBSD.org)