From owner-freebsd-bugs@FreeBSD.ORG Wed Jul 29 06:30:09 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 2CA29106566B for ; Wed, 29 Jul 2009 06:30:09 +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 1A9998FC12 for ; Wed, 29 Jul 2009 06:30:09 +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 n6T6U8xL061627 for ; Wed, 29 Jul 2009 06:30:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n6T6U8uG061623; Wed, 29 Jul 2009 06:30:08 GMT (envelope-from gnats) Date: Wed, 29 Jul 2009 06:30:08 GMT Message-Id: <200907290630.n6T6U8uG061623@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: Wed, 29 Jul 2009 06:30:09 -0000 The following reply was made to PR kern/134584; it has been noted by GNATS. From: "barbara" To: "to\.my\.trociny" Cc: "bug-followup" Subject: Re: kern/134584: [panic] spin lock held too long Date: Wed, 29 Jul 2009 08:29:49 +0200 > > On Mon, 27 Jul 2009 22:00:05 GMT barbara wrote: > > b> In the meanwhile I\'ve rebuilt my kernel adding WITNESS, KDB, DDB = options.=3D > b> Is this what you need? > b> I\'m not able to work with the debugger. I suppose I have to type = the comm=3D > b> ands you asked (ps, show alllocks) when it\'s panicking and the de= bbugger =3D > b> starts and write down the output with pen and paper, am I corrent?= Or is =3D > b> there a way to redirect or dump the output somewhere? > b> Sorry, I\'ll try reading the chapter in the dev. handbook and I wi= ll try t=3D > b> o do my best, but please, tell me if you have some suggestions. > > You can use `capture on\' command in ddb to record all ddb output to th= e > capture buffer. Then you will be able to extract it from core after reb= oot > running: > > ddb capture print > > Also, as it is desktop pc, I suppose you are running X. Then on panic d= db > console will be unreachable. In this case you can use textdump(4) facil= ity to > script commands you would like to run automatically on panic. Something= like > this: > > ddb script \'kdb.enter.panic=3Dcapture on; show pcpu; show allpcpu; bt;= ps; show \\ > locks; show alllocks; show lockedvnods; alltrace; call doadump; reset\= ' > > Please note, alltrace output is rather large and might not fit to captu= re > buffer. To be sure all output is stored in the buffer you can increase = the > value of debug.ddb.capture.bufsize sysctl. > > See ddb(8) and textdump(4) for details. > Thank you very much! Now I hope my box will panic soon :) Barbara