Created attachment 120713 [details] kernel log the screen always become messy, many words are not shown. the screen is totally corrupted. i am using HDMI cable to connect the display.
Bug scrub: ---------- Could you attach a screenshot showing the problem? Please provide details about your HW and SW configuration and some steps. This HowTo can help you: https://01.org/linuxgraphics/documentation/how-report-bugs Thank you.
Created attachment 121011 [details] screenshot
-- system architecture: Linux ruilings-bdw 4.4.0-rc4+ #14 SMP Tue Dec 15 16:33:33 CST 2015 x86_64 x86_64 x86_64 GNU/Linux -- kernel version: 4.4.0-rc4+ -- Linux distribution: Ubuntu 14.04 LTS -- Machine or mother board model: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz x 4 stepping:4 microcode: 0x19 -- Display connector: HDMI I am using drm-intel-nightly, but a little old version, the git log is: commit ad271e93d840de70c04628f8d87796a684f1ed70 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Sat Dec 12 12:19:19 2015 +0100 drm-intel-nightly: 2015y-12m-12d-11h-18m-40s UTC integration manifest commit 2751a3cb868ce7be267b644a5b12e5ccee9ef7c5 Merge: 91c2a5d 8ba718e Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Sat Dec 12 12:19:18 2015 +0100 Merge remote-tracking branch 'origin/topic/kerneldoc' into drm-intel-nightly commit 91c2a5dc0e7678e23f7f1d1651cf2dfacebe4ce2 Merge: 7a165d1 d6e6e14 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Sat Dec 12 12:19:17 2015 +0100 Merge remote-tracking branch 'origin/topic/drm-misc' into drm-intel-nightly # Conflicts: # drivers/gpu/drm/i915/intel_dp.c # drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c # drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c # drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c
I tried with a BDW-U platform with same CPU, I'm not able to reproduce it. Installing the graphic stack will probably solve your problem. You can follow this guide to install last version of each drivers: https://01.org/linuxgraphics/documentation/build-guide-0 Or install the last release: https://01.org/linuxgraphics/downloads/2015q4-intel-graphics-stack-release Or also use this installer: https://01.org/linuxgraphics/downloads/intel-graphics-installer-linux-1.2.1 I decrease priority and severity until you confirm. My configuration: WSB5 : Wilson Beach PVT2 Hardware Platform: Wilson Beach PVT2 Ultrabook CPU: Intel(R) Core (TM) i5-5300U CPU @ 2.30GHz (family: 6, model: 61 stepping: 4) SoC: Broadwell 2+2 F0 (QDF : QH3F) Chipset PCH: Wildcat Point B2 Software Linux distribution: Ubuntu 14.04 LTS 64 bits Kernel: drm-intel-nightly 4.5.0-rc1 5d3deb0 from http://cgit.freedesktop.org/drm-intel commit 5d3deb0902a962218ad9b0e583e4d1bbdec29f9a Author: Rodrigo Vivi <rodrigo.vivi@intel.com> Date: Mon Feb 1 12:05:18 2016 -0800 drm-intel-nightly: 2016y-02m-01d-20h-05m-03s UTC integration manifest BIOS : BDW-E1R1.86C.0095.R09.1410300006 ME FW : 10.0.30.1060 Ksc : 1.22 drm: tag libdrm-2.4.66-18 432e08d from http://cgit.freedesktop.org/mesa/drm/ mesa: tag mesa-11.0.9 835d29d from http://cgit.freedesktop.org/mesa/mesa/ cairo: tag 1.15.2 4243389 from http://cgit.freedesktop.org/cairo waffle: master 45e7090 from https://github.com/waffle-gl/waffle xorg-server-macros: master d7acec2 from git://git.freedesktop.org/git/xorg/util/macros libva: tag libva-1.6.1 09b2f1f from http://cgit.freedesktop.org/libva/ vaapi-intel-driver: tag 1.6.1 f6fe842 from http://cgit.freedesktop.org/vaapi/intel-driver LCD monitor AOC I2369V
[ 6.107986] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in has_infoframe (expected 1, found 0) [ 6.107987] ------------[ cut here ]------------ [ 6.108009] WARNING: CPU: 3 PID: 173 at drivers/gpu/drm/i915/intel_display.c:12949 intel_atomic_commit+0x11da/0x17e0 [i915]() [ 6.108009] pipe state doesn't match! [ 6.108030] Modules linked in: i915 snd_hda_intel snd_hda_codec x86_pkg_temp_thermal snd_hda_core intel_powerclamp kvm_intel kvm snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi hid_generic snd_seq irqbypass drm_kms_helper crct10dif_pclmul crc32_pclmul drm aesni_intel snd_seq_device aes_x86_64 snd_timer lrw gf128mul glue_helper ablk_helper snd cryptd mei_me mei usbhid i2c_algo_bit fb_sys_fops serio_raw syscopyarea lpc_ich sysfillrect soundcore sysimgblt rfcomm winbond_cir rc_core bnep video dw_dmac dw_dmac_core bluetooth i2c_hid hid parport_pc i2c_designware_platform ppdev 8250_dw i2c_designware_core acpi_pad spi_pxa2xx_platform coretemp lp binfmt_misc mac_hid parport nls_iso8859_1 e1000e ptp ahci libahci pps_core sdhci_acpi sdhci [ 6.108032] CPU: 3 PID: 173 Comm: kworker/u16:4 Not tainted 4.4.0-rc4+ #14 [ 6.108032] Hardware name: Intel Corporation Broadwell Client platform/SawTooth Peak, BIOS BDW-E1R1.86C.0108.R00.1412212013 12/21/2014 [ 6.108035] Workqueue: events_unbound async_run_entry_fn [ 6.108037] ffffffffa06a4a78 ffff88002d64b8d0 ffffffff81394714 ffff88002d64b918 [ 6.108038] ffff88002d64b908 ffffffff81074d36 ffff8800a94fac00 ffff88013d4eb000 [ 6.108039] ffff8800a973b348 ffff8800a94f9800 ffff88013da2ba00 ffff88002d64b968 [ 6.108039] Call Trace: [ 6.108042] [<ffffffff81394714>] dump_stack+0x44/0x60 [ 6.108044] [<ffffffff81074d36>] warn_slowpath_common+0x86/0xc0 [ 6.108045] [<ffffffff81074dbc>] warn_slowpath_fmt+0x4c/0x50 [ 6.108064] [<ffffffffa06409fa>] intel_atomic_commit+0x11da/0x17e0 [i915] [ 6.108077] [<ffffffffa02e3324>] ? drm_atomic_check_only+0x144/0x5f0 [drm] [ 6.108085] [<ffffffffa02e3e27>] ? drm_atomic_add_affected_connectors+0x27/0xf0 [drm] [ 6.108093] [<ffffffffa02e3807>] drm_atomic_commit+0x37/0x60 [drm] [ 6.108099] [<ffffffffa034bdd7>] restore_fbdev_mode+0x237/0x260 [drm_kms_helper] [ 6.108107] [<ffffffffa02e293a>] ? drm_modeset_lock_all_ctx+0x9a/0xb0 [drm] [ 6.108111] [<ffffffffa034dfa3>] drm_fb_helper_restore_fbdev_mode_unlocked+0x33/0x80 [drm_kms_helper] [ 6.108114] [<ffffffffa034e01d>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper] [ 6.108135] [<ffffffffa065667a>] intel_fbdev_set_par+0x1a/0x60 [i915] [ 6.108138] [<ffffffff81407df3>] fbcon_init+0x533/0x5a0 [ 6.108140] [<ffffffff8149a96a>] visual_init+0xca/0x130 [ 6.108142] [<ffffffff8149cf07>] do_bind_con_driver+0x167/0x3a0 [ 6.108143] [<ffffffff8149d3ec>] do_take_over_console+0xac/0x1d0 [ 6.108145] [<ffffffff814030e7>] do_fbcon_takeover+0x57/0xb0 [ 6.108146] [<ffffffff8140886d>] fbcon_event_notify+0x64d/0x750 [ 6.108148] [<ffffffff8109351a>] notifier_call_chain+0x4a/0x70 [ 6.108150] [<ffffffff81093837>] __blocking_notifier_call_chain+0x47/0x60 [ 6.108151] [<ffffffff81093866>] blocking_notifier_call_chain+0x16/0x20 [ 6.108153] [<ffffffff8140df7b>] fb_notifier_call_chain+0x1b/0x20 [ 6.108154] [<ffffffff8140ff08>] register_framebuffer+0x1f8/0x320 [ 6.108158] [<ffffffffa034e278>] drm_fb_helper_initial_config+0x238/0x3d0 [drm_kms_helper] [ 6.108177] [<ffffffffa06578ef>] intel_fbdev_initial_config+0x1f/0x30 [i915] [ 6.108178] [<ffffffff81094f08>] async_run_entry_fn+0x48/0x150 [ 6.108179] [<ffffffff8108c987>] process_one_work+0x157/0x3e0 [ 6.108180] [<ffffffff8108d36e>] worker_thread+0x4e/0x470 [ 6.108181] [<ffffffff8108d320>] ? rescuer_thread+0x300/0x300 [ 6.108182] [<ffffffff810925f9>] kthread+0xc9/0xe0 [ 6.108184] [<ffffffff81092530>] ? kthread_park+0x60/0x60 [ 6.108186] [<ffffffff81780ccf>] ret_from_fork+0x3f/0x70 [ 6.108187] [<ffffffff81092530>] ? kthread_park+0x60/0x60 [ 6.108188] ---[ end trace af26bfe4e6de48d5 ]--- [ 6.163745] Console: switching to colour frame buffer device 240x75 [ 6.167704] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device could you help explain what the dmesg means? nothing wong?
(In reply to ruiling from comment #2) > Created attachment 121011 [details] > screenshot I don't think this is a kernel bug.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.