Summary: | [NV92] errors when starts gnome-shell - INVALID_VALUE class 0x8297 mthd 0x0e04 data 0xfebf0000 | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | mattia.b89 <mattia.b89> | ||||
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | minor | ||||||
Priority: | medium | ||||||
Version: | unspecified | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Are there any rendering issues, or just these errors? $ lookup -a 92 -d NV01_SUBCHAN -- -v obj-class NV84_3D e04 0xfebf0000 SCISSOR_HORIZ[0] => { MIN = 0 | MAX = 65215 } $ lookup -a 92 -d NV01_SUBCHAN -- -v obj-class NV84_3D e08 0xfebf0000 SCISSOR_VERT[0] => { MIN = 0 | MAX = 65215 } Those indeed appear to be invalid. I thought I had a thing clamping the value... What version of mesa are you using? Hm, looks like the clamping is missing on the blit_3d path, but that'd only be an issue if someone had specified negative scissor bounds... hopefully the upper layers disallow that. (In reply to comment #1) > Are there any rendering issues, or just these errors? > > $ lookup -a 92 -d NV01_SUBCHAN -- -v obj-class NV84_3D e04 0xfebf0000 > SCISSOR_HORIZ[0] => { MIN = 0 | MAX = 65215 } > $ lookup -a 92 -d NV01_SUBCHAN -- -v obj-class NV84_3D e08 0xfebf0000 > SCISSOR_VERT[0] => { MIN = 0 | MAX = 65215 } > > Those indeed appear to be invalid. I thought I had a thing clamping the > value... What version of mesa are you using? > > Hm, looks like the clamping is missing on the blit_3d path, but that'd only > be an issue if someone had specified negative scissor bounds... hopefully > the upper layers disallow that. probably I have that issue/artifact: sometime, portion of a window isn't drawed but because simply gray mesa-10.1.3-1 I don't have "lookup" command and I don't find how to get it....teach it to me (In reply to comment #2) > probably I have that issue/artifact: sometime, portion of a window isn't > drawed but because simply gray > > mesa-10.1.3-1 Can you check if this still happens with mesa 10.2-rc3? This should have the clamping logic I mentioned above. (Except in the 3d blit path, but I'm hoping that's not the issue.) > > I don't have "lookup" command and I don't find how to get it....teach it to > me lookup is from envytools. You shouldn't need to use it, unless you're interested in nouveau dev. That was just to decode the errors. (In reply to comment #3) > (In reply to comment #2) > > probably I have that issue/artifact: sometime, portion of a window isn't > > drawed but because simply gray > > > > mesa-10.1.3-1 > > Can you check if this still happens with mesa 10.2-rc3? This should have the > clamping logic I mentioned above. (Except in the 3d blit path, but I'm > hoping that's not the issue.) > at the moment I can't try, but when I can I'll do it ! > > > > I don't have "lookup" command and I don't find how to get it....teach it to > > me > > lookup is from envytools. You shouldn't need to use it, unless you're > interested in nouveau dev. That was just to decode the errors. with mesa-10.1.4-1 the issue remain is! with mesa 10.2.0rc4 I haven't the issue I mark this bug as solved |
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.
Created attachment 99275 [details] log from dmesg I get these two non-fatal errors with gnome-shell: [ 164.903589] nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_VALUE [ 164.903603] nouveau E[ PGRAPH][0000:01:00.0] ch 4 [0x003f92b000 gnome-shell[1242]] subc 3 class 0x8297 mthd 0x0e04 data 0xfebf0000 [ 164.903616] nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_VALUE [ 164.903622] nouveau E[ PGRAPH][0000:01:00.0] ch 4 [0x003f92b000 gnome-shell[1242]] subc 3 class 0x8297 mthd 0x0e08 data 0xffc70000 my configuration: x86_64 archlinux kernel-3.14.2-1 xf86-video-nouveau-1.0.10-2 gnome-shell-3.12.2-1