Date: Wed, 16 May 2018 09:54:32 -0400 From: Mike Tancsa <mike@sentex.net> To: Dimitry Andric <dim@FreeBSD.org> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@FreeBSD.org> Subject: Re: uptime / w coredumping on RELENG11 (i386 only) Message-ID: <865dd1e1-b29e-7d5b-41a5-e23a07b2f981@sentex.net> In-Reply-To: <18E4C626-410B-417F-89F2-4F16074749A1@FreeBSD.org> References: <990862af-7bee-0d4b-c01f-d7fc8e5b6cfe@sentex.net> <955d6681-0048-5e09-cca6-4691b05bf48f@sentex.net> <18E4C626-410B-417F-89F2-4F16074749A1@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/15/2018 2:31 PM, Dimitry Andric wrote: > On 15 May 2018, at 20:22, Mike Tancsa <mike@sentex.net> wrote: >> >>> >>> Anyone else see this ? > > See <https://bugs.freebsd.org/227552>. There is a fix coming up. > Hi, I tried the patch and did a full rebuild and it indeed fixed the problem for me. Is the bug potentially more wide spread that just libxo ? Also does it possibly affect amd64, just in a non obvious way ? ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?865dd1e1-b29e-7d5b-41a5-e23a07b2f981>