Kernel Oops when closing the lid on Dell XPS 14z



Hello,

I'm running Sid on my Dell XPS 14z, everything is up to date. Suspend works fine when I select it from the menu. But when I close the lid, it crashes. If I suspend first with the menu, and then close the lid, it works correcty.

I tried kernel 3.3 trunk and got the same problem.

Intel X driver is 2.18.0-2+b1.

Here is the output from syslog:
May 21 18:20:15 TichoLaptop kernel: [ 1658.787327] BUG: unable to handle kernel paging request at ffffc9001193396c
May 21 18:20:15 TichoLaptop kernel: [ 1658.787415] IP: [<ffffffff812474b8>] gen6_write_entry+0x4c/0x4f
May 21 18:20:15 TichoLaptop kernel: [ 1658.787493] PGD 1cf023067 PUD 1cf024067 PMD 1c89ee067 PTE 0
May 21 18:20:15 TichoLaptop kernel: [ 1658.787570] Oops: 0002 [#1] SMP
May 21 18:20:15 TichoLaptop kernel: [ 1658.787614] CPU 1
May 21 18:20:15 TichoLaptop kernel: [ 1658.787637] Modules linked in: aesni_intel cryptd aes_x86_64 aes_generic acpi_cpufreq mperf cpufreq_powersave cpufreq_conservative cpufreq_userspace cpufreq_stats bnep rfcomm fuse loop ixgb 8390 8139too mii uvcvideo videodev v4l2_compat_ioctl32 media snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb bluetooth crc16 arc4 sr_mod cdrom iwlwifi snd_hda_intel i915 snd_hda_codec mac80211 snd_hwdep drm_kms_helper cfg80211 drm snd_pcm xhci_hcd snd_page_alloc processor battery dell_wmi dell_laptop ehci_hcd usbcore rfkill rts_pstor(C) snd_timer i2c_algo_bit i2c_i801 dcdbas iTCO_wdt i2c_core iTCO_vendor_support snd ac psmouse sparse_keymap serio_raw power_supply button soundcore video atl1c usb_common wmi thermal_sys evdev pcspkr ext3 mbcache jbd sd_mod crc_t10dif ahci libahci libata scsi_mod
May 21 18:20:15 TichoLaptop kernel: [ 1658.788707]
May 21 18:20:15 TichoLaptop kernel: [ 1658.788732] Pid: 9739, comm: Xorg Tainted: G C 3.2.0-2-amd64 #1 Dell Inc. XPS L412Z/008DD8
May 21 18:20:15 TichoLaptop kernel: [ 1658.788847] RIP: 0010:[<ffffffff812474b8>] [<ffffffff812474b8>] gen6_write_entry+0x4c/0x4f
May 21 18:20:15 TichoLaptop kernel: [ 1658.788951] RSP: 0018:ffff8801c49b3aa0 EFLAGS: 00010202
May 21 18:20:15 TichoLaptop kernel: [ 1658.789017] RAX: 00000000738b2015 RBX: 0000000000000500 RCX: 0000000000010001
May 21 18:20:15 TichoLaptop kernel: [ 1658.789098] RDX: 00000001738b2010 RSI: ffffc9001193396c RDI: 00000001738b2000
May 21 18:20:15 TichoLaptop kernel: [ 1658.789178] RBP: 000000000000ce5b R08: 0000000000000000 R09: 0000000000049e04
May 21 18:20:15 TichoLaptop kernel: [ 1658.789261] R10: ffffc90011900000 R11: 0000000000002d2d R12: 0000000000000000
May 21 18:20:15 TichoLaptop kernel: [ 1658.789328] R13: 0000000000010001 R14: ffff8801b0ba2000 R15: 0000000000000001
May 21 18:20:15 TichoLaptop kernel: [ 1658.789388] FS: 00007fbff0f5a880(0000) GS:ffff8801cfa40000(0000) knlGS:0000000000000000
May 21 18:20:15 TichoLaptop kernel: [ 1658.789456] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 21 18:20:15 TichoLaptop kernel: [ 1658.789503] CR2: ffffc9001193396c CR3: 00000001a9c1c000 CR4: 00000000000406e0
May 21 18:20:15 TichoLaptop kernel: [ 1658.789562] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
May 21 18:20:15 TichoLaptop kernel: [ 1658.789622] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
May 21 18:20:15 TichoLaptop kernel: [ 1658.789681] Process Xorg (pid: 9739, threadinfo ffff8801c49b2000, task ffff8801c644d6d0)
May 21 18:20:15 TichoLaptop kernel: [ 1658.789746] Stack:
May 21 18:20:15 TichoLaptop kernel: [ 1658.789765] ffffffff81248526 ffff8801b0ba2000 0000000000000000 000012d000000000
May 21 18:20:15 TichoLaptop kernel: [ 1658.789859] ffff880161435a00 0000000000010001 0000000000001000 ffff8801c71c0000
May 21 18:20:15 TichoLaptop kernel: [ 1658.789956] 0000000000000500 0000000000000500 ffffffffa02ec93c ffff880161435a00
May 21 18:20:15 TichoLaptop kernel: [ 1658.790058] Call Trace:
May 21 18:20:15 TichoLaptop kernel: [ 1658.790097] [<ffffffff81248526>] ? intel_gtt_insert_sg_entries+0x45/0x8d
May 21 18:20:15 TichoLaptop kernel: [ 1658.790192] [<ffffffffa02ec93c>] ? i915_gem_gtt_bind_object+0x98/0xc6 [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790286] [<ffffffffa02e6ade>] ? i915_gem_object_bind_to_gtt+0x34c/0x495 [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790380] [<ffffffff812f4d36>] ? sk_wake_async+0x19/0x3c
May 21 18:20:15 TichoLaptop kernel: [ 1658.790458] [<ffffffffa02e8f0e>] ? i915_gem_object_pin+0xb9/0x12d [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790550] [<ffffffffa02eb75b>] ? i915_gem_do_execbuffer.isra.6+0x2f3/0x10e2 [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790647] [<ffffffffa02eb32a>] ? i915_gem_execbuffer_reserve.isra.4+0x1b3/0x2e7 [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790752] [<ffffffffa02eb8ad>] ? i915_gem_do_execbuffer.isra.6+0x445/0x10e2 [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790847] [<ffffffffa02ec7b3>] ? i915_gem_execbuffer2+0x4f/0x140 [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.790933] [<ffffffffa02ec842>] ? i915_gem_execbuffer2+0xde/0x140 [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.791021] [<ffffffffa025e61f>] ? drm_ioctl+0x289/0x35e [drm]
May 21 18:20:15 TichoLaptop kernel: [ 1658.791100] [<ffffffffa02ec764>] ? i915_gem_execbuffer+0x21a/0x21a [i915]
May 21 18:20:15 TichoLaptop kernel: [ 1658.791183] [<ffffffff811065fd>] ? do_vfs_ioctl+0x459/0x49a
May 21 18:20:15 TichoLaptop kernel: [ 1658.791254] [<ffffffff81106689>] ? sys_ioctl+0x4b/0x72
May 21 18:20:15 TichoLaptop kernel: [ 1658.791316] [<ffffffff810f93c7>] ? sys_read+0x5f/0x6b
May 21 18:20:15 TichoLaptop kernel: [ 1658.791373] [<ffffffff8134e3d2>] ? system_call_fastpath+0x16/0x1b
May 21 18:20:15 TichoLaptop kernel: [ 1658.791425] Code: 01 00 75 05 83 c0 0f eb 03 83 c0 0d 48 89 fa 4c 8b 15 05 36 5b 00 89 f6 48 c1 ea 1c 81 e2 f0 0f 00 00 48 09 fa 49 8d 34 b2 09 d0 <89> 06 c3 c3 48 c7 c0 60 aa 7f 81 c3 48 8b 05 a5 35 5b 00 48 8b
May 21 18:20:15 TichoLaptop kernel: [ 1658.794109] RIP [<ffffffff812474b8>] gen6_write_entry+0x4c/0x4f
May 21 18:20:15 TichoLaptop kernel: [ 1658.796497] RSP <ffff8801c49b3aa0>

I looked online, but I couldn't find a workaround.

Let me know if more information are needed.

Thanks
Sylvain


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Archive: http://lists.debian.org/4FBAE496.90906@xxxxxxxxxxx



Relevant Pages

  • Re: Kernel Oops when closing the lid on Dell XPS 14z
    ... If I suspend first with the menu, and then close the lid, it ... That's curious because closing the lid and suspending from menu should ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Re: Thinkpad Backlight Trouble in X in Testing
    ... Suspend on lid close is also no longer working. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Suspend problem on T60
    ... problem suspending my computer by shutting the lid. ... screensaver, but did not suspend. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • Laptop Suspend Function FC4
    ... Can anyone tell me how I can get my laptop to suspend properly? ... When I close the lid to my laptop it seems to suspend but I have to reboot to get it back to get it ... To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list ...
    (Fedora)
  • Re: Please explain this: (suspend/resume w/ RH 9 on Dell Latitude C840)
    ... I wondered what this 'suspend' stuff was alla bout. ... s'posedly would restore everything when the lid was opened again. ... from the BIOS that tells the o/s to write its current state in a special ... computer on *with the display off* when the lid is closed. ...
    (comp.os.linux.setup)