Date: Fri, 25 Sep 2020 20:46:57 +0300 From: xt <xtouqh@hotmail.com> To: "Sergey V. Dyatko" <sergey.dyatko@gmail.com>, Kristof Provost <kp@FreeBSD.org> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: iflib/bridge kernel panic Message-ID: <AM0PR06MB3986053B045707EF404B4749C0360@AM0PR06MB3986.eurprd06.prod.outlook.com> In-Reply-To: <20200925204745.6a08e357@laptop.domain> References: <CAExMvskTkVprZsfXHBUv9stpiCo1QBAzoOg1VrWd4kRbz0NyJg@mail.gmail.com> <58CADEBB-64FD-414E-AB19-E4F8D3CABCA5@FreeBSD.org> <20200925204745.6a08e357@laptop.domain>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AM0PR06MB3986053B045707EF404B4749C0360>