From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 204365] New: amdgpu crashes when using parameter "drm.edid_firmware"
Date: Mon, 29 Jul 2019 14:21:22 +0000 [thread overview]
Message-ID: <bug-204365-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=204365
Bug ID: 204365
Summary: amdgpu crashes when using parameter
"drm.edid_firmware"
Product: Drivers
Version: 2.5
Kernel Version: 5.2.4
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: felixhaedicke@web.de
Regression: No
Created attachment 284027
--> https://bugzilla.kernel.org/attachment.cgi?id=284027&action=edit
dmesg log with amdgpu crash
As a workaround for the problem described in bug 204363, I am using the
parameter "drm.edid_firmware" parameter to override the EDID.
This EDID seems to work fine, if I log in to my desktop (GNOME 3.32 unter
X.org) before plugging in the HDMI cable to the projector. But when the HDMI
cable is plugged in during boot, or when launching Wayland or X.org when the
cable is plugged in, the graphics driver crashes with the following error
message:
kernel BUG at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:6264!
Full dmesg log attached.
--
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
reply other threads:[~2019-07-29 14:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-204365-2300@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 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.