| Summary: | [i915] kernel 3.11.2 intel_pipe_config_compare ERROR | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Carsten Mattner <carstenmattner> | ||||||||||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||||||
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||||||
| Severity: | normal | ||||||||||||||||
| Priority: | medium | CC: | da_audiophile, freedesktop, intel-gfx-bugs, mike.parker | ||||||||||||||
| Version: | unspecified | ||||||||||||||||
| Hardware: | x86 (IA32) | ||||||||||||||||
| OS: | Linux (All) | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| i915 platform: | i915 features: | ||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Carsten Mattner
2013-09-27 08:43:45 UTC
Distro bug: https://bugs.archlinux.org/task/37085 Hardware is Intel 945GM Can you please test with the latest drm-intel-fixes git branch from http://cgit.freedesktop.org/~danvet/drm-intel/ If the issue persists please boot with drm.debug=0xe, reproduce the WARN and then attach the complete dmesg to this bug report. (In reply to comment #3) > Can you please test with the latest drm-intel-fixes git branch from > http://cgit.freedesktop.org/~danvet/drm-intel/ > > If the issue persists please boot with drm.debug=0xe, reproduce the WARN and > then attach the complete dmesg to this bug report. I tried with 3.11.1 and that one's still good. I don't know if I can get a kernel built but might give a try later and can't reboot the machine at the moment anyhow. Don't you think https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=cc0ffca95bf3e8cd393327c444c5bf4493deda90 is at fault? I can confirm the bug on my i7-3770k (onboard HD 4000). If I revert the commit that Carsten linked in comment #4, I get no such error in dmesg. Section of dmsg under 3.11.2 without revert: [ 0.738132] fbcon: inteldrmfb (fb0) is primary device [ 0.939391] [drm:intel_dp_complete_link_train] *ERROR* failed to train DP, aborting [ 1.022675] [drm:intel_pipe_config_compare] *ERROR* mismatch in pch_pfit.size (expected 0, found 167773600) [ 1.022675] ------------[ cut here ]------------ [ 1.022686] WARNING: CPU: 0 PID: 78 at drivers/gpu/drm/i915/intel_display.c:8299 check_crtc_state+0x59f/0x9d0 [i915]() [ 1.022687] pipe state doesn't match! [ 1.022689] Modules linked in: i915(+) video button i2c_algo_bit intel_agp intel_gtt drm_kms_helper drm i2c_core [ 1.022690] CPU: 0 PID: 78 Comm: modprobe Not tainted 3.11.2-1-custom #1 [ 1.022691] Hardware name: System manufacturer System Product Name/P8Z77-V PRO, BIOS 2104 08/13/2013 [ 1.022693] 0000000000000009 ffff880408647180 ffffffff8147721d ffff8804086471c8 [ 1.022694] ffff8804086471b8 ffffffff81048efd ffff880409a1b6d8 ffff8804085d6800 [ 1.022695] 0000000000000001 ffff8804085d6ca0 ffff880409a1b000 ffff880408647218 [ 1.022696] Call Trace: [ 1.022699] [<ffffffff8147721d>] dump_stack+0x54/0x8d [ 1.022701] [<ffffffff81048efd>] warn_slowpath_common+0x7d/0xa0 [ 1.022702] [<ffffffff81048f6c>] warn_slowpath_fmt+0x4c/0x50 [ 1.022711] [<ffffffffa00be91f>] check_crtc_state+0x59f/0x9d0 [i915] [ 1.022720] [<ffffffffa00c91e3>] intel_modeset_check_state+0x2c3/0x770 [i915] [ 1.022727] [<ffffffffa00c9725>] intel_set_mode+0x25/0x30 [i915] [ 1.022733] [<ffffffffa00c9f92>] intel_crtc_set_config+0x762/0x920 [i915] [ 1.022737] [<ffffffffa001dc5d>] drm_mode_set_config_internal+0x5d/0xe0 [drm] [ 1.022739] [<ffffffffa0064681>] drm_fb_helper_set_par+0x71/0xf0 [drm_kms_helper] [ 1.022741] [<ffffffff812bd2b4>] fbcon_init+0x504/0x580 [ 1.022743] [<ffffffff813180fc>] visual_init+0xbc/0x120 [ 1.022744] [<ffffffff8131a6a3>] do_bind_con_driver+0x163/0x380 [ 1.022745] [<ffffffff8131aea4>] do_take_over_console+0x114/0x1c0 [ 1.022747] [<ffffffff812bd393>] do_fbcon_takeover+0x63/0xd0 [ 1.022748] [<ffffffff812c1ae5>] fbcon_event_notify+0x605/0x720 [ 1.022750] [<ffffffff8148164c>] notifier_call_chain+0x4c/0x70 [ 1.022751] [<ffffffff8106fe3d>] __blocking_notifier_call_chain+0x4d/0x70 [ 1.022752] [<ffffffff8106fe76>] blocking_notifier_call_chain+0x16/0x20 [ 1.022754] [<ffffffff812b190b>] fb_notifier_call_chain+0x1b/0x20 [ 1.022755] [<ffffffff812b38dd>] register_framebuffer+0x1dd/0x310 [ 1.022757] [<ffffffffa006442f>] drm_fb_helper_initial_config+0x32f/0x510 [drm_kms_helper] [ 1.022760] [<ffffffffa001c75f>] ? drm_mode_config_reset+0xcf/0xf0 [drm] [ 1.022762] [<ffffffff8115dfc5>] ? kmem_cache_alloc_trace+0x225/0x270 [ 1.022763] [<ffffffffa00628a9>] ? drm_fb_helper_init+0x179/0x210 [drm_kms_helper] [ 1.022773] [<ffffffffa00ea551>] intel_fbdev_initial_config+0x21/0x30 [i915] [ 1.022781] [<ffffffffa0099351>] i915_driver_load+0xdc1/0xdf0 [i915] [ 1.022785] [<ffffffffa0019486>] drm_get_pci_dev+0x166/0x280 [drm] [ 1.022792] [<ffffffffa009471c>] i915_pci_probe+0x2c/0x70 [i915] [ 1.022794] [<ffffffff81289d7e>] local_pci_probe+0x3e/0x70 [ 1.022796] [<ffffffff81289f71>] pci_device_probe+0x111/0x120 [ 1.022798] [<ffffffff8133b927>] driver_probe_device+0x87/0x3a0 [ 1.022799] [<ffffffff8133bd13>] __driver_attach+0x93/0xa0 [ 1.022800] [<ffffffff8133bc80>] ? __device_attach+0x40/0x40 [ 1.022802] [<ffffffff81339843>] bus_for_each_dev+0x63/0xa0 [ 1.022803] [<ffffffff8133b37e>] driver_attach+0x1e/0x20 [ 1.022804] [<ffffffff8133af18>] bus_add_driver+0x1e8/0x2a0 [ 1.022805] [<ffffffffa012a000>] ? 0xffffffffa0129fff [ 1.022806] [<ffffffff8133c384>] driver_register+0x74/0x150 [ 1.022807] [<ffffffffa012a000>] ? 0xffffffffa0129fff [ 1.022808] [<ffffffff81289bfd>] __pci_register_driver+0x4d/0x50 [ 1.022811] [<ffffffffa00196ba>] drm_pci_init+0x11a/0x130 [drm] [ 1.022812] [<ffffffff8147ac8e>] ? mutex_unlock+0xe/0x10 [ 1.022813] [<ffffffffa012a000>] ? 0xffffffffa0129fff [ 1.022820] [<ffffffffa012a066>] i915_init+0x66/0x68 [i915] [ 1.022821] [<ffffffff810002c2>] do_one_initcall+0xf2/0x1a0 [ 1.022822] [<ffffffff8106fe48>] ? __blocking_notifier_call_chain+0x58/0x70 [ 1.022824] [<ffffffff810aa4c7>] load_module+0x1b17/0x25b0 [ 1.022825] [<ffffffff810a6f10>] ? store_uevent+0x40/0x40 [ 1.022827] [<ffffffff810ab0d6>] SyS_finit_module+0x86/0xb0 [ 1.022829] [<ffffffff81485546>] system_call_fastpath+0x1a/0x1f [ 1.022829] ---[ end trace 90f11c6df3f24fdf ]--- Neglected to mention my box is x86_64 so I changed the tag on the bug (op's was i686). Jon: You have a different bug, please separate a new report for it. When you do so please boot with drm.debug=0xe and attach the complete dmesg. Carsten: Strange that the regression is from 3.11.1 to .2. But without the drm.debug=0xe dmesg I can't really tell much more. @Daniel - I rebooted with the debug flag bug could not replicate the error?! Removing the debug flag as well, booted into a non-error state. This is using the stock kernel (i.e. without reverting that commit). Created attachment 86795 [details]
dmesg output
Comment on attachment 86795 [details]
dmesg output
This is on a headless home server, reproducible at every boot, error first showed up in 3.11.2 when updating from 3.11.1
(In reply to comment #10) > Comment on attachment 86795 [details] > dmesg output > > This is on a headless home server, reproducible at every boot, error first > showed up in 3.11.2 when updating from 3.11.1 This is a dupe of bug #69791. In general _please_ file new bug reports, it's much easier for us to mark a bug as a duplicate than to untangle a maze of me-too reports that effectively are all different bug reports. I know that bugzilla gives you a neat list of possible dupes, but ignoring that is usually the best option. Of course if an upstream dev told you (on irc or so) that there's a bug report already that's different. Created attachment 86906 [details]
3.11.1 drm.debug=0xe
Created attachment 86907 [details]
3.11.2 drm.debug=0xe
Attached dmesg. Fix is on it's way to stable kernels. Thanks for reporting this issue and please reopen in case my analysis is wrong. *** This bug has been marked as a duplicate of bug 69791 *** Created attachment 86947 [details]
3.11.1 drm.debug=0xe
Created attachment 86948 [details]
3.11.2 drm.debug=0xe
Created attachment 86949 [details]
3.11.3 drm.debug=0xe
(In reply to comment #15) > Fix is on it's way to stable kernels. Thanks for reporting this issue and > please reopen in case my analysis is wrong. > > *** This bug has been marked as a duplicate of bug 69791 *** Same problem with 3.11.3 switched back to 3.11.1. I've somehow lost the cc: stable tag. Just sent a mail to greg, so this should get fixed asap. Confirming Comment 19, issue NOT fixed by 3.11.3 (In reply to comment #21) > Confirming Comment 19, issue NOT fixed by 3.11.3 The patch is on it's way, reopening the bug won't make it faster. And indeed, it landed already in 3.11.4: commit ca17380a57e7c94dc443fe4fd078bdb07e147b7f Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Tue Sep 10 11:44:30 2013 +0200 drm/i915/tv: clear adjusted_mode.flags Geez ... Confirmed as fixed in 3.11.4 Closing old verified. |
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.