From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 47191] New: random xorg hang with PGRAPH_TRAP_TPDMA_2D - TP 0 - Unknown fault at address
Date: Sat, 10 Mar 2012 18:34:31 +0000 [thread overview]
Message-ID: <bug-47191-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=47191
Bug #: 47191
Summary: random xorg hang with PGRAPH_TRAP_TPDMA_2D - TP 0 -
Unknown fault at address
Classification: Unclassified
Product: xorg
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: high
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: htexmexh-1jCL+rEOqeNBDgjK7y7TUQ@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
I get random xorg hangs where the only thing I can do is REISUB out. I am
running the nouveau driver with xorg-server-1.9.5 and kernel 3.2.7.
I find this in /var/log/messages at the time of the crash:
Mar 10 16:03:52 greatdemonslayer kernel: [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_TPDMA_2D - TP 0 - Unknown fault at address 002422c400
Mar 10 16:03:52 greatdemonslayer kernel: [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_TPDMA_2D - TP 0 - e0c: 00000000, e18: 00000000, e1c: 00100000, e20:
00000037, e24: 0$
Mar 10 16:03:52 greatdemonslayer kernel: [drm] nouveau 0000:01:00.0: PGRAPH -
TRAP
Mar 10 16:03:52 greatdemonslayer kernel: [drm] nouveau 0000:01:00.0: PGRAPH -
ch 2 (0x0000b30000) subc 2 class 0x502d mthd 0x0860 data 0xffffffff
Mar 10 16:03:52 greatdemonslayer kernel: [drm] nouveau 0000:01:00.0: VM:
trapped write at 0x002422c400 on ch 2 [0x00000b30] PGRAPH/PROP/DST2D reason:
PAGE_NOT_PRESENT
Mar 10 16:05:55 greatdemonslayer kernel: [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_TPDMA_2D - TP 0 - Unknown fault at address 002526b300
Mar 10 16:05:55 greatdemonslayer kernel: [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_TPDMA_2D - TP 0 - e0c: 00000000, e18: 00000000, e1c: 000c0000, e20:
00000037, e24: 0$
Mar 10 16:05:55 greatdemonslayer kernel: [drm] nouveau 0000:01:00.0: PGRAPH -
TRAP
Mar 10 16:05:55 greatdemonslayer kernel: [drm] nouveau 0000:01:00.0: PGRAPH -
ch 2 (0x0000b30000) subc 2 class 0x502d mthd 0x0860 data 0x00000000
Mar 10 16:05:55 greatdemonslayer kernel: [drm] nouveau 0000:01:00.0: VM:
trapped write at 0x002526b300 on ch 2 [0x00000b30] PGRAPH/PROP/DST2D reason:
PAGE_NOT_PRESENT
Mar 10 16:35:46 greatdemonslayer -- MARK --
I have gotten similar hangs with recent proprietary nvidia drivers, and that's
why I switched to nouveau. I don't know if this is hardware related, but it
didn't happen with older nvidia drivers.
--
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:[~2012-03-10 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 18:34 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-47191-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-08-25 17:45 ` [Bug 47191] random xorg hang with PGRAPH_TRAP_TPDMA_2D - TP 0 - Unknown fault at address bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-26 23:42 ` 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-47191-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox