Bug 1302619 - [abrt] WARNING: CPU: 0 PID: 4 at drivers/gpu/drm/i915/intel_dp_mst.c:513 intel_dp_destroy_mst_connector+0x100/0x110 [i915]() [drm_kms_helper]
Summary: [abrt] WARNING: CPU: 0 PID: 4 at drivers/gpu/drm/i915/intel_dp_mst.c:513 inte...
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:f6ec9953e98fa6f3d2e4db070c2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-28 09:51 UTC by Petr Schindler
Modified: 2017-08-08 12:42 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-08-08 12:42:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (71.09 KB, text/plain)
2016-01-28 09:51 UTC, Petr Schindler
no flags Details

Description Petr Schindler 2016-01-28 09:51:07 UTC
Description of problem:
I haven't seen anything to happen. Only after this oops occured gnome-shell stopped spamming with:
led 28 10:09:08 dhcp-2-247.brq.redhat.com org.gnome.Shell.desktop[3768]: (gnome-shell:3768): Gdk-WARNING **: gdk-frame-clock: layout continuously requested, giving up after 4 tries
messages. (bug https://bugzilla.gnome.org/show_bug.cgi?id=758893)

Additional info:
reporter:       libreport-2.6.3
WARNING: CPU: 0 PID: 4 at drivers/gpu/drm/i915/intel_dp_mst.c:513 intel_dp_destroy_mst_connector+0x100/0x110 [i915]()
Disabling mst crtc failed with -22
Modules linked in: vfat fat xt_CHECKSUM tun ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_addrtype nf_conntrack_netbios_ns nf_conntrack_broadcast br_netfilter ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 dm_thin_pool dm_persistent_data dm_bio_prison libcrc32c loop xt_conntrack ebtable_broute bridge stp llc ebtable_nat ebtable_filter ebtables ip6table_security ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_filter ip6_tables iptable_security iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle bnep arc4 fuse intel_rapl iTCO_wdt iTCO_vendor_support x86_pkg_temp_thermal coretemp iwlmvm snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi kvm_intel uvcvideo snd_hda_intel videobuf2_vmalloc mac80211
 videobuf2_memops videobuf2_v4l2 kvm snd_hda_codec videobuf2_core snd_hda_core btusb irqbypass snd_hwdep joydev videodev btrtl iwlwifi btbcm snd_seq btintel snd_seq_device bluetooth media snd_pcm rtsx_pci_ms cfg80211 memstick thinkpad_acpi snd_timer snd rfkill mei_me mei ie31200_edac soundcore shpchp i2c_i801 edac_core lpc_ich tpm_tis tpm wmi nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt uas usb_storage i915 rtsx_pci_sdmmc mmc_core i2c_algo_bit drm_kms_helper crct10dif_pclmul e1000e crc32_pclmul crc32c_intel drm ghash_clmulni_intel serio_raw rtsx_pci ptp pps_core fjes video
CPU: 0 PID: 4 Comm: kworker/0:0 Not tainted 4.5.0-0.rc1.git0.1.fc24.x86_64 #1
Hardware name: LENOVO 20BFS0W505/20BFS0W505, BIOS GMET31WW (1.11 ) 10/16/2013
Workqueue: events drm_dp_destroy_connector_work [drm_kms_helper]
 0000000000000000 00000000fa21a6d6 ffff88040c28bcd8 ffffffff813cb16f
 ffff88040c28bd20 ffff88040c28bd10 ffffffff810a3ad2 ffff8804068a7000
 ffff88040bfc3800 ffff880406834a70 ffff8804068a6820 ffff880406834658
Call Trace:
 [<ffffffff813cb16f>] dump_stack+0x44/0x55
 [<ffffffff810a3ad2>] warn_slowpath_common+0x82/0xc0
 [<ffffffff810a3b6c>] warn_slowpath_fmt+0x5c/0x80
 [<ffffffffa0161712>] ? drm_atomic_helper_set_config+0x92/0xb0 [drm_kms_helper]
 [<ffffffffa008e69e>] ? drm_atomic_state_free+0x4e/0x70 [drm]
 [<ffffffffa0212490>] intel_dp_destroy_mst_connector+0x100/0x110 [i915]
 [<ffffffffa015b19f>] drm_dp_destroy_connector_work+0x6f/0xe0 [drm_kms_helper]
 [<ffffffff810bbf21>] process_one_work+0x1a1/0x3f0
 [<ffffffff810bc1be>] worker_thread+0x4e/0x480
 [<ffffffff810bc170>] ? process_one_work+0x3f0/0x3f0
 [<ffffffff810c1fc8>] kthread+0xd8/0xf0
 [<ffffffff810c1ef0>] ? kthread_worker_fn+0x170/0x170
 [<ffffffff817bd6ff>] ret_from_fork+0x3f/0x70
 [<ffffffff810c1ef0>] ? kthread_worker_fn+0x170/0x170

Comment 1 Petr Schindler 2016-01-28 09:51:15 UTC
Created attachment 1119080 [details]
File: dmesg

Comment 2 Jan Kurik 2016-02-24 14:21:20 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase

Comment 3 Fedora End Of Life 2017-07-25 19:51:23 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 4 Fedora End Of Life 2017-08-08 12:42:42 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.