Date: Sun, 5 Jan 2014 11:01:55 +0200 From: Markiyan Kushnir <markiyan.kushnir@gmail.com> To: freebsd-current@freebsd.org Subject: Re: 11.0-CURRENT panic (nfsd?) Message-ID: <CACvtUJcw5iE8tmdLR4jB%2B373J2BQYCbY=cp9dE-agQP%2BDkw8xA@mail.gmail.com> In-Reply-To: <CACvtUJe0UJ%2BeKayG%2BThtVY_mZe4hYR=utJdJt4j_x2M06dgYXA@mail.gmail.com> References: <CACvtUJe0UJ%2BeKayG%2BThtVY_mZe4hYR=utJdJt4j_x2M06dgYXA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Please ignore the attached core.txt.1.gz, and see the new core.txt.2.gz in this attachment. I confused files. -- Markiyan. 2014/1/5 Markiyan Kushnir <markiyan.kushnir@gmail.com>: > 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. > > -- > Markiyan.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACvtUJcw5iE8tmdLR4jB%2B373J2BQYCbY=cp9dE-agQP%2BDkw8xA>