From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 51144] New: significant pixel corruption in text
Date: Fri, 15 Jun 2012 23:26:27 +0000 [thread overview]
Message-ID: <bug-51144-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=51144
Bug #: 51144
Summary: significant pixel corruption in text
Classification: Unclassified
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: basile-VdE74OAlGqnvXjIo7pOF+l6hYfS7NtTn@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 63099
--> https://bugs.freedesktop.org/attachment.cgi?id=63099
photo of screen portion with corrupted text pixels
(perhaps bug similar to 20363)
with latest git of xf86-video-nouveau:
commit 36d3f8c28c55c05ccf4efa985831d2d249bad2fe
Author: Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date: Wed Jun 13 22:41:58 2012 +1000
dri2: kill debug spam
Signed-off-by: Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
with latest git of drm
% git log
commit d1fcfb17b9642ae351b03056a27b328f314ca80a
Author: Jerome Glisse <jglisse-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date: Tue Jun 12 18:09:55 2012 -0400
radeon: force 1D array mode for z/stencil surface
On r6xx or evergreen z/stencil surface don't support linear or
linear aligned surface, force 1D tiled mode for those.
Signed-off-by: Jerome Glisse <jglisse-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
=======================================
hardware (bought last week, june 2012):
motherboard ASUS P8Z77-V
Intel(R) Core(TM) i7-3770K CPU
one graphic card Gigabyte GTS 450
16Gb RAM, SSD disk + Sata disks
=========================
kernel: Linux 3.4.2 AMD64 (downloaded from kernel.org, compiled thru make-kpkg)
% lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller
(rev 09)
00:01.0 PCI bridge: Intel Corporation 3rd Gen Core processor PCI Express Root
Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series Chipset Family USB xHCI Host
Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series Chipset Family MEI
Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network
Connection (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series Chipset Family USB Enhanced
Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series Chipset Family High Definition
Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series Chipset Family PCI Express Root
Port 1 (rev c4)
00:1c.3 PCI bridge: Intel Corporation 7 Series Chipset Family PCI Express Root
Port 4 (rev c4)
00:1c.4 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c4)
00:1c.7 PCI bridge: Intel Corporation 7 Series Chipset Family PCI Express Root
Port 8 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series Chipset Family USB Enhanced
Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Z77 Express Chipset LPC Controller (rev
04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA
AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series Chipset Family SMBus Controller (rev
04)
01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTS 450]
(rev a1)
01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller
(rev a1)
03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller
(rev 01)
04:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge
(rev 03)
06:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host
Controller
--
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-06-15 23:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 23:26 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-51144-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-06-15 23:33 ` [Bug 51144] significant pixel corruption in text ; driver nouveau - GF116 [GeForce GTS 450] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 6:28 ` [Bug 51144] significant pixel corruption in text bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 6:31 ` [Bug 51144] significant pixel corruption in text nouveau - GF116 [GeForce GTS 450] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 6:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 6:37 ` [Bug 51144] significant pixel corruption in text ; driver " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 6:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 10:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 10:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-16 12:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-17 22:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-18 5:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-28 11:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-28 17:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-03 8:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-03 14:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-03 15:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-03 15:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-05 11:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-12 1:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-26 2:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27 2:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27 5:32 ` 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-51144-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.