Date: Sat, 17 Feb 2018 16:39:43 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Andrew Reilly <areilly@bigpond.net.au> Cc: current@freebsd.org, kib@freebsd.org Subject: Re: Since last week (today) current on my Ryzen box is unstable Message-ID: <e0f1de46-8411-b8ec-4457-b293bbb44488@FreeBSD.org> In-Reply-To: <0CEA9D55-D488-42EC-BBDE-D0B7CE58BAEA@bigpond.net.au> References: <0CEA9D55-D488-42EC-BBDE-D0B7CE58BAEA@bigpond.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17/02/2018 14:16, Andrew Reilly wrote: > Today's rebuild has given me uptimes of below an hour, usually. The box will > stay up in single user mode long enough to rebuild world/kernel, but > multi-user it is panicking at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c:1592 > > The backtrace shows that it gets to this panic from a sendfile() syscall. > The line above is in the middle of a big edit that's part of svn revision > 329363. The tripping assertion seems to suggest that m->valid != 0, for > whatever that's worth. The panic message and the backtrace would be a good start, but a crash dump is probably what's really needed to analyze the issue. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e0f1de46-8411-b8ec-4457-b293bbb44488>