Bug 100433 - Kernel Oops on attempting to return from locked screen on gnome-session
Summary: Kernel Oops on attempting to return from locked screen on gnome-session
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/nouveau (show other bugs)
Version: 17.0
Hardware: Other All
: medium normal
Assignee: Nouveau Project
QA Contact: Nouveau Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-28 12:22 UTC by Atri
Modified: 2019-09-18 20:45 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
journalctl -b -1 (see events around Mar 27 22:25:08) (2.56 MB, text/x-log)
2017-03-28 12:22 UTC, Atri 		Details
View All

Description Atri 2017-03-28 12:22:15 UTC 
Created attachment 130500 [details]
journalctl -b -1 (see events around Mar 27 22:25:08)

Since the upgrade to kernel 4.10.3 (and continuing on 4.10.4), my gnome-session consistently fails to return from a lock screen, sometimes showing me a completely black screen, with only an immobile mouse pointer visible, at other times the monitor goes off into sleep mode never to return. Logs show that the kernel "oops" at around this point. I have to finally emergency reboot the system. journal log attached.

:~> uname -r
4.10.3-1-default

Graphics: Gallium 0.4 on NVA8
Comment 1 Atri 2017-04-09 19:48:22 UTC 
Still happening with 4/10/8, with crashes like these:

Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000020
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: IP: dma_fence_wait_timeout+0x30/0x110
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: PGD 3c068a067 
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: PUD 3c3ca4067 
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: PMD 0 
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: 
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: Oops: 0000 [#1] PREEMPT SMP
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: Modules linked in: fuse af_packet msr snd_hda_codec_hdmi joydev iTCO_wdt snd_hda_codec_realtek iTCO_vendor_support snd_hda_codec_generic intel_rapl hid_generic eda
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel:  xhci_pci firewire_core drm_kms_helper ehci_pci crc_itu_t syscopyarea xhci_hcd sysfillrect ehci_hcd sysimgblt fb_sys_fops ttm usbcore drm wmi button sg efivarfs
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: CPU: 3 PID: 8309 Comm: gnome-shell Not tainted 4.10.8-1-default #1
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: Hardware name: PRIMINFO UNLOCK INSTALL/P9X79, BIOS 4701 05/06/2014
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: task: ffff8fce446b8000 task.stack: ffffa997c6414000
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: RIP: 0010:dma_fence_wait_timeout+0x30/0x110
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: RSP: 0018:ffffa997c6417be8 EFLAGS: 00010206
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: RDX: 7fffffffffffffff RSI: 0000000000000001 RDI: ffff8fcd03ef4300
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: RBP: ffff8fcd03ef4300 R08: 0000000000009330 R09: 0000000000000000
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: R10: 0000000000000000 R11: 0000000000000002 R12: 0000000000000001
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: R13: 7fffffffffffffff R14: ffff8fcea9c02800 R15: 0000000000000001
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: FS:  00007fdf1ac43ac0(0000) GS:ffff8fceaf2c0000(0000) knlGS:0000000000000000
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: CR2: 0000000000000020 CR3: 00000003b681a000 CR4: 00000000001406e0
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: Call Trace:
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel:  nouveau_fence_sync+0x118/0x250 [nouveau]
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel:  nouveau_gem_ioctl_pushbuf+0x8f5/0x1660 [nouveau]
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel:  drm_ioctl+0x1ec/0x410 [drm]
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel:  ? nouveau_gem_ioctl_new+0x120/0x120 [nouveau]
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel:  nouveau_drm_ioctl+0x66/0xc0 [nouveau]
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel:  do_vfs_ioctl+0x8f/0x5d0
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel:  ? __sys_recvmsg+0x5d/0x70
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel:  ? __fget+0x70/0xc0
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel:  SyS_ioctl+0x74/0x80
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel:  entry_SYSCALL_64_fastpath+0x1e/0xad
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: Code: 48 85 d2 41 55 41 54 55 53 0f 88 d4 00 00 00 48 89 fd 41 89 f4 49 89 d5 0f 1f 44 00 00 48 8b 45 08 41 0f b6 f4 4c 89 ea 48 89 ef <ff> 50 20 49 89 c4 0f 1f 44
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: RIP: dma_fence_wait_timeout+0x30/0x110 RSP: ffffa997c6417be8
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: CR2: 0000000000000020
Apr 09 06:15:28 mal.theo.phys.ulg.ac.be kernel: ---[ end trace ca8c6158d9e341a9 ]---
Comment 2 Atri 2017-04-14 22:42:03 UTC 
(In reply to Atri from comment #1)
> Still happening with 4/10/8, with crashes like these:

Sorry, obviously I meant with kernel 4.10.8 there.

Also, just to add, uninstalling the nouveau driver (and running e.g. on llvmpipe) makes this problem disappear.
Comment 3 Pierre Moreau 2017-04-15 15:14:13 UTC 
If you use the modesetting DDX, or update the Nouveau DDX to 1.0.14, does it still happen?
Comment 4 Atri 2017-04-16 01:54:05 UTC 
I am using nouveau 1.0.14 and modesetting, it still happens.
Comment 5 GitLab Migration User 2019-09-18 20:45:11 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1130.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.