https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212812
Sean Chittenden <se...@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ma...@freebsd.org
--- Comment #96 from Sean Chittenden <se...@freebsd.org> ---
I believe this has been fixed. There were a number of commits that markj@
made, but I believe the following was the actual culprit (thank you markj@!):
https://reviews.freebsd.org/D16515
I've been using a version of -CURRENT that is 4d old (~Aug 9th 2018,
12.0-ALPHA1) and have not had any problems since upgrading my kernel to pull in
these patches.
At best the mfs workarounds only reduce the likelihood of occurrence, but don't
actually prevent the problem. It would be good for someone else to confirm
this so we can begin removing the incorrect suggestion in pkg-message and point
people in the direction of upgrading to a version of the kernel that doesn't
have this bug.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-chromium@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-chromium
To unsubscribe, send any mail to "freebsd-chromium-unsubscr...@freebsd.org"
