FS#34027 - [linux] 3.7.x - 3.8.x black screen after resume from sleep with i915
Attached to Project:
Arch Linux
Opened by Vasili (3point2) - Tuesday, 26 February 2013, 11:58 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 30 July 2013, 10:26 GMT
Opened by Vasili (3point2) - Tuesday, 26 February 2013, 11:58 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 30 July 2013, 10:26 GMT
|
Details
Description:
Occasionally when resuming my ThinkPad T61 from sleep, I get a completely black screen, no backlight, nothing. The system seems to be running and my "fix" is to switch to a tty and hit ctrl-alt-delete to reboot. The same bug is reported here: https://bugzilla.redhat.com/show_bug.cgi?id=907486 It's happened to me several times in the last few months (and across the last few kernel upgrades). Additional info: * kernel 3.7.7-1-ARCH Feb 24 23:42:34 hal kernel: [drm:intel_pipe_set_base] *ERROR* No FB bound Feb 24 23:42:34 hal kernel: ------------[ cut here ]------------ Feb 24 23:42:34 hal kernel: WARNING: at drivers/gpu/drm/i915/intel_display.c:3354 i9xx_crtc_enable+0x1d3/0x1f0 [i915]() Feb 24 23:42:34 hal kernel: Hardware name: 7658CTO Feb 24 23:42:34 hal kernel: Modules linked in: fuse tp_smapi(O) btusb bluetooth snd_hda_codec_analog arc4 pcmcia iTCO_wdt snd_hda_intel snd_hda_code Feb 24 23:42:34 hal kernel: Pid: 5569, comm: systemd-sleep Tainted: G O 3.7.7-1-ARCH #1 Feb 24 23:42:34 hal systemd-sleep[5569]: System resumed. Feb 24 23:42:34 hal kernel: Call Trace: Feb 24 23:42:34 hal kernel: [<ffffffff8105753f>] warn_slowpath_common+0x7f/0xc0 Feb 24 23:42:34 hal kernel: [<ffffffff8105759a>] warn_slowpath_null+0x1a/0x20 Feb 24 23:42:34 hal kernel: [<ffffffffa00a4673>] i9xx_crtc_enable+0x1d3/0x1f0 [i915] Feb 24 23:42:34 hal kernel: [<ffffffffa00ab253>] intel_set_mode+0x7b3/0xa50 [i915] Feb 24 23:42:34 hal kernel: [<ffffffffa0007667>] ? bit_xfer+0x297/0x540 [i2c_algo_bit] Feb 24 23:42:34 hal kernel: [<ffffffffa00adbd9>] intel_modeset_setup_hw_state+0x579/0x880 [i915] Feb 24 23:42:34 hal kernel: [<ffffffffa00afe85>] intel_lid_notify+0xb5/0xd0 [i915] Feb 24 23:42:34 hal kernel: [<ffffffff814bf12d>] notifier_call_chain+0x4d/0x70 Feb 24 23:42:34 hal kernel: [<ffffffff810819d8>] __blocking_notifier_call_chain+0x58/0x80 Feb 24 23:42:34 hal kernel: [<ffffffffa0046105>] ? acpi_lid_send_state+0xb7/0xb7 [button] Feb 24 23:42:34 hal kernel: [<ffffffff81081a16>] blocking_notifier_call_chain+0x16/0x20 Feb 24 23:42:34 hal kernel: [<ffffffffa00460d5>] acpi_lid_send_state+0x87/0xb7 [button] Feb 24 23:42:34 hal kernel: [<ffffffffa0046125>] acpi_button_resume+0x20/0x22 [button] Feb 24 23:42:34 hal kernel: [<ffffffff8134bd68>] dpm_run_callback+0x58/0x90 Feb 24 23:42:34 hal kernel: [<ffffffff8134c4ae>] device_resume+0xde/0x200 Feb 24 23:42:34 hal kernel: [<ffffffff8134d5d1>] dpm_resume+0x121/0x250 Feb 24 23:42:34 hal kernel: [<ffffffff8134d925>] dpm_resume_end+0x15/0x30 Feb 24 23:42:34 hal kernel: [<ffffffff812cac49>] ? acpi_suspend_begin_old+0x2d/0x2d Feb 24 23:42:34 hal kernel: [<ffffffff8109f936>] suspend_devices_and_enter+0xb6/0x340 Feb 24 23:42:34 hal kernel: [<ffffffff8109fd7a>] pm_suspend+0x1ba/0x230 Feb 24 23:42:34 hal kernel: [<ffffffff8109f045>] state_store+0xa5/0xc0 Feb 24 23:42:34 hal kernel: [<ffffffff8126b5af>] kobj_attr_store+0xf/0x20 Feb 24 23:42:34 hal kernel: [<ffffffff811f771d>] sysfs_write_file+0xcd/0x140 Feb 24 23:42:34 hal kernel: [<ffffffff81184788>] vfs_write+0xa8/0x180 Feb 24 23:42:34 hal kernel: [<ffffffff81184ad2>] sys_write+0x52/0xa0 Feb 24 23:42:34 hal kernel: [<ffffffff814bf0de>] ? do_page_fault+0xe/0x10 Feb 24 23:42:34 hal kernel: [<ffffffff814c301d>] system_call_fastpath+0x1a/0x1f Feb 24 23:42:34 hal kernel: ---[ end trace 40e10c23d7004b75 ]--- This is followed by several more traces, see the attached file. Steps to reproduce: This happens very occasionally (less than once a week with daily sleep/wake cycles) when waking up the laptop from sleep by opening the lid. 
i915.crash
(33.1 KiB)
|
This task depends upon
a better fix than rebooting is to put the laptop back to sleep and wake it up again. on the second wakeup the screen works again.
Happens sometimes when waking up in the dock station. My workaround was to switch to an tty and restart kdm service, but you lose your KDE session then.