Date: Fri, 20 May 2016 09:41:53 -0400 From: Robert Blayzor <rblayzor.bulk@inoc.net> To: stable@freebsd.org Subject: Re: Failed to write core file (error 14) Message-ID: <F715F09D-B915-419F-8D1C-BA337BBAEBBB@inoc.net> In-Reply-To: <573DECFB.9000707@erik.eu> References: <0C2CA3A7-181E-43FA-B381-53341DF3D9CD@gmail.com> <573DECFB.9000707@erik.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 19, 2016, at 12:42 PM, Erik <freebsd@erik.eu> wrote: >=20 > This sounds like: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204426 > and > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204764 >=20 >=20 > This problem exists since 10.2. > 10.1 is fine. The bug actually exists in 10.1 as well, at least from what I = experienced; it just happened =E2=80=9Cless=E2=80=9D. Something in 10.2 = agitated so the problem happened more frequently. I can confirm that it = did not exist in 10.0 however. Even with the fix from Bug 204426, I started experiencing some other = strange issues reported in: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209471 A process seems to get stuck in state =E2=80=9Cvmf_de=E2=80=9D. (from = the patch). I=E2=80=99m just having a hard time consistently recreating = the problem. I=E2=80=99m not sure what causes it or when. -- Robert inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP Key: 78BEDCE1 @ pgp.mit.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F715F09D-B915-419F-8D1C-BA337BBAEBBB>