Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 26 Sep 2020 10:14:35 +0300
From:      "S.N. Trigub" <strigub@dialektika.com>
To:        "Sergey V. Dyatko" <sergey.dyatko@gmail.com>, "Kristof Provost" <kp@FreeBSD.org>, "xt" <xtouqh@hotmail.com>
Cc:        "FreeBSD Current" <freebsd-current@freebsd.org>
Subject:   Re: iflib/bridge kernel panic
Message-ID:  <1646C7B3113541C0A684AD846CBF1EC0@SERJHOME>
In-Reply-To: <AM0PR06MB3986053B045707EF404B4749C0360@AM0PR06MB3986.eurprd06.prod.outlook.com>
References:  <CAExMvskTkVprZsfXHBUv9stpiCo1QBAzoOg1VrWd4kRbz0NyJg@mail.gmail.com> <58CADEBB-64FD-414E-AB19-E4F8D3CABCA5@FreeBSD.org> <20200925204745.6a08e357@laptop.domain> <AM0PR06MB3986053B045707EF404B4749C0360@AM0PR06MB3986.eurprd06.prod.outlook.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi!

There is some serios issue in kernel related to network interfaces.
See my message
"speedtest.net in multi connections mode causes the FreeBSD 13-CURRENT 
router to crash"
from 28 aug 2020.

I noticed that kernel every time goes into panic if users run on client 
computers in browser
speedtest.net in multi connections mode.
If my external network interface use VLAN this panic occurs when uplink has 
speed 100Mbits per second.
Without VLAN speedtest passes without any problems at 100Mbits channel but 
every time goes into panic
at 1Gbits outer channel.
During crash, the console screen goes out and the server (router) stops 
responding to the keyboard.
Can anyone do this test on their machine?

Sergei.


From: xt
Sent: Friday, September 25, 2020 8:46 PM
To: Sergey V. Dyatko ; Kristof Provost
Cc: FreeBSD Current
Subject: Re: iflib/bridge kernel panic

Sergey V. Dyatko wrote:
> On Mon, 21 Sep 2020 09:57:40 +0200
> "Kristof Provost" <kp@FreeBSD.org> wrote:
>
>> On 21 Sep 2020, at 2:52, Shawn Webb wrote:
>>>>  From latest HEAD on a Dell Precision 7550 laptop:
>>>
>>> https://gist.github.com/lattera/a0803f31f58bcf8ead51ac1ebbc447e2
>>>
>>> The last working boot environment was 14 Aug 2020. If I get some time to
>>> bisect commits, I'll try to figure out the culprit.
>>>
>> Try https://reviews.freebsd.org/D26418
>>
>> Best regards,
>> Kristof
>
> I'm not sure, but doesn't this panic have the same root as mine?
> Sorry, but I haven't text console and can post only screenshot[s]
>   from IP-KVM
> https://gyazo.com/fee41c5267e9fc543d43901e498b7c94
>
> rc.conf have something like:
> clonned_interfaces="lagg0 vlan101"
> ifconfig_lagg0="laggproto lacp laggport em0 laggport em1 x.x.x.x/mask"
> ifconfig_vlan101="vlan 101 vlandev lagg0 192.168.1.29/24"
>
> without VLAN part all works fine.
> Installed from FreeBSD-13.0-CURRENT-amd64-20200924-3c514403bef-disc1.iso

Yes, same panic.
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1646C7B3113541C0A684AD846CBF1EC0>