From: Bjorn Helgaas <helgaas@kernel.org>
To: "Lazar, Lijo" <lijo.lazar@amd.com>
Cc: 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, "Tom Seewald" <tseewald@gmail.com>,
"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 06:04:37 -0500 [thread overview]
Message-ID: <20220819110437.GA2432401@bhelgaas> (raw)
In-Reply-To: <fc036a10-5c13-fdd7-9d98-2b5f0f8af383@amd.com>
On Fri, Aug 19, 2022 at 02:03:59PM +0530, Lazar, Lijo wrote:
> Or, it could be amdgpu or some other software component -
>
> register mmio base: 0x95E00000
> Address 0x95e7f000
>
> 0x95e7f000 indicates access from CPU to a register offset 0x7FE000. This
> doesn't look like a valid register offset for this chip (device
> [1002:73df]). Any other clues in dmesg?
The complete dmesg is at
https://bugzilla.kernel.org/attachment.cgi?id=301596
WARNING: multiple messages have this Message-ID (diff)
From: Bjorn Helgaas <helgaas@kernel.org>
To: "Lazar, Lijo" <lijo.lazar@amd.com>
Cc: "Christian König" <christian.koenig@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Xinhui Pan" <Xinhui.Pan@amd.com>,
regressions@lists.linux.dev, "David Airlie" <airlied@linux.ie>,
linux-pci@vger.kernel.org, amd-gfx@lists.freedesktop.org,
"Tom Seewald" <tseewald@gmail.com>,
"Kai-Heng Feng" <kai.heng.feng@canonical.com>,
"Daniel Vetter" <daniel@ffwll.ch>, "Stefan Roese" <sr@denx.de>
Subject: Re: [Bug 216373] New: Uncorrected errors reported for AMD GPU
Date: Fri, 19 Aug 2022 06:04:37 -0500 [thread overview]
Message-ID: <20220819110437.GA2432401@bhelgaas> (raw)
In-Reply-To: <fc036a10-5c13-fdd7-9d98-2b5f0f8af383@amd.com>
On Fri, Aug 19, 2022 at 02:03:59PM +0530, Lazar, Lijo wrote:
> Or, it could be amdgpu or some other software component -
>
> register mmio base: 0x95E00000
> Address 0x95e7f000
>
> 0x95e7f000 indicates access from CPU to a register offset 0x7FE000. This
> doesn't look like a valid register offset for this chip (device
> [1002:73df]). Any other clues in dmesg?
The complete dmesg is at
https://bugzilla.kernel.org/attachment.cgi?id=301596
next prev parent reply other threads:[~2022-08-19 11:04 UTC|newest]
Thread overview: 32+ 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-18 20:38 ` Bjorn Helgaas
2022-08-19 7:05 ` Christian König
2022-08-19 7:05 ` Christian König
2022-08-19 8:33 ` Lazar, Lijo
2022-08-19 11:04 ` Bjorn Helgaas [this message]
2022-08-19 11:04 ` Bjorn Helgaas
2022-08-19 17:13 ` Bjorn Helgaas
2022-08-19 17:13 ` Bjorn Helgaas
2022-08-19 19:07 ` Bjorn Helgaas
2022-08-19 19:07 ` Bjorn Helgaas
2022-08-20 7:52 ` Lazar, Lijo
2022-08-23 17:04 ` Tom Seewald
2022-08-23 17:04 ` Tom Seewald
2022-08-24 5:10 ` Lazar, Lijo
2022-08-24 5:10 ` Lazar, Lijo
2022-08-24 14:45 ` Tom Seewald
2022-08-24 14:45 ` Tom Seewald
2022-08-25 6:40 ` Stefan Roese
2022-08-25 6:40 ` Stefan Roese
2022-08-25 7:34 ` Christian König
2022-08-25 7:34 ` Christian König
2022-08-25 7:54 ` Lazar, Lijo
2022-08-25 7:54 ` Lazar, Lijo
2022-08-25 8:18 ` Christian König
2022-08-25 8:18 ` Christian König
2022-08-25 17:48 ` Bjorn Helgaas
2022-08-25 17:48 ` Bjorn Helgaas
2022-08-26 7:10 ` Christian König
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=20220819110437.GA2432401@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.