Date: Wed, 02 Dec 2015 19:09:21 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 204949] panic: mtx_lock of spin mutex @ /usr/src/head/sys/kern/vfs_subr.c:512 Message-ID: <bug-204949-8-PVDaZ7nX7v@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204949-8@https.bugs.freebsd.org/bugzilla/> References: <bug-204949-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204949 --- Comment #7 from Jason Unovitch <junovitch@freebsd.org> --- (In reply to Konstantin Belousov from comment #6) > What does 'M' mean in your kernel revision ? What changes did you apply ? I have applied the patch in bug 158160 to let coretemp recognize my Atom CPU. This only impacts my home router but I have it applied to my source for this NAS machine as well even though it is a no-op there. The relevant files changed: M share/man/man4/coretemp.4 M sys/dev/coretemp/coretemp.c I realize the core dumps are rather useless now without the kernel.debug. I'm learning as I go here. Let me know what else you may need. > From the core at the reference above, in kgdb do 'frame 12\nprint *mp' and post the result. https://people.FreeBSD.org/~junovitch/working/PR204949/r291461M-GENERIC-crashdump/frame12-printmp.txt -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204949-8-PVDaZ7nX7v>