Bug 68854 - [NV04] PROTECTION_ERROR / PROTECTION_FAULT
Summary: [NV04] PROTECTION_ERROR / PROTECTION_FAULT
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on: 68835
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-02 16:36 UTC by Mauro Molinari
Modified: 2019-12-04 08:35 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (22.93 KB, text/plain)
2013-09-02 19:04 UTC, Mauro Molinari
no flags Details
dmesg output taken after the same boot from which Xorg.0.log was taken (51.92 KB, text/plain)
2013-09-02 19:05 UTC, Mauro Molinari
no flags Details

Description Mauro Molinari 2013-09-02 16:36:32 UTC
+++ This bug was initially created as a clone of Bug #68835 +++

Running Fedora 19 with a live USB on an old system with Creative Labs Graphics Blaster Riva TNT:

Linux localhost 3.9.5-301.fc19.i686 #1 SMP Tue Jun 11 20:01:50 UTC 2013 i686 i686 i386 GNU/Linux

If I run dmesg I see some errors like:

[   99.820645] nouveau E[  PGRAPH][0000:01:00.0]  NOTIFY nsource: PROTECTION_ERROR nstatus: PROTECTION_FAULT
[   99.820677] nouveau E[  PGRAPH][0000:01:00.0] ch 1 [X[666]] subc 2 class 0x0042 mthd 0x0180 data 0x00003a04
[   99.820697] nouveau E[  PGRAPH][0000:01:00.0]  NOTIFY nsource: PROTECTION_ERROR nstatus: PROTECTION_FAULT
[   99.820714] nouveau E[  PGRAPH][0000:01:00.0] ch 1 [X[666]] subc 6 class 0x0044 mthd 0x0180 data 0x00003a04
[   99.820732] nouveau E[  PGRAPH][0000:01:00.0]  NOTIFY nsource: PROTECTION_ERROR nstatus: PROTECTION_FAULT
[   99.820749] nouveau E[  PGRAPH][0000:01:00.0] ch 1 [X[666]] subc 6 class 0x0043 mthd 0x0180 data 0x00003a04
[   99.821101] nouveau E[  PGRAPH][0000:01:00.0]  NOTIFY nsource: PROTECTION_ERROR nstatus: PROTECTION_FAULT
[   99.821121] nouveau E[  PGRAPH][0000:01:00.0] ch 1 [X[666]] subc 6 class 0x0019 mthd 0x0180 data 0x00003a04

or:

[ 1226.534609] nouveau E[  PGRAPH][0000:01:00.0]  NOTIFY nsource: PROTECTION_ERROR nstatus: PROTECTION_FAULT
[ 1226.534644] nouveau E[  PGRAPH][0000:01:00.0] ch 1 [X[2044]] subc 2 class 0x0042 mthd 0x0180 data 0x00003a04
[ 1226.534664] nouveau E[  PGRAPH][0000:01:00.0]  NOTIFY nsource: PROTECTION_ERROR nstatus: PROTECTION_FAULT
[ 1226.534680] nouveau E[  PGRAPH][0000:01:00.0] ch 1 [X[2044]] subc 6 class 0x0044 mthd 0x0180 data 0x00003a04
[ 1226.534699] nouveau E[  PGRAPH][0000:01:00.0]  NOTIFY nsource: PROTECTION_ERROR nstatus: PROTECTION_FAULT
[ 1226.534716] nouveau E[  PGRAPH][0000:01:00.0] ch 1 [X[2044]] subc 6 class 0x0043 mthd 0x0180 data 0x00003a04
[ 1226.535080] nouveau E[  PGRAPH][0000:01:00.0]  NOTIFY nsource: PROTECTION_ERROR nstatus: PROTECTION_FAULT
[ 1226.535099] nouveau E[  PGRAPH][0000:01:00.0] ch 1 [X[2044]] subc 6 class 0x0019 mthd 0x0180 data 0x00003a04

The first lines appear at boot. The second ones after a wakeup from S3. However, other wakeup events (from S3 or S4) didn't show the same error. Please see my dmesg.txt attached to bug #68835 for the full output.
Comment 1 Ilia Mirkin 2013-09-02 17:09:11 UTC
Could you also attach the Xorg.0.log file (should be in /var/log/) after you see those errors, hopefully there's something in there too.
Comment 2 Mauro Molinari 2013-09-02 19:04:45 UTC
Created attachment 85086 [details]
Xorg.0.log

Here is the Xorg.0.log captured after boot. I'm going to attach a new dmesg output taken together with this Xorg.0.log, maybe it's easier understand relationships between the two log files...
Comment 3 Mauro Molinari 2013-09-02 19:05:47 UTC
Created attachment 85087 [details]
dmesg output taken after the same boot from which Xorg.0.log was taken
Comment 4 Mauro Molinari 2013-09-02 19:13:11 UTC
By the way, it shouldn't be in any kind related to this, however X starts at 1024x767 at 60 Hz, while my monitor supports up to 1280x1024 (which is its native resolution) at a maximum refresh rate of 75 Hz (72 Hz and 60 Hz also supported). Is this another (separate) problem?
Comment 5 Mauro Molinari 2014-01-28 22:47:05 UTC
I created bug #74164 for the resolution issue cited in comment 4.
Comment 6 Ilia Mirkin 2014-01-28 22:50:55 UTC
I looked into this issue earlier, it looks like the NvNull object being attached to the various DMA_NOTIFY methods of the relevant other objects. Haven't had a chance to check if I also see this on my NV05 yet. That code is shared by all pre-nv50 cards though.
Comment 7 Martin Peres 2019-12-04 08:35:53 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/54.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.