Bug 1082007 - [abrt] WARNING: CPU: 0 PID: 732 at drivers/gpu/drm/i915/intel_display.c:3915 intel_modeset_check_state+0x754/0x760 [i915]()
Summary: [abrt] WARNING: CPU: 0 PID: 732 at drivers/gpu/drm/i915/intel_display.c:3915 ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 20
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:bf4b16938a3d210836930adf33e...
: 1079683 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-28 13:09 UTC by Nelson Jesus
Modified: 2015-06-29 19:45 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 19:45:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (133.65 KB, text/plain)
2014-03-28 13:09 UTC, Nelson Jesus
no flags Details

Description Nelson Jesus 2014-03-28 13:09:01 UTC
Description of problem:
I install Fedora 20, and this warning appeared on the screen. Thanks

Additional info:
reporter:       libreport-2.1.9
WARNING: CPU: 0 PID: 732 at drivers/gpu/drm/i915/intel_display.c:3915 intel_modeset_check_state+0x754/0x760 [i915]()
wrong connector dpms state
Modules linked in: nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6t_REJECT xt_conntrack bnep bluetooth ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw arc4 b43 bcma mac80211 cfg80211 sky2 sdhci_pci iTCO_wdt sdhci ssb mmc_core iTCO_vendor_support uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev lpc_ich media mfd_core dell_wmi sparse_keymap coretemp r592 memstick dell_laptop rfkill dcdbas snd_hda_codec_idt snd_hda_codec_hdmi joydev snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm microcode serio_raw i2c_i801 acpi_cpufreq mperf snd_page_alloc snd_timer snd soundcore wmi nfsd auth_rpcgss nfs_acl lockd sunrpc i915 i2c_algo_bit drm_kms_helper ata_generic firewire_ohci pata_acpi firewire_core drm crc_itu_t i2c_core video
CPU: 0 PID: 732 Comm: Xorg Not tainted 3.11.10-301.fc20.i686+PAE #1
Hardware name: Dell Inc. Inspiron 1525                   /0U990C, BIOS A17 10/27/2009
 00000000 00000000 f0365b18 c0992d0d f0365b58 f0365b48 c04549de f81ae0ca
 f0365b74 000002dc f81a5818 00000f4b f816a474 f816a474 f460c000 f6ebfc00
 f6ebe6bc f0365b60 c0454a33 00000009 f0365b58 f81ae0ca f0365b74 f0365bb0
Call Trace:
 [<c0992d0d>] dump_stack+0x41/0x52
 [<c04549de>] warn_slowpath_common+0x7e/0xa0
 [<f816a474>] ? intel_modeset_check_state+0x754/0x760 [i915]
 [<f816a474>] ? intel_modeset_check_state+0x754/0x760 [i915]
 [<c0454a33>] warn_slowpath_fmt+0x33/0x40
 [<f816a474>] intel_modeset_check_state+0x754/0x760 [i915]
 [<f816a4f0>] intel_set_mode+0x30/0x40 [i915]
 [<f816b600>] intel_get_load_detect_pipe+0x230/0x3a0 [i915]
 [<f818ac07>] intel_tv_detect+0xe7/0x4a0 [i915]
 [<f7e581f5>] ? __i2c_transfer+0x55/0x70 [i2c_core]
 [<f7f13428>] drm_helper_probe_single_connector_modes+0x1b8/0x340 [drm_kms_helper]
 [<f7f56df5>] drm_mode_getconnector+0x305/0x350 [drm]
 [<f7f56af0>] ? drm_mode_getcrtc+0xc0/0xc0 [drm]
 [<f7f49caa>] drm_ioctl+0x47a/0x520 [drm]
 [<c05064a7>] ? perf_cgroup_switch+0x67/0x160
 [<f7f56af0>] ? drm_mode_getcrtc+0xc0/0xc0 [drm]
 [<c04192fe>] ? __restore_xstate_sig+0x36e/0x4f0
 [<f7f49830>] ? drm_copy_field+0x70/0x70 [drm]
 [<c056f7f6>] do_vfs_ioctl+0x2e6/0x4d0
 [<c06374fa>] ? inode_has_perm.isra.32.constprop.61+0x3a/0x50
 [<c0637637>] ? file_has_perm+0x87/0x90
 [<c06379fc>] ? selinux_file_ioctl+0x4c/0xf0
 [<c056fa40>] SyS_ioctl+0x60/0x80
 [<c04c64a7>] ? __audit_syscall_exit+0x177/0x260
 [<c04c64a7>] ? __audit_syscall_exit+0x177/0x260
 [<c099ff0d>] sysenter_do_call+0x12/0x28
 [<c04c64a7>] ? __audit_syscall_exit+0x177/0x260
 [<c04c64a7>] ? __audit_syscall_exit+0x177/0x260

Comment 1 Nelson Jesus 2014-03-28 13:09:08 UTC
Created attachment 879822 [details]
File: dmesg

Comment 2 Adam Jackson 2014-05-21 17:36:54 UTC
*** Bug 1079683 has been marked as a duplicate of this bug. ***

Comment 3 Fedora End Of Life 2015-05-29 11:23:33 UTC
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.

Comment 4 Fedora End Of Life 2015-06-29 19:45:08 UTC
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.


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