Date: Mon, 6 Jun 2022 14:17:26 -0400 From: Mark Johnston <markj@freebsd.org> To: Paul Floyd <paulf2718@gmail.com> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Hang ast / pipelk / piperd Message-ID: <Yp5Etji1nw6CB9gb@nuc> In-Reply-To: <bf595064-e03c-e69d-9d93-3f7de52360c0@gmail.com> References: <84015bf9-8504-1c3c-0ba5-58d0d7824843@gmail.com> <dca6a5b4-6f0c-98c0-2f2d-6e5da7405af4@gmail.com> <YpTRj7jVE0jfbxPO@nuc> <b598c89e-f11a-eed1-3d74-c3ef37bc400a@gmail.com> <Ypd0ziZKcZ2pgm0P@nuc> <bf595064-e03c-e69d-9d93-3f7de52360c0@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 01, 2022 at 11:27:52PM +0200, Paul Floyd wrote: > On 6/1/22 14:16, Mark Johnston wrote: > > The fact that the problem apparently only occurs with 1 CPU suggests a > > scheduler bug, indeed. > > Here is the fresh procstat output I was able to reproduce the problem locally and narrow down the bug somewhat. If you can test a kernel patch, please try this one: https://reviews.freebsd.org/D35415 . I verified that it solves the hang in my test setup, but I didn't go any further than that yet.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Yp5Etji1nw6CB9gb>