4.16.2+ lightdm logon screen will not unblank after monitors fall asleep
Submitted by Joel Sass
Assigned to Default DRI bug account
Link to original bug (#106192)
Description
Created attachment 139008
Initial boot - everything was fine.
If I leave my computer at the logon screen and the monitors fall asleep, I cannot wake them. Requires a reboot.
Looks like there was a dmesg error, and Xorg.0.log reflects a failure when attempting to use screen 0.
I'll include the xorg.conf because that may have had something to do with it according to the Xorg.0.log.
Attachment 139008, "Initial boot - everything was fine.":
Xorg.0.log.old
Activity
Attachment 139009, "Xorg failure when screen was blanked in lightdm":
Xorg.0.logLooks like a kernel bug issue. This
[ 966.373770] BUG: unable to handle kernel paging request at ffffb419820f3c60
[ 966.373776] IP: __ww_mutex_lock.isra.3+0x283/0x670
[ 966.373777] PGD 46ed48067 P4D 46ed48067 PUD 46ed49067 PMD 461fc5067 PTE 0
[ 966.373780] Oops: 0000 [#2] SMP PTI
[ 966.373781] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc rfcomm ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables bnep binfmt_misc btusb btrtl btbcm btintel bluetooth snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel ecdh_generic snd_hda_codec applesmc input_leds input_polldev intel_powerclamp coretemp snd_seq_midi snd_hda_core intel_cstate snd_seq_midi_event snd_hwdep snd_rawmidi snd_pcm snd_seq snd_seq_device snd_timer snd lpc_ich kvm_intel kvm irqbypass soundcore shpchp i5500_temp mac_hid ioatdma i7core_edac dca parport_pc ppdev lp parport autofs4 raid10 raid456
[ 966.373810] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear amdkfd amd_iommu_v2 amdgpu chash i2c_algo_bit gpu_sched ttm hid_generic drm_kms_helper e1000e firewire_ohci syscopyarea sysfillrect usbhid sysimgblt ptp fb_sys_fops pata_acpi firewire_core crc_itu_t hid pps_core drm
[ 966.373825] CPU: 4 PID: 3205 Comm: Xorg Tainted: G D W I 4.16.2+ #1 (closed)
[ 966.373826] Hardware name: Apple Inc. MacPro4,1/Mac-F221BEC8, BIOS MP41.88Z.0081.B07.0910130729 10/13/09
[ 966.373828] RIP: 0010:__ww_mutex_lock.isra.3+0x283/0x670
[ 966.373828] RSP: 0018:ffffb41982473870 EFLAGS: 00010282
[ 966.373829] RAX: ffffb419820f3c58 RBX: ffff9735a1096830 RCX: 00000000000000e7
[ 966.373830] RDX: ffff9735a530be81 RSI: ffff97357cbbbe80 RDI: ffffb41982473890
[ 966.373831] RBP: ffffb419824738f0 R08: ffff9735a34ab080 R09: ffff9735a3ab0b80
[ 966.373831] R10: ffffb41982473908 R11: 0000000000002800 R12: 0000000000000002
[ 966.373832] R13: ffff9735a1096828 R14: ffffb419824739c8 R15: 0000000000000000
[ 966.373833] FS: 00007faa1e832a00(0000) GS:ffff9735af300000(0000) knlGS:0000000000000000
[ 966.373834] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 966.373835] CR2: ffffb419820f3c60 CR3: 0000000443164000 CR4: 00000000000006e0
[ 966.373836] Call Trace:
[ 966.373839] __ww_mutex_lock_slowpath+0x16/0x20
[ 966.373840] ? __ww_mutex_lock_slowpath+0x16/0x20
[ 966.373841] ww_mutex_lock+0x5a/0x70
[ 966.373852] drm_modeset_lock+0x35/0xb0 [drm]
[ 966.373858] drm_atomic_get_crtc_state+0x5b/0x110 [drm]
[ 966.373865] drm_atomic_get_plane_state+0xec/0x110 [drm]
[ 966.373870] restore_fbdev_mode_atomic+0xd5/0x200 [drm_kms_helper]
[ 966.373873] restore_fbdev_mode+0x31/0x140 [drm_kms_helper]
[ 966.373875] ? _cond_resched+0x19/0x40
[ 966.373878] drm_fb_helper_restore_fbdev_mode_unlocked+0x4e/0xa0 [drm_kms_helper]
[ 966.373881] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper]
[ 966.373883] fb_set_var+0x19f/0x440
[ 966.373885] ? mem_cgroup_uncharge_list+0x69/0x90
[ 966.373888] fbcon_blank+0x2b7/0x3a0
[ 966.373891] do_unblank_screen+0xba/0x1b0
[ 966.373892] vt_ioctl+0x4e1/0x1150
[ 966.373894] ? jbd2_journal_stop+0xf6/0x3f0
[ 966.373896] tty_ioctl+0xf6/0x8c0
[ 966.373898] ? fsnotify_grab_connector+0x43/0x70
[ 966.373900] ? call_rcu_sched+0x17/0x20
[ 966.373901] do_vfs_ioctl+0xa8/0x630
[ 966.373903] ? __fput+0x193/0x220
[ 966.373904] SyS_ioctl+0x79/0x90
[ 966.373907] do_syscall_64+0x73/0x130
[ 966.373908] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 966.373909] RIP: 0033:0x7faa1c69bf47
[ 966.373910] RSP: 002b:00007ffd3892b788 EFLAGS: 00003246 ORIG_RAX: 0000000000000010
[ 966.373911] RAX: ffffffffffffffda RBX: 000055aa519db820 RCX: 00007faa1c69bf47
[ 966.373912] RDX: 0000000000000000 RSI: 0000000000004b3a RDI: 000000000000000a
[ 966.373912] RBP: 00007ffd3892b800 R08: 000055aa5257a420 R09: 000055aa5257a100
[ 966.373913] R10: 000000000000003a R11: 0000000000003246 R12: 00007ffd3892b970
[ 966.373914] R13: 0000000000000001 R14: 0000000000000005 R15: 000055aa519e5360
[ 966.373915] Code: cd 03 00 00 45 84 ff 0f 85 43 02 00 00 48 89 df e8 03 34 00 00 e9 39 ff ff ff 49 8b 45 20 48 85 c0 0f 84 38 03 00 00 49 8b 4e 08<48>8b 50 08 48 39 d1 0f 88 27 03 00 00 48 39 d1 75 09 49 39 c6
[ 966.373934] RIP: __ww_mutex_lock.isra.3+0x283/0x670 RSP: ffffb41982473870
[ 966.373935] CR2: ffffb419820f3c60
[ 966.373936] ---[ end trace 57a9c31f2648be5f ]---Attachment 139010, "Dmesg shows kernel error after freezing. Had to acquire with ssh.":
dmesg_outAttachment 139011, "Xorg.conf from frozen screen 0":
xorg.conf.oldThis issue hasn't had any activity since 2019-11-19. The AMD driver stack changes rapidly and contains lots of shared code across products so it's possible that it has already been fixed. Please upgrade to a current stable kernel and userspace stack and try again. If you still experience this issue with the latest driver stack, please capture relevant logging and open a new issue referring back to this one.
