Bug 1400834

Summary: [abrt] WARNING: CPU: 0 PID: 1476 at drivers/gpu/drm/i915/intel_runtime_pm.c:633 skl_enable_dc6+0xab/0xd0 [i915]
Product: [Fedora] Fedora Reporter: dizzy <rkrist>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: ajax, gtwilliams, hancockrwd, jean-baptiste, kernel-maint, whr778, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/07265a31149a58d4629511030343df4b0756cb93
Whiteboard: abrt_hash:4a09df8a1a7156624b4ad3a640d8f56a7c29143a;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:03:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dmesg none

Description dizzy 2016-12-02 08:02:39 UTC
Additional info:
reporter:       libreport-2.8.0
WARNING: CPU: 0 PID: 1476 at drivers/gpu/drm/i915/intel_runtime_pm.c:633 skl_enable_dc6+0xab/0xd0 [i915]
DC6 already programmed to be enabled.
Modules linked in: nls_utf8 isofs bnep fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge ip6table_mangle ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_raw ip6table_security iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables vfat fat intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp kvm_intel mei_wdt iTCO_wdt snd_hda_codec_realtek iTCO_vendor_support sparse_keymap snd_hda_codec_generic ppdev kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel
 intel_cstate snd_hda_codec intel_uncore snd_hda_core intel_rapl_perf snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd mei_me i2c_i801 soundcore i2c_smbus mei hci_uart shpchp wmi btbcm btqca btintel bluetooth parport_pc parport pinctrl_sunrisepoint acpi_pad pinctrl_intel intel_lpss_acpi acpi_als rfkill tpm_tis intel_lpss tpm_tis_core kfifo_buf industrialio tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc btrfs uas usb_storage 8021q garp stp llc mrp xor i915 raid6_pq i2c_algo_bit e1000e drm_kms_helper crc32c_intel ptp drm serio_raw pps_core video i2c_hid fjes
CPU: 0 PID: 1476 Comm: gnome-shell Not tainted 4.8.6-300.fc25.x86_64 #1
Hardware name: Acer Veriton M6640G/Veriton M6640G, BIOS R01-B1 08/05/2016
 0000000000000286 0000000042648fbb ffff8a5c1888ba20 ffffffff8a3e5ebd
 ffff8a5c1888ba70 0000000000000000 ffff8a5c1888ba60 ffffffff8a0a0e8b
 0000027900400000 ffff8a5c15020000 ffff8a5c15020000 ffff8a5c15020000
Call Trace:
 [<ffffffff8a3e5ebd>] dump_stack+0x63/0x86
 [<ffffffff8a0a0e8b>] __warn+0xcb/0xf0
 [<ffffffff8a0a0f0f>] warn_slowpath_fmt+0x5f/0x80
 [<ffffffffc0502e1b>] skl_enable_dc6+0xab/0xd0 [i915]
 [<ffffffffc0502e71>] gen9_dc_off_power_well_disable+0x31/0x40 [i915]
 [<ffffffffc050072c>] intel_power_well_disable+0x2c/0x50 [i915]
 [<ffffffffc050077e>] intel_power_well_put+0x2e/0x60 [i915]
 [<ffffffffc0503b19>] intel_display_power_put+0xa9/0x100 [i915]
 [<ffffffffc0565493>] intel_atomic_commit_tail+0x743/0x1050 [i915]
 [<ffffffffc056d826>] ? intel_prepare_plane_fb+0x106/0x2b0 [i915]
 [<ffffffffc05661de>] intel_atomic_commit+0x43e/0x550 [i915]
 [<ffffffffc03e50d7>] ? drm_atomic_check_only+0x187/0x610 [drm]
 [<ffffffffc044ce09>] ? __drm_atomic_helper_crtc_duplicate_state+0x89/0xa0 [drm_kms_helper]
 [<ffffffffc03e5597>] drm_atomic_commit+0x37/0x60 [drm]
 [<ffffffffc044dded>] drm_atomic_helper_connector_dpms+0xed/0x1a0 [drm_kms_helper]
 [<ffffffffc03d99d6>] drm_mode_obj_set_property_ioctl+0x236/0x250 [drm]
 [<ffffffffc03cafa0>] drm_ioctl+0x200/0x4f0 [drm]
 [<ffffffffc03d97a0>] ? drm_mode_obj_get_properties_ioctl+0xb0/0xb0 [drm]
 [<ffffffff8a29e69c>] ? eventfd_read+0x5c/0x90
 [<ffffffff8a264dd3>] do_vfs_ioctl+0xa3/0x5f0
 [<ffffffff8a265399>] SyS_ioctl+0x79/0x90
 [<ffffffff8a802572>] entry_SYSCALL_64_fastpath+0x1a/0xa4

Comment 1 dizzy 2016-12-02 08:02:48 UTC
Created attachment 1227190 [details]
File: dmesg

Comment 2 Fedora End Of Life 2017-11-16 15:32:33 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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-12-12 10:03:57 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.