Bug 92456 - 4.3.0-rc5 triggers warning in intel_pipe_config_compare
Summary: 4.3.0-rc5 triggers warning in intel_pipe_config_compare
Status: CLOSED DUPLICATE of bug 89055
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
: 92997 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-10-14 07:50 UTC by Oliver Neukum
Modified: 2017-07-24 22:44 UTC (History)
6 users (show)

See Also:
i915 platform: HSW
i915 features: display/Other


Attachments
lspci -v (10.52 KB, text/plain)
2015-10-14 07:50 UTC, Oliver Neukum
no flags Details
dmesg of boot with drm.debug=14 (138.45 KB, text/plain)
2015-10-14 09:23 UTC, Oliver Neukum
no flags Details

Description Oliver Neukum 2015-10-14 07:50:13 UTC
Created attachment 118866 [details]
lspci -v

This is on an HP Laptop with Intel and Nvidia GPUs. The internal display is used and the laptop docked but without an external monitor.

[    6.842218] [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in has_drrs (expected 1, found 0)
[    6.842219] ------------[ cut here ]------------
[    6.842238] WARNING: CPU: 6 PID: 259 at drivers/gpu/drm/i915/intel_display.c:12724 intel_modeset_check_state+0x575/0x8e0 [i915]()
[    6.842238] pipe state doesn't match!
[    6.842246] Modules linked in: crc32c_intel(E) i915(E) i2c_algo_bit(E) ahci(E) libahci(E) drm_kms_helper(E) ehci_pci(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) ehci_hcd(E) fb_sys_fops(E) libata(E) usbcore(E) usb_common(E
) drm(E) wmi(E) video(E) button(E) sg(E) scsi_mod(E) autofs4(E)
[    6.842248] CPU: 6 PID: 259 Comm: kworker/6:2 Tainted: G            E   4.3.0-rc5-default+ #1
[    6.842249] Hardware name: Hewlett-Packard HP EliteBook 8780w/190A, BIOS L70 Ver. 93.01 05/17/2013
[    6.842254] Workqueue: events output_poll_execute [drm_kms_helper]
[    6.842256]  ffffffffa030e900 ffff88068f8abb58 ffffffff812e3e26 ffff88068f8abba0
[    6.842257]  ffff88068f8abb90 ffffffff810647a6 ffff88068fab6800 ffff88068fbc5000
[    6.842258]  ffff88068e15db50 ffff880692bbe000 ffff88068f02ba00 ffff88068f8abbf0
[    6.842258] Call Trace:
[    6.842262]  [<ffffffff812e3e26>] dump_stack+0x44/0x5e
[    6.842265]  [<ffffffff810647a6>] warn_slowpath_common+0x86/0xc0
[    6.842267]  [<ffffffff8106482c>] warn_slowpath_fmt+0x4c/0x50
[    6.842282]  [<ffffffffa02a19a5>] intel_modeset_check_state+0x575/0x8e0 [i915]
[    6.842299]  [<ffffffffa02ad202>] intel_atomic_commit+0x5d2/0x630 [i915]
[    6.842312]  [<ffffffffa0090a07>] drm_atomic_commit+0x37/0x60 [drm]
[    6.842316]  [<ffffffffa01f5293>] restore_fbdev_mode+0x2a3/0x2e0 [drm_kms_helper]
[    6.842320]  [<ffffffffa01f72c3>] drm_fb_helper_restore_fbdev_mode_unlocked+0x33/0x80 [drm_kms_helper]
[    6.842323]  [<ffffffffa01f733c>] drm_fb_helper_set_par+0x2c/0x50 [drm_kms_helper]
[    6.842326]  [<ffffffffa01f7242>] drm_fb_helper_hotplug_event+0xa2/0xf0 [drm_kms_helper]
[    6.842346]  [<ffffffffa02c260e>] intel_fbdev_output_poll_changed+0x1e/0x30 [i915]
[    6.842349]  [<ffffffffa01eb557>] drm_kms_helper_hotplug_event+0x27/0x30 [drm_kms_helper]
[    6.842351]  [<ffffffffa01eb62d>] output_poll_execute+0x6d/0x1d0 [drm_kms_helper]
[    6.842353]  [<ffffffff8107c119>] process_one_work+0x149/0x3e0
[    6.842355]  [<ffffffff8107c94a>] worker_thread+0x11a/0x460
[    6.842357]  [<ffffffff815a2d6d>] ? __schedule+0x33d/0x8f0
[    6.842359]  [<ffffffff8107c830>] ? max_active_store+0x60/0x60
[    6.842360]  [<ffffffff81081d69>] kthread+0xc9/0xe0
[    6.842361]  [<ffffffff81081ca0>] ? kthread_park+0x60/0x60
[    6.842362]  [<ffffffff815a6f9f>] ret_from_fork+0x3f/0x70
[    6.842363]  [<ffffffff81081ca0>] ? kthread_park+0x60/0x60
[    6.842364] ---[ end trace c65beefcd9389153 ]---
[    6.842442] Console: switching to colour frame buffer device 200x56
[    6.849059] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Comment 1 Oliver Neukum 2015-10-14 07:51:02 UTC
Tested at state:

commit 32b1f6e0b6e8981eb0dd91c4ddf57372c822004a
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Tue Oct 13 17:48:35 2015 +0200

    drm-intel-nightly: 2015y-10m-13d-15h-47m-52s UTC integration manifest
Comment 2 Oliver Neukum 2015-10-14 07:52:41 UTC
This is likely the same issue as reported in
https://bugzilla.kernel.org/show_bug.cgi?id=104041
Comment 3 Oliver Neukum 2015-10-14 08:14:19 UTC
The warning is also triggered by booting in the undocked state.
Comment 4 Jani Nikula 2015-10-14 08:40:04 UTC
(In reply to Oliver Neukum from comment #2)
> This is likely the same issue as reported in
> https://bugzilla.kernel.org/show_bug.cgi?id=104041

Yes, I thought we had that covered already, but apparently now. Let's track this here anyway, we're migrating all bugs to fdo bugzilla.

Please attach dmesg with drm.debug=14 module parameter set, all the way from boot.
Comment 5 Oliver Neukum 2015-10-14 09:23:12 UTC
Created attachment 118867 [details]
dmesg of boot with drm.debug=14
Comment 6 Diego Elio Pettenò 2015-11-06 01:29:32 UTC
I'm having the same has_drrs error on a completely different laptop:

[170621.720794] ------------[ cut here ]------------
[170621.720803] WARNING: CPU: 2 PID: 317 at drivers/gpu/drm/i915/intel_display.c:12700 intel_atomic_commit+0xc26/0x1240()
[170621.720805] pipe state doesn't match!
[170621.720807] Modules linked in: cmac ecb rtsx_usb_sdmmc mmc_core btusb btintel bluetooth iwldvm iwlwifi microcode input_leds int3403_thermal int3402_thermal int3400_thermal int340x_thermal_zone acpi_thermal_rel efivarfs
[170621.720834] CPU: 2 PID: 317 Comm: X Tainted: G     U  W       4.3.0-rc7 #124
[170621.720837] Hardware name: ASUSTeK COMPUTER INC. UX31A/UX31A, BIOS UX31A.219 06/14/2013
[170621.720840]  ffffffffb9a87ed8 ffffffffb92f5c49 ffff8800d56ebbd0 ffffffffb90bc73c
[170621.720846]  ffff8800d7b8fc00 ffff8800d56ebc20 ffff8800cfb11400 ffff8800b4efe000
[170621.720851]  ffff8800d9351350 ffffffffb90bc7b7 ffffffffb9aba8cd 0000000000000018
[170621.720856] Call Trace:
[170621.720867]  [<ffffffffb92f5c49>] ? dump_stack+0x47/0x6e
[170621.720875]  [<ffffffffb90bc73c>] ? warn_slowpath_common+0x7c/0xb0
[170621.720880]  [<ffffffffb90bc7b7>] ? warn_slowpath_fmt+0x47/0x50
[170621.720886]  [<ffffffffb946e75a>] ? intel_dp_get_config+0x16a/0x1f0
[170621.720892]  [<ffffffffb944c5a6>] ? intel_atomic_commit+0xc26/0x1240
[170621.720900]  [<ffffffffb93bba5e>] ? drm_atomic_helper_check_planes+0xfe/0x1a0
[170621.720906]  [<ffffffffb93bb2c1>] ? drm_atomic_helper_set_config+0x391/0x420
[170621.720912]  [<ffffffffb93ce96b>] ? drm_mode_set_config_internal+0x5b/0xf0
[170621.720917]  [<ffffffffb93d2189>] ? drm_mode_setcrtc+0xd9/0x4e0
[170621.720922]  [<ffffffffb93c4c21>] ? drm_ioctl+0x251/0x410
[170621.720929]  [<ffffffffb9548122>] ? evdev_read+0x172/0x2d0
[170621.720961]  [<ffffffffb93d20b0>] ? drm_mode_setplane+0x1c0/0x1c0
[170621.720973]  [<ffffffffb91d5012>] ? do_vfs_ioctl+0x2c2/0x4b0
[170621.720984]  [<ffffffffb91dddab>] ? __fget+0x6b/0xb0
[170621.720993]  [<ffffffffb91d5236>] ? SyS_ioctl+0x36/0x70
[170621.721005]  [<ffffffffb97c5dd7>] ? entry_SYSCALL_64_fastpath+0x12/0x6a
[170621.721015] ---[ end trace 04a11c179822e960 ]---
Comment 7 Yaroslav Halchenko 2015-11-18 19:29:17 UTC
didn't see this one when filed 
https://bugs.freedesktop.org/show_bug.cgi?id=92997
In my case it is also HP laptop but with Intel and Radeon. And I also get entire system stalled quite frequently whenever manipulation with displays is happening
Comment 8 Jani Nikula 2015-11-19 10:54:22 UTC
*** Bug 92997 has been marked as a duplicate of this bug. ***
Comment 9 Max Lin 2015-11-24 10:17:22 UTC
I've the likely same issue on my HP 820 G1 laptop with very similar call trace.

Nov 24 02:09:00 linux-18ru kernel: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in has_drrs (expected 1, found 0)
Nov 24 02:09:00 linux-18ru kernel: ------------[ cut here ]------------
Nov 24 02:09:00 linux-18ru kernel: WARNING: CPU: 0 PID: 79 at ../drivers/gpu/drm/i915/intel_display.c:12700 intel_modeset_check_state+0x5aa/0x870 [i915]()
Nov 24 02:09:00 linux-18ru kernel: pipe state doesn't match!
Nov 24 02:09:00 linux-18ru kernel: Modules linked in: btrfs xor raid6_pq rtsx_pci_sdmmc mmc_core crc32c_intel rtsx_pci ehci_pci serio_raw mfd_core ehci_hcd i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm xhci_pci xhci_hcd e1000e usbcore ptp pps_core usb_common video button fjes sg efivarfs
Nov 24 02:09:00 linux-18ru kernel: CPU: 0 PID: 79 Comm: kworker/u16:4 Not tainted 4.3.0-2-default #1
Nov 24 02:09:00 linux-18ru kernel: Hardware name: Hewlett-Packard HP EliteBook 820 G1/1991, BIOS L71 Ver. 01.32 07/20/2015
Nov 24 02:09:00 linux-18ru kernel: Workqueue: events_unbound async_run_entry_fn
Nov 24 02:09:00 linux-18ru kernel:  ffffffffa02eb898 ffff88003f823848 ffffffff81363719 ffff88003f823890
Nov 24 02:09:00 linux-18ru kernel:  ffff88003f823880 ffffffff81068cf2 ffff88003f832800 ffff88003fa28000
Nov 24 02:09:00 linux-18ru kernel:  ffff88003fb7b800 ffff88003f9ec200 0000000000000000 ffff88003f8238e0
Nov 24 02:09:00 linux-18ru kernel: Call Trace:
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff81008385>] try_stack_unwind+0x175/0x190
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff81007203>] dump_trace+0x93/0x3a0
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff810083eb>] show_trace_log_lvl+0x4b/0x60
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff8100761c>] show_stack_log_lvl+0x10c/0x180
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff81008485>] show_stack+0x25/0x50
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff81363719>] dump_stack+0x4b/0x72
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff81068cf2>] warn_slowpath_common+0x82/0xc0
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff81068d7c>] warn_slowpath_fmt+0x4c/0x50
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffffa02815ba>] intel_modeset_check_state+0x5aa/0x870 [i915]
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffffa028c6a4>] intel_atomic_commit+0x434/0x640 [i915]
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffffa0149487>] drm_atomic_commit+0x37/0x60 [drm]
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffffa01cf90f>] drm_atomic_helper_set_config+0x1bf/0x420 [drm_kms_helper]
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffffa0138d02>] drm_mode_set_config_internal+0x62/0x100 [drm]
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffffa01d2723>] restore_fbdev_mode+0xb3/0x110 [drm_kms_helper]
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffffa01d45d5>] drm_fb_helper_restore_fbdev_mode_unlocked+0x25/0x70 [drm_kms_helper]
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffffa01d464d>] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper]
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffffa02a0d3a>] intel_fbdev_set_par+0x1a/0x60 [i915]
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff813d3100>] fbcon_init+0x570/0x5f0
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff8144d54a>] visual_init+0xca/0x130
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff8144f381>] do_bind_con_driver+0x1c1/0x3a0
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff8144f899>] do_take_over_console+0x149/0x1a0
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff813cf037>] do_fbcon_takeover+0x57/0xb0
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff813d3b78>] fbcon_event_notify+0x658/0x750
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff8108796a>] notifier_call_chain+0x4a/0x70
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff81087ce7>] __blocking_notifier_call_chain+0x47/0x60
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff81087d16>] blocking_notifier_call_chain+0x16/0x20
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff813d931b>] fb_notifier_call_chain+0x1b/0x20
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff813db480>] register_framebuffer+0x200/0x330
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffffa01d48c0>] drm_fb_helper_initial_config+0x250/0x3e0 [drm_kms_helper]
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffffa02a17bb>] intel_fbdev_initial_config+0x1b/0x20 [i915]
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff81089468>] async_run_entry_fn+0x48/0x150
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff81080c89>] process_one_work+0x159/0x470
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff81080fe8>] worker_thread+0x48/0x4a0
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff81086c79>] kthread+0xc9/0xe0
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff8166e84f>] ret_from_fork+0x3f/0x70
Nov 24 02:09:00 linux-18ru kernel: DWARF2 unwinder stuck at ret_from_fork+0x3f/0x70
Nov 24 02:09:00 linux-18ru kernel: 
Nov 24 02:09:00 linux-18ru kernel: Leftover inexact backtrace:
Nov 24 02:09:00 linux-18ru kernel:  [<ffffffff81086bb0>] ? kthread_worker_fn+0x170/0x170
Nov 24 02:09:00 linux-18ru kernel: ---[ end trace ef43474069fa1d14 ]---
Comment 10 Martin 2015-12-11 08:03:51 UTC
Still present for me in 4.3.1 on Dell XPS 13 (i7-3537U)
Comment 11 Andreas Gnau 2015-12-23 00:25:21 UTC
Fixed for me in 4.4-rc5. Can someone else confirm this?

The change was merged in 4.4-rc4:
drm/i915: Don't compare has_drrs strictly in pipe config
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=13b13dfaaa39ab52b0f433c6744f4638793cbf7b
Comment 12 Steffen Weber 2015-12-23 08:07:43 UTC
I'm using an HP EliteBook 840 G1 attached to an "HP 2013 UltraSlim Docking Station" with two external displays and applying the patch to Linux 4.3.3 has fixed the error for me. Thanks!
Comment 13 Thomas 2016-03-04 13:37:21 UTC
still exists here on Lenovo Thinkpad 560 with Intel/Radeon graphics (with docking station)

[  506.937762] WARNING: CPU: 2 PID: 1120 at ../drivers/gpu/drm/i915/intel_pm.c:3597 skl_update_other_pipe_wm+0x1ba/0x1c0 [i915]()
[  506.937763] WARN_ON(!wm_changed)
[  506.937764] Modules linked in:
[  506.937765]  fuse rfcomm af_packet nf_log_ipv6 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_pkttype ip6t_REJECT xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT iptable_raw xt_CT iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables bnep drbg ansi_cprng dm_crypt ax88179_178a usbnet mii snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic snd_usb_audio snd_usbmidi_lib snd_rawmidi arc4 uvcvideo videobuf2_vmalloc videobuf2_memops x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel videobuf2_v4l2 videobuf2_core v4l2_common kvm irqbypass crct10dif_pclmul crc32_pclmul videodev snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crc32c_intel snd_pcm
[  506.937869]  btusb btrtl btbcm btintel bluetooth thinkpad_acpi snd_seq iwlmvm mac80211 snd_seq_device snd_timer iTCO_wdt iTCO_vendor_support snd dm_mod iwlwifi rtsx_pci_ms aesni_intel memstick aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd mei_me cfg80211 pcspkr soundcore serio_raw e1000e ptp pps_core i2c_i801 rfkill battery ac shpchp mei thermal wmi fjes tpm_tis tpm hid_generic usbhid rtsx_pci_sdmmc mmc_core i915 radeon i2c_algo_bit drm_kms_helper ttm rtsx_pci mfd_core xhci_pci xhci_hcd usbcore usb_common syscopyarea sysfillrect sysimgblt fb_sys_fops drm video button sg
[  506.937905] CPU: 2 PID: 1120 Comm: X Tainted: G        W       4.4.3-1.g171b8f1-default #1
[  506.937907] Hardware name: LENOVO 20EV000YGE/20EV000YGE, BIOS R00ET37W (1.12 ) 01/17/2016
[  506.937910]  0000000000000000 ffff88042d8677d0 ffffffff813828b1 ffff88042d867818
[  506.937913]  ffffffffa046fc28 ffff88042d867808 ffffffff8107d712 ffff880430b67000
[  506.937916]  ffff88042d867934 ffff880098175000 0000000000000000 ffff88042d8678a0
[  506.937919] Call Trace:
[  506.937924]  [<ffffffff8101b0e5>] try_stack_unwind+0x175/0x190
[  506.937930]  [<ffffffff8101a039>] dump_trace+0x69/0x3a0
[  506.937934]  [<ffffffff8101b14b>] show_trace_log_lvl+0x4b/0x60
[  506.937946]  [<ffffffff8101a47c>] show_stack_log_lvl+0x10c/0x180
[  506.937956]  [<ffffffff8101b1e5>] show_stack+0x25/0x50
[  506.937963]  [<ffffffff813828b1>] dump_stack+0x63/0x82
[  506.937971]  [<ffffffff8107d712>] warn_slowpath_common+0x82/0xc0
[  506.937976]  [<ffffffff8107d79c>] warn_slowpath_fmt+0x4c/0x50
[  506.937995]  [<ffffffffa03abc4a>] skl_update_other_pipe_wm+0x1ba/0x1c0 [i915]
[  506.938024]  [<ffffffffa03abe82>] skl_update_wm+0x232/0x720 [i915]
[  506.938044]  [<ffffffffa03b024e>] intel_update_watermarks+0x1e/0x30 [i915]
[  506.938073]  [<ffffffffa0417bc0>] haswell_crtc_enable+0x370/0x870 [i915]
[  506.938102]  [<ffffffffa0414b68>] intel_atomic_commit+0x448/0x6d0 [i915]
[  506.938126]  [<ffffffffa00492d7>] drm_atomic_commit+0x37/0x60 [drm]
[  506.938142]  [<ffffffffa01b3ec6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
[  506.938159]  [<ffffffffa0038892>] drm_mode_set_config_internal+0x62/0x100 [drm]
[  506.938176]  [<ffffffffa003cd2f>] drm_mode_setcrtc+0x3bf/0x4e0 [drm]
[  506.938192]  [<ffffffffa002e612>] drm_ioctl+0x152/0x540 [drm]
[  506.938198]  [<ffffffff8120fdd8>] do_vfs_ioctl+0x288/0x470
[  506.938205]  [<ffffffff81210039>] SyS_ioctl+0x79/0x90
[  506.938211]  [<ffffffff816aebf6>] entry_SYSCALL_64_fastpath+0x16/0x75
[  506.940380] DWARF2 unwinder stuck at entry_SYSCALL_64_fastpath+0x16/0x75
Comment 14 Jani Nikula 2016-06-16 07:35:57 UTC
Please reopen if the problem persists with current drm-intel-nightly.

*** This bug has been marked as a duplicate of bug 89055 ***


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.