Bug 48890 - dmesg full of DATA_ERROR SEMANTIC_PTSZ_OVER_LIMIT errors on nouveau driver
Summary: dmesg full of DATA_ERROR SEMANTIC_PTSZ_OVER_LIMIT errors on nouveau driver
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: git
Hardware: Other Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-18 12:12 UTC by Alen Skondro
Modified: 2012-04-25 14:23 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg log (495.48 KB, text/plain)
2012-04-18 12:12 UTC, Alen Skondro
no flags Details

Description Alen Skondro 2012-04-18 12:12:18 UTC
Created attachment 60270 [details]
dmesg log

I have a GTX260 (NV50 I guess) and currently I'm getting a lot of DATA_ERROR SEMANTIC_PTSZ_OVER_LIMIT errors in dmesg.

Whenever I see that Chrome has some rendering issues I look in the dmesg log file and see all the errors mentioned above.

I can't say for sure that only Chrome produces these errors... 

My system is:
Linux arch 3.4.0-1-mainline #1 SMP PREEMPT Mon Apr 16 23:30:21 CEST 2012 x86_64 Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux

- mesa (latest from git)
- libdrm (latest from git)
- xf86-video-nouveau (latest from git)
- xserver 1.12.1
Comment 1 Christoph Bumiller 2012-04-18 13:41:44 UTC
Could you provide the commit id you're at please ? I thought I'd fixed this issue with e55c276255db9cba0a3b6780913a1e924cb6ff6b.
Comment 2 Alen Skondro 2012-04-18 14:35:30 UTC
Sorry, I couldn't find out on which commit exactly I was so I rebuilt mesa with the latest commit 86f53e6d6bd07e2bc3ffcadeb9a4418fbae06e0b.

dmesg is still showing the same errors.

Tell me if need anything else.
Comment 3 Christoph Bumiller 2012-04-18 16:38:47 UTC
Thanks, it would be nice to know the version of Chrome you're using and a specific action / site that triggers the error.
Comment 4 Alen Skondro 2012-04-19 04:58:16 UTC
Chrome version is 20.

I think that all sites produce this.
In fact, as soon as I open chrome the errors start to appear.
Comment 5 Christoph Bumiller 2012-04-24 11:29:36 UTC
Found an application that produces the same error, I hope it's fixed now (with mesa commit 29a0c8cd60b6e1fc9ad39e626852ce598fe4d2b4).
Comment 6 Alen Skondro 2012-04-25 14:04:48 UTC
Confirmed, there are no error messages anymore.

Thank you!


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.