[Bug 92456] 4.3.0-rc5 triggers warning in intel_pipe_config_compare

Tue Nov 24 02:17:22 PST 2015

https://bugs.freedesktop.org/show_bug.cgi?id=92456

--- Comment #9 from Max Lin <mlin at suse.com> ---
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 ]---

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20151124/f9d8d963/attachment.html>