From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 71620] New: nouveau_fence_wait_uevent NULL pointer dereference
Date: Thu, 14 Nov 2013 18:55:54 +0000 [thread overview]
Message-ID: <bug-71620-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2390 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=71620
Priority: medium
Bug ID: 71620
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: nouveau_fence_wait_uevent NULL pointer dereference
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: kdatanasov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: Drivers/DRI/nouveau
Product: Mesa
Created attachment 89234
--> https://bugs.freedesktop.org/attachment.cgi?id=89234&action=edit
patch_to_protect_fence_channel
Upon normal computer operation user session(GNOME-Shell) sometimes will just
terminate. Problem seems more common if two users are logged in(GNOME-Shell)
for a day.
GPU:
NVIDIA Corporation C77 [GeForce 8300] (rev a2)
kernel version:
3.12.0-upstream
Relevent dmesg output:
[29434.602169] Call Trace:
[29434.602188] [<ffffffffa010b6db>] ?
nouveau_fence_wait_uevent.isra.1+0x1b/0x3f0 [nouveau]
[29434.602208] [<ffffffffa010b676>] ? nouveau_fence_update+0x76/0x90 [nouveau]
[29434.602228] [<ffffffffa010bb36>] nouveau_fence_wait+0x86/0x1a0 [nouveau]
[29434.602248] [<ffffffffa010d7a5>] nouveau_bo_fence_wait+0x15/0x20 [nouveau]
[29434.602260] [<ffffffffa00658a1>] ttm_bo_wait+0x91/0x190 [ttm]
[29434.602279] [<ffffffffa0112e57>] nouveau_gem_ioctl_cpu_prep+0x57/0xe0
[nouveau]
[29434.602294] [<ffffffffa0010c52>] drm_ioctl+0x502/0x630 [drm]
[29434.602313] [<ffffffffa0108d11>] nouveau_drm_ioctl+0x51/0x90 [nouveau]
[29434.602324] [<ffffffff811b3690>] do_vfs_ioctl+0x2e0/0x4c0
[29434.602332] [<ffffffff811a2e2e>] ? ____fput+0xe/0x10
[29434.602340] [<ffffffff81080544>] ? task_work_run+0xa4/0xe0
[29434.602347] [<ffffffff811b38f1>] SyS_ioctl+0x81/0xa0
[29434.602356] [<ffffffff814f81ad>] system_call_fastpath+0x1a/0x1f
[29434.602364] Code: c3 0f 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41
57 49 89 f7 41 56 41 55 41 54 41 89 d4 53 48 89 fb 48 83 ec 58 48 8b 07 <48> 8b
48 08 48 8b 91 f8 00 00 00 4c 8b b1 b0 07 00 00 48 8b 42
I'm trying some change(adding it as patch) - no problem so far, but since I
have zero experience in kernel/driver workflow definitely not sure if it's OK.
Regards, K
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3873 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2013-11-14 18:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 18:55 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-71620-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-11-24 21:01 ` [Bug 71620] nouveau_fence_wait_uevent NULL pointer dereference bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-12 2:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-25 12:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-25 12:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-28 0:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-17 0:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-22 22:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-28 15:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-71620-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.