Description of problem: Thise happened during boot, but the computer seems to be working OK. Additional info: reporter: libreport-2.2.3 WARNING: CPU: 1 PID: 168 at drivers/gpu/drm/i915/intel_display.c:902 intel_wait_for_vblank+0x1e7/0x1f0 [i915]() vblank wait timed out Modules linked in: i915 ums_realtek uas i2c_algo_bit drm_kms_helper usb_storage drm video CPU: 1 PID: 168 Comm: plymouthd Not tainted 3.17.3-200.fc20.i686+PAE #1 Hardware name: TOSHIBA Satellite L305/Portable PC, BIOS 1.80 03/20/2009 c0cd8947 4bf39db2 00000000 f43b7bd8 c0a35ff9 f43b7c18 f43b7c08 c0460cfe f84ab712 f43b7c38 000000a8 f84a1c68 00000386 f844eb47 f844eb47 f64b8000 00070040 0000000a f43b7c24 c0460d5e 00000009 f43b7c18 f84ab712 f43b7c38 Call Trace: [<c0a35ff9>] dump_stack+0x41/0x52 [<c0460cfe>] warn_slowpath_common+0x7e/0xa0 [<f844eb47>] ? intel_wait_for_vblank+0x1e7/0x1f0 [i915] [<f844eb47>] ? intel_wait_for_vblank+0x1e7/0x1f0 [i915] [<c0460d5e>] warn_slowpath_fmt+0x3e/0x60 [<f844eb47>] intel_wait_for_vblank+0x1e7/0x1f0 [i915] [<f8485809>] intel_tv_detect+0x219/0x5f0 [i915] [<f7fa4788>] drm_helper_probe_single_connector_modes_merge_bits+0x278/0x370 [drm_kms_helper] [<c0a3a180>] ? mutex_lock+0x10/0x28 [<f7fa4897>] drm_helper_probe_single_connector_modes+0x17/0x20 [drm_kms_helper] [<f8092425>] drm_mode_getconnector+0x325/0x3a0 [drm] [<f8092100>] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [<f80863cf>] drm_ioctl+0x1cf/0x520 [drm] [<f8092100>] ? drm_mode_getcrtc+0xc0/0xc0 [drm] [<c05064a7>] ? tracing_entries_read+0xa7/0x190 [<f8086200>] ? drm_copy_field+0x70/0x70 [drm] [<c059e69a>] do_vfs_ioctl+0x2ea/0x4b0 [<c066e392>] ? inode_has_perm.isra.32+0x32/0x40 [<c066e4e7>] ? file_has_perm+0x97/0xa0 [<c066ef5c>] ? selinux_file_ioctl+0x4c/0xf0 [<c059e8c0>] SyS_ioctl+0x60/0x90 [<c04c64a7>] ? __clockevents_unbind+0x67/0xf0 [<c04c64a7>] ? __clockevents_unbind+0x67/0xf0 [<c0a3c7df>] sysenter_do_call+0x12/0x12 [<c04c64a7>] ? __clockevents_unbind+0x67/0xf0 [<c04c64a7>] ? __clockevents_unbind+0x67/0xf0
Created attachment 962328 [details] File: dmesg
*** This bug has been marked as a duplicate of bug 1144620 ***