Description of problem: Happened on lenovo T520 using the kernel intel drivers. 1) Closed the lid (AFAIK computer did *not* sleep after that). Left the computer. 2) Came the next day. Opened the lid. Primary display (=external) went to suspend mode and the secondary one (the laptop one) was left turned off (I turned it off before step 1 with xrandr). 3) Not even switching to virtual ttys worked, so I switched off the computer the hard way (holding the power button). Additional info: BUG: unable to handle kernel NULL pointer dereference at 0000000000000060 IP: [<ffffffffa011a13b>] ironlake_crtc_mode_set+0x5bb/0x1a50 [i915] PGD 0 Oops: 0000 [#1] SMP Modules linked in: fuse ebtable_nat xt_CHECKSUM bridge stp llc nfsv3 nfs_acl nfsv4 auth_rpcgss nfs dns_resolver fscache lockd sunrpc ipt_MASQUERADE nf_conntrack_netbios_ns nf_conntrack_broadcast ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables rfcomm bnep be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i 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 dm_crypt btusb bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media arc4 snd_hda_codec_hdmi iwldvm mac80211 snd_hda_codec_conexant iwlwifi snd_hda_intel snd_hda_codec snd_hwdep iTCO_wdt snd_seq snd_seq_device iTCO_vendor_support snd_pcm thinkpad_acpi e1000e lpc_ich snd_page_alloc mei snd_timer cfg80211 mfd_core i2c_i801 coretemp snd soundcore rfkill microcode vhost_net tun macvtap macvlan kvm_intel kvm uinput binfmt_misc i915 crc32c_intel ghash_clmulni_intel i2c_algo_bit sdhci_pci drm_kms_helper sdhci firewire_ohci drm mmc_core firewire_core crc_itu_t i2c_core wmi video CPU 0 Pid: 13557, comm: kworker/0:1 Not tainted 3.7.2-204.fc18.x86_64 #1 LENOVO 4243BQ9/4243BQ9 RIP: 0010:[<ffffffffa011a13b>] [<ffffffffa011a13b>] ironlake_crtc_mode_set+0x5bb/0x1a50 [i915] RSP: 0018:ffff8801e56737d8 EFLAGS: 00010246 RAX: ffff88020dc74c20 RBX: ffff88020dc74c18 RCX: 0000000000000000 RDX: ffff880108ec8d00 RSI: ffffffffa015bf7b RDI: 0000000000000004 RBP: ffff8801e5673928 R08: 0000000000000008 R09: 0000000000000000 R10: ffff88020dc74800 R11: ffff88020d4dc000 R12: ffff88020dc74970 R13: ffff88020dc72000 R14: ffff88020dc74c08 R15: ffff88020dc74c20 FS: 0000000000000000(0000) GS:ffff88021e200000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000060 CR3: 0000000001c0b000 CR4: 00000000000427e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process kworker/0:1 (pid: 13557, threadinfo ffff8801e5672000, task ffff8801e1c52e40) Stack: ffff8801e5673888 fffffffffffffffd ffff88010d8d2640 ffff88020d4dc000 ffff88020dc74800 0000000000000001 ffff88020d4dc000 0000000000000001 0000000000000000 0000000000000286 ffff8801e5673838 ffffffffa00f56ae Call Trace: [<ffffffffa00f56ae>] ? i915_pipe_enabled+0x1e/0x30 [i915] [<ffffffffa00f73fb>] ? ironlake_enable_vblank+0x2b/0x90 [i915] [<ffffffffa011e726>] intel_set_mode+0x626/0xa50 [i915] [<ffffffff81353b55>] ? acpi_ds_create_operands+0x6c/0xc4 [<ffffffffa01211e9>] intel_modeset_setup_hw_state+0x579/0x880 [i915] [<ffffffffa01234e5>] intel_lid_notify+0xb5/0xd0 [i915] [<ffffffff816398ed>] notifier_call_chain+0x4d/0x70 [<ffffffff81088278>] __blocking_notifier_call_chain+0x58/0x80 [<ffffffff810882b6>] blocking_notifier_call_chain+0x16/0x20 [<ffffffff8136e012>] acpi_lid_send_state+0x81/0xb2 [<ffffffff8136e49a>] acpi_button_notify+0x3d/0xaa [<ffffffff81349e65>] acpi_device_notify+0x19/0x1b [<ffffffff81356b2d>] acpi_ev_notify_dispatch+0x41/0x5c [<ffffffff81346dd5>] acpi_os_execute_deferred+0x25/0x32 [<ffffffff8107a487>] process_one_work+0x147/0x490 [<ffffffff81346db0>] ? acpi_os_wait_events_complete+0x23/0x23 [<ffffffff8107cd1e>] worker_thread+0x15e/0x450 [<ffffffff8107cbc0>] ? busy_worker_rebind_fn+0x110/0x110 [<ffffffff81081c80>] kthread+0xc0/0xd0 [<ffffffff81010000>] ? ftrace_raw_event_xen_mmu_flush_tlb_others+0x50/0xe0 [<ffffffff81081bc0>] ? kthread_create_on_node+0x120/0x120 [<ffffffff8163de2c>] ret_from_fork+0x7c/0xb0 [<ffffffff81081bc0>] ? kthread_create_on_node+0x120/0x120 Code: f8 0f 85 8a fd ff ff 66 0f 1f 84 00 00 00 00 00 48 8b 95 70 ff ff ff f6 82 c8 00 00 00 10 0f 85 cc 0c 00 00 48 8b 8d 30 ff ff ff <8b> 49 60 89 c8 83 e8 08 83 f8 28 0f 86 dc 0a 00 00 31 c0 48 c7 RIP [<ffffffffa011a13b>] ironlake_crtc_mode_set+0x5bb/0x1a50 [i915] RSP <ffff8801e56737d8> CR2: 0000000000000060
*** Bug 895123 has been marked as a duplicate of this bug. ***
Experiencing exactly the same problem if I close the lid even for a few seconds. The system reports: Not tainted 3.7.9-201.fc18.x86_64 #1 Dell Inc. Latitude E6320/0GJF11 I marked Bug 895123 as a duplicate; it was filed against xorg-x11-drv-intel. I think the reporter there is saying that this is fixed in Rawhide kernel-3.8.0-0.rc3.git1.2.fc19.x86_64, so this might be relatively easy to backport. ABRT did not report the problem, I assume because I had to reboot to recover from it. But obviously it is a serious problem to have a laptop you can't suspend, even if it is hardware-specific.
(In reply to comment #2) > Experiencing exactly the same problem if I close the lid even for a few > seconds. The system reports: > Not tainted 3.7.9-201.fc18.x86_64 #1 Dell Inc. Latitude E6320/0GJF11 > > I marked Bug 895123 as a duplicate; it was filed against xorg-x11-drv-intel. We file DRM bugs against the relative xorg driver on purpose. > I think the reporter there is saying that this is fixed in Rawhide > kernel-3.8.0-0.rc3.git1.2.fc19.x86_64, so this might be relatively easy to > backport. This is neither "EasyFix" nor "Triaged". Pointing to a newer -rcX kernel is great, but that doesn't mean it's easy to pick out the specific commit that fixed it and since there's no root cause and only a single report that it's working, it isn't triaged either. We appreciate the effort. F18 should be getting a 3.8 kernel soon. In the meantime, you can test 3.8.0-1.fc19 from rawhide/koji and let us know if that fixes things for you.
> > I think the reporter there is saying that this is fixed in Rawhide > > kernel-3.8.0-0.rc3.git1.2.fc19.x86_64, so this might be relatively easy to > > backport. > > This is neither "EasyFix" nor "Triaged". Pointing to a newer -rcX kernel is > great, but that doesn't mean it's easy to pick out the specific commit that > fixed it and since there's no root cause and only a single report that it's > working, it isn't triaged either. > > We appreciate the effort. F18 should be getting a 3.8 kernel soon. In the > meantime, you can test 3.8.0-1.fc19 from rawhide/koji and let us know if > that fixes things for you. A few comment as the submitter of Bug 895123 The stack trace I submitted for this problem was with kernel-3.8.0-0.rc3.git1.2.fc19.x86_64. [triggered with the listed additional i915 driver options] I claimed a different problem might be fixed by kernel-3.8.0-0.rc3.git1.2.fc19.x86_64 [well that problem comes up but much less frequently than with 3.7 kernel] I had this issue only once. I've been using various 3.8 rc kernels since then without problems. [and I haven't used the additional i915 driver options again]
I can now close the lid with kernel-3.8.3-201.fc18.x86_64 and I do not see this problem.
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.