From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 48890] New: dmesg full of DATA_ERROR SEMANTIC_PTSZ_OVER_LIMIT errors on nouveau driver
Date: Wed, 18 Apr 2012 12:12:18 +0000 [thread overview]
Message-ID: <bug-48890-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=48890
Bug #: 48890
Summary: dmesg full of DATA_ERROR SEMANTIC_PTSZ_OVER_LIMIT
errors on nouveau driver
Classification: Unclassified
Product: xorg
Version: git
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: askondro-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 60270
--> https://bugs.freedesktop.org/attachment.cgi?id=60270
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
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-04-18 12:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 12:12 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-48890-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-04-18 20:41 ` [Bug 48890] dmesg full of DATA_ERROR SEMANTIC_PTSZ_OVER_LIMIT errors on nouveau driver bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-18 21:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-18 23:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-19 11:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-24 18:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-25 21:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-04-25 21:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-48890-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.