Description of problem: ABRT messages came up after overnight suspend/resume on f18 install with rawhide nodebug kernel Version-Release number of selected component (if applicable): kernel-3.8.0-0.rc6.git0.2.fc19.x86_64 How reproducible: Came up once. [but 9 stack traces for this one occurence] Additional info: /var/log/messages has: {{{ Feb 3 01:15:40 asterix NetworkManager[557]: <info> (wlan0) supports 5 scan SSIDs Feb 3 08:58:15 asterix kernel: [39110.057820] [<ffffffff8107f7e0>] ? kthread_stop+0xf0/0xf0 Feb 3 08:58:15 asterix kernel: [39110.057828] [<ffffffff8163e62c>] ret_from_fork+0x7c/0xb0 Feb 3 08:58:15 asterix kernel: [39110.057837] [<ffffffff8107f7e0>] ? kthread_stop+0xf0/0xf0 Feb 3 08:58:15 asterix kernel: [39110.057841] ---[ end trace 07d396baddbbd2c3 ]--- Feb 3 08:58:15 asterix kernel: [39110.057844] ACPI: Preparing to enter system sleep state S3 Feb 3 08:58:15 asterix kernel: [39110.057848] ------------[ cut here ]------------ Feb 3 08:58:15 asterix kernel: [39110.057876] WARNING: at drivers/gpu/drm/i915/intel_display.c:7864 intel_modeset_check_state+0x4ba/0x600 [i915]() Feb 3 08:58:15 asterix kernel: [39110.057878] Hardware name: 417152U Feb 3 08:58:15 asterix kernel: [39110.057879] encoder's hw state doesn't match sw tracking (expected 0, found 1) Feb 3 08:58:15 asterix kernel: [39110.057936] Modules linked in: fuse ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat xt_CHECKSUM iptable_mangle bridge stp llc ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 be2iscsi iscsi_boot_sysfs nf_conntrack_ipv4 bnx2i cnic uio nf_defrag_ipv4 cxgb4i ip6table_filter xt_conntrack ip6_tables nf_conntrack cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_intel snd_hda_codec snd_hwdep arc4 iwldvm mac80211 snd_seq snd_seq_device snd_pcm snd_page_alloc iwlwifi cfg80211 thinkpad_acpi snd_timer snd tpm_tis e1000e iTCO_wdt iTCO_vendor_support mei lpc_ich soundcore coretemp i2c_i801 microcode mfd_core rfkill tpm tpm_bios vhost_net tun macvtap macvlan kvm_intel kvm nfsd auth_rpcgss nfs_acl lockd uinput sunrpc binfmt_misc i915 crc32c_intel ghash_clmulni_intel i2c_algo_bit drm_kms_helper sdhci_pci drm sdhci mmc_core i2c_core wmi video Feb 3 08:58:15 asterix kernel: [39110.057967] Pid: 11779, comm: kworker/0:2 Tainted: G W 3.8.0-0.rc6.git0.2.fc19.x86_64 #1 Feb 3 08:58:15 asterix kernel: [39110.057967] Call Trace: Feb 3 08:58:15 asterix kernel: [39110.057992] [<ffffffffa0109a00>] ? intel_modeset_check_state+0x400/0x600 [i915] Feb 3 08:58:15 asterix kernel: [39110.057999] [<ffffffff8105c1f0>] warn_slowpath_common+0x70/0xa0 Feb 3 08:58:15 asterix kernel: [39110.058004] [<ffffffff8105c26c>] warn_slowpath_fmt+0x4c/0x50 Feb 3 08:58:15 asterix kernel: [39110.058035] [<ffffffffa0113328>] ? intel_dp_get_hw_state+0x178/0x1b0 [i915] Feb 3 08:58:15 asterix kernel: [39110.058060] [<ffffffffa0109aba>] intel_modeset_check_state+0x4ba/0x600 [i915] Feb 3 08:58:15 asterix kernel: [39110.058084] [<ffffffffa010a36f>] intel_set_mode+0x6ff/0x940 [i915] Feb 3 08:58:15 asterix kernel: [39110.058109] [<ffffffff8117e4e6>] ? kmem_cache_free+0x46/0x1f0 Feb 3 08:58:15 asterix kernel: [39110.058138] [<ffffffffa010cd09>] intel_modeset_setup_hw_state+0x5b9/0x9a0 [i915] Feb 3 08:58:15 asterix kernel: [39110.058166] [<ffffffffa010eb51>] intel_lid_notify+0xa1/0xc0 [i915] Feb 3 08:58:15 asterix kernel: [39110.058170] [<ffffffff8163a2bc>] notifier_call_chain+0x4c/0x70 Feb 3 08:58:15 asterix kernel: [39110.058174] [<ffffffff81085cad>] __blocking_notifier_call_chain+0x4d/0x70 Feb 3 08:58:15 asterix kernel: [39110.058179] [<ffffffff81085ce6>] blocking_notifier_call_chain+0x16/0x20 Feb 3 08:58:15 asterix kernel: [39110.058182] [<ffffffff81373927>] acpi_lid_send_state+0x7f/0xad Feb 3 08:58:15 asterix kernel: [39110.058186] [<ffffffff81373da7>] acpi_button_notify+0x3d/0xaa Feb 3 08:58:15 asterix kernel: [39110.058192] [<ffffffff8134efb9>] acpi_device_notify+0x19/0x1b Feb 3 08:58:15 asterix kernel: [39110.058196] [<ffffffff8135c960>] acpi_ev_notify_dispatch+0x44/0x5c Feb 3 08:58:15 asterix kernel: [39110.058200] [<ffffffff8134b7bc>] acpi_os_execute_deferred+0x25/0x32 Feb 3 08:58:15 asterix kernel: [39110.058206] [<ffffffff81078b15>] process_one_work+0x1a5/0x520 Feb 3 08:58:15 asterix kernel: [39110.058211] [<ffffffff8134b797>] ? acpi_os_wait_events_complete+0x23/0x23 Feb 3 08:58:15 asterix kernel: [39110.058217] [<ffffffff8107a927>] worker_thread+0x1b7/0x570 Feb 3 08:58:15 asterix kernel: [39110.058223] [<ffffffff8107a770>] ? manage_workers+0x300/0x300 Feb 3 08:58:15 asterix kernel: [39110.058228] [<ffffffff8107f8a0>] kthread+0xc0/0xd0 Feb 3 08:58:15 asterix kernel: [39110.058232] [<ffffffff8107f7e0>] ? kthread_stop+0xf0/0xf0 Feb 3 08:58:15 asterix kernel: [39110.058237] [<ffffffff8163e62c>] ret_from_fork+0x7c/0xb0 Feb 3 08:58:15 asterix kernel: [39110.058242] [<ffffffff8107f7e0>] ? kthread_stop+0xf0/0xf0 Feb 3 08:58:15 asterix kernel: [39110.058232] [<ffffffff8107f7e0>] ? kthread_stop+0xf0/0xf0 Feb 3 08:58:15 asterix kernel: [39110.058237] [<ffffffff8163e62c>] ret_from_fork+0x7c/0xb0 Feb 3 08:58:15 asterix kernel: [39110.058242] [<ffffffff8107f7e0>] ? kthread_stop+0xf0/0xf0 Feb 3 08:58:15 asterix kernel: [39110.058244] ---[ end trace 07d396baddbbd2c4 ]--- Feb 3 08:58:15 asterix kernel: [39110.058248] ------------[ cut here ]------------ }}} <<< listed 9 times >>> I haven't seen this message [with intel_dp_get_hw_state in the stacktrace] before - or in other bugzilla entries with intel_modeset_check_state Previous kernels booted [which didn't show this issue] [root@asterix ~]# last reboot reboot system boot 3.8.0-0.rc6.git0 Fri Feb 1 18:28 - 10:42 (1+16:14) reboot system boot 3.8.0-0.rc5.git3 Fri Feb 1 09:23 - 17:59 (08:35) reboot system boot 3.8.0-0.rc5.git1 Wed Jan 30 17:14 - 09:23 (1+16:08) reboot system boot 3.8.0-0.rc5.git0 Wed Jan 30 16:11 - 17:13 (01:02) Perhaps the hardware misbehaved when it was resuming for overnight sleep.
Note: the message says 'Tainted: G W' - but there is no other trace in the log so perhaps it was caused by the following? {{{ Feb 3 08:58:15 asterix kernel: [39110.057820] [<ffffffff8107f7e0>] ? kthread_stop+0xf0/0xf0 Feb 3 08:58:15 asterix kernel: [39110.057828] [<ffffffff8163e62c>] ret_from_fork+0x7c/0xb0 Feb 3 08:58:15 asterix kernel: [39110.057837] [<ffffffff8107f7e0>] ? kthread_stop+0xf0/0xf0 Feb 3 08:58:15 asterix kernel: [39110.057841] ---[ end trace 07d396baddbbd2c3 ]--- }}}
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
*** Bug 988041 has been marked as a duplicate of this bug. ***
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.
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.