From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 35876] New: Hard GPU hang on nvidia
Date: Fri, 1 Apr 2011 08:58:47 -0700 (PDT) [thread overview]
Message-ID: <bug-35876-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=35876
Summary: Hard GPU hang on nvidia
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: maximlevitsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Created an attachment (id=45137)
--> (https://bugs.freedesktop.org/attachment.cgi?id=45137)
git snapshot
Hardware: Geforce 8400M GS - (0x086700a2)
Acer Aspire 5720G
Userspace: Git tips of all components except Xserver.
In attached file, you see the latest commits of each tree
Kernel drm version: dd34154f9bd75d13caefffd9d6086a1d23a45856
drm/nouveau: use static vidshift of 2 on volt 0x30 tables
This already happened here many times.
Just 2D usage of compiz is enough.
I will eventually test if even just 2D usage can trigger this.
I get this in the kernel log:
<3>[17638.684109] [drm] nouveau 0000:01:00.0: vm flush timeout: engine 0
<3>[17644.904441] [drm] nouveau 0000:01:00.0: PRAMIN flush timeout
<6>[17645.869768] [drm] nouveau 0000:01:00.0: PFIFO_INTR 0x04000000 - Ch 2
<3>[17645.966182] [drm] nouveau 0000:01:00.0: vm flush timeout: engine 5
(Extracted using ram based "black-box", a fixed area in the system memory I
read after a crash.)
System freezes fully.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-04-01 15:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 15:58 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-35876-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-04-02 2:49 ` [Bug 35876] Hard GPU hang on nvidia bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-07 13:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-21 2:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-21 2:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-21 2:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-21 13:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-05-21 13:47 ` [Bug 35876] Hard GPU hangs on NV86 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-05 0:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-12 22:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-12 23:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-12 23:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-13 0:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-14 0:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-23 2:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-23 3:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-24 1:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-24 1:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-24 1:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-25 20:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-25 20:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-25 23:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27 2:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27 2:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27 2:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27 3:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27 3:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27 21:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-27 21:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-31 0:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-31 1:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-31 1:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-31 1:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-02-12 21:14 ` 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-35876-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.