Bugzilla – Bug 15276
text rendering, PGRAPH_ERROR/ILLEGAL_MTHD/PROTECTION_FAULT spam in syslog
Last modified: 2009-02-01 14:12:36 UTC
Created attachment 15578 [details]
syslog & Xorg log
Not sure if these are related, but some text doesn't render and I get PGRAPH_ERROR spam in syslog).
The apps I was using are openbox (text in menu doesn't render), xterm (text renders), epiphany (menu text doesn't render, some website text renders).
I've attached the xorg log and the stretch of syslog (with drm debug=1) when Xorg was active.
I built xorg and nouveau from git yesterday using jhbuild.
The nv driver in Debian sid doesn't have this problem (2.1.8).
What framebuffer driver are you using here ? If it's nvidiafb, it's not supported (this driver stomps all over the card state to the point we can't really maintain it properly).
I don't seem to have any fb driver loaded. I have it installed, but lsmod | grep nvidia only points out the nvidia_agp driver. lsmod | grep fb reports nothing.
There is this line:
Mar 31 16:07:18 morrison kernel: [drm] Used old pci detect: framebuffer loaded
It's either a *fb driver, or the nvidia binary driver, which is bad in any case.
I purged everything from the nvidia 96xx legacy proprietary driver after I verified that it still sucks (used to kernel freeze occasionally, now kernel freezes when X starts) and before starting with nouveau stuff.
Looks like the fb thing was caused by vesafb being compiled into my kernel and having vga=... on the kernel command-line. Without this, I still get the same syslog spam and the text rendering issue. The monitor attached to the computer is now being used on another computer, I'll get you the updated logs later tonight.
Created attachment 15598 [details]
log without vesafb
New log attached without the vesafb thing. Same issues as before.
When I add MigrationHeuristic greedy to xorg.conf the fonts situation is fixed.
I still get the PGRAPH_ERROR syslog spam though.
This is with Debian sid, Linux 2.6.26 and xserver-xorg-video-nouveau 1:0.0.10~git+20090105+7dc567d-1.
Ah, I actually noticed this bug earlier today and was planning on seeing if you still had the hw available. I think I know the issue here, I'll push the fix to xf86-video-nouveau git. If you're able to update afterwards, I'd love to know if it fixes things for you.
Will attempt that (or pester the Debian nouveau maintainer), please let me know when you've pushed the changes and to where.
The fix is in the 2D driver now. If you don't want to wait for the debian maintainers to repackage the updates, you can install the driver yourself from git.
If you start to follow the instructions at http://nouveau.freedesktop.org/wiki/InstallNouveau from step 7 you should be fine.
Applied your patch to the Debian package and now I no longer get the PGRAPH_ERROR spam.
With the patch I can see the fonts fine with or without MigrationHeuristic greedy.
Without the MigrationHeuristic greedy, I see some horizontal pixel breakage on the Debian swirl at xdm after logging in and then logging out. Looks like maybe uninitialised pixels being passed to the GPU, unsure about this.
After building git master, installing nouveau_drv.so and restarting X/xdm I can still see the pixel breakage.
Anyway, I think this bug can be closed now since the fonts and PGRAPH_ERROR things are fixed, thanks heaps!
BTW, the Debian partition on the machine is for development, so if you need me to try anything on it, please let me know (http://bonedaddy.net/pabs3/about/#contact).
BTW, during testing the git master driver, I saw some "Bad page state in process 'Xorg'" messages on the console, the kernel printed a backtrace too:
Bad page state in process 'Xorg'
page:c1000000 flags:0x00000400 mapping:00000000 mapcount:0 count:0
Trying to fix it up, but a reboot is needed
Pid: 5881, comm: Xorg Not tainted 2.6.26-1-686 #1
[<ee92e21f>] agp_generic_destroy_page+0x3a/0x52 [agpgart]
[<ee92e95e>] agp_free_memory+0x8a/0xac [agpgart]
[<eea96240>] drm_agp_free_memory+0xb/0x13 [drm]
[<eea937ca>] drm_free_agp+0x5/0xe [drm]
[<eea914dc>] drm_lastclose+0x150/0x31b [drm]
Thanks for testing, I'll close this bug as fixed. As for your other issues, feel free to file bugs for them so they don't get forgotten :)