From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208947] amdgpu DisplayPort won't recognize all display modes after 5.9 merges
Date: Sat, 02 Jan 2021 03:22:24 +0000 [thread overview]
Message-ID: <bug-208947-2300-7oCmXEcroT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208947-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208947
JerryD (jvdelisle@charter.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle@charter.net
--- Comment #18 from JerryD (jvdelisle@charter.net) ---
From comment 8 of bug #210849
[ 224.767359] Call Trace:
[ 224.767529] amdgpu_dm_backlight_update_status+0xb4/0xc0 [amdgpu]
[ 224.767535] backlight_suspend+0x6a/0x80
[ 224.767538] ? brightness_store+0x50/0x50
[ 224.767541] dpm_run_callback+0x4f/0x140
[ 224.767544] __device_suspend+0x11c/0x4a0
[ 224.767547] dpm_suspend+0x117/0x250
[ 224.767549] dpm_suspend_start+0x77/0x80
[ 224.767554] suspend_devices_and_enter+0xe6/0x7f0
[ 224.767557] pm_suspend.cold+0x333/0x38c
[ 224.767560] state_store+0x71/0xd0
[ 224.767565] kernfs_fop_write+0xce/0x1b0
[ 224.767569] vfs_write+0xc7/0x1f0
[ 224.767572] ksys_write+0x4f/0xc0
[ 224.767576] do_syscall_64+0x4d/0x90
[ 224.767580] entry_SYSCALL_64_after_hwframe+0x44/0xa9
Does this look like the same bug?
--
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-01-02 3:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 21:02 [Bug 208947] New: amdgpu DisplayPort won't recognize all display modes after 5.9 merges bugzilla-daemon
2020-08-18 0:19 ` [Bug 208947] " bugzilla-daemon
2020-08-18 13:28 ` bugzilla-daemon
2020-08-18 18:22 ` bugzilla-daemon
2020-08-18 18:24 ` bugzilla-daemon
2020-08-18 18:27 ` bugzilla-daemon
2020-08-18 18:29 ` bugzilla-daemon
2020-08-18 18:30 ` bugzilla-daemon
2020-08-18 23:30 ` bugzilla-daemon
2020-08-19 22:22 ` bugzilla-daemon
2020-08-19 22:53 ` bugzilla-daemon
2020-08-20 3:20 ` bugzilla-daemon
2020-08-20 5:01 ` bugzilla-daemon
2020-08-20 23:22 ` bugzilla-daemon
2020-08-20 23:31 ` bugzilla-daemon
2020-08-21 2:18 ` bugzilla-daemon
2020-08-21 2:51 ` bugzilla-daemon
2020-08-21 19:52 ` bugzilla-daemon
2020-08-22 22:52 ` bugzilla-daemon
2021-01-02 3:22 ` bugzilla-daemon [this message]
2021-01-03 8:59 ` bugzilla-daemon
2021-01-03 9:05 ` bugzilla-daemon
2021-01-10 22:59 ` 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-208947-2300-7oCmXEcroT@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