On Fri, Oct 11, 2013 at 11:26 AM, Anton Shterenlikht <mexas_at_bris.ac.uk> wrote: > >From davide.italiano_at_gmail.com Thu Sep 26 13:12:30 2013 >>On Thu, Sep 26, 2013 at 12:23 PM, Anton Shterenlikht <mexas_at_bris.ac.uk> wrote: >>> >>> Regarding textdump(4), I'm not clear where the following >>> "scripts" should be located and used: >>> >> >>[snip] >> >>> Are these ddb(8) commands? Or do I set these in /etc/rc.conf? >>> >> >>The scripts (quotes unneeded) should be located in /etc/ddb.conf. >>I think you want ddb_enable="YES" in your /etc/rc.conf > > I've set textdump following the man page. > > I've got several more deadlocks, but > it seems savecore causes deadlock too! > > # savecore > savecore: reboot after panic: deadlkres: possible deadlock detected for 0xe0000000129d2000, blocked for 902608 ticks > savecore: writing core to ./vmcore.5 > > When the size of vmcore.x file gets to about 9GB, > I get a deadlock again. > > What can I do now? > > Thanks > > Anton > If you're not able to get a full dump, a textdump would be enough. In your DDB scripts just remove the 'call doadump' step and you should be done, unless I'm missing something. Please adjust the script as well to include all the informations requested as mentioned in my previous link, e.g. 'show lockedvnods' is not mentioned on the example section of textdump(4) manpage but it could be useful to ease debugging. Thanks for your time, -- Davide "There are no solved problems; there are only problems that are more or less solved" -- Henri PoincareReceived on Fri Oct 11 2013 - 11:17:44 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:42 UTC