Date: Sat, 20 Jun 2015 14:07:51 +0300 From: Dmitry Sivachenko <trtrmitya@gmail.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: FreeBSD Stable ML <stable@freebsd.org>, alc@freebsd.org Subject: Re: panic: wm_page_unwire Message-ID: <7643BD12-C684-4C50-93A8-C25CE5A535EC@gmail.com> In-Reply-To: <20150620100116.GU2080@kib.kiev.ua> References: <8436D969-5AF2-4189-A509-B44669906AEB@gmail.com> <60FB4B9C-CC80-4269-8C94-F9DE3D98EE0D@gmail.com> <20150620100116.GU2080@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 20 =C9=C0=CE=D1 2015 =C7., at 13:01, Konstantin Belousov = <kostikbel@gmail.com> wrote: >=20 >=20 > I was able to reproduce something related, this may be very well your > problem. Take the attached program. Select a scratch file on UFS = mount > point, say x. Run the following commands: > mlock_modify x& > dd if=3D/dev/zero of=3Dx bs=3D1 count=3D1 > fg > ^C <- system might panic at this point, if buffers are in short supply > dd if=3D/dev/zero of=3Dx bs=3D1 count=3D1 <- at this point, the system = must panic Yes, that is exactly two cases when I was able to reproduce a panic, so = it is apparently my issue. I tried your patch and I can confirm that it does fix the problem. Thanks!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7643BD12-C684-4C50-93A8-C25CE5A535EC>