Bug 93267 - BUG: unable to handle kernel paging request in reservation_object_wait_timeout_rcu
Summary: BUG: unable to handle kernel paging request in reservation_object_wait_timeou...
Status: NEW
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-05 21:59 UTC by Marcin Slusarz
Modified: 2015-12-05 21:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcin Slusarz 2015-12-05 21:59:46 UTC
BUG: unable to handle kernel paging request at ffffc9000327f018
IP: [<ffffffff81533a4d>] reservation_object_wait_timeout_rcu+0x31d/0x510
PGD 13a8a1067 PUD 13a8a2067 PMD 31d16067 PTE 0
Oops: 0000 [#1] PREEMPT SMP 
Modules linked in: drbg ctr ccm rfcomm bnep binfmt_misc arc4 iwldvm mac80211 iwlwifi uvcvideo cfg80211 snd_hda_codec_hdmi rtsx_usb snd_hda_codec_idt snd_hda_codec_generic btusb videobuf2_vmalloc snd_hda_intel btrtl snd_hda_codec btbcm videobuf2_memops btintel bluetooth videobuf2_v4l2 videobuf2_core v4l2_common snd_hwdep videodev snd_hda_core snd_pcm dell_wmi dell_laptop sparse_keymap dcdbas snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq x86_pkg_temp_thermal serio_raw coretemp snd_timer snd_seq_device snd soundcore lpc_ich parport_pc ppdev lp parport hid_generic nouveau ahci psmouse i915 libahci mxm_wmi ttm i2c_algo_bit drm_kms_helper usbhid syscopyarea hid sysfillrect sysimgblt fb_sys_fops drm wmi video
CPU: 1 PID: 976 Comm: Xorg Not tainted 4.4.0-rc3 #60
Hardware name: Dell Inc.          Inspiron 7720/04M3YM, BIOS A07 08/16/2012
task: ffff880032b2a540 ti: ffff8801346c4000 task.ti: ffff8801346c4000
RIP: 0010:[<ffffffff81533a4d>]  [<ffffffff81533a4d>] reservation_object_wait_timeout_rcu+0x31d/0x510
RSP: 0018:ffff8801346c7ce8  EFLAGS: 00010246
RAX: ffffc9000327f000 RBX: ffff88011e6b0300 RCX: 000000000327d000
RDX: 000000000327d000 RSI: 0000000000000000 RDI: ffffffff81c5efc0
RBP: ffff8801346c7d30 R08: 0000000000000000 R09: 0000000000000000
R10: ffff880032b2a540 R11: 0000000000000000 R12: ffff880032c99d58
R13: 0000000000000000 R14: 0000000000001d4c R15: ffff8800330009b8
FS:  00007f9271ca1980(0000) GS:ffff88013f240000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc9000327f018 CR3: 0000000135f80000 CR4: 00000000001406e0
Stack:
 ffffffff815337cd 00000001817432f1 ffff880033000a50 00000002016c7d30
 00000000fffffff0 0000000000000000 ffff880033000800 ffff880033000bf0
 ffffffffa03cd4f0 ffff8801346c7d68 ffffffffa035dced ffffffffa035dd23
Call Trace:
 [<ffffffff815337cd>] ? reservation_object_wait_timeout_rcu+0x9d/0x510
 [<ffffffffa035dced>] nouveau_gem_ioctl_cpu_prep+0x6d/0x160 [nouveau]
 [<ffffffffa035dd23>] ? nouveau_gem_ioctl_cpu_prep+0xa3/0x160 [nouveau]
 [<ffffffffa0072a2b>] drm_ioctl+0x14b/0x530 [drm]
 [<ffffffffa035dc80>] ? nouveau_gem_ioctl_pushbuf+0xce0/0xce0 [nouveau]
 [<ffffffff814e98a0>] ? rpm_resume+0xf0/0x7b0
 [<ffffffff814e9fad>] ? __pm_runtime_resume+0x4d/0x60
 [<ffffffff8110848d>] ? trace_hardirqs_on+0xd/0x10
 [<ffffffff81743392>] ? _raw_spin_unlock_irqrestore+0x42/0x70
 [<ffffffffa0354777>] nouveau_drm_ioctl+0x67/0xc0 [nouveau]
 [<ffffffff8124aa11>] do_vfs_ioctl+0x301/0x550
 [<ffffffff812566aa>] ? __fget_light+0x2a/0x90
 [<ffffffff8124acd9>] SyS_ioctl+0x79/0x90
 [<ffffffff81743c5b>] entry_SYSCALL_64_fastpath+0x16/0x73
Code: fe ff ff 48 c7 c2 18 f1 a2 81 be 92 03 00 00 48 c7 c7 f5 eb a2 81 c6 05 50 65 7f 00 01 e8 ec 30 bd ff e9 2a fe ff ff 48 8b 43 08 <48> 8b 40 18 48 85 c0 0f 84 03 fe ff ff 48 89 df ff d0 84 c0 0f 
RIP  [<ffffffff81533a4d>] reservation_object_wait_timeout_rcu+0x31d/0x510
 RSP <ffff8801346c7ce8>
CR2: ffffc9000327f018
---[ end trace 4f0c12fc10089ab5 ]---

For some reason it's easy to reproduce using Warsow 2.0 - I had hit it twice in the main menu.


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.