Date: Thu, 27 Apr 2017 16:45:19 -0400 From: Tom Uffner <tom@uffner.com> To: freebsd-current <freebsd-current@freebsd.org> Subject: Re: panics in network stack in 12-current Message-ID: <e8888a26-71ba-2df3-ede1-10d9aedf008f@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
[-- Attachment #1 --]
Andrey V. Elsukov wrote:
> On 27.04.2017 08:42, Tom Uffner wrote:
>> Tom Uffner wrote:
>>> Andrey V. Elsukov wrote:
>>>> I think the most of these panics should be fixed in r315956.
>>>
>>> thanks. I'll give it a try and report back as soon as I have a result.
>>
>> r315956 panicked about 22 min after boot. failed to dump a core.
>
> Why not update to the latest revision?
>
> 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.
attached is a text dump from this version
[-- Attachment #2 --]
BZh91AY&SYz z`;lyC}+cgAzI}z<>va
\ zm=%CC"z@xut]ُ3ȋ'}vzj=춽<>*@^QPnϯwl8\Q}iϛ\ϳ*溷o5]vϼ3n(t{bE{ޚlw7}Z苄d[j۷vnFnk62۹12y8bW늧&>C:% 4 S54R
!B&iS&4`&