Re: deadlkres: possible deadlock detected for 0xe000000012aed200, blocked for 900014 ticks

John Baldwin <[email protected]>
Newsgroups gmane.os.freebsd.current,gmane.os.freebsd.devel.ia64
Message-ID <[email protected]>
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?

-- 
John Baldwin
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.