Date: Thu, 25 Sep 2008 19:05:58 -0400 From: Jeff Wheelhouse <freebsd-hackers@wheelhouse.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: panic: lockmgr on FreeBSD 7.0-RELEASE-p4 amd64 Message-ID: <E263BAA0-6B65-429B-A332-6AF374D4B91E@wheelhouse.org> In-Reply-To: <200809251553.48978.jhb@freebsd.org> References: <D1048988-FAB7-4EDE-9EB8-8E01041C3F2A@wheelhouse.org> <200809250845.06042.jhb@freebsd.org> <61B6EB36-0E0C-4FFA-A84B-B434050B6244@wheelhouse.org> <200809251553.48978.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 25, 2008, at 3:53 PM, John Baldwin wrote: > You can use KTR instead of printf perhaps and then use 'show ktr' > from DDB. > This won't have the same impact on timing as printf(). I would > include PIDs > in any KTR traces you do so it's easier to parse the interleaved > entries from > multiple CPUs. OK, while I am educating myself about how KTR works, what would you like to see? Just mp->mnt_vnodecovered? > Also, if you have a good test case, it might be worth > grabbing a box w/o gmirror that can generate a crashdump and > reproduce it > there. Not an option for us right now; spare 8-core boxes are hard to come by. We're looking for a USB hard drive or something we can dump to. Thanks, Jeff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E263BAA0-6B65-429B-A332-6AF374D4B91E>