>From jhb_at_freebsd.org Wed Oct 23 16:54:12 2013 > >On Wednesday, October 23, 2013 5:27:10 am Anton Shterenlikht wrote: >> This time alllocks has lots of info. >> >> I updated the PR: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007 > >Hmm, unfortunately it seems like all the stack traces did not work. There are >lots of threads blocked on VM-related locks, and CPU 0 is running vm_daemon. >Probably would need a stack trace of that thread to see what it is doing (this >is part of why a real crash dump would be far better than a textdump as you >can get more info after the crash instead of having to know in advance >everything you want). I saw earlier you had a thread to get textdumps to >work. Did you ever have regular crashdumps working? No. I have another deadlock panic when savecore is running. That panic dumps core, then on reboot when savecore is running I get another deadlock panic, and so on. However, I do get about 8-10gb vmcore* files before the panic happens. Presumably these are truncated somehow. Do you think these incomplete vmcores can still be useful? If you send some instructions on what to try, I'll give it a go, or I can post a vmcore somewhere. Many thanks AntonReceived on Wed Oct 23 2013 - 16:01:50 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:43 UTC