[Bug 86411] New: Ivybridge Intel graphics crash very early in boot process/delay in monitor availability

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=86411

            Bug ID: 86411
           Summary: Ivybridge Intel graphics crash very early in boot
                    process/delay in monitor availability
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.17.1
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - Intel)
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: da_audiophile at yahoo.com
                CC: intel-gfx-bugs at lists.freedesktop.org
        Regression: No

Created attachment 154011
  --> https://bugzilla.kernel.org/attachment.cgi?id=154011&action=edit
dmesg with debug flag

Since updating to 3.17.1, my Ivybridge graphics consistently crash upon boot
leaving the screen black (monitor goes to standby) for a good 30 sec after
booting.  Attached is dmesg with the drm.debug=14 kernel parameter.  I pulled
out a few salient lines below.  I am using the display port in order to drive
my 2560x1440 monitor if that is relevant.

My CPU is an Intel i7-3770k (Ivy) and I am using the integrated HD 4000
graphics together with the distro provided driver packages: intel-dri
libva-intel-driver xf86-video-intel.

Glad to provide additional logs/info upon request.

[    0.691112] [drm:intel_pipe_config_compare] *ERROR* mismatch in
pch_pfit.enabled (expected 0, found 1)
[    0.691113] ------------[ cut here ]------------
[    0.691148] WARNING: CPU: 0 PID: 78 at
drivers/gpu/drm/i915/intel_display.c:10659 check_crtc_state+0x7f3/0xe60
[i915]()
[    0.691149] pipe state doesn't match!
[    0.691154] Modules linked in: i915(+) button intel_gtt i2c_algo_bit video
drm_kms_helper drm i2c_core
[    0.691156] CPU: 0 PID: 78 Comm: modprobe Not tainted 3.17.1-1-custom #1
[    0.691157] Hardware name: System manufacturer System Product Name/P8Z77-V
PRO, BIOS 2104 08/13/2013
[    0.691160]  0000000000000000 00000000d0807c40 ffff8807f25770c8
ffffffff814fedd9
[    0.691162]  ffff8807f2577110 ffff8807f2577100 ffffffff8105693d
ffff8807f43e8060
[    0.691164]  ffff8807f3dbf000 ffff8807f3dbf338 ffff8807f43e8000
ffff8807f43e8708
[    0.691164] Call Trace:
[    0.691169]  [<ffffffff814fedd9>] dump_stack+0x4d/0x6f
[    0.691172]  [<ffffffff8105693d>] warn_slowpath_common+0x7d/0xa0
[    0.691174]  [<ffffffff810569bc>] warn_slowpath_fmt+0x5c/0x80
[    0.691202]  [<ffffffffa00ddee3>] check_crtc_state+0x7f3/0xe60 [i915]
[    0.691227]  [<ffffffffa00ec689>] intel_modeset_check_state+0x219/0x7b0
[i915]
[    0.691247]  [<ffffffffa00eccb5>] intel_set_mode+0x25/0x30 [i915]
[    0.691265]  [<ffffffffa00ede54>] intel_crtc_set_config+0xaf4/0xef0 [i915]
[    0.691273]  [<ffffffffa0026304>] drm_mode_set_config_internal+0x64/0xe0
[drm]
[    0.691277]  [<ffffffffa007e1a3>] restore_fbdev_mode+0xb3/0xe0
[drm_kms_helper]
[    0.691280]  [<ffffffffa007e1f3>]
drm_fb_helper_restore_fbdev_mode_unlocked+0x23/0x40 [drm_kms_helper]
[    0.691284]  [<ffffffffa0080418>] drm_fb_helper_set_par+0x28/0x70
[drm_kms_helper]
[    0.691325]  [<ffffffffa00f8f3a>] intel_fbdev_set_par+0x1a/0x60 [i915]
[    0.691328]  [<ffffffff812e7038>] fbcon_init+0x578/0x600
[    0.691331]  [<ffffffff8134f5b8>] visual_init+0xb8/0x120
[    0.691334]  [<ffffffff81351ad6>] do_bind_con_driver+0x176/0x3f0
[    0.691336]  [<ffffffff813522f4>] do_take_over_console+0xb4/0x1b0
[    0.691339]  [<ffffffff812e7123>] do_fbcon_takeover+0x63/0xd0
[    0.691341]  [<ffffffff812eb79d>] fbcon_event_notify+0x6cd/0x7d0
[    0.691344]  [<ffffffff8107525d>] notifier_call_chain+0x4d/0x70
[    0.691347]  [<ffffffff81075627>] __blocking_notifier_call_chain+0x47/0x60
[    0.691350]  [<ffffffff81075656>] blocking_notifier_call_chain+0x16/0x20
[    0.691352]  [<ffffffff812f1aeb>] fb_notifier_call_chain+0x1b/0x20
[    0.691354]  [<ffffffff812f3cee>] register_framebuffer+0x20e/0x360
[    0.691357]  [<ffffffffa0080247>] drm_fb_helper_initial_config+0x377/0x520
[drm_kms_helper]
[    0.691377]  [<ffffffffa00d1782>] ? gen6_write32+0x72/0x110 [i915]
[    0.691397]  [<ffffffffa00f9b1f>] intel_fbdev_initial_config+0x1f/0x30
[i915]
[    0.691422]  [<ffffffffa011faf1>] i915_driver_load+0x1051/0x10b0 [i915]
[    0.691429]  [<ffffffffa001ffbd>] drm_dev_register+0xad/0x100 [drm]
[    0.691435]  [<ffffffffa00228b8>] drm_get_pci_dev+0xd8/0x200 [drm]
[    0.691452]  [<ffffffffa008a45b>] i915_pci_probe+0x3b/0x60 [i915]
[    0.691454]  [<ffffffff812c2b15>] local_pci_probe+0x45/0xa0
[    0.691456]  [<ffffffff812c2a65>] ? pci_match_device+0xe5/0x110
[    0.691458]  [<ffffffff812c2c71>] pci_device_probe+0x101/0x150
[    0.691461]  [<ffffffff813771e3>] driver_probe_device+0xa3/0x410
[    0.691463]  [<ffffffff8137761b>] __driver_attach+0x8b/0x90
[    0.691465]  [<ffffffff81377590>] ? __device_attach+0x40/0x40
[    0.691467]  [<ffffffff81375003>] bus_for_each_dev+0x73/0xc0
[    0.691469]  [<ffffffff81376c6e>] driver_attach+0x1e/0x20
[    0.691471]  [<ffffffff81376850>] bus_add_driver+0x180/0x250
[    0.691473]  [<ffffffff81377eb4>] driver_register+0x64/0xf0
[    0.691475]  [<ffffffff812c247b>] __pci_register_driver+0x4b/0x50
[    0.691480]  [<ffffffffa0022aea>] drm_pci_init+0x10a/0x140 [drm]
[    0.691481]  [<ffffffffa0169000>] ? 0xffffffffa0169000
[    0.691497]  [<ffffffffa0169089>] i915_init+0x89/0x90 [i915]
[    0.691499]  [<ffffffff81000318>] do_one_initcall+0xd8/0x200
[    0.691502]  [<ffffffff81189616>] ? kfree+0x196/0x1a0
[    0.691505]  [<ffffffff8116e0f2>] ? __vunmap+0xa2/0x100
[    0.691508]  [<ffffffff810d0ccc>] load_module+0x1dcc/0x26a0
[    0.691511]  [<ffffffff810cd1f0>] ? store_uevent+0x70/0x70
[    0.691514]  [<ffffffff811a9d87>] ? kernel_read+0x57/0x90
[    0.691517]  [<ffffffff810d1766>] SyS_finit_module+0xa6/0xe0
[    0.691520]  [<ffffffff81504c52>] system_call_fastpath+0x16/0x1b
[    0.691521] ---[ end trace 881ad6f9fdbe08de ]---

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.