On 31/05/2018 05:04, Jonathan T. Looney wrote: > On Tue, May 29, 2018 at 10:18 AM, Andriy Gapon <a...@freebsd.org > <mailto:a...@freebsd.org>> wrote: > > > [ping] > > On 21/05/2018 11:44, Andriy Gapon wrote: > > > > FreeBSD 12.0-CURRENT amd64 r332472 > > Does this panic ring a bell to anyone? > > Has it already been fixed? > > Thank you! > > > Is there any chance that r333703 fixes this problem for you? It fixes a race > that can manifest itself in other ways. I'm honestly not sure whether it could > also cause this problem.
Thank you for the suggestion. I guess it's worth trying that fix. I'll report back in a while. -- Andriy Gapon _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
