From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206987] [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration
Date: Thu, 11 Feb 2021 14:51:55 +0000 [thread overview]
Message-ID: <bug-206987-2300-Tb7ntLRHpM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206987-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206987
--- Comment #40 from Alex Deucher (alexdeucher@gmail.com) ---
(In reply to Jan Kokemüller from comment #39)
> Created attachment 295225 [details]
> Call DC_FP_START() / DC_FP_END() in dcn21_validate_bandwidth
>
> Could it be that DC_FP_START()/DC_FP_END() aka
> kernel_fpu_begin()/kernel_fpu_end() are not called in the
> *_validate_bandwidth code path on AMD Renoir systems? To my untrained eye it
> looks like it is missing, while it _is_ there for dcn20.
>
> I've been running the attached patch for 2 days now with some KVM VMs open
> and the system seems stable. Previously, I had similar crashes/backtraces
> @krakopo described.
>
> I'm happy to help testing any patches. I'm running a Thinkpad T14 with a AMD
> Ryzen 7 PRO 4750U (Renoir).
Looks correct. Care to send out a proper git patch?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-02-11 14:51 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 19:51 [Bug 206987] New: [drm] [amdgpu] Whole system crashes when the driver is in mode_support_and_system_configuration bugzilla-daemon
2020-03-26 19:54 ` [Bug 206987] " bugzilla-daemon
2020-03-26 21:36 ` bugzilla-daemon
2020-03-26 21:37 ` bugzilla-daemon
2020-04-04 7:40 ` bugzilla-daemon
2020-04-04 7:41 ` bugzilla-daemon
2020-04-04 7:42 ` bugzilla-daemon
2020-04-18 13:15 ` bugzilla-daemon
2020-04-18 13:19 ` bugzilla-daemon
2020-04-19 11:42 ` bugzilla-daemon
2020-04-19 11:43 ` bugzilla-daemon
2020-04-23 5:15 ` bugzilla-daemon
2020-04-23 5:15 ` bugzilla-daemon
2020-04-25 8:44 ` bugzilla-daemon
2020-04-25 8:44 ` bugzilla-daemon
2020-04-27 19:20 ` bugzilla-daemon
2020-04-27 19:20 ` bugzilla-daemon
2020-05-02 14:18 ` bugzilla-daemon
2020-05-23 1:52 ` bugzilla-daemon
2020-05-23 1:56 ` bugzilla-daemon
2020-05-23 1:58 ` bugzilla-daemon
2020-05-28 14:17 ` bugzilla-daemon
2020-05-28 16:05 ` bugzilla-daemon
2020-05-28 16:24 ` bugzilla-daemon
2020-05-28 18:56 ` bugzilla-daemon
2020-06-02 3:50 ` bugzilla-daemon
2020-06-03 1:34 ` bugzilla-daemon
2020-06-03 1:35 ` bugzilla-daemon
2020-06-03 1:36 ` bugzilla-daemon
2020-06-03 2:00 ` bugzilla-daemon
2020-06-03 2:28 ` bugzilla-daemon
2020-06-03 5:14 ` bugzilla-daemon
2020-06-03 11:05 ` bugzilla-daemon
2020-06-06 1:29 ` bugzilla-daemon
2020-06-06 6:42 ` bugzilla-daemon
2020-07-03 22:22 ` bugzilla-daemon
2020-07-15 16:07 ` bugzilla-daemon
2020-07-15 16:12 ` bugzilla-daemon
2020-07-17 4:40 ` bugzilla-daemon
2020-07-23 1:47 ` bugzilla-daemon
2020-08-19 6:37 ` bugzilla-daemon
2020-08-19 6:51 ` bugzilla-daemon
2020-08-20 3:30 ` bugzilla-daemon
2020-08-20 4:11 ` bugzilla-daemon
2020-08-20 4:21 ` bugzilla-daemon
2020-08-20 4:24 ` bugzilla-daemon
2021-02-11 7:48 ` bugzilla-daemon
2021-02-11 14:51 ` bugzilla-daemon [this message]
2021-02-11 18:36 ` bugzilla-daemon
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=bug-206987-2300-Tb7ntLRHpM@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@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;
as well as URLs for NNTP newsgroup(s).