FS#46704 - [linux] Monitor does not wake up from sleep (console only)
Attached to Project:
Arch Linux
Opened by Gerry Kessler (renegat) - Tuesday, 13 October 2015, 22:29 GMT
Last edited by Jan de Groot (JGC) - Monday, 16 October 2017, 09:03 GMT
Opened by Gerry Kessler (renegat) - Tuesday, 13 October 2015, 22:29 GMT
Last edited by Jan de Groot (JGC) - Monday, 16 October 2017, 09:03 GMT
|
Details
Packages: Linux 4.2.2-1-ARCH
Architecture: x86_64 Plattform: VGA Intel Bay-Trail Atom Processor Z36xxx/Z37xxx Series Graphics & Display Devices affected: Intel NUC D2820FYKH, Asus J1800I-A, Zotac ZBOX CI320... Monitors testet: BenQ GL2450 (HDMI)/ acer AL1923 (DVI) Description: In console without X started after a few minutes monitor connected via DVI or HDMI goes to power save mode (sleep) and powers down. Now you are not able to wake your monitor again - only way to get monitor on again is to reboot. Even when starting X blindly monitor stays off. What it should be doing: Monitor should wake up on keystroke or mouse movement or even power up on starting X Additional info (log): kernel: ------------[ cut here ]------------ WARNING: CPU: 0 PID: 465 at drivers/gpu/drm/i915/intel_display.c:429 vlv_clock+0x73/0xa0 [i915]() WARN_ON(clock->n == 0 || clock->p == 0) Modules linked in: fuse xt_conntrack iptable_filter ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_co sch_fq_codel ip_tables x_tables ext4 crc16 mbcache jbd2 sha256_ssse3 sha256_generic hmac drbg ansi_cprng xts gf128mul algif_skcipher af_alg CPU: 0 PID: 465 Comm: systemd-logind Tainted: G W 4.2.2-1-ARCH #1 [142B blob data] 0000000000000000 000000000b8ae44d ffff8800b4587518 ffffffff8156b9da 0000000000000000 ffff8800b4587570 ffff8800b4587558 ffffffff81074886 ffff8800b4587538 ffff8800b45876b0 0000000000000000 ffff880139827b50 Call Trace: [<ffffffff8156b9da>] dump_stack+0x4c/0x6e [<ffffffff81074886>] warn_slowpath_common+0x86/0xc0 [<ffffffff81074915>] warn_slowpath_fmt+0x55/0x70 [<ffffffffa011e983>] vlv_clock+0x73/0xa0 [i915] [<ffffffffa0126f59>] i9xx_get_pipe_config+0x2e9/0x680 [i915] [<ffffffff810e36d7>] ? ktime_get+0x37/0xa0 [<ffffffffa0123800>] check_crtc_state+0x160/0xf80 [i915] [<ffffffffa00194ba>] ? drm_calc_vbltimestamp_from_scanoutpos+0x17a/0x330 [drm] [<ffffffffa01369f6>] intel_modeset_check_state+0x216/0xb50 [i915] [<ffffffffa013100c>] ? __intel_set_mode+0x92c/0xb60 [i915] [<ffffffffa0138037>] intel_crtc_set_config+0x4c7/0x580 [i915] [<ffffffffa00229f6>] drm_mode_set_config_internal+0x66/0x100 [drm] [<ffffffffa0088552>] restore_fbdev_mode+0xc2/0xf0 [drm_kms_helper] [<ffffffffa008a4b9>] drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x70 [drm_kms_helper] [<ffffffffa014738e>] intel_fbdev_restore_mode+0x1e/0x50 [i915] [<ffffffffa017069e>] i915_driver_lastclose+0xe/0x20 [i915] [<ffffffffa001699e>] drm_lastclose+0x2e/0x140 [drm] [<ffffffffa0016dc6>] drm_release+0x316/0x500 [drm] [<ffffffff811d23fc>] __fput+0x9c/0x1f0 [<ffffffff811d259e>] ____fput+0xe/0x10 [<ffffffff810907db>] task_work_run+0x9b/0xb0 [<ffffffff81076fa5>] do_exit+0x395/0xb40 [<ffffffff810a520b>] ? set_next_entity+0xab/0x440 [<ffffffff810777db>] do_group_exit+0x3b/0xb0 [<ffffffff8108282c>] get_signal+0x23c/0x630 [<ffffffff81015337>] do_signal+0x37/0x6a0 [<ffffffff81216472>] ? ep_poll+0x392/0x3f0 [<ffffffff8109d880>] ? wake_up_q+0x70/0x70 [<ffffffff810159fb>] do_notify_resume+0x5b/0x70 [<ffffffff8157113c>] int_signal+0x12/0x17 ---[ end trace bf231c83a3591756 ]--- ------------[ cut here ]------------ Steps to reproduce: Update to packages mentioned above, boot into console (not X!) and wait till monitor turns off. No way to get it on again. Downgrading linux (4.2.2-1 -> 4.1.6-1) solves the issue for the moment |
This task depends upon
Maybe this bug has something to do/is related to this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=88012
https://github.com/OpenELEC/OpenELEC.tv/issues/3726
As far as I understand it the Bay Trail GPU driver is broken, when it comes to powersaving/switching between power states.