From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 210849] Black screen after resume from long suspend. Open/Close lid. AMDGPU
Date: Fri, 01 Jan 2021 18:04:12 +0000 [thread overview]
Message-ID: <bug-210849-2300-h2HM1AXhA1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210849-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210849
--- Comment #8 from JerryD (jvdelisle@charter.net) ---
In the 5.18 kernel which does not hang on me I also have a segfault:
[ 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
This happens coming out of suspend. So pretty sure amdgpu is the culprit.
--
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-01 18:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 11:15 [Bug 210849] New: Black screen after resume from long suspend. Open/Close lid. AMDGPU bugzilla-daemon
2020-12-22 11:18 ` [Bug 210849] " bugzilla-daemon
2020-12-22 11:18 ` bugzilla-daemon
2020-12-22 11:20 ` bugzilla-daemon
2020-12-22 11:25 ` bugzilla-daemon
2020-12-22 11:28 ` bugzilla-daemon
2020-12-23 18:36 ` bugzilla-daemon
2020-12-27 3:03 ` bugzilla-daemon
2020-12-27 3:31 ` bugzilla-daemon
2020-12-30 20:53 ` bugzilla-daemon
2021-01-01 18:04 ` bugzilla-daemon [this message]
2021-01-05 20:43 ` bugzilla-daemon
2021-02-05 4:35 ` bugzilla-daemon
2021-02-05 15:40 ` bugzilla-daemon
2021-02-05 17:46 ` bugzilla-daemon
2021-02-05 18:37 ` bugzilla-daemon
2021-02-05 19:01 ` bugzilla-daemon
2021-02-06 16:52 ` bugzilla-daemon
2021-02-09 4:40 ` bugzilla-daemon
2021-02-13 1:30 ` bugzilla-daemon
2021-03-08 3:01 ` 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-210849-2300-h2HM1AXhA1@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