Bug 1204509 - OOPS: 3.19.1-201.fc21.i686+PAE: drivers/gpu/drm/drm_irq.c:1121 drm_wait_one_vblank+0x164/0x170 [drm]()
Summary: OOPS: 3.19.1-201.fc21.i686+PAE: drivers/gpu/drm/drm_irq.c:1121 drm_wait_one_v...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 21
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1205099 1205210 1205227 1205571 1206199 1207519 1208190 1208468 1208656 1208868 1209024 1210531 1211032 1211349 1211378 1211633 1212948 1214509 1215424 1216104 1224407 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-22 18:54 UTC by customercare
Modified: 2015-12-02 17:44 UTC (History)
29 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 10:23:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description customercare 2015-03-22 18:54:18 UTC
Hardware name: Acer TravelMate 2420/Garda-910  
Kernel:        3.19.1-201.fc21.i686+PAE #1

Happens on System Boot:

Kernel Oops : 

WARNING: CPU: 0 PID: 273 at drivers/gpu/drm/drm_irq.c:1121
drm_wait_one_vblank+0x164/0x170 [drm]()
vblank not available on crtc 0, ret=-22
Modules linked in: i915 8139too i2c_algo_bit drm_kms_helper drm
ata_generic 8139cp pata_acpi yenta_socket mii video
CPU: 0 PID: 273 Comm: plymouthd Tainted: G        W     
3.19.1-201.fc21.i686+PAE #1
Hardware name: Acer TravelMate 2420/Garda-910                          
, BIOS V1.01      12/15/2005
 c0d269c7 00be2399 00000000 f6a45a20 c0a79f1e f6a45a64 f6a45a54 c0466a4b
 f81ed1fc f6a45a84 00000111 f81eb4a3 00000461 f81c7d04 00000461 f81c7d04
 f6bf0000 f6a16c00 00000000 f6a45a70 c0466abe 00000009 f6a45a64 f81ed1fc
Call Trace:
 [<c0a79f1e>] dump_stack+0x41/0x52
 [<c0466a4b>] warn_slowpath_common+0x8b/0xc0
 [<f81c7d04>] ? drm_wait_one_vblank+0x164/0x170 [drm]
 [<f81c7d04>] ? drm_wait_one_vblank+0x164/0x170 [drm]
 [<c0466abe>] warn_slowpath_fmt+0x3e/0x60
 [<f81c7d04>] drm_wait_one_vblank+0x164/0x170 [drm]
 [<f83b3fe2>] intel_enable_tv+0x22/0x60 [i915]
 [<f8380fdd>] i9xx_crtc_enable+0x35d/0x420 [i915]
 [<f837f8e5>] __intel_set_mode+0x8d5/0xab0 [i915]
 [<f83852b6>] intel_set_mode+0x76/0xb0 [i915]
 [<f83854ed>] intel_get_load_detect_pipe+0x1fd/0x4a0 [i915]
 [<f8384799>] ? intel_modeset_check_state+0x219/0xc50 [i915]
 [<f83b4b46>] intel_tv_detect+0x106/0x5c0 [i915]
 [<f81257f8>]
drm_helper_probe_single_connector_modes_merge_bits+0x2c8/0x410
[drm_kms_helper]
 [<c0a7d2f0>] ? mutex_lock+0x10/0x30
 [<f8125957>] drm_helper_probe_single_connector_modes+0x17/0x20
[drm_kms_helper]
 [<f81d3332>] drm_mode_getconnector+0x352/0x3d0 [drm]
 [<f81d2fe0>] ? drm_mode_getcrtc+0xd0/0xd0 [drm]
 [<f81c61b5>] drm_ioctl+0x1f5/0x560 [drm]
 [<c0551d70>] ? __put_single_page+0x20/0x20
 [<f81d2fe0>] ? drm_mode_getcrtc+0xd0/0xd0 [drm]
 [<c05064a7>] ? subbuf_splice_actor.isra.13+0x267/0x2f0
 [<f81c5fc0>] ? drm_getmap+0xc0/0xc0 [drm]
 [<c05b5882>] do_vfs_ioctl+0x322/0x540
 [<c068d892>] ? inode_has_perm.isra.30+0x32/0x50
 [<c068d9f7>] ? file_has_perm+0x97/0xa0
 [<c068e61b>] ? selinux_file_ioctl+0x4b/0xe0
 [<c05b5b00>] SyS_ioctl+0x60/0x90
 [<c04c64a7>] ? SyS_timer_delete+0x87/0x130
 [<c04c64a7>] ? SyS_timer_delete+0x87/0x130
 [<c0a7f7df>] sysenter_do_call+0x12/0x12
 [<c04c64a7>] ? SyS_timer_delete+0x87/0x130
 [<c04c64a7>] ? SyS_timer_delete+0x87/0x130

Comment 1 customercare 2015-04-08 10:44:28 UTC
confirmed: it is in 3.19.3 too.

Comment 2 Adam Jackson 2015-05-27 15:54:39 UTC
*** Bug 1205099 has been marked as a duplicate of this bug. ***

Comment 3 Adam Jackson 2015-05-27 15:54:43 UTC
*** Bug 1205210 has been marked as a duplicate of this bug. ***

Comment 4 Adam Jackson 2015-05-27 15:54:46 UTC
*** Bug 1205227 has been marked as a duplicate of this bug. ***

Comment 5 Adam Jackson 2015-05-27 15:54:49 UTC
*** Bug 1205571 has been marked as a duplicate of this bug. ***

Comment 6 Adam Jackson 2015-05-27 15:54:53 UTC
*** Bug 1206199 has been marked as a duplicate of this bug. ***

Comment 7 Adam Jackson 2015-05-27 15:54:56 UTC
*** Bug 1207519 has been marked as a duplicate of this bug. ***

Comment 8 Adam Jackson 2015-05-27 15:54:59 UTC
*** Bug 1208190 has been marked as a duplicate of this bug. ***

Comment 9 Adam Jackson 2015-05-27 15:55:03 UTC
*** Bug 1208468 has been marked as a duplicate of this bug. ***

Comment 10 Adam Jackson 2015-05-27 15:55:07 UTC
*** Bug 1208656 has been marked as a duplicate of this bug. ***

Comment 11 Adam Jackson 2015-05-27 15:55:10 UTC
*** Bug 1208868 has been marked as a duplicate of this bug. ***

Comment 12 Adam Jackson 2015-05-27 15:55:13 UTC
*** Bug 1209024 has been marked as a duplicate of this bug. ***

Comment 13 Adam Jackson 2015-05-27 15:55:18 UTC
*** Bug 1210531 has been marked as a duplicate of this bug. ***

Comment 14 Adam Jackson 2015-05-27 15:55:22 UTC
*** Bug 1211032 has been marked as a duplicate of this bug. ***

Comment 15 Adam Jackson 2015-05-27 15:55:26 UTC
*** Bug 1211349 has been marked as a duplicate of this bug. ***

Comment 16 Adam Jackson 2015-05-27 15:55:30 UTC
*** Bug 1211378 has been marked as a duplicate of this bug. ***

Comment 17 Adam Jackson 2015-05-27 15:55:34 UTC
*** Bug 1211633 has been marked as a duplicate of this bug. ***

Comment 18 Adam Jackson 2015-05-27 15:55:39 UTC
*** Bug 1212948 has been marked as a duplicate of this bug. ***

Comment 19 Adam Jackson 2015-05-27 15:55:43 UTC
*** Bug 1214509 has been marked as a duplicate of this bug. ***

Comment 20 Adam Jackson 2015-05-27 15:55:47 UTC
*** Bug 1215424 has been marked as a duplicate of this bug. ***

Comment 21 Adam Jackson 2015-05-27 15:55:52 UTC
*** Bug 1216104 has been marked as a duplicate of this bug. ***

Comment 22 Adam Jackson 2015-05-27 15:55:56 UTC
*** Bug 1224407 has been marked as a duplicate of this bug. ***

Comment 23 mock 2015-08-04 14:32:36 UTC
not sure if this is the same problem, but the error is similar on my dell insprion. i keep finding my laptop display will not come back to life after closing my lid and opening back up. i have my /etc/systemd/logind.conf file set to HandleLidSwitch=lock, and it has worked up until the last few kernel updates.

i have tried kernels 4.1.3-200, 4.1.3-201, and am currently on 4.2.0-0.rc5.git0.2.fc23.x86_64 to attempt to avoid this problem.

here's the snip from my journalctl -k -b -1:

Aug 04 10:11:29 madagascar kernel: ------------[ cut here ]------------
Aug 04 10:11:29 madagascar kernel: WARNING: CPU: 2 PID: 845 at drivers/gpu/drm/drm_irq.c:1162 drm_wait_one_vblank+0x173/0x1c0 [drm]()
Aug 04 10:11:29 madagascar kernel: vblank not available on crtc 0, ret=-22
Aug 04 10:11:29 madagascar kernel: Modules linked in: hidp rfcomm fuse cmac xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun ip6t_rpfilter ip6t_REJECT nf_reject_i
Aug 04 10:11:29 madagascar kernel:  vfat fat crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel uvcvideo i2c_i801 snd_hda_intel snd_hda_codec hid_sensor_ac
Aug 04 10:11:29 madagascar kernel:  int3400_thermal acpi_thermal_rel binfmt_misc uas usb_storage hid_sensor_hub hid_multitouch i915 i2c_algo_bit drm_kms_helper drm ser
Aug 04 10:11:29 madagascar kernel: CPU: 2 PID: 845 Comm: systemd-logind Tainted: G        W       4.2.0-0.rc5.git0.2.fc23.x86_64 #1
Aug 04 10:11:29 madagascar kernel: Hardware name: Dell Inc. Inspiron 7348/067RT2, BIOS A01 11/26/2014
Aug 04 10:11:29 madagascar kernel:  0000000000000000 00000000f72748c3 ffff88024c6df838 ffffffff8176e150
Aug 04 10:11:29 madagascar kernel:  0000000000000000 ffff88024c6df890 ffff88024c6df878 ffffffff8109c786
Aug 04 10:11:29 madagascar kernel:  0000000000000000 ffff88003f9fc000 ffff88003f9fc000 0000000000000000
Aug 04 10:11:29 madagascar kernel: Call Trace:
Aug 04 10:11:29 madagascar kernel:  [<ffffffff8176e150>] dump_stack+0x45/0x57
Aug 04 10:11:29 madagascar kernel:  [<ffffffff8109c786>] warn_slowpath_common+0x86/0xc0
Aug 04 10:11:29 madagascar kernel:  [<ffffffff8109c815>] warn_slowpath_fmt+0x55/0x70
Aug 04 10:11:29 madagascar kernel:  [<ffffffffa0063113>] drm_wait_one_vblank+0x173/0x1c0 [drm]
Aug 04 10:11:29 madagascar kernel:  [<ffffffffa0152c82>] intel_finish_crtc_commit+0x162/0x170 [i915]
Aug 04 10:11:29 madagascar kernel:  [<ffffffffa00d3836>] drm_atomic_helper_commit_planes+0x106/0x200 [drm_kms_helper]
Aug 04 10:11:29 madagascar kernel:  [<ffffffffa0153ebd>] __intel_set_mode+0x8ad/0xb80 [i915]
Aug 04 10:11:29 madagascar kernel:  [<ffffffffa015ae49>] intel_crtc_set_config+0x2c9/0x600 [i915]
Aug 04 10:11:29 madagascar kernel:  [<ffffffffa006c326>] drm_mode_set_config_internal+0x66/0x100 [drm]
Aug 04 10:11:29 madagascar kernel:  [<ffffffffa00d4512>] restore_fbdev_mode+0xc2/0xf0 [drm_kms_helper]
Aug 04 10:11:29 madagascar kernel:  [<ffffffffa00d6399>] drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x70 [drm_kms_helper]
Aug 04 10:11:29 madagascar kernel:  [<ffffffffa016a43e>] intel_fbdev_restore_mode+0x1e/0x50 [i915]
Aug 04 10:11:29 madagascar kernel:  [<ffffffffa01938ee>] i915_driver_lastclose+0xe/0x20 [i915]
Aug 04 10:11:29 madagascar kernel:  [<ffffffffa005f8ee>] drm_lastclose+0x2e/0x140 [drm]
Aug 04 10:11:29 madagascar kernel:  [<ffffffffa005fcaf>] drm_release+0x2af/0x490 [drm]
Aug 04 10:11:29 madagascar kernel:  [<ffffffff8121ad7c>] __fput+0xdc/0x1e0
Aug 04 10:11:29 madagascar kernel:  [<ffffffff8121aece>] ____fput+0xe/0x10
Aug 04 10:11:29 madagascar kernel:  [<ffffffff810b8e1b>] task_work_run+0x9b/0xb0
Aug 04 10:11:29 madagascar kernel:  [<ffffffff8109ee91>] do_exit+0x391/0xae0
Aug 04 10:11:29 madagascar kernel:  [<ffffffff8109f677>] do_group_exit+0x47/0xb0
Aug 04 10:11:29 madagascar kernel:  [<ffffffff810aaa64>] get_signal+0x274/0x600
Aug 04 10:11:29 madagascar kernel:  [<ffffffff811d115a>] ? handle_mm_fault+0xc8a/0x17d0
Aug 04 10:11:29 madagascar kernel:  [<ffffffff81014347>] do_signal+0x37/0x6b0
Aug 04 10:11:29 madagascar kernel:  [<ffffffff8101d959>] ? read_tsc+0x9/0x10
Aug 04 10:11:29 madagascar kernel:  [<ffffffff81109a15>] ? ktime_get_ts64+0x45/0xf0
Aug 04 10:11:29 madagascar kernel:  [<ffffffff8122d14a>] ? poll_select_copy_remaining+0x11a/0x140
Aug 04 10:11:29 madagascar kernel:  [<ffffffff8122ea55>] ? SyS_ppoll+0xf5/0x1b0
Aug 04 10:11:29 madagascar kernel:  [<ffffffff81014a3c>] do_notify_resume+0x7c/0x90
Aug 04 10:11:29 madagascar kernel:  [<ffffffff8177493c>] int_signal+0x12/0x17
Aug 04 10:11:29 madagascar kernel: ---[ end trace e51d5f8fbd2a4cc1 ]---


please let me know if you need more.

Comment 24 Fedora End Of Life 2015-11-04 10:45:30 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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.

Comment 25 Fedora End Of Life 2015-12-02 10:23:31 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.


Note You need to log in before you can comment on or make changes to this bug.