Date: Sun, 27 Sep 2020 17:51:32 +0200 From: "Kristof Provost" <kp@FreeBSD.org> To: "Shawn Webb" <shawn.webb@hardenedbsd.org> Cc: "FreeBSD Current" <freebsd-current@freebsd.org>, "Alexander Leidinger" <Alexander@leidinger.net> Subject: Re: iflib/bridge kernel panic Message-ID: <7FE1F106-2CEE-4692-95D0-14C5229ED768@FreeBSD.org> In-Reply-To: <20200921121627.3dovpumnl6xub3kn@mutt-hbsd> References: <CAExMvskTkVprZsfXHBUv9stpiCo1QBAzoOg1VrWd4kRbz0NyJg@mail.gmail.com> <58CADEBB-64FD-414E-AB19-E4F8D3CABCA5@FreeBSD.org> <20200921121627.3dovpumnl6xub3kn@mutt-hbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 Sep 2020, at 14:16, Shawn Webb wrote: > On Mon, Sep 21, 2020 at 09:57:40AM +0200, Kristof Provost 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 > > That seems to fix the kernel panic. dmesg gets spammed with a freak > ton of these LOR messages now: > Here’s an early version of a task queue based approach: http://people.freebsd.org/~kp/0001-bridge-Cope-with-if_ioctl-s-that-sleep.patch That still needs to be cleaned up, but this should resolve the sleep issue and the LOR. Best regards, Kristof
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7FE1F106-2CEE-4692-95D0-14C5229ED768>