From: Michael Cree <mcree@orcon.net.nz>
To: Bob Tracy <rct@frus.com>, "Maciej W. Rozycki" <macro@orcam.me.uk>,
debian-alpha@lists.debian.org, linux-alpha@vger.kernel.org
Cc: "Christian König" <christian.koenig@amd.com>
Subject: Re: X11 system lockup with 5.11.0 kernel
Date: Mon, 5 Apr 2021 21:58:25 +1200 [thread overview]
Message-ID: <20210405095825.GA17443@tower> (raw)
In-Reply-To: <20210405045515.GA6637@tower>
On Mon, Apr 05, 2021 at 04:55:15PM +1200, Michael Cree wrote:
> On Sun, Apr 04, 2021 at 11:47:58PM -0500, Bob Tracy wrote:
> > On Wed, Mar 31, 2021 at 11:04:42AM +0200, Maciej W. Rozycki wrote:
> > > I think the only feasible way of determining what has happened here is
> > > that you track the offending change down by bisecting the upstream kernel
> > > repository with `git bisect'.
> >
> > That would normally be what I would do, and it may yet happen. Problem
> > is, I don't have a 64-bit system with enough disk space to do the kernel
> > builds with a cross-compiler, and local (native) builds on the PWS are
> > taking 36+ hours each these days. Unless I get *really* lucky with the
> > bisects, the task will take a couple of weeks.
>
> Confirmed that v5.11.0 hard locks up on presenting the X-Desktop
> login screen whereas v5.10.0 is fine. This is on a XP1000 with
> a Radeon HD4350.
And the first bad commit is:
0fe3cf3a53b5c1205ec7d321be1185b075dff205 is the first bad commit
commit 0fe3cf3a53b5c1205ec7d321be1185b075dff205
Author: Christian König <christian.koenig@amd.com>
Date: Sat Oct 24 13:12:23 2020 +0200
drm/radeon: switch to new allocator v2
It should be able to handle all cases here.
v2: fix debugfs as well
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Dave Airlie <airlied@redhat.com>
Reviewed-by: Madhav Chauhan <madhav.chauhan@amd.com>
Tested-by: Huang Rui <ray.huang@amd.com>
Link: https://patchwork.freedesktop.org/patch/397088/?series=83051&rev=1
:040000 040000 4e643ef861b921392bc67be21a42298c91c7ff7a b36453567c3176a3cd50fa0b23886b0fd642560d M drivers
Cheers
Michael.
next prev parent reply other threads:[~2021-04-05 9:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 14:48 X11 system lockup with 5.11.0 kernel Bob Tracy
2021-03-26 4:37 ` Bob Tracy
2021-03-31 9:04 ` Maciej W. Rozycki
2021-04-05 4:47 ` Bob Tracy
2021-04-05 4:55 ` Michael Cree
2021-04-05 9:58 ` Michael Cree [this message]
2021-04-05 10:14 ` Kirsten Bromilow
2021-04-06 7:08 ` Christian König
2021-04-06 9:14 ` Michael Cree
2021-04-06 10:15 ` Christian König
2021-04-06 10:19 ` John Paul Adrian Glaubitz
2021-06-03 3:41 ` Bob Tracy
2021-06-03 13:15 ` Maciej W. Rozycki
2021-06-04 5:18 ` Bob Tracy
2021-06-04 5:37 ` Bob Tracy
2021-07-01 12:41 ` Bob Tracy
2021-09-05 23:00 ` Michael Cree
2021-09-23 14:07 ` Bob Tracy
2021-04-06 10:08 ` Kirsten Bromilow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210405095825.GA17443@tower \
--to=mcree@orcon.net.nz \
--cc=christian.koenig@amd.com \
--cc=debian-alpha@lists.debian.org \
--cc=linux-alpha@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=rct@frus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).