Bug 958295 - [abrt] WARNING: at drivers/gpu/drm/i915/intel_display.c:3854 intel_modeset_check_state+0x5f9/0x600 [i915]()
Summary: [abrt] WARNING: at drivers/gpu/drm/i915/intel_display.c:3854 intel_modeset_ch...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6af85cc9524994de83eba1c4ed8...
: 978428 981700 981924 984093 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-30 20:38 UTC by Lukáš Zachar
Modified: 2015-02-17 15:07 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 15:07:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (90.70 KB, text/plain)
2013-04-30 20:38 UTC, Lukáš Zachar
no flags Details

Description Lukáš Zachar 2013-04-30 20:38:28 UTC
Description of problem:
I have external monitor connected to VGA port. 
This warning happens each time the screen is resumed after the standby. 
E.g.: 
1. wait until the screensaver timeouts and screen is switched to standby
2. move the mouse 

IIRC similar problem happens on F18 too (same HW configuration).
If there are any logs/strace/whatever I should attach just let me know.

Additional info:
WARNING: at drivers/gpu/drm/i915/intel_display.c:3854 intel_modeset_check_state+0x5f9/0x600 [i915]()
Hardware name: Inspiron 1525                   
wrong connector dpms state
Modules linked in: dm_crypt tcp_lp fuse ebtable_nat nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6table_nat nf_nat_ipv6 ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack bnep ebtable_filter bluetooth ebtables ip6table_filter ip6_tables iTCO_wdt arc4 iwl3945 iwlegacy snd_hda_codec_idt dell_laptop uvcvideo dell_wmi snd_hda_codec_hdmi iTCO_vendor_support acpi_cpufreq videobuf2_vmalloc videobuf2_memops videobuf2_core videodev snd_hda_intel mperf mac80211 sparse_keymap cfg80211 coretemp snd_hda_codec snd_hwdep dcdbas media joydev rfkill snd_seq snd_seq_device sdhci_pci snd_pcm sdhci mmc_core serio_raw snd_page_alloc snd_timer snd soundcore microcode i2c_i801 r592 sky2 lpc_ich memstick mfd_core vhost_net tun macvtap macvlan kvm_intel kvm xfs libcrc32c i915 firewire_ohci firewire_core crc_itu_t i2c_algo_bit drm_kms_helper drm i2c_core wmi video uinput
Pid: 411, comm: Xorg Not tainted 3.9.0-0.rc8.git0.2.fc19.x86_64 #1
Call Trace:
 [<ffffffffa00d5d00>] ? intel_modeset_check_state+0x540/0x600 [i915]
 [<ffffffff8105cd86>] warn_slowpath_common+0x66/0x80
 [<ffffffff8105cdec>] warn_slowpath_fmt+0x4c/0x50
 [<ffffffffa00d5db9>] intel_modeset_check_state+0x5f9/0x600 [i915]
 [<ffffffffa00d5e00>] intel_connector_dpms+0x40/0x70 [i915]
 [<ffffffffa003a498>] drm_mode_obj_set_property_ioctl+0x308/0x320 [drm]
 [<ffffffffa003a4e0>] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
 [<ffffffffa00292c9>] drm_ioctl+0x4e9/0x5b0 [drm]
 [<ffffffffa003a4b0>] ? drm_mode_obj_set_property_ioctl+0x320/0x320 [drm]
 [<ffffffff8113783a>] ? __free_pages+0x4a/0x80
 [<ffffffff811aad15>] do_vfs_ioctl+0x305/0x520
 [<ffffffff81293ffe>] ? file_has_perm+0x8e/0xa0
 [<ffffffff8119acbe>] ? ____fput+0xe/0x10
 [<ffffffff811aafb1>] sys_ioctl+0x81/0xa0
 [<ffffffff8164d759>] system_call_fastpath+0x16/0x1b

Comment 1 Lukáš Zachar 2013-04-30 20:38:33 UTC
Created attachment 741990 [details]
File: dmesg

Comment 2 Adam Jackson 2014-05-21 17:34:15 UTC
*** Bug 981924 has been marked as a duplicate of this bug. ***

Comment 3 Adam Jackson 2014-05-21 17:34:19 UTC
*** Bug 981700 has been marked as a duplicate of this bug. ***

Comment 4 Adam Jackson 2014-05-21 17:34:23 UTC
*** Bug 978428 has been marked as a duplicate of this bug. ***

Comment 5 Adam Jackson 2014-11-18 19:06:22 UTC
*** Bug 984093 has been marked as a duplicate of this bug. ***

Comment 6 Adam Jackson 2014-11-18 19:35:39 UTC
If you're still seeing this against F20 or later, please file a new report.

Comment 7 Adam Jackson 2014-11-18 19:38:53 UTC
Filed against old F19 kernel, closing.  If you're still experiencing this with a current f19-updates kernel, please reopen.

Comment 8 Fedora End Of Life 2015-01-09 18:00:49 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 9 Fedora End Of Life 2015-02-17 15:07:16 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.