Description of problem: I tried to resume my laptop (in a docking station) and I had only a black screen. But it seemed to be alive. So I suspended it again using a keyboard shortcut and then resumed it again. This time my screen was working. This is what I've found in dmesg: [25642.458055] [drm:intel_pipe_set_base] *ERROR* No FB bound [25642.458058] ------------[ cut here ]------------ [25642.458083] WARNING: at drivers/gpu/drm/i915/intel_display.c:3354 i9xx_crtc_enable+0x1d3/0x1f0 [i915]() [25642.458084] Hardware name: 2241B48 [25642.458102] Modules linked in: tun fuse rfcomm bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev btusb bluetooth media snd_hda_codec_conexant iTCO_wdt snd_hda_intel snd_hda_codec arc4 iTCO_vendor_support iwldvm coretemp snd_hwdep kvm_intel snd_seq mac80211 snd_seq_device kvm thinkpad_acpi ppdev lpc_ich r592 memstick snd_pcm vboxnetadp(OF) iwlwifi i2c_i801 e1000e parport_pc mei mfd_core snd_page_alloc snd_timer vboxnetflt(OF) microcode snd parport cfg80211 soundcore rfkill vboxdrv(OF) uinput dm_crypt hid_logitech_dj firewire_ohci sdhci_pci sdhci i915 mmc_core firewire_core crc_itu_t yenta_socket i2c_algo_bit drm_kms_helper drm i2c_core wmi video [25642.458104] Pid: 13729, comm: pm-suspend Tainted: GF C O 3.7.5-201.fc18.x86_64 #1 [25642.458104] Call Trace: [25642.458109] [<ffffffff8105e67f>] warn_slowpath_common+0x7f/0xc0 [25642.458111] [<ffffffff8105e6da>] warn_slowpath_null+0x1a/0x20 [25642.458120] [<ffffffffa00c5ce3>] i9xx_crtc_enable+0x1d3/0x1f0 [i915] [25642.458135] [<ffffffffa00cc8f3>] intel_set_mode+0x7b3/0xa50 [i915] [25642.458138] [<ffffffff81353f05>] ? acpi_ds_create_operands+0x6c/0xc4 [25642.458149] [<ffffffffa00cf229>] intel_modeset_setup_hw_state+0x579/0x880 [i915] [25642.458158] [<ffffffffa00d1525>] intel_lid_notify+0xb5/0xd0 [i915] [25642.458161] [<ffffffff81639bad>] notifier_call_chain+0x4d/0x70 [25642.458163] [<ffffffff810883c8>] __blocking_notifier_call_chain+0x58/0x80 [25642.458165] [<ffffffff8136e3f3>] ? acpi_lid_send_state+0xb2/0xb2 [25642.458166] [<ffffffff81088406>] blocking_notifier_call_chain+0x16/0x20 [25642.458167] [<ffffffff8136e3c2>] acpi_lid_send_state+0x81/0xb2 [25642.458168] [<ffffffff8136e413>] acpi_button_resume+0x20/0x22 [25642.458170] [<ffffffff813da8c8>] dpm_run_callback+0x58/0x90 [25642.458171] [<ffffffff813db29e>] device_resume+0xde/0x200 [25642.458172] [<ffffffff813dc041>] dpm_resume+0x121/0x240 [25642.458173] [<ffffffff813dc375>] dpm_resume_end+0x15/0x30 [25642.458176] [<ffffffff81348c3e>] ? acpi_suspend_begin_old+0x2d/0x2d [25642.458178] [<ffffffff810a6016>] suspend_devices_and_enter+0xb6/0x2f0 [25642.458179] [<ffffffff810a63e4>] pm_suspend+0x194/0x230 [25642.458180] [<ffffffff810a5377>] state_store+0x87/0xf0 [25642.458182] [<ffffffff812e90df>] kobj_attr_store+0xf/0x20 [25642.458184] [<ffffffff81207838>] sysfs_write_file+0xd8/0x150 [25642.458186] [<ffffffff811953dc>] vfs_write+0xac/0x180 [25642.458187] [<ffffffff81195722>] sys_write+0x52/0xa0 [25642.458188] [<ffffffff81639b5e>] ? do_page_fault+0xe/0x10 [25642.458190] [<ffffffff8163e199>] system_call_fastpath+0x16/0x1b [25642.458191] ---[ end trace 80bfc6fc58640149 ]--- And some further exceptions. Whole dmesg attached. Version-Release number of selected component (if applicable): 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) kernel-3.7.5-201.fc18.x86_64 xorg-x11-drv-intel-2.20.19-1.fc18.x86_64 How reproducible: hardly, first time I saw it
Created attachment 692772 [details] dmesg
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.