[Bug 52061] [snb dp] intel_wait_for_pipe_off timed out

[bugzilla-daemon at bugzilla.kernel.org]

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

Adam Williamson <awilliam at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |awilliam at redhat.com

--- Comment #15 from Adam Williamson <awilliam at redhat.com> ---
There's a longstanding similar downstream report at
https://bugzilla.redhat.com/show_bug.cgi?id=929220 . I have had a similar
intel_wait_for_pipe_off timeout on my Sony Vaio Z (2010 version, VPCZ1,
graphics adapter an 8086:0046) for many kernel revisions now, and it persists
with 3.14 (latest kernel to hit Fedora 20). The 3.14 incarnation looks like
this:

WARNING: CPU: 0 PID: 283 at drivers/gpu/drm/i915/intel_display.c:851
intel_wait_for_pipe_off+0x1db/0x1f0 [i915]()
pipe_off wait timed out
Modules linked in: crct10dif_pclmul crc32_pclmul crc32c_intel i915(+)
ghash_clmulni_intel e1000e i2c_algo_bit drm_kms_helper ptp drm pps_core
i2c_core video
CPU: 0 PID: 283 Comm: systemd-udevd Not tainted 3.13.10-200.fc20.x86_64 #1
Hardware name: Sony Corporation VPCZ112GD/VAIO, BIOS R3031C3 10/04/2011
 0000000000000009 ffff88024ce172e8 ffffffff81687eac ffff88024ce17330
 ffff88024ce17320 ffffffff8106d4dd ffff880036964000 0000000000070008
 00000000fffb7b27 0000000000000000 ffff88024ccdd320 ffff88024ce17380
Call Trace:
 [<ffffffff81687eac>] dump_stack+0x45/0x56
 [<ffffffff8106d4dd>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff8106d54c>] warn_slowpath_fmt+0x4c/0x50
 [<ffffffffa015d9c8>] ? gen5_read32+0x48/0xc0 [i915]
 [<ffffffffa011e2ab>] intel_wait_for_pipe_off+0x1db/0x1f0 [i915]
 [<ffffffffa011e360>] intel_disable_pipe+0xa0/0xb0 [i915]
 [<ffffffffa011f434>] ironlake_crtc_disable+0xe4/0x940 [i915]
 [<ffffffffa011b39e>] ? intel_dump_pipe_config.isra.46+0x35e/0x370 [i915]
 [<ffffffffa0126374>] __intel_set_mode+0x7e4/0x14d0 [i915]
 [<ffffffffa0129456>] intel_set_mode+0x16/0x30 [i915]
 [<ffffffffa0129d0b>] intel_crtc_set_config+0x7ab/0x9a0 [i915]
 [<ffffffffa0031a5d>] drm_mode_set_config_internal+0x5d/0xe0 [drm]
 [<ffffffffa0088f41>] drm_fb_helper_set_par+0x71/0xf0 [drm_kms_helper]
 [<ffffffff8137b534>] fbcon_init+0x4f4/0x570
 [<ffffffff813eb3b8>] visual_init+0xb8/0x120
 [<ffffffff813edcd3>] do_bind_con_driver+0x163/0x330
 [<ffffffff813ee484>] do_take_over_console+0x114/0x1c0
 [<ffffffff81376df3>] do_fbcon_takeover+0x63/0xd0
 [<ffffffff8137c09d>] fbcon_event_notify+0x60d/0x720
 [<ffffffff81692a1c>] notifier_call_chain+0x4c/0x70
 [<ffffffff81093a0d>] __blocking_notifier_call_chain+0x4d/0x70
 [<ffffffff81093a46>] blocking_notifier_call_chain+0x16/0x20
 [<ffffffff8136db4b>] fb_notifier_call_chain+0x1b/0x20
 [<ffffffff8136fb2b>] register_framebuffer+0x1db/0x320
 [<ffffffffa0088bef>] drm_fb_helper_initial_config+0x32f/0x500 [drm_kms_helper]
 [<ffffffffa015d9c8>] ? gen5_read32+0x48/0xc0 [i915]
 [<ffffffffa015dbfb>] ? gen5_write32+0x4b/0xb0 [i915]
 [<ffffffffa0163ff1>] intel_fbdev_initial_config+0x21/0x30 [i915]
 [<ffffffffa00ee2ac>] i915_driver_load+0xe0c/0xe40 [i915]
 [<ffffffffa002ba92>] drm_dev_register+0xa2/0x1e0 [drm]
 [<ffffffffa002d962>] drm_get_pci_dev+0x92/0x140 [drm]
 [<ffffffffa00ea67c>] i915_pci_probe+0x3c/0x90 [i915]
 [<ffffffff81352295>] local_pci_probe+0x45/0xa0
 [<ffffffff81093a18>] ? __blocking_notifier_call_chain+0x58/0x70
 [<ffffffff81353611>] pci_device_probe+0xd1/0x130
 [<ffffffff81418305>] driver_probe_device+0x125/0x3a0
 [<ffffffff81418653>] __driver_attach+0x93/0xa0
 [<ffffffff814185c0>] ? __device_attach+0x40/0x40
 [<ffffffff81416293>] bus_for_each_dev+0x63/0xa0
 [<ffffffff81417cbe>] driver_attach+0x1e/0x20
 [<ffffffff814178a0>] bus_add_driver+0x180/0x250
 [<ffffffffa01aa000>] ? 0xffffffffa01a9fff
 [<ffffffff81418c94>] driver_register+0x64/0xf0
 [<ffffffffa01aa000>] ? 0xffffffffa01a9fff
 [<ffffffff81351c3c>] __pci_register_driver+0x4c/0x50
 [<ffffffffa002db2a>] drm_pci_init+0x11a/0x130 [drm]
 [<ffffffffa01aa000>] ? 0xffffffffa01a9fff
 [<ffffffffa01aa066>] i915_init+0x66/0x68 [i915]
 [<ffffffff8100214a>] do_one_initcall+0xfa/0x1b0
 [<ffffffff810548d3>] ? set_memory_nx+0x43/0x50
 [<ffffffff810e07ed>] load_module+0x1e1d/0x25b0
 [<ffffffff810dc500>] ? store_uevent+0x40/0x40
 [<ffffffff810e10f6>] SyS_finit_module+0x86/0xb0
 [<ffffffff81696e69>] system_call_fastpath+0x16/0x1b

I hit this on, I think, every single boot of the affected laptop - it does not
happen only when an external display is connected. There doesn't appear to be
any phantom display either - xrandr reports only eDP1 (the laptop's internal
display) as connected, which is correct.

Let me know if I can provide any further info, or if this too should be filed
as a separate bug.

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