From: Matthew Hall <mhall@mhcomputing.net>
To: "Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: "Pan, Xinhui" <Xinhui.Pan@amd.com>,
"Koenig, Christian" <Christian.Koenig@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: AMDGPU crash - request for assistance triaging / reporting
Date: Fri, 21 Jul 2023 11:01:31 -0700 [thread overview]
Message-ID: <20230721180131.GA10297@mhcomputing.net> (raw)
In-Reply-To: <BL1PR12MB514416A3C79BA1E6F43FEF83F73FA@BL1PR12MB5144.namprd12.prod.outlook.com>
On Fri, Jul 21, 2023 at 01:33:02PM +0000, Deucher, Alexander wrote:
> Please file a bug here:
> https://gitlab.freedesktop.org/drm/amd/-/issues
OK, here it is:
https://gitlab.freedesktop.org/drm/amd/-/issues/2718
> I believe the Z16 was certified on ubuntu, so you should have a good
> experience with the latest ubuntu LTS with the OEM kernel package.
I tried everything stock first, and that causes the crash more than the newer
kernel, with more serious memory ring corruption sorts of errors.
The messages from the newer kernels are tamer and less frequent, but still
present.
> One issue we've run into is with the PSR TCON controller on some
> models. Disabling PSR in the driver can work around that.
I see some directions about disabling the PSR using some sysfs controls. Is
there a more reliable way of disabling it with a boot flag or something that's
more... guaranteed to intercept it and shut it off before any display managers
launch? Here is what I am currently seeing, let me know what else I can dump
out...
# find /sys/kernel/debug | fgrep -i psr | sort
/sys/kernel/debug/dri/1/eDP-1/psr_capability
/sys/kernel/debug/dri/1/eDP-1/psr_residency
/sys/kernel/debug/dri/1/eDP-1/psr_state
# head -1000 /sys/kernel/debug/dri/1/eDP-1/psr_*
==> /sys/kernel/debug/dri/1/eDP-1/psr_capability <==
Sink support: yes [0x01]
Driver support: yes
==> /sys/kernel/debug/dri/1/eDP-1/psr_residency <==
0
==> /sys/kernel/debug/dri/1/eDP-1/psr_state <==
0
> A newer kernel also fixes the issue.
How new? Or what branch or sub-branch? I have compiled plenty of them back
when Linux used to need it more often in the 90s. So I will gladly run
whatever you want and get logs or whatever.
Thanks again for your assistance.
Regards,
Matthew.
next prev parent reply other threads:[~2023-07-21 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 3:43 AMDGPU crash - request for assistance triaging / reporting Matthew Hall
2023-07-21 13:33 ` Deucher, Alexander
2023-07-21 18:01 ` Matthew Hall [this message]
2024-02-22 0:14 ` Matthew Hall
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=20230721180131.GA10297@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=Alexander.Deucher@amd.com \
--cc=Christian.Koenig@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=amd-gfx@lists.freedesktop.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