linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Niklas <Hgntkwis@vfemail.net>
To: linux-kernel@vger.kernel.org
Cc: christian.koenig@amd.com, alexander.deucher@amd.com,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	David1.Zhou@amd.com
Subject: [Regression] amdgpu driver broken on AMD HD7770 GHz edition.
Date: Thu, 15 Apr 2021 21:25:08 -0400	[thread overview]
Message-ID: <20210415212508.7ef57d73@Zen-II-x12.niklas.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2181 bytes --]

Hello,
I have tested and found this bug to occur on the specified bisected
commit through Linux Kernel version 5.11.12.
I am running Devuan (Debian) Linux with a hand created kernel config. I'm
attaching it.

I've bisected the kernel and found the broken commit. Here's how I got
there in case you're curious: for i in "start v4.19-rc1 v4.18" bad good
good skip skip good good skip good skip good skip good good bad good good
bad good bad good bad bad good; do git bisect $i; done

The broken commit is this one:
commit 8eaf2b1faaf4358c6337785f2192055c6ef41e0d
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Mon Jul 2 14:35:36 2018 -0500

    drm/amdgpu: switch firmware path for SI parts
    
    Use separate firmware path for amdgpu to avoid conflicts
    with radeon on SI parts.
    
    Reviewed-by: Chunming Zhou <david1.zhou@amd.com>
    Reviewed-by: Christian Knig <christian.koenig@amd.com>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

 drivers/gpu/drm/amd/amdgpu/gfx_v6_0.c | 56 +++++++++++++++++------------------
 drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c | 14 ++++-----
 drivers/gpu/drm/amd/amdgpu/si_dpm.c   | 22 +++++++------- 3 files
 changed, 46 insertions(+), 46 deletions(-)

The last few messages before the whole system, including the network
part of the LK and USB subsystem of the LK freezes up/powers down are:
#15
#16
#17
#18
#19
#20
#21
#22
#23

I think that's telling my that I have 24 threads in my 3900X.

During boot up, I don't even reach init. The whole system freezes. I
don't see any boot up messages that suggest a problem with anything. I
see only a very few massages at all. I did enable early printk.

Steps to reproduce:
1: Build kernel with my config on a bad commit.
2: Boot new kernel (with an AMD HD7770 GPU installed, of course).
3: profit.

If you even think of suggesting I upgrade to a newer GPU, recall also
that there are none in stock -- and any GPU that is is priced
unbelievably high. I'd love a newer GPU. But I'm going to have to wait
like I have been for years for RDNA's big Navi (I was hoping it was
compute/gaming oriented like a Titan. It looks like it's not.
Grrrr, more waiting...)

Thanks,
David

[-- Attachment #2: config-regression.conf.xz --]
[-- Type: application/x-xz, Size: 44208 bytes --]

             reply	other threads:[~2021-04-16  1:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16  1:25 David Niklas [this message]
2021-04-16  2:16 ` [Regression] amdgpu driver broken on AMD HD7770 GHz edition David Niklas
2021-04-16  5:35   ` Alex Deucher

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=20210415212508.7ef57d73@Zen-II-x12.niklas.com \
    --to=hgntkwis@vfemail.net \
    --cc=David1.Zhou@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).