Date: Thu, 26 Dec 2013 14:18:52 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: Berend de Boer <berend@pobox.com> Cc: freebsd-pf@freebsd.org Subject: Re: Network severely unstable 10.0-PRERELEASE Message-ID: <20131226101852.GO71033@FreeBSD.org> In-Reply-To: <20131226101738.GN71033@glebius.int.ru> References: <87sitku33x.wl%berend@pobox.com> <20131225132752.GK71033@FreeBSD.org> <877gasu3oa.wl%berend@pobox.com> <20131226101738.GN71033@glebius.int.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 26, 2013 at 02:17:38PM +0400, Gleb Smirnoff wrote: T> On Thu, Dec 26, 2013 at 08:32:53AM +1300, Berend de Boer wrote: T> B> Gleb> Does the system panic the same way as described in T> B> Gleb> misc/182141) on 10.0? T> B> T> B> Indeed, no change. Purely a kernel issue. Repeatable since FreeBSD T> B> 9.x, across 10.x, across 32-bit and 64-bit. T> B> T> B> There's a related issue: T> B> T> B> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/182557 T> B> T> B> Let me know if you need anything else from me. T> B> T> B> I've just grabbed the latest FreeBSD 10 sources, and recompiling now. T> B> T> B> Next Monday I'm able to enable the bug triggering keyword again (not T> B> now, all the family is here and wants a stable network :-) ). T> T> What is the bug triggering keyword? Can you please provide a minimal T> configuration that reproduced the bug? Already see it in the kern/182557. Thanks! -- Totus tuus, Glebius.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131226101852.GO71033>