From: Bjorn Helgaas <helgaas@kernel.org>
To: Tom Seewald <tseewald@gmail.com>
Cc: "Lijo Lazar" <lijo.lazar@amd.com>,
regressions@lists.linux.dev, "David Airlie" <airlied@linux.ie>,
linux-pci@vger.kernel.org, "Xinhui Pan" <Xinhui.Pan@amd.com>,
amd-gfx@lists.freedesktop.org,
"Kai-Heng Feng" <kai.heng.feng@canonical.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Stefan Roese" <sr@denx.de>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [Bug 216373] New: Uncorrected errors reported for AMD GPU
Date: Fri, 19 Aug 2022 14:07:25 -0500 [thread overview]
Message-ID: <20220819190725.GA2499154@bhelgaas> (raw)
In-Reply-To: <20220819171303.GA2491617@bhelgaas>
On Fri, Aug 19, 2022 at 12:13:03PM -0500, Bjorn Helgaas wrote:
> On Thu, Aug 18, 2022 at 03:38:12PM -0500, Bjorn Helgaas wrote:
> > [Adding amdgpu folks]
> >
> > On Wed, Aug 17, 2022 at 11:45:15PM +0000, bugzilla-daemon@kernel.org wrote:
> > > https://bugzilla.kernel.org/show_bug.cgi?id=216373
> > >
> > > Bug ID: 216373
> > > Summary: Uncorrected errors reported for AMD GPU
> > > Kernel Version: v6.0-rc1
> > > Regression: No
>
> Tom, thanks for trying out "pci=noaer". Hopefully we won't need the
> workaround for long.
>
> Could I trouble you to try the debug patch below and see if we get any
> stack trace clues in dmesg when the error happens? I'm sure the
> experts would have a better approach, but I'm amdgpu-illiterate, so
> this is all I can do :)
Thanks for doing this, Tom! For everybody else, Tom attached a dmesg
log to the bugzilla: https://bugzilla.kernel.org/attachment.cgi?id=301606
Lots of traces of the form:
amdgpu_device_wreg.part.0.cold+0xb/0x17 [amdgpu]
amdgpu_gart_invalidate_tlb+0x22/0x60 [amdgpu]
gmc_v10_0_hw_init+0x44/0x180 [amdgpu]
amdgpu_device_wreg.part.0.cold+0xb/0x17 [amdgpu]
gmc_v10_0_hw_init+0xa8/0x180 [amdgpu]
amdgpu_device_wreg.part.0.cold+0xb/0x17 [amdgpu]
gmc_v10_0_flush_gpu_tlb+0x35/0x280 [amdgpu]
amdgpu_gart_invalidate_tlb+0x46/0x60 [amdgpu]
gmc_v10_0_hw_init+0x44/0x180 [amdgpu]
I tried connecting the dots but I gave up chasing all the function
pointers.
next prev parent reply other threads:[~2022-08-19 19:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-216373-41252@https.bugzilla.kernel.org/>
2022-08-18 20:38 ` [Bug 216373] New: Uncorrected errors reported for AMD GPU Bjorn Helgaas
2022-08-19 7:05 ` Christian König
2022-08-19 8:33 ` Lazar, Lijo
2022-08-19 11:04 ` Bjorn Helgaas
2022-08-19 17:13 ` Bjorn Helgaas
2022-08-19 19:07 ` Bjorn Helgaas [this message]
2022-08-20 7:52 ` Lazar, Lijo
2022-08-23 17:04 ` Tom Seewald
2022-08-24 5:10 ` Lazar, Lijo
2022-08-24 14:45 ` Tom Seewald
2022-08-25 6:40 ` Stefan Roese
2022-08-25 7:34 ` Christian König
2022-08-25 7:54 ` Lazar, Lijo
2022-08-25 8:18 ` Christian König
2022-08-25 17:48 ` Bjorn Helgaas
2022-08-26 7:10 ` Christian König
2022-08-25 15:05 ` Felix Kuehling
2022-08-23 16:01 ` [Bug 216373] New: Uncorrected errors reported for AMD GPU #forregzbot Thorsten Leemhuis
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=20220819190725.GA2499154@bhelgaas \
--to=helgaas@kernel.org \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=kai.heng.feng@canonical.com \
--cc=lijo.lazar@amd.com \
--cc=linux-pci@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=sr@denx.de \
--cc=tseewald@gmail.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).