Bug 24271 - PGRAPH_ERROR , often after suspend/resume
Summary: PGRAPH_ERROR , often after suspend/resume
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: 7.4 (2008.09)
Hardware: Other All
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-01 23:59 UTC by Xavier
Modified: 2011-02-15 03:04 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
boot into X, first suspend/resume went fine, second suspend/resume triggered the PGRAPH_ERROR (210.59 KB, text/plain)
2009-10-01 23:59 UTC, Xavier
no flags Details
xorg log. I am using X 1.7 now but had the exact same problem on 1.6 (22.56 KB, text/plain)
2009-10-02 00:03 UTC, Xavier
no flags Details

Description Xavier 2009-10-01 23:59:55 UTC
Created attachment 29993 [details]
boot into X, first suspend/resume went fine, second suspend/resume triggered the PGRAPH_ERROR

Almost every time I suspend/resume, a PGRAPH_ERROR appears in dmesg. I cannot see any bad consequences of it, but it doesn't seem normal so I thought I would report it.

[  327.678728] [drm] nouveau 0000:01:00.0: PGRAPH_ERROR - nSource: PROTECTION_ERROR DMA_R_PROTECTION, nStatus:
[  327.678734] [drm] nouveau 0000:01:00.0: PGRAPH_ERROR - Ch 1/1 Class 0x502d Mthd 0x08dc Data 0x00000000:0x00000060
[  327.678736] [drm] nouveau 0000:01:00.0: magic set 1:
[  327.678739] [drm] nouveau 0000:01:00.0: 	0x00408900: 0x80000077
[  327.678743] [drm] nouveau 0000:01:00.0: 	0x00408904: 0xfbef7fff
[  327.678746] [drm] nouveau 0000:01:00.0: 	0x00408908: 0xfff5dfff
[  327.678749] [drm] nouveau 0000:01:00.0: 	0x0040890c: 0xc000d7eb
[  327.678752] [drm] nouveau 0000:01:00.0: 	0x00408910: 0xffff3fef
[  327.678756] [drm] nouveau 0000:01:00.0: 	0x00408e08: 0x800bbf61
[  327.678760] [drm] nouveau 0000:01:00.0: 	0x00408e0c: 0x00000000
[  327.678763] [drm] nouveau 0000:01:00.0: 	0x00408e10: 0xf6e27b40
[  327.678766] [drm] nouveau 0000:01:00.0: 	0x00408e14: 0x0000007f
[  327.678769] [drm] nouveau 0000:01:00.0: 	0x00408e18: 0x001948a8
[  327.678772] [drm] nouveau 0000:01:00.0: 	0x00408e1c: 0x3dfdb57d
[  327.678775] [drm] nouveau 0000:01:00.0: 	0x00408e20: 0x063f3f6b
[  327.678778] [drm] nouveau 0000:01:00.0: 	0x00408e24: 0x0f33037f
[  327.678781] [drm] nouveau 0000:01:00.0: magic set 2:
[  327.678784] [drm] nouveau 0000:01:00.0: 	0x00409900: 0x8000007f
[  327.678787] [drm] nouveau 0000:01:00.0: 	0x00409904: 0xdf677bdf
[  327.678790] [drm] nouveau 0000:01:00.0: 	0x00409908: 0xfdffbfdf
[  327.678793] [drm] nouveau 0000:01:00.0: 	0x0040990c: 0xc000defd
[  327.678796] [drm] nouveau 0000:01:00.0: 	0x00409910: 0xfffd3fef
[  327.678801] [drm] nouveau 0000:01:00.0: 	0x00409e08: 0x800c8a49
[  327.678804] [drm] nouveau 0000:01:00.0: 	0x00409e0c: 0x00000000
[  327.678807] [drm] nouveau 0000:01:00.0: 	0x00409e10: 0xf5fb6d60
[  327.678810] [drm] nouveau 0000:01:00.0: 	0x00409e14: 0x000000fa
[  327.678813] [drm] nouveau 0000:01:00.0: 	0x00409e18: 0x44906309
[  327.678816] [drm] nouveau 0000:01:00.0: 	0x00409e1c: 0xfafefee7
[  327.678819] [drm] nouveau 0000:01:00.0: 	0x00409e20: 0x05277f78
[  327.678822] [drm] nouveau 0000:01:00.0: 	0x00409e24: 0x0b33037f
Comment 1 Xavier 2009-10-02 00:03:03 UTC
Created attachment 29994 [details]
xorg log. I am using X 1.7 now but had the exact same problem on 1.6
Comment 2 Ben Skeggs 2009-10-02 01:24:44 UTC
The message is harmless.  You'll also so it on the first X startup after a cold boot in all likelihood.  The cause isn't known exactly, but I suspect it's random garbage in the card's error reporting regs and not an actual error per se.

I haven't been able to track down exactly how to avoid it as of yet.

So, as long as everything works fine, ignore the message :)
Comment 3 Xavier 2009-10-02 01:32:20 UTC
In my situation, it indeed looks totally harmless. Though pgraph errors seemed to be often associated with more severe problems in the past (as I found in irc log or in the bugtracker), so I was a bit unsure. Good to know I can safely ignore it :)

For some reasons, it seems more likely to trigger after suspend/resume than on a fresh boot. I saw it many times after suspend/resume and only once after a cold boot. But well that probably does not help.

Anyway, everything works fine, no big deal !
Comment 4 Xavier 2011-02-15 03:04:11 UTC
I didn't see these for a very long time.


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.