Description of problem: Resume from suspend. Additional info: WARNING: at drivers/pnp/pnpacpi/core.c:98 pnpacpi_set_resources+0x131/0x140() Hardware name: 766636G Modules linked in: ipt_MASQUERADE nf_conntrack_netbios_ns nf_conntrack_broadcast ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables rfcomm bnep snd_hda_codec_analog iTCO_wdt iTCO_vendor_support arc4 ppdev coretemp kvm_intel kvm microcode i2c_i801 iwl4965 iwlegacy snd_hda_intel snd_hda_codec lpc_ich mfd_core snd_hwdep mac80211 snd_seq snd_seq_device snd_pcm cfg80211 snd_page_alloc snd_timer btusb bluetooth e1000e thinkpad_acpi snd soundcore rfkill parport_pc parport uinput xts gf128mul dm_crypt firewire_ohci sdhci_pci sdhci yenta_socket mmc_core firewire_core crc_itu_t i915 i2c_algo_bit drm_kms_helper drm i2c_core video Pid: 5400, comm: systemd-sleep Not tainted 3.6.11-3.fc18.x86_64 #1 Call Trace: [<ffffffff8105c8df>] warn_slowpath_common+0x7f/0xc0 [<ffffffff8105c93a>] warn_slowpath_null+0x1a/0x20 [<ffffffff81373831>] pnpacpi_set_resources+0x131/0x140 [<ffffffff8136f8d0>] ? pnp_device_shutdown+0x30/0x30 [<ffffffff81371126>] pnp_start_dev+0x46/0x80 [<ffffffff8136f948>] pnp_bus_resume+0x78/0x80 [<ffffffff813ce718>] dpm_run_callback+0x58/0x90 [<ffffffff813cee82>] device_resume+0x112/0x250 [<ffffffff813cfe41>] dpm_resume+0x121/0x240 [<ffffffff813d0185>] dpm_resume_end+0x15/0x30 [<ffffffff8133e772>] ? acpi_suspend_begin_old+0x2d/0x2d [<ffffffff810a3a66>] suspend_devices_and_enter+0xb6/0x2f0 [<ffffffff810a3e34>] pm_suspend+0x194/0x230 [<ffffffff810a2df7>] state_store+0x87/0xf0 [<ffffffff812de26f>] kobj_attr_store+0xf/0x20 [<ffffffff81200e98>] sysfs_write_file+0xd8/0x150 [<ffffffff811908cc>] vfs_write+0xac/0x180 [<ffffffff81190bfa>] sys_write+0x4a/0x90 [<ffffffff8162bd69>] system_call_fastpath+0x16/0x1b
change display setup to dual display in gnome 3 Package: kernel OS Release: Fedora release 18 (Spherical Cow)
Is this still being seen with 3.8.x?
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
happening for me as well on kernel-3.8.8-202.fc18.x86_64