Date: Thu, 27 Apr 2017 13:02:57 -0400 From: Tom Uffner <tom@uffner.com> To: "Andrey V. Elsukov" <bu7cher@yandex.ru>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: panics in network stack in 12-current Message-ID: <0dda5011-e74c-50d1-e8fa-088f123e30d2@uffner.com> In-Reply-To: <b401fa22-17ae-24c2-d5fc-bd70c8ee197f@yandex.ru> References: <bccb9c51-3dc2-ea38-15ff-0dbef83b25c1@uffner.com> <92a10822-3fde-f839-1836-92e8d936f2b6@yandex.ru> <841f1d22-b563-862c-a367-a475356781ef@uffner.com> <9c1f65f4-162b-a83d-1246-31d9e0525e4a@uffner.com> <b401fa22-17ae-24c2-d5fc-bd70c8ee197f@yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrey V. Elsukov wrote: > On 27.04.2017 08:42, Tom Uffner wrote: >> r315956 panicked about 22 min after boot. failed to dump a core. > > Why not update to the latest revision? I did several times a while ago, but didn't get a panic free system. I was hoping to bisect the point the point where the problem actually occurred and maybe send a patch instead of just begging for help. trouble was, I got down to a small number of revisions and none of them had any changes that looked even remotely related to my problem. I'll give today's HEAD a try. > Probably this is flowtable related, don't think it is usable. > Anyway we need the trace to determine the cause. Also it seems you have > VIMAGE enabled. This also have some known panics. OK, I will also try disabling flowtable. Not sure about VIMAGE. I don't have it specifically enabled, but I don't have it specifically disabled either if it defaults to on. I don't know much about it. I have also tried using the GENERIC kernel instead of my custom one, but it was even less stable on my hardware and bricked the system instead of panicking and producing a core dump.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0dda5011-e74c-50d1-e8fa-088f123e30d2>