Date: Sat, 20 Jun 2015 10:23:39 +0300 From: Dmitry Sivachenko <trtrmitya@gmail.com> To: FreeBSD Stable ML <stable@freebsd.org> Subject: Re: panic: wm_page_unwire Message-ID: <60FB4B9C-CC80-4269-8C94-F9DE3D98EE0D@gmail.com> In-Reply-To: <8436D969-5AF2-4189-A509-B44669906AEB@gmail.com> References: <8436D969-5AF2-4189-A509-B44669906AEB@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 19 =D0=B8=D1=8E=D0=BD=D1=8F 2015 =D0=B3., at 22:57, Dmitry = Sivachenko <trtrmitya@gmail.com> wrote: >=20 > Hello, >=20 > got this panic today on my 10.1-STABLE #0 r279956 box: >=20 > <Screen Shot 2015-06-19 at 22.52.57.png> Well, I tracked this down a bit. Rather easy way to panic -stable box = (mine is r279956), but I can't reliably reproduce this. It happens when there is a process running which mmap()+mlock() some = file, and while it is running this file is modified on disk (not rm+mv, but open the same file, truncate and write some other data = into it). After process exits, system will panic with high probability. So far I got 2 cases: 1) run process which mlock()'s a file; modify that file; stop process = and system panics 2) run process which mlock()'s a file; modify that file; stop process = [no panic so far]; modify that file again and system panics. Panic message is the same: panic: vm_page_unwire: page <xxxx>'s wire = count is zero=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?60FB4B9C-CC80-4269-8C94-F9DE3D98EE0D>