From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 14961] New: NV30: random dma queue hang
Date: Tue, 11 Mar 2008 14:11:58 -0700 (PDT) [thread overview]
Message-ID: <bug-14961-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=14961
Summary: NV30: random dma queue hang
Product: xorg
Version: 7.3
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: pmandin-/BqsFWbVIFRWk0Htik3J/w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Sometimes I got this in the kernel logs:
[drm] PGRAPH_ERROR - nSource: LIMIT_ZETA, nStatus: PROTECTION_FAULT
[drm] PGRAPH_ERROR - Ch 2/2 Class 0x009f Mthd 0x0308 Data 0x00000007:0x011c0130
I checked every calls in DDX driver that set data to method 0x308 for class
0x9f (NV12_IMAGE_BLIT), and did not find anything that may cause the error. It
happens either at start time (heavy bus usage, to load everything from disk),
when I move a big window (opaque mode), or sometimes more randomly.
I notice some big lags just before it triggers, and X crashes with DMA queue
hang error. It's like the fifo data has been overwritten. Enabling
NOUVEAU_DMA_DEBUG in DDX did not show anything wrong.
Card is 0x10de:0x0309, NV30GL
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2008-03-11 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 21:11 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-14961-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-01-13 23:20 ` [Bug 14961] NV30: random dma queue hang bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-17 10:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-19 21: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-14961-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.