Bug 1171649

Summary: [abrt] WARNING: CPU: 2 PID: 301 at drivers/gpu/drm/i915/intel_display.c:902 intel_wait_for_vblank+0x209/0x210 [i915]()
Product: [Fedora] Fedora Reporter: Vitaly Isaev <vitalyisaev2>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ajax, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e9ddd829c41c958573d4d554e4ea01f684459d7c
Whiteboard: abrt_hash:8c807597d36e2a2997a9565b6646cf88c8f919b9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-27 16:11:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: dmesg none

Description Vitaly Isaev 2014-12-08 10:12:43 UTC 
Description of problem:
It seems like this problem occures almost every time when the computer stops. Actually it fails to stop, and when I click "F10", I can only see this warning. 

Hardware: GPU NVIDIA GeForce GT 620M 1GB on ASUS UX32V Notebook;
Kernel: 3.17.4-200.fc20.x86_64

Additional info:
reporter:       libreport-2.2.3
WARNING: CPU: 2 PID: 301 at drivers/gpu/drm/i915/intel_display.c:902 intel_wait_for_vblank+0x209/0x210 [i915]()
vblank wait timed out
Modules linked in: nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper drm wmi video
CPU: 2 PID: 301 Comm: plymouthd Not tainted 3.17.4-200.fc20.x86_64 #1
Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.213 11/16/2012
 0000000000000000 00000000eab5d9e8 ffff8800c27fbb68 ffffffff81726d2c
 ffff8800c27fbbb0 ffff8800c27fbba0 ffffffff81092e6d ffff880036780000
 0000000000070040 000000000000028b 00000000fffb7822 ffff880127f6b000
Call Trace:
 [<ffffffff81726d2c>] dump_stack+0x45/0x56
 [<ffffffff81092e6d>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff81092eec>] warn_slowpath_fmt+0x5c/0x80
 [<ffffffffa0143209>] intel_wait_for_vblank+0x209/0x210 [i915]
 [<ffffffffa014e038>] intel_pipe_set_base+0x188/0x3d0 [i915]
 [<ffffffffa01510fd>] intel_crtc_set_config+0x9bd/0xe60 [i915]
 [<ffffffffa0027584>] drm_mode_set_config_internal+0x64/0xf0 [drm]
 [<ffffffffa002bb58>] drm_mode_setcrtc+0xe8/0x5c0 [drm]
 [<ffffffffa001de0c>] drm_ioctl+0x1ec/0x660 [drm]
 [<ffffffff811bff0d>] ? mmap_region+0x19d/0x640
 [<ffffffff81212e50>] do_vfs_ioctl+0x2e0/0x4a0
 [<ffffffff81213091>] SyS_ioctl+0x81/0xa0
 [<ffffffff8172e3e9>] system_call_fastpath+0x16/0x1b
Comment 1 Vitaly Isaev 2014-12-08 10:12:57 UTC 
Created attachment 965740 [details]
File: dmesg
Comment 2 Adam Jackson 2015-05-27 16:11:02 UTC 

*** This bug has been marked as a duplicate of bug 1144620 ***