From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bob Tracy Subject: Re: X11 system lockup with 5.11.0 kernel Date: Fri, 4 Jun 2021 00:18:58 -0500 Message-ID: References: <20210405045515.GA6637@tower> <20210405095825.GA17443@tower> <20210406091431.GA4462@tower> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: List-ID: Content-Type: text/plain; charset="iso-8859-1" To: "Maciej W. Rozycki" Cc: John Paul Adrian Glaubitz , Christian =?iso-8859-1?Q?K=F6nig?= , Michael Cree , debian-alpha@lists.debian.org, linux-alpha@vger.kernel.org On Thu, Jun 03, 2021 at 03:15:05PM +0200, Maciej W. Rozycki wrote: > I have lost track about this issue, so please fill me in as to whether=20 > the offending commit causing the regression has been bisected or not. It has. Michael Cree reported the following back on April 5th: And the first bad commit is: 0fe3cf3a53b5c1205ec7d321be1185b075dff205 is the first bad commit commit 0fe3cf3a53b5c1205ec7d321be1185b075dff205 Author: Christian K=F6nig Date: Sat Oct 24 13:12:23 2020 +0200 drm/radeon: switch to new allocator v2 =20 It should be able to handle all cases here. =20 v2: fix debugfs as well =20 Signed-off-by: Christian K=F6nig Reviewed-by: Dave Airlie Reviewed-by: Madhav Chauhan Tested-by: Huang Rui Link: https://patchwork.freedesktop.org/patch/397088/?series=3D83051&re= v=3D1 :040000 040000 4e643ef861b921392bc67be21a42298c91c7ff7a b36453567c3176a3cd5= 0fa0b23886b0fd642560d M drivers --Bob