From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105018] Kernel panic when waking up after screen goes blank.
Date: Mon, 30 Apr 2018 14:10:19 +0000 [thread overview]
Message-ID: <bug-105018-502-APvMz71FAC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105018-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 4569 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #31 from Öyvind Saether <oyvinds@everdot.org> ---
Kernel 4.17.0-rc3-linus.git-keumjo4.17.0-rc3-linus.git-keumjo on a 2400G with a
RX 560 GPU:
> login to xfce desktop
> type "xset dpms force standby" in a terminal
screens go blank and there is no more response from the box, looks dead. But
it's possible to ssh into it and find the following information in dmesg:
[12743.692027] ------------[ cut here ]------------
[12743.692030] kernel BUG at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:4708!
[12743.692039] invalid opcode: 0000 [#1] SMP NOPTI
[12743.692041] Modules linked in: twofish_generic twofish_avx_x86_64
twofish_x86_64_3way twofish_x86_64 twofish_common loop serpent_avx2
serpent_avx_x86_64 serpent_sse2_x86_64 serpent_generic rfcomm fuse
rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache
nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT
nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge
stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6
ip6table_mangle lz4 lz4_compress ip6table_raw ip6table_security iptable_nat
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c
iptable_mangle iptable_raw iptable_security ebtable_filter ebtables
ip6table_filter ip6_tables cmac bnep sunrpc vfat fat snd_hda_codec_realtek
snd_hda_codec_generic
[12743.692069] snd_hda_codec_hdmi snd_hda_intel btusb snd_hda_codec btrtl
btbcm edac_mce_amd btintel bluetooth snd_hda_core snd_hwdep snd_seq kvm_amd ccp
wmi_bmof kvm snd_seq_device snd_pcm ecdh_generic snd_timer irqbypass rfkill
joydev pcspkr snd soundcore shpchp i2c_piix4 k10temp wmi video acpi_cpufreq
binfmt_misc dm_crypt amdkfd raid1 amd_iommu_v2 amdgpu chash i2c_algo_bit
gpu_sched drm_kms_helper ttm drm crct10dif_pclmul crc32_pclmul crc32c_intel
ghash_clmulni_intel r8169 mii
[12743.692091] CPU: 6 PID: 3708 Comm: Xorg Not tainted
4.17.0-rc3-linus.git-keumjo #3
[12743.692093] Hardware name: System manufacturer System Product Name/TUF
B350M-PLUS GAMING, BIOS 4009 04/14/2018
[12743.692154] RIP: 0010:dm_update_crtcs_state+0x419/0x480 [amdgpu]
[12743.692156] RSP: 0018:ffffb4e688f07b30 EFLAGS: 00010246
[12743.692158] RAX: ffff8b720090d001 RBX: ffff8b720527d000 RCX:
000000000008dccc
[12743.692160] RDX: 000000000008dccb RSI: ffff8b723eda6160 RDI:
ffff8b723e806e80
[12743.692162] RBP: ffff8b720275c000 R08: 0000000000026160 R09:
0000000000000000
[12743.692163] R10: ffffdb50a0024200 R11: 0000000000000a00 R12:
0000000000000000
[12743.692165] R13: ffff8b7205189800 R14: ffff8b720090ec00 R15:
ffff8b71f16c8a00
[12743.692167] FS: 00007f88668e2ac0(0000) GS:ffff8b723ed80000(0000)
knlGS:0000000000000000
[12743.692169] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[12743.692170] CR2: 00007f885f886000 CR3: 00000007fbc90000 CR4:
00000000003406e0
[12743.692172] Call Trace:
[12743.692231] amdgpu_dm_atomic_check+0x1b1/0x3b0 [amdgpu]
[12743.692248] drm_atomic_check_only+0x360/0x4f0 [drm]
[12743.692264] drm_atomic_commit+0x13/0x50 [drm]
[12743.692278] drm_atomic_connector_commit_dpms+0xdb/0x100 [drm]
[12743.692292] drm_mode_obj_set_property_ioctl+0x178/0x280 [drm]
[12743.692307] ? drm_mode_connector_set_obj_prop+0x80/0x80 [drm]
[12743.692320] drm_mode_connector_property_set_ioctl+0x39/0x60 [drm]
[12743.692333] drm_ioctl_kernel+0x5b/0xb0 [drm]
[12743.692346] drm_ioctl+0x1b3/0x370 [drm]
[12743.692359] ? drm_mode_connector_set_obj_prop+0x80/0x80 [drm]
[12743.692364] ? _cond_resched+0x15/0x30
[12743.692404] amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
[12743.692408] do_vfs_ioctl+0xa4/0x610
[12743.692411] ksys_ioctl+0x60/0x90
[12743.692414] ? ksys_read+0x9c/0xb0
[12743.692416] __x64_sys_ioctl+0x16/0x20
[12743.692420] do_syscall_64+0x5b/0x160
[12743.692423] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[12743.692425] Code: ff ff e9 21 fe ff ff 48 83 3c 24 00 0f 84 2f fe ff ff 48
8b 3c 24 e8 e7 99 07 00 80 7c 24 0f 00 0f 85 02 fe ff ff e9 40 ff ff ff <0f> 0b
48 83 c4 20 b8 ea ff ff ff 5b 5d 41 5c 41 5d 41 5e 41 5f
[12743.692510] RIP: dm_update_crtcs_state+0x419/0x480 [amdgpu] RSP:
ffffb4e688f07b30
[12743.692525] ---[ end trace fb5e2b69e8f8d9c9 ]---
There's no recovery from this; service lightdm restart doesn't restart it.
shutdown -r now doens't reboot either, just hangs (can't tell why since screens
are blank and ssh closes)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 5412 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-04-30 14:10 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 1:13 [Bug 105018] Kernel panic when waking up after screen goes blank bugzilla-daemon
2018-02-09 1:16 ` bugzilla-daemon
2018-02-09 9:21 ` bugzilla-daemon
2018-02-10 17:25 ` bugzilla-daemon
2018-02-10 17:31 ` bugzilla-daemon
2018-02-11 0:32 ` bugzilla-daemon
2018-02-12 15:55 ` bugzilla-daemon
2018-02-13 3:30 ` bugzilla-daemon
2018-02-13 3:38 ` bugzilla-daemon
2018-02-13 16:13 ` bugzilla-daemon
2018-02-13 16:13 ` bugzilla-daemon
2018-02-13 16:13 ` bugzilla-daemon
2018-02-13 16:14 ` bugzilla-daemon
2018-02-13 16:14 ` bugzilla-daemon
2018-02-13 18:40 ` bugzilla-daemon
2018-02-14 5:55 ` bugzilla-daemon
2018-02-14 6:14 ` bugzilla-daemon
2018-02-14 6:52 ` bugzilla-daemon
2018-02-14 14:35 ` bugzilla-daemon
2018-02-14 16:13 ` bugzilla-daemon
2018-02-15 20:59 ` bugzilla-daemon
2018-02-23 23:23 ` bugzilla-daemon
2018-02-27 5:23 ` bugzilla-daemon
2018-03-16 0:40 ` bugzilla-daemon
2018-03-20 0:55 ` bugzilla-daemon
2018-03-22 0:09 ` bugzilla-daemon
2018-03-24 12:49 ` bugzilla-daemon
2018-03-24 12:58 ` bugzilla-daemon
2018-03-26 1:25 ` bugzilla-daemon
2018-04-12 0:41 ` bugzilla-daemon
2018-04-12 4:19 ` bugzilla-daemon
2018-04-13 0:25 ` bugzilla-daemon
2018-04-30 14:10 ` bugzilla-daemon [this message]
2018-04-30 14:55 ` bugzilla-daemon
2018-05-01 13:37 ` bugzilla-daemon
2018-05-01 13:56 ` bugzilla-daemon
2018-06-23 13:26 ` bugzilla-daemon
2018-06-27 18:51 ` bugzilla-daemon
2018-07-05 5:56 ` bugzilla-daemon
2018-07-05 6:03 ` bugzilla-daemon
2018-09-06 18:12 ` bugzilla-daemon
2018-09-07 7:40 ` bugzilla-daemon
2018-09-07 22:35 ` bugzilla-daemon
2018-12-10 14:47 ` 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-105018-502-APvMz71FAC@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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).