From owner-freebsd-bugs@FreeBSD.ORG Mon Jul 27 22:00:06 2009 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B45E1065676 for ; Mon, 27 Jul 2009 22:00:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 392B78FC1D for ; Mon, 27 Jul 2009 22:00:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n6RM05Zm018513 for ; Mon, 27 Jul 2009 22:00:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n6RM05sd018512; Mon, 27 Jul 2009 22:00:05 GMT (envelope-from gnats) Date: Mon, 27 Jul 2009 22:00:05 GMT Message-Id: <200907272200.n6RM05sd018512@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "barbara" Cc: Subject: Re: kern/134584: [panic] spin lock held too long X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: barbara List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jul 2009 22:00:06 -0000 The following reply was made to PR kern/134584; it has been noted by GNATS. From: "barbara" To: "attilio" Cc: "bug-followup" , "FreeBSD-stable" Subject: Re: kern/134584: [panic] spin lock held too long Date: Mon, 27 Jul 2009 23:56:10 +0200 > 2009/7/26 barbara : > > It happened again, on shutdown. > > As the previous time, it happened after a high (for a desktop) uptime= and, if it could matter, after running net-p2p/transmission-gtk2 for sev= eral hours. > > I don't know if it's related, but often quitting transmission, doesn'= t terminate the process. Sometimes it end after several minutes the gui e= xited, sometimes it's still running after hours. > > I've noticed it as the destination folder is on a manually mounted de= vice and I can't umount it as fstat reports the device used by a transmis= sion process. > > So I often have to kill it. > > This happened both the time I had this kind of panic. > > What hw is that? How many CPUs does it have? > It's desktop pc, dual Athlon CPU, VIA chipset and... You can find my dmesg.boot here: http://pastebin.com/f507125f1 Aks if you need more info! In the meanwhile I've rebuilt my kernel adding WITNESS, KDB, DDB options.= Is this what you need? I'm not able to work with the debugger. I suppose I have to type the comm= ands you asked (ps, show alllocks) when it's panicking and the debbugger = starts and write down the output with pen and paper, am I corrent? Or is = there a way to redirect or dump the output somewhere? Sorry, I'll try reading the chapter in the dev. handbook and I will try t= o do my best, but please, tell me if you have some suggestions. I'll try to reproduce the problem, even it's not happening regularly. If you need more info or to test code, etc. I'll be glad to help you. BTW, can the output of crashinfo be of any help? Here you can find ps -ax= l from crashinfo: http://pastebin.com/f3d54f01b Thanks Barbara