From owner-freebsd-current@FreeBSD.ORG Fri Dec 12 10:35:12 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFA151065670 for ; Fri, 12 Dec 2008 10:35:11 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from mainframe.kkip.pl (kkip.pl [87.105.164.78]) by mx1.freebsd.org (Postfix) with ESMTP id 809F58FC22 for ; Fri, 12 Dec 2008 10:35:10 +0000 (UTC) (envelope-from admin@kkip.pl) Received: from admin.admin.lan.kkip.pl ([10.66.3.254]) by mainframe.kkip.pl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LB5MQ-0003sf-4c; Fri, 12 Dec 2008 11:35:08 +0100 Message-ID: <49423E5A.10900@kkip.pl> Date: Fri, 12 Dec 2008 11:35:06 +0100 From: Bartosz Stec User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Kostik Belousov References: <4940A685.7040608@psg.com> <494216C2.7080606@kkip.pl> <20081212095238.GY2038@deviant.kiev.zoral.com.ua> In-Reply-To: <20081212095238.GY2038@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-User: admin@kkip.pl X-Authenticator: plain X-Sender-Verify: SUCCEEDED (sender exists & accepts mail) X-Spam-Score: -8.9 X-Spam-Score-Int: -88 X-Exim-Version: 4.69 (build at 01-Nov-2008 10:39:57) X-Date: 2008-12-12 11:35:08 X-Connected-IP: 10.66.3.254:3405 X-Message-Linecount: 131 X-Body-Linecount: 117 X-Message-Size: 5507 X-Body-Size: 4815 X-Received-Count: 1 X-Recipient-Count: 3 X-Local-Recipient-Count: 3 X-Local-Recipient-Defer-Count: 0 X-Local-Recipient-Fail-Count: 0 Cc: Randy Bush , FreeBSD Current Subject: Re: panic: sleeping thread & bufwrite: buffer is not busy??? 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: Fri, 12 Dec 2008 10:35:12 -0000 Kostik Belousov pisze: > On Fri, Dec 12, 2008 at 08:46:10AM +0100, Bartosz Stec wrote: > >> Randy Bush pisze: >> >>> i386 soekris 5501 >>> current as of Dec 11 00:27 gmt >>> >>> Unread portion of the kernel message buffer: >>> Sleeping thread (tid 100054, pid 646) owns a non-sleepable lock >>> panic: sleeping thread >>> panic: bufwrite: buffer is not busy??? >>> Uptime: 2m1s >>> Physical memory: 503 MB >>> >>> #0 doadump () at pcpu.h:246 >>> #1 0xc0571f33 in boot (howto=260) at >>> /usr/src/sys/kern/kern_shutdown.c:420 >>> #2 0xc05720f7 in panic (fmt=Variable "fmt" is not available.) >>> at /usr/src/sys/kern/kern_shutdown.c:576 >>> #3 0xc06fc75c in ffs_bufwrite (bp=0xc2937e20) >>> at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1786 >>> #4 0xc05c7250 in vfs_bio_awrite (bp=0xc2937e20) at buf.h:385 >>> #5 0xc05cfee0 in vop_stdfsync (ap=0xc2a89b34) >>> at /usr/src/sys/kern/vfs_default.c:479 >>> #6 0xc0520ad3 in devfs_fsync (ap=0xc2a89b34) >>> at /usr/src/sys/fs/devfs/devfs_vnops.c:485 >>> #7 0xc074e50e in VOP_FSYNC_APV (vop=0xc07cc800, a=0xc2a89b34) >>> at vnode_if.c:1007 >>> #8 0xc06fd0a2 in ffs_sync (mp=0xc2e33c80, waitfor=2, td=0xc2c28480) >>> at vnode_if.h:529 >>> #9 0xc05e0803 in sync (td=0xc2c28480, uap=0x0) >>> at /usr/src/sys/kern/vfs_syscalls.c:149 >>> #10 0xc0571ad2 in boot (howto=256) at >>> /usr/src/sys/kern/kern_shutdown.c:312 >>> #11 0xc05720f7 in panic (fmt=Variable "fmt" is not available.) >>> at /usr/src/sys/kern/kern_shutdown.c:576 >>> #12 0xc059ec81 in propagate_priority (td=0xc2e696c0) >>> at /usr/src/sys/kern/subr_turnstile.c:222 >>> #13 0xc059f551 in turnstile_wait (ts=0xc2c0ee10, owner=0xc2e696c0, >>> queue=Variable "queue" is not available.) >>> at /usr/src/sys/kern/subr_turnstile.c:738 >>> #14 0xc0570c73 in _rw_wlock_hard (rw=0xc2cdcd80, tid=3267527808, >>> file=0x0, line=0) >>> at /usr/src/sys/kern/kern_rwlock.c:705 >>> #15 0xc06bdcb6 in in6_mtutimo (rock=0xc2cdcd00) >>> at /usr/src/sys/netinet6/in6_rmx.c:437 >>> #16 0xc0580f77 in softclock (arg=0xc07ffbe0) >>> at /usr/src/sys/kern/kern_timeout.c:398 >>> #17 0xc055790a in intr_event_execute_handlers (p=0xc2c257ec, >>> ie=0xc2c22400) >>> at /usr/src/sys/kern/kern_intr.c:1134 >>> #18 0xc0558933 in ithread_loop (arg=0xc2c07ba0) >>> at /usr/src/sys/kern/kern_intr.c:1147 >>> #19 0xc0555cb6 in fork_exit (callout=0xc05588d0 , >>> arg=0xc2c07ba0, frame=0xc2a89d38) at >>> /usr/src/sys/kern/kern_fork.c:821 >>> #20 0xc0730a50 in fork_trampoline () at >>> /usr/src/sys/i386/i386/exception.s:270 >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@freebsd.org" >>> >> I have similiar problem: >> >> Dump header from device /dev/ad0s1b >> Architecture: i386 >> Architecture Version: 2 >> Dump Length: 216797184B (206 MB) >> Blocksize: 512 >> Dumptime: Thu Dec 11 20:20:45 2008 >> Hostname: serwer.obsysa.net >> Magic: FreeBSD Kernel Dump >> Version String: FreeBSD 8.0-CURRENT #3: Thu Dec 11 16:55:50 CET 2008 >> ncpnc@serwer.obsysa.net:/usr/obj/usr/src/sys/ATHLON8 >> Panic String: sleeping thread >> Dump Parity: 1830535215 >> Bounds: 0 >> Dump Status: good >> >> Unfortunately I cannot provide more debug information at this time >> because kernel was built without debugging options. (I will rebuild it >> if needed) However I can still provide some info: >> - kernel panic while loading modules, just after loding ZFS module (I >> have RAIDZ configuration) and after a couple of minutes without any >> visible action on the screen. >> - I have this panic with *every* build I made after 7 Dec 2008, but I >> don't remember wchich day exactly I have experienced that for the first >> time. >> - For now I'm using kernel builded 7 Dec 2008 and no panic seen at all. >> > > You are mixing the issues without a reason. To claim that you problem > is similar, you need to show the similar backtrace. The panic shown is > the late manifestation of a problem, it is kind a catch-all for some > sort of locking issues. > OK. I'll try to build debug kernel today and I will provide backtrace. I forgot to mention in my last post that I saw very similiar (if not identical) lines to: Sleeping thread (tid 100054, pid 646) owns a non-sleepable lock panic: sleeping thread panic: bufwrite: buffer is not busy??? while checking dmesg buffer after one of the panics earlier. That's why I assumed it's probably the same issue. Sorry for confusion, they're my first steps with CURRENT and very first experience with kernel panic :). Cheers! -- Bartosz Stec