Date: Tue, 11 Oct 2016 08:30:06 -0300 From: Cassiano Peixoto <peixotocassiano@gmail.com> To: Eugene Grosbein <eugen@grosbein.net> Cc: =?UTF-8?B?0JDQvdC00YDQtdC5INCb0LXRg9GI0LrQuNC9?= <laa88rf@gmail.com>, net@freebsd.org Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. Message-ID: <CAJajdNUXOrzWDKVmSB1Xm_G6zqBhMsZ2vesDcAw2CPGFBU0xtg@mail.gmail.com> In-Reply-To: <57FC859F.5000200@grosbein.net> References: <CAAFYNruF4gFAiTCAhyRUQzcovW2osrKn4ehiuNR0btJCZbnOGg@mail.gmail.com> <57FC859F.5000200@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, There are many users complaining about this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114 I've been dealing with this issue for one year with no solution. mpd5 as pppoe server on FreeBSD is useless with this bug. I really would like to see it working again, i think it's quite important to both project and many users. Thanks. On Tue, Oct 11, 2016 at 3:24 AM, Eugene Grosbein <eugen@grosbein.net> wrote: > 11.10.2016 11:02, Андрей Леушкин пишет: > >> Hello. I have problem with "FreeBSD nas 10.3-RELEASE FreeBSD 10.3-RELEASE >> #0: Fri Oct 7 21:12:56 YEKT 2016 nas@nas:/usr/obj/usr/src/sys/nasv3 >> amd64" >> >> Kernel panic is repeated at intervals of 2-3 days. At first I thought that >> the problem is in the hardware, but the problem did not go away after >> replacing the server platform. >> >> Coredumps and more info on link >> https://drive.google.com/open?id=0BxciMy2q7ZjTTkIxem9wTE1tM2M >> >> Sorry for my english. >> I'll wait for an answer. >> > > This is known and long-stanging problem in the FreeBSD network stack. > It shows up when you have lots of network interfaced created/removed > frequently > like in your case of Network Access Server (PPtP, PPPoE etc). > > Generally, people run into this problem using mpd5 network daemon. > mpd5 uses NETGRAPH kernel subsystem to process traffic and > if an interface disappears (f.e., ,user disconnected) > while kernel still processes traffic obtained from this interface, it > panices. > > There were lots of reports of this problem. Noone seems to be working on > it at the moment. > You should fill a PR using Bugzilla and attach your logs to it. > > Eugene Grosbein > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJajdNUXOrzWDKVmSB1Xm_G6zqBhMsZ2vesDcAw2CPGFBU0xtg>