From owner-freebsd-current@FreeBSD.ORG Thu Jun 14 14:38:10 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 02D9D16A468 for ; Thu, 14 Jun 2007 14:38:10 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 6E67613C487 for ; Thu, 14 Jun 2007 14:38:09 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 14 Jun 2007 14:38:07 -0000 Received: from h081217094222.dyn.cm.kabsi.at (EHLO taxman.pepperland) [81.217.94.222] by mail.gmx.net (mp043) with SMTP; 14 Jun 2007 16:38:07 +0200 X-Authenticated: #16703784 X-Provags-ID: V01U2FsdGVkX18GlVQJOrgGnTY1PxUy8La2evqLjMRxvG07YO0QWS XlDYqCgBiUsK7v From: Stefan Ehmann To: freebsd-current@freebsd.org Date: Thu, 14 Jun 2007 16:38:05 +0200 User-Agent: KMail/1.9.6 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706141638.06342.shoesoft@gmx.net> X-Y-GMX-Trusted: 0 Cc: Michiel Boland Subject: Re: panic in drm_ioctl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 14 Jun 2007 14:38:10 -0000 On Thursday 14 June 2007 15:11:53 Michiel Boland wrote: > Hi. My box just crashed with > > panic: mtx_lock() of destroyed mutex @ /usr/src/sys/kern/kern_mutex.c:151 > KDB: stack backtrace: > db_trace_self_wrapper(c07268c7,d6131ad8,c054562a,c0724173,c079ff00,...) at > db_trace_self_wrapper+0x26 > kdb_backtrace(c0724173,c079ff00,c0723186,d6131ae4,d6131ae4,...) at > kdb_backtrace+0x29 panic(c0723186,c072304c,97,c0571e48,c079fd50,...) at > panic+0xaa > _mtx_lock_flags(c29ee8c0,0,c072304c,97,d6131b44,...) at > _mtx_lock_flags+0x59 lock_mtx(c29ee8c0,0,c0724b6b,eb,0,...) at > lock_mtx+0x29 > _sleep(c3ef9d84,c29ee8c0,154,c07133ca,bb8,...) at _sleep+0x3bd > i915_irq_wait(c29e6300,80046445,c43885d0,3,c38b1800,...) at > i915_irq_wait+0x16d drm_ioctl(c29e6300,80046445,c43885d0,3,c38b1800,...) at > drm_ioctl+0x337 giant_ioctl(c29e6300,80046445,c43885d0,3,c38b1800,...) at > giant_ioctl+0x56 > devfs_ioctl_f(c3004510,80046445,c43885d0,c388ad80,c38b1800,...) at > devfs_ioctl_f+0xc9 kern_ioctl(c38b1800,4,80046445,c43885d0,9baad5,...) at > kern_ioctl+0x243 ioctl(c38b1800,d6131cfc,c,d6131ca0,c07612b0,...) at > ioctl+0x134 > syscall(d6131d38) at syscall+0x288 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x286d9a1f, esp = 0xbfbfe04c, > ebp = 0xbfbfe068 --- > > This is a ~7 days old -CURRENT with INVARIANTS and i915drm. > Is there any point investigating this? Or should I just csup and hope > that that will fix it? :) > > (I still have a debug kernel and core file if anyone is interested.) I am seeing a bunch of these witness warnings when starting Xorg that might be related. CURRENT as of today: uma_zalloc_arg: zone "64" with the following non-sleepable locks held: exclusive sleep mutex drm device r = 0 (0xc2fd40d8) locked @ /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_drv.c:907 KDB: stack backtrace: db_trace_self_wrapper(c0a39fdb,d4f8b9d8,c077ac8d,c0a3a39e,d4f8b9ec,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a3a39e,d4f8b9ec,4,1,0,...) at kdb_backtrace+0x29 witness_warn(5,0,c0a5632b,c0a3d197,66666666,...) at witness_warn+0x1cd uma_zalloc_arg(c1472d20,0,102,2,c0baeb64,...) at uma_zalloc_arg+0x34 malloc(2c,c0ae81c0,102,12,c340ed30,...) at malloc+0xd2 sysctl_add_oid(c340ed4c,c0baeb64,ffffffff,c340ed30,80000001,...) at sysctl_add_oid+0x95 alloc_bounce_zone(44,c0ae4f60,101,1000,c2d4d0b0,...) at alloc_bounce_zone+0x16d bus_dma_tag_create(0,1000,0,ffffffff,ffffffff,...) at bus_dma_tag_create+0x1a9 drm_pci_alloc(c2fd4000,1000,1000,ffffffff,c2fd40d8,...) at drm_pci_alloc+0xdf i915_dma_init(c3392000,80446440,c340ec00,3,c3003a00,...) at i915_dma_init+0x217 drm_ioctl(c3392000,80446440,c340ec00,3,c3003a00,...) at drm_ioctl+0x37a giant_ioctl(c3392000,80446440,c340ec00,3,c3003a00,...) at giant_ioctl+0x56 devfs_ioctl_f(c2ff9510,80446440,c340ec00,c3393b00,c3003a00,...) at devfs_ioctl_f+0xc9 kern_ioctl(c3003a00,9,80446440,c340ec00,0,...) at kern_ioctl+0x243 ioctl(c3003a00,d4f8bcfc,c,c0a28324,c0ae0e30,...) at ioctl+0x134 syscall(d4f8bd38) at syscall+0x2b3 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x283e13cf, esp = 0xbfbfea6c, ebp = 0xbfbfea88 --- But a quick search revealed a post from June 2006 with an identical looking output. The poster received no answer though. Stefan