Created attachment 718093 [details]
File: dmesg

I've hit this one too (my abrt reports an oops I've hit today as a dupe of this). On a Sony Vaio Z VPC-Z1 (2010 model), I don't think it was associated with any particular action. Let me know if I can provide more details. abrt's count for this on my system is 3.

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

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

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Created attachment 840106 [details]
still happening in F20 with a 3.12 kernel

This is still happening on my Vaio Z in F20, with a 3.12 kernel. Latest clean trace attached.

Hi,

Also seeing this issue on Fedora 20, with kernel 3.12.7-300.fc20.x86_64 on a Dell U3011 monitor connected with displayport connector.

System is a Dell Optiplex 990 with "Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)" gpu.

100% reproducible on each boot.

Regards,

Rik


Stack trace looks similar:

Jan 15 10:29:34 lucifer kernel: WARNING: CPU: 2 PID: 310 at drivers/gpu/drm/i915/intel_display.c:844 intel_wait_for_pipe_off+0x108/0x1e0 [i915]
Jan 15 10:29:34 lucifer kernel: pipe_off wait timed out
Jan 15 10:29:34 lucifer kernel: Modules linked in: raid1 raid0 i915(+) i2c_algo_bit drm_kms_helper drm i2c_core video
Jan 15 10:29:34 lucifer kernel: CPU: 2 PID: 310 Comm: systemd-udevd Not tainted 3.12.7-300.fc20.x86_64 #1
Jan 15 10:29:34 lucifer kernel: Hardware name: Dell Inc. OptiPlex 990/06D7TR, BIOS A17 03/14/2013
Jan 15 10:29:34 lucifer kernel:  0000000000000009 ffff88041465f2d0 ffffffff8166799b ffff88041465f318
Jan 15 10:29:34 lucifer kernel:  ffff88041465f308 ffffffff8106921d 0000000000070008 ffff88041355c000
Jan 15 10:29:34 lucifer kernel:  00000000fffb7287 ffff88041465ffd8 ffff88041441cc18 ffff88041465f368
Jan 15 10:29:34 lucifer kernel: Call Trace:
Jan 15 10:29:34 lucifer kernel:  [<ffffffff8166799b>] dump_stack+0x45/0x56
Jan 15 10:29:34 lucifer kernel:  [<ffffffff8106921d>] warn_slowpath_common+0x7d/0xa0
Jan 15 10:29:34 lucifer kernel:  [<ffffffff8106928c>] warn_slowpath_fmt+0x4c/0x50
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa00b5088>] intel_wait_for_pipe_off+0x108/0x1e0 [i915]
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa00b51f2>] intel_disable_pipe+0x92/0xa0 [i915]
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa00b7f36>] ironlake_crtc_disable+0xd6/0x950 [i915]
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa00bcc44>] __intel_set_mode+0x804/0x1420 [i915]
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa00bfce6>] intel_set_mode+0x16/0x30 [i915]
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa00c05e3>] intel_crtc_set_config+0x7e3/0x9d0 [i915]
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa002d1bd>] drm_mode_set_config_internal+0x5d/0xe0 [drm]
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa007a631>] drm_fb_helper_set_par+0x71/0xf0 [drm_kms_helper]
Jan 15 10:29:34 lucifer kernel:  [<ffffffff81369964>] fbcon_init+0x4f4/0x570
Jan 15 10:29:34 lucifer kernel:  [<ffffffff813d9a98>] visual_init+0xb8/0x120
Jan 15 10:29:34 lucifer kernel:  [<ffffffff813dc283>] do_bind_con_driver+0x163/0x330
Jan 15 10:29:34 lucifer kernel:  [<ffffffff813dca34>] do_take_over_console+0x114/0x1c0
Jan 15 10:29:34 lucifer kernel:  [<ffffffff81365223>] do_fbcon_takeover+0x63/0xd0
Jan 15 10:29:34 lucifer kernel:  [<ffffffff8136a4cd>] fbcon_event_notify+0x60d/0x720
Jan 15 10:29:34 lucifer kernel:  [<ffffffff816723dc>] notifier_call_chain+0x4c/0x70
Jan 15 10:29:34 lucifer kernel:  [<ffffffff810909bd>] __blocking_notifier_call_chain+0x4d/0x70
Jan 15 10:29:34 lucifer kernel:  [<ffffffff810909f6>] blocking_notifier_call_chain+0x16/0x20
Jan 15 10:29:34 lucifer kernel:  [<ffffffff8135bfdb>] fb_notifier_call_chain+0x1b/0x20
Jan 15 10:29:34 lucifer kernel:  [<ffffffff8135dfab>] register_framebuffer+0x1db/0x310
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa007a2df>] drm_fb_helper_initial_config+0x32f/0x500 [drm_kms_helper]
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa00ef03b>] ? i915_read32+0x6b/0x140 [i915]
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa00e31b1>] intel_fbdev_initial_config+0x21/0x30 [i915]
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa008a307>] i915_driver_load+0xf27/0xf50 [i915]
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa0028ef9>] drm_get_pci_dev+0x129/0x2e0 [drm]
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa008665c>] i915_pci_probe+0x2c/0x70 [i915]
Jan 15 10:29:34 lucifer kernel:  [<ffffffff813408ee>] local_pci_probe+0x3e/0x70
Jan 15 10:29:34 lucifer kernel:  [<ffffffff81341c91>] pci_device_probe+0x121/0x130
Jan 15 10:29:34 lucifer kernel:  [<ffffffff81405075>] driver_probe_device+0x125/0x3a0
Jan 15 10:29:34 lucifer kernel:  [<ffffffff814053c3>] __driver_attach+0x93/0xa0
Jan 15 10:29:34 lucifer kernel:  [<ffffffff81405330>] ? __device_attach+0x40/0x40
Jan 15 10:29:34 lucifer kernel:  [<ffffffff81402e93>] bus_for_each_dev+0x63/0xa0
Jan 15 10:29:34 lucifer kernel:  [<ffffffff81404a2e>] driver_attach+0x1e/0x20
Jan 15 10:29:34 lucifer kernel:  [<ffffffff814045a0>] bus_add_driver+0x200/0x2d0
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa0133000>] ? 0xffffffffa0132fff
Jan 15 10:29:34 lucifer kernel:  [<ffffffff81405a04>] driver_register+0x64/0xf0
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa0133000>] ? 0xffffffffa0132fff
Jan 15 10:29:34 lucifer kernel:  [<ffffffff8134076c>] __pci_register_driver+0x4c/0x50
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa00291ca>] drm_pci_init+0x11a/0x130 [drm]
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa0133000>] ? 0xffffffffa0132fff
Jan 15 10:29:34 lucifer kernel:  [<ffffffffa0133066>] i915_init+0x66/0x68 [i915]
Jan 15 10:29:34 lucifer kernel:  [<ffffffff810020f2>] do_one_initcall+0xf2/0x1a0
Jan 15 10:29:34 lucifer kernel:  [<ffffffff81054533>] ? set_memory_nx+0x43/0x50
Jan 15 10:29:34 lucifer kernel:  [<ffffffff810d694d>] load_module+0x1b9d/0x2640
Jan 15 10:29:34 lucifer kernel:  [<ffffffff810d2b00>] ? store_uevent+0x40/0x40
Jan 15 10:29:34 lucifer kernel:  [<ffffffff810d7566>] SyS_finit_module+0x86/0xb0
Jan 15 10:29:34 lucifer kernel:  [<ffffffff81676969>] system_call_fastpath+0x16/0x1b
Jan 15 10:29:34 lucifer kernel: ---[ end trace 4b742a8c4f5b0e9b ]---

Still happening with 3.14.1-200.fc20.x86_64 .

Note: my version of this happens with no external displays connected at all. Just happens on every single boot on my affected laptop.

There are two kernel.org reports for similar bugs:

https://bugzilla.kernel.org/show_bug.cgi?id=52061 is for the one that affects Sandybridge systems
https://bugzilla.kernel.org/show_bug.cgi?id=62251 is for Ironlake systems

There is also a freedesktop.org report for Ironlake:

https://bugs.freedesktop.org/show_bug.cgi?id=54687

Rik, I believe yours may be the Sandybridge case, which upstream seems to indicate is not quite the same as the Ironlake case.

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

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

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

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

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

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

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

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

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

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

Filed against old F19 kernel, closing.  If you're still experiencing this with a current f19-updates kernel, please reopen.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.