Date: Tue, 11 Oct 2016 13:24:31 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: =?UTF-8?B?0JDQvdC00YDQtdC5INCb0LXRg9GI0LrQuNC9?= <laa88rf@gmail.com>, net@freebsd.org Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. Message-ID: <57FC859F.5000200@grosbein.net> In-Reply-To: <CAAFYNruF4gFAiTCAhyRUQzcovW2osrKn4ehiuNR0btJCZbnOGg@mail.gmail.com> References: <CAAFYNruF4gFAiTCAhyRUQzcovW2osrKn4ehiuNR0btJCZbnOGg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57FC859F.5000200>