Hamza Sheikh wrote:
I may have encountered something similar on an EdgeRouter Lite running
r317256. It's serving as network gateway at home. After some time the
WAN connection goes dead. It starts working with either (a)
reconnecting the network cable or (b) pinging any IP on the internet
from th
On Thu, Apr 27, 2017 at 10:02 AM, Tom Uffner wrote:
> 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
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
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 pr
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.
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.
___
free
Andrey V. Elsukov wrote:
On 26.04.2017 04:03, Tom Uffner 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.
___
freebsd-current@freebsd.org mailing list
https://l
On 26.04.2017 04:03, Tom Uffner wrote:
> Since updating my -current box to 12 several months ago, I have been
> trying to pin down several elusive and probably related panics.
>
> they always manifest a a trap out of rw_wlock_hard()
>
> i am fairly certain that r302409 was stable, revs up through
Since updating my -current box to 12 several months ago, I have been trying to
pin down several elusive and probably related panics.
they always manifest a a trap out of rw_wlock_hard()
i am fairly certain that r302409 was stable, revs up through r306792 may be
stable, or perhaps I just didn't
