Bug 1392184 - [abrt] WARNING: CPU: 3 PID: 118 at drivers/gpu/drm/i915/intel_display.c:13647 intel_atomic_commit_tail+0x1152/0x1160 [i915]
Summary: [abrt] WARNING: CPU: 3 PID: 118 at drivers/gpu/drm/i915/intel_display.c:13647...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 24
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:3529d8ba91ea43478754f06c62a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-05 18:30 UTC by Sam Varshavchik
Modified: 2017-08-08 19:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 19:09:04 UTC
Type: ---


Attachments (Terms of Use)
File: dmesg (76.66 KB, text/plain)
2016-11-05 18:31 UTC, Sam Varshavchik
no flags Details

Description Sam Varshavchik 2016-11-05 18:30:56 UTC
Additional info:
reporter:       libreport-2.7.2
WARNING: CPU: 3 PID: 118 at drivers/gpu/drm/i915/intel_display.c:13647 intel_atomic_commit_tail+0x1152/0x1160 [i915]
pipe A vblank wait timed out
Modules linked in: ccm ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_raw ip6table_mangle ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_security iptable_raw iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_security ebtable_filter ebtables ip6table_filter ip6_tables snd_hda_codec_via snd_hda_codec_generic snd_hda_codec_hdmi intel_rapl snd_soc_rt5640 x86_pkg_temp_thermal snd_hda_intel snd_soc_rl6231 intel_powerclamp snd_soc_core coretemp snd_hda_codec snd_compress snd_pcm_dmaengine kvm_intel ac97_bus uvcvideo snd_hda_core videobuf2_vmalloc arc4 kvm videobuf2_memops snd_hwdep snd_seq snd_seq_device snd_pcm videobuf2_v4l2 irqbypass ath9k ath9k_common
 ath9k_hw intel_cstate intel_uncore snd_timer videobuf2_core videodev media mac80211 intel_rapl_perf ath snd cfg80211 soundcore iTCO_wdt iTCO_vendor_support rfkill joydev snd_soc_sst_acpi snd_soc_sst_match rtsx_pci_ms wmi memstick elan_i2c spi_pxa2xx_platform i2c_designware_platform i2c_designware_core shpchp lpc_ich mei_me mei ie31200_edac dw_dmac dw_dmac_core edac_core i2c_i801 i2c_smbus tpm_crb tpm_tis tpm_tis_core tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt i915 crct10dif_pclmul crc32_pclmul crc32c_intel rtsx_pci_sdmmc i2c_algo_bit ghash_clmulni_intel drm_kms_helper drm serio_raw r8169 rtsx_pci mii sdhci_acpi sdhci video mmc_core i2c_hid fjes
CPU: 3 PID: 118 Comm: kworker/u8:2 Not tainted 4.8.4-200.fc24.x86_64 #1
Hardware name: Think Penguin Snares Penguin-SB/Snares Penguin-SB, BIOS 1.05SB.02TPG 08/26/2015
Workqueue: events_unbound async_run_entry_fn
 0000000000000286 000000002954b326 ffff9910498bfa30 ffffffffab3e5d0d
 ffff9910498bfa80 0000000000000000 ffff9910498bfa70 ffffffffab0a0e4b
 0000354f2954b326 ffff9910484c0000 0000000000000000 0000000000000000
Call Trace:
 [<ffffffffab3e5d0d>] dump_stack+0x63/0x86
 [<ffffffffab0a0e4b>] __warn+0xcb/0xf0
 [<ffffffffab0a0ecf>] warn_slowpath_fmt+0x5f/0x80
 [<ffffffffab0e4a93>] ? finish_wait+0x53/0x70
 [<ffffffffc024eb82>] intel_atomic_commit_tail+0x1152/0x1160 [i915]
 [<ffffffffab0e4cf0>] ? prepare_to_wait_event+0xf0/0xf0
 [<ffffffffc024efce>] intel_atomic_commit+0x43e/0x550 [i915]
 [<ffffffffc01390d7>] ? drm_atomic_check_only+0x187/0x610 [drm]
 [<ffffffffc01eca98>] ? intel_runtime_pm_put+0x68/0xb0 [i915]
 [<ffffffffc0139597>] drm_atomic_commit+0x37/0x60 [drm]
 [<ffffffffc02588d0>] __intel_display_resume+0x70/0xb0 [i915]
 [<ffffffffc0258b68>] intel_display_resume+0xd8/0x110 [i915]
 [<ffffffffc01cc5e1>] i915_drm_resume+0xe1/0x170 [i915]
 [<ffffffffc01cc68e>] i915_pm_restore+0x1e/0x30 [i915]
 [<ffffffffc01cc6be>] i915_pm_resume+0xe/0x10 [i915]
 [<ffffffffab439c34>] pci_pm_resume+0x64/0xa0
 [<ffffffffab439bd0>] ? pci_pm_thaw+0x90/0x90
 [<ffffffffab53b2ed>] dpm_run_callback+0x4d/0x120
 [<ffffffffab53b846>] device_resume+0xa6/0x200
 [<ffffffffab53b9bd>] async_resume+0x1d/0x50
 [<ffffffffab0c35b9>] async_run_entry_fn+0x39/0x140
 [<ffffffffab0baa34>] process_one_work+0x184/0x430
 [<ffffffffab0bad2e>] worker_thread+0x4e/0x480
 [<ffffffffab0bace0>] ? process_one_work+0x430/0x430
 [<ffffffffab0c0bc8>] kthread+0xd8/0xf0
 [<ffffffffab80277f>] ret_from_fork+0x1f/0x40
 [<ffffffffab0c0af0>] ? kthread_worker_fn+0x180/0x180

Potential duplicate: bug 1385194

Comment 1 Sam Varshavchik 2016-11-05 18:31:05 UTC
Created attachment 1217609 [details]
File: dmesg

Comment 2 Fedora End Of Life 2017-07-25 23:46:52 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 3 Fedora End Of Life 2017-08-08 19:09:04 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.