Date: Sun, 5 Jan 2014 11:06:18 +0200 From: Markiyan Kushnir <markiyan.kushnir@gmail.com> To: Markiyan Kushnir <markiyan.kushnir@gmail.com>, freebsd-current@freebsd.org Subject: Re: 11.0-CURRENT panic (nfsd?) Message-ID: <CACvtUJf1mgNWPqJ4i1j_W8FZO3FELWskCYqrXkYz8BbypdcdUg@mail.gmail.com> In-Reply-To: <20140105090211.GS99167@funkthat.com> References: <CACvtUJe0UJ%2BeKayG%2BThtVY_mZe4hYR=utJdJt4j_x2M06dgYXA@mail.gmail.com> <20140105090211.GS99167@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2014/1/5 John-Mark Gurney <jmg@funkthat.com>: > Markiyan Kushnir wrote this message on Sun, Jan 05, 2014 at 10:57 +0200: >> I started to see a reliable panic on a recent CURRENT: >> >> $ uname -a >> FreeBSD mkushnir.mooo.com 11.0-CURRENT FreeBSD 11.0-CURRENT #0 >> r260296: Sun Jan 5 07:14:50 EET 2014 >> root@vm.mkushnir.mooo.com:/usr/obj/usr/src.svnup/sys/MAREK amd64 >> >> The panic is always triggered by the first request to the nfs service >> (this machine runs a PXE server). >> >> The core.txt is attached. Please let me know if I can help more. > > Apparently the mime-type on the attachment was bad and got scrubbed... > > Maybe include it inline if it isn't too long? > It's 144KB long. I will share it via Google Drive: https://drive.google.com/file/d/0B9Q-zpUXxqCnNVhBY0M5ZzU4d1k/edit?usp=sharing -- Markiyan. > -- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACvtUJf1mgNWPqJ4i1j_W8FZO3FELWskCYqrXkYz8BbypdcdUg>