*** Bug 1206284 has been marked as a duplicate of this bug. ***

Description of problem:
On boot, and on screen saver exit I get a consistant "drm_wait_one_vblank" error on an older intel core 2 duao machine with fedora 21. I don't see it on a new intel I5 machine running fedora 20. This error is new, and was never seen on either machine in the past. I conclude (without solid evidence) that this problem is due to the intel graphic interface "wake up" on older intel processor machines. Either a new graphics instruction is used (not available in older machines) or a necessary time delay has been eliminated in the software "wake up" process.

Version-Release number of selected component:
kernel

Additional info:
reporter:       libreport-2.3.0
cmdline:        BOOT_IMAGE=/vmlinuz-3.19.3-200.fc21.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap vconsole.font=latarcyrheb-sun16 rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
kernel:         3.19.3-200.fc21.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
WARNING: CPU: 0 PID: 55 at drivers/gpu/drm/drm_irq.c:1121 drm_wait_one_vblank+0x190/0x1a0 [drm]()
vblank not available on crtc 0, ret=-22
Modules linked in: i915 e1000e firewire_ohci firewire_core ata_generic pata_acpi i2c_algo_bit video crc_itu_t drm_kms_helper drm pata_marvell ptp pps_core
CPU: 0 PID: 55 Comm: kworker/u8:2 Not tainted 3.19.3-200.fc21.x86_64 #1
Hardware name:                  /DG33TL, BIOS DPP3510J.86A.0572.2009.0715.2346 07/15/2009
Workqueue: events_unbound async_run_entry_fn
 0000000000000000 00000000721621ec ffff8800cb22f648 ffffffff8176e215
 0000000000000000 ffff8800cb22f6a0 ffff8800cb22f688 ffffffff8109bc1a
 ffff8800cb22f688 ffff880035d02000 ffff880035d38000 0000000000000000
Call Trace:
 [<ffffffff8176e215>] dump_stack+0x45/0x57
 [<ffffffff8109bc1a>] warn_slowpath_common+0x8a/0xc0
 [<ffffffff8109bca5>] warn_slowpath_fmt+0x55/0x70
 [<ffffffffa0023930>] drm_wait_one_vblank+0x190/0x1a0 [drm]
 [<ffffffffa01c0f5f>] intel_enable_sdvo+0x7f/0x150 [i915]
 [<ffffffffa018cc4b>] i9xx_crtc_enable+0x3fb/0x4c0 [i915]
 [<ffffffffa014c122>] ? i915_gem_object_unpin_from_display_plane+0x12/0x70 [i915]
 [<ffffffffa018b1c2>] __intel_set_mode+0x8a2/0xca0 [i915]
 [<ffffffffa01926eb>] intel_crtc_set_config+0xc2b/0xfc0 [i915]
 [<ffffffffa002cb86>] drm_mode_set_config_internal+0x66/0x100 [drm]
 [<ffffffffa008ce78>] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper]
 [<ffffffffa008eed9>] drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x80 [drm_kms_helper]
 [<ffffffffa008ef52>] drm_fb_helper_set_par+0x22/0x50 [drm_kms_helper]
 [<ffffffffa019fc7a>] intel_fbdev_set_par+0x1a/0x60 [i915]
 [<ffffffff81405778>] fbcon_init+0x578/0x600
 [<ffffffff81484eac>] visual_init+0xbc/0x120
 [<ffffffff8148777e>] do_bind_con_driver+0x17e/0x3b0
 [<ffffffff81487f54>] do_take_over_console+0xb4/0x1b0
 [<ffffffff81400553>] do_fbcon_takeover+0x63/0xd0
 [<ffffffff8140629d>] fbcon_event_notify+0x6cd/0x7d0
 [<ffffffff810bb4df>] notifier_call_chain+0x4f/0x80
 [<ffffffff810bb85b>] __blocking_notifier_call_chain+0x4b/0x70
 [<ffffffff810bb896>] blocking_notifier_call_chain+0x16/0x20
 [<ffffffff8140c20b>] fb_notifier_call_chain+0x1b/0x20
 [<ffffffff8140e5d4>] register_framebuffer+0x214/0x360
 [<ffffffffa008f1e4>] drm_fb_helper_initial_config+0x264/0x3d0 [drm_kms_helper]
 [<ffffffffa01a0fdb>] intel_fbdev_initial_config+0x1b/0x20 [i915]
 [<ffffffff810bd06a>] async_run_entry_fn+0x4a/0x150
 [<ffffffff810b487c>] process_one_work+0x14c/0x3f0
 [<ffffffff810b52f3>] worker_thread+0x53/0x470
 [<ffffffff810b52a0>] ? rescuer_thread+0x300/0x300
 [<ffffffff810ba548>] kthread+0xd8/0xf0
 [<ffffffff810ba470>] ? kthread_create_on_node+0x1b0/0x1b0
 [<ffffffff81774958>] ret_from_fork+0x58/0x90
 [<ffffffff810ba470>] ? kthread_create_on_node+0x1b0/0x1b0

Problem resolved by re installing Fedora 21-KDE OS:

I installed a empty disk drive and installed Fedora 21 live-KDE-x86-64-21-5. I have not re-installed all software, but It looks like the problem does not exist on a fresh installation. I have never installed any proprietary drivers, only the installs in the fedora repository. I used chkroot and rkhunter on the problem drive and found 2 warnings but no problems.

History:
Fedora 20 KDE was installed a year ago and worked well. I updated to fedora 21 2-months ago using the yum fedup command. The system still worked well with no above failure notifications; however, KDE automatic update mechanism no longer worked. Internet research indicated that it was a KDE problem; therefore, I used yum update instead. A month later, after multiple yum updates, the above problem emerged. Since my drives are removable, I simply removed the problem drive and re-built a new one.

The motherboard is an old (>10-years) Intel DG33 with a core 2 Duo E8400 processor. This system now works very well.

I'm also seeing this on a laptop with integrated Intel graphics.

Let me know if you'd like me to gather more info.

It seems to have started with the upgrade to kernel 3.19.3-100.fc20.x86_64

Unfortunately, i am not a Linux guru and am not able to suggest diagnostic methods. I can only suggest re-installing. Having dismissed my credentials, my internet researched suggested that this error indicates a "unsigned driver installation". In my case, no "special" drivers were installed. Naturally I jumped to the conclusion that I should check for a virus. I installed and ran the following:
--- System Security -------
sudo yum instal claimtk
sudo yum install chkrootkit
sudo yum install rkhunter
... but found nothing unusual. 

At the moment, my system is re-built (Fedora 21 live-KDE-x86-64-21-5) and back to almost normal. A few small, but not obstructive, problems which I had before still exist, but all of the above symptoms have vanished. Specifically, power down does not always turn off the computer and sometimes a blank black boxes replace pop-up messages. Firefox has caused problems before, but it seams totally reliable now.

We have a new Asus home built I-5, and it has worked flawlessly untouched for almost a year with fedora 20. My wife uses this one and it doesn't get the use/abuse mine does. The age of our older machines may be a factor.

Hope this helps.

Using : kernel 3.19.3-200.fc21.x86_64

After the latest automatic update elements by Software(3.14.4-1.fc21) have been loaded, the error message on boot-up has disappeared.

The error message still remaining for each wake-up from hibernation.

I've tried also on two prior kernel versions (3.19.2-201.fc21, and 3.19.1-201.fc21), and have found the same result ( boot-up time ; without error message / wake-up form hibernation : with error message), before it ends up with system crash on 3.19.2-201.fc21.

There may be another problem than kernel itself...

Best regards,
Takuo

I still see this with kernel 3.19.4-100.fc20.x86_64

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