From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 27211] New: endless PROTECTION_FAULT logs, Nouveau drm, TNT card
Date: Sat, 20 Mar 2010 12:28:44 -0700 (PDT) [thread overview]
Message-ID: <bug-27211-502@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=27211
Summary: endless PROTECTION_FAULT logs, Nouveau drm, TNT card
Product: DRI
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/other
AssignedTo: dri-devel@lists.sourceforge.net
ReportedBy: bzipitidoo@hotmail.com
Created an attachment (id=34263)
--> (http://bugs.freedesktop.org/attachment.cgi?id=34263)
/var/log/messages.log
I put Arch Linux on a Pentium II with a Diamond Viper V550 card (Riva TNT). If
I use the VESA driver, it works fine. But if I use Nouveau, the boot sequence
never finishes. After the udev message, the screen goes blank and I hear
endless disk activity. Thousands of these messages were being logged:
Mar 17 07:39:33 talc kernel: [drm] nouveau 0000:01:00.0: PGRAPH_NOTIFY -
nSource: PATCH_EXCEPTION, nStatus: INVALID_STATE PROTECTION_FAULT
Mar 17 07:39:33 talc kernel: [drm] nouveau 0000:01:00.0: PGRAPH_NOTIFY - Ch 0/3
Class 0x004a Mthd 0x0c18 Data 0x00000720:0x00000000
Relevant packages:
[root@talc log]# pacman -Qs kernel26
local/kernel26 2.6.32.10-1 (base)
The Linux Kernel and modules
local/kernel26-firmware 2.6.32.10-1 (base)
The included firmware files of the Linux Kernel
[root@talc log]# pacman -Qs nouveau
local/nouveau-drm 0.0.15_20100212-1
nvidia opensource X driver
local/xf86-video-nouveau 0.0.15_git20100221-1
Open Source 3D acceleration driver for nVidia cards (experimental)
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next reply other threads:[~2010-03-20 19:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 19:28 bugzilla-daemon [this message]
2010-03-20 19:42 ` [Bug 27211] endless PROTECTION_FAULT logs, Nouveau drm, TNT card bugzilla-daemon
2010-03-21 2:58 ` bugzilla-daemon
2010-03-21 8:48 ` bugzilla-daemon
2010-03-21 8:59 ` bugzilla-daemon
2010-03-23 0:40 ` bugzilla-daemon
2010-04-11 18:19 ` bugzilla-daemon
2010-05-12 6:35 ` bugzilla-daemon
2010-05-12 9:45 ` bugzilla-daemon
2010-05-12 21:59 ` bugzilla-daemon
2010-05-12 22:01 ` bugzilla-daemon
2010-05-13 9:10 ` bugzilla-daemon
2010-05-13 16:51 ` bugzilla-daemon
2010-05-13 19:56 ` bugzilla-daemon
2010-05-13 20:01 ` bugzilla-daemon
2010-05-13 20:07 ` bugzilla-daemon
2010-05-13 20:28 ` bugzilla-daemon
2013-05-24 14:03 ` bugzilla-daemon
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-27211-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.sourceforge.net \
/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