Created attachment 86073 [details] full current dmesg Hi there, I've never seen this warning before today. Sorry if it's a duplicate. No adverse affects noticed so far... [ 9491.888203] ------------[ cut here ]------------ [ 9491.888230] WARNING: CPU: 0 PID: 1937 at drivers/gpu/drm/i915/intel_display.c:1104 assert_cursor.constprop.60+0xbc/0xc0() [ 9491.888233] cursor on pipe A assertion failure (expected off, current on) [ 9491.888235] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec brcmsmac cordic brcmutil snd_hwdep snd_pcm snd_page_alloc snd_timer snd coretemp kvm_intel dell_wmi kvm lpc_ich nouveau mfd_core mxm_wmi bcma atl1c ttm wmi [ 9491.888288] CPU: 0 PID: 1937 Comm: X Tainted: G W 3.12.0-rc1-next-20130918 #1 [ 9491.888290] Hardware name: Alienware M11x R2/M11x R2, BIOS A04 11/23/2010 [ 9491.888292] 0000000000000009 ffff88007649d908 ffffffff81660de6 0000000000000007 [ 9491.888295] ffff88007649d958 ffff88007649d948 ffffffff81045077 ffff88007649d938 [ 9491.888298] 0000000000000000 0000000000000000 0000000000000000 0000000000000001 [ 9491.888314] Call Trace: [ 9491.888322] [<ffffffff81660de6>] dump_stack+0x4f/0x84 [ 9491.888328] [<ffffffff81045077>] warn_slowpath_common+0x87/0xb0 [ 9491.888331] [<ffffffff81045141>] warn_slowpath_fmt+0x41/0x50 [ 9491.888346] [<ffffffff8138d88c>] assert_cursor.constprop.60+0xbc/0xc0 [ 9491.888350] [<ffffffff8138fb89>] intel_enable_pipe+0x49/0x1b0 [ 9491.888354] [<ffffffff81390dcf>] ironlake_crtc_enable+0x12f/0xc50 [ 9491.888359] [<ffffffff81396d20>] __intel_set_mode+0x780/0x1460 [ 9491.888364] [<ffffffff81399f21>] intel_set_mode+0x11/0x30 [ 9491.888380] [<ffffffff8139a763>] intel_crtc_set_config+0x823/0xa10 [ 9491.888386] [<ffffffff81350eed>] drm_mode_set_config_internal+0x5d/0xe0 [ 9491.888390] [<ffffffff81353423>] drm_mode_setcrtc+0xf3/0x630 [ 9491.888396] [<ffffffff81344219>] drm_ioctl+0x509/0x630 [ 9491.888412] [<ffffffff81353330>] ? drm_mode_setplane+0x3b0/0x3b0 [ 9491.888418] [<ffffffff81155a07>] do_vfs_ioctl+0x87/0x520 [ 9491.888422] [<ffffffff81145820>] ? __sb_end_write+0x30/0x70 [ 9491.888426] [<ffffffff8115f9fc>] ? fget_light+0x4c/0x100 [ 9491.888429] [<ffffffff81155f31>] SyS_ioctl+0x91/0xb0 [ 9491.888448] [<ffffffff8166fd22>] system_call_fastpath+0x16/0x1b [ 9491.888451] ---[ end trace c7127599d378d79d ]---
I think this has been fixed in the last 8 hours from the commits on drm-intel-next, sorry.
Cool, and thanks anyway for the report. Please reopen if it pops up again.
Hi there, i have same problem. Using this kernel and indel-next http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2014-07-26-utopic/ [ 8619.885005] ------------[ cut here ]------------ [ 8619.885043] WARNING: CPU: 0 PID: 1184 at /home/apw/COD/linux/drivers/gpu/drm/i915/intel_display.c:1226 assert_cursor.constprop.79+0xa9/0xb0 [i915]() [ 8619.885045] cursor on pipe A assertion failure (expected off, current on) [ 8619.885046] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) intel_rapl x86_pkg_temp_thermal hid_multitouch intel_powerclamp arc4 btusb coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel uvcvideo videobuf2_vmalloc videobuf2_memops aes_x86_64 videobuf2_core lrw v4l2_common gf128mul videodev glue_helper media ablk_helper cryptd microcode joydev bnep rfcomm serio_raw iwlmvm bluetooth mac80211 6lowpan_iphc snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic rtsx_pci_ms memstick snd_hda_intel iwlwifi snd_hda_controller thinkpad_acpi snd_hda_codec nvram cfg80211 snd_seq_midi intel_smartconnect snd_seq_midi_event snd_hwdep mac_hid snd_rawmidi lpc_ich snd_pcm snd_seq snd_seq_device snd_timer snd mei_me mei soundcore parport_pc ppdev lp parport nls_iso8859_1 usbhid hid rtsx_pci_sdmmc i915 psmouse ahci libahci rtsx_pci i2c_algo_bit drm_kms_helper e1000e drm ptp pps_core wmi video [ 8619.885094] CPU: 0 PID: 1184 Comm: Xorg Tainted: G OE 3.16.0-997-generic #201407260205 [ 8619.885096] Hardware name: LENOVO 20AR001GXS/20AR001GXS, BIOS GJET77WW (2.27 ) 05/20/2014 [ 8619.885097] 00000000000004ca ffff88020cf97a78 ffffffff82783a5c 0000000000000007 [ 8619.885100] ffff88020cf97ac8 ffff88020cf97ab8 ffffffff8207007c ffff88020cf97ae8 [ 8619.885103] 0000000000000000 0000000000000003 0000000000000000 ffff88020ea8b000 [ 8619.885106] Call Trace: [ 8619.885111] [<ffffffff82783a5c>] dump_stack+0x46/0x58 [ 8619.885115] [<ffffffff8207007c>] warn_slowpath_common+0x8c/0xc0 [ 8619.885117] [<ffffffff82070166>] warn_slowpath_fmt+0x46/0x50 [ 8619.885137] [<ffffffffc02f8a89>] assert_cursor.constprop.79+0xa9/0xb0 [i915] [ 8619.885155] [<ffffffffc02fd999>] intel_enable_pipe+0x49/0x210 [i915] [ 8619.885172] [<ffffffffc03046bd>] haswell_crtc_enable+0x1cd/0x360 [i915] [ 8619.885189] [<ffffffffc03026a7>] __intel_set_mode+0x327/0x490 [i915] [ 8619.885206] [<ffffffffc0306a66>] intel_set_mode+0x16/0x30 [i915] [ 8619.885222] [<ffffffffc030756e>] intel_crtc_set_config+0x1ee/0x370 [i915] [ 8619.885225] [<ffffffff8278f8d6>] ? mutex_lock+0x16/0x37 [ 8619.885239] [<ffffffffc01b0093>] drm_mode_set_config_internal+0x63/0xf0 [drm] [ 8619.885251] [<ffffffffc01b47d0>] drm_mode_setcrtc+0x280/0x4d0 [drm] [ 8619.885260] [<ffffffffc01a3e76>] drm_ioctl+0x2e6/0x590 [drm] [ 8619.885271] [<ffffffffc01b4550>] ? drm_mode_setplane+0x200/0x200 [drm] [ 8619.885275] [<ffffffff820a8edd>] ? vtime_account_user+0x5d/0x70 [ 8619.885278] [<ffffffff821f15d5>] do_vfs_ioctl+0x75/0x2c0 [ 8619.885281] [<ffffffff820247e5>] ? syscall_trace_enter+0x165/0x280 [ 8619.885284] [<ffffffff821fbba5>] ? __fget_light+0x25/0x70 [ 8619.885286] [<ffffffff821f18b1>] SyS_ioctl+0x91/0xb0 [ 8619.885289] [<ffffffff8279173f>] tracesys+0xe1/0xe6 [ 8619.885291] ---[ end trace 125324d31e62864d ]---
(In reply to comment #3) > Hi there, i have same problem. Using this kernel and indel-next > http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2014-07-26- > utopic/ Please post full dmesg with drm.debug=0xe module parameter set.
I've seen the error with a somewhat similar stacktrace when attaching a HDMI output with existing eDP. enable_fbc=0 avoids this error for me (but doesn't yet help with getting HDMI up and running, which is a different issue)
Ok, the debug dmesg didn't ever show up, and we really need this one to debug this. So closing. Please reopen once you provide the relevant information and the problem still persists on latest kernels. To everyone else: Just because the backtrace looks similar doesn't mean it's the same bug. Please file a new bug and please supply dmesg with drm.debug=0xe set right away. Thanks.
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.