Bug 1042516 - [abrt] WARNING: CPU: 0 PID: 3940 at drivers/gpu/drm/i915/intel_display.c:8255 intel_modeset_check_state+0x653/0x7a0 [i915]() [NEEDINFO]
Summary: [abrt] WARNING: CPU: 0 PID: 3940 at drivers/gpu/drm/i915/intel_display.c:8255...
Keywords:
Status: CLOSED DUPLICATE of bug 1015746
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:5784b396b58152ffcec938b6fac...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 23:21 UTC by David Jaša
Modified: 2014-10-29 16:16 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-13 00:06:20 UTC
Type: ---
felipevsw: needinfo? (extras-qa)


Attachments (Terms of Use)
File: dmesg (113.65 KB, text/plain)
2013-12-12 23:21 UTC, David Jaša
no flags Details

Description David Jaša 2013-12-12 23:21:42 UTC
Description of problem:
the oops report appeared after gdm stop & start between two gnome-shell sessions.

Additional info:
reporter:       libreport-2.1.9
WARNING: CPU: 0 PID: 3940 at drivers/gpu/drm/i915/intel_display.c:8255 intel_modeset_check_state+0x653/0x7a0 [i915]()
encoder's hw state doesn't match sw tracking (expected 1, found 0)
Modules linked in: tun tcp_lp rfcomm fuse nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6t_REJECT xt_conntrack 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 bnep dm_crypt arc4 iwldvm mac80211 uvcvideo snd_hda_codec_hdmi videobuf2_vmalloc videobuf2_memops videobuf2_core snd_hda_codec_conexant videodev media coretemp snd_hda_intel kvm_intel snd_hda_codec kvm snd_hwdep snd_seq crc32_pclmul snd_seq_device crc32c_intel snd_pcm ghash_clmulni_intel snd_page_alloc iTCO_wdt iTCO_vendor_support iwlwifi cfg80211 sdhci_pci sdhci mmc_core shpchp mxm_wmi mei_me intel_ips i2c_i801 e1000e ptp pps_core thinkpad_acpi wmi microcode serio_raw snd_timer btusb bluetooth mei lpc_ich mfd_core snd rfkill tpm_tis soundcore tpm tpm_bios acpi_cpufreq mperf nfsd auth_rpcgss nfs_acl lockd sunrpc i915 firewire_ohci i2c_algo_bit drm_kms_helper firewire_core drm crc_itu_t i2c_core video
CPU: 0 PID: 3940 Comm: Xorg Not tainted 3.11.10-301.fc20.x86_64 #1
Hardware name: LENOVO 4384AT6/4384AT6, BIOS 6MET61WW (1.24 ) 06/07/2010
 0000000000000009 ffff880225f15c48 ffffffff816441db ffff880225f15c90
 ffff880225f15c80 ffffffff8106715d 0000000000000001 ffff880225f15d0c
 ffff88022ce29460 ffff88022d4d1000 ffff88022ce29000 ffff880225f15ce0
Call Trace:
 [<ffffffff816441db>] dump_stack+0x45/0x56
 [<ffffffff8106715d>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff810671cc>] warn_slowpath_fmt+0x4c/0x50
 [<ffffffffa00d0303>] intel_modeset_check_state+0x653/0x7a0 [i915]
 [<ffffffffa00d048e>] intel_connector_dpms+0x3e/0x50 [i915]
 [<ffffffffa0036f68>] drm_mode_obj_set_property_ioctl+0x308/0x320 [drm]
 [<ffffffffa0036fb0>] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
 [<ffffffffa0026122>] drm_ioctl+0x512/0x640 [drm]
 [<ffffffff811bac7d>] do_vfs_ioctl+0x2dd/0x4b0
 [<ffffffff811baed1>] SyS_ioctl+0x81/0xa0
 [<ffffffff816533d9>] system_call_fastpath+0x16/0x1b

Comment 1 David Jaša 2013-12-12 23:21:49 UTC
Created attachment 836075 [details]
File: dmesg

Comment 2 Josh Boyer 2013-12-13 00:06:20 UTC

*** This bug has been marked as a duplicate of bug 1015746 ***

Comment 3 Felipe van Schaik Willig 2014-10-29 16:16:22 UTC
This one was closed as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1015746, and that one was closed because F18 isn't supported anymore.
Fair enough, however, this is still happening on Fedora 20, so shouldn't this one be reopened?


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