Re: kern/49368: 8(?) pixel artifacts in X, eventual kernel crash

[christos%zoulas.com@localhost (Christos Zoulas)]

The following reply was made to PR kern/49368; it has been noted by GNATS.

From: christos%zoulas.com@localhost (Christos Zoulas)
To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost, 
	gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/49368: 8(?) pixel artifacts in X, eventual kernel crash
Date: Thu, 6 Nov 2014 09:56:13 -0500

 On Nov 6,  2:50pm, andrew.cagney%gmail.com@localhost (andrew.cagney%gmail.com@localhost) wrote:
 -- Subject: kern/49368: 8(?) pixel artifacts in X, eventual kernel crash
 
 | >Number:         49368
 | >Category:       kern
 | >Synopsis:       8(?) pixel artifacts in X, eventual kernel crash
 | >Confidential:   no
 | >Severity:       serious
 | >Priority:       medium
 | >Responsible:    kern-bug-people
 | >State:          open
 | >Class:          sw-bug
 | >Submitter-Id:   net
 | >Arrival-Date:   Thu Nov 06 14:50:00 +0000 2014
 | >Originator:     Andrew Cagney
 | >Release:        7.99.1 NetBSD 7.99.1 (GENERIC) #3: Thu Nov  6 09:01:49 UTC 2014
 | >Organization:
 | >Environment:
 | 7.99.1 NetBSD 7.99.1 (GENERIC) #3: Thu Nov  6 09:01:49 UTC 2014 (the UTC is a lie, it is Canada/Eastern)
 | >Description:
 | More of a story, clearly things are going in the right direction:
 | 
 | - installed GENERIC.201410252300Z, noticed laptop was only doing 1024x768 but things stable
 | 
 | - updated kernel to a few days ago, noticed laptop now correctly switches to full 720P but:
 | -- see 8(?) pixel horizontal artifacts being left where things like buttons and icons are being drawn
 | -- shortly after starting firefox things freeze (should probably find another machine to see if it is pingable)
 | 
 | - updated to kernel to just now
 | -- tearing still occurring
 | -- hasn't crashed, yet
 | 
 | -- other info:
 | 
 | running gnome from tip of current pkgsrc branch
 | 
 | Samsung 530U which is pretty standard intel:
 | 
 | cpu0 at mainbus0 apid 0: Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz, id 0x206a7
 | cpu1 at mainbus0 apid 1: Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz, id 0x206a7
 | cpu2 at mainbus0 apid 2: Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz, id 0x206a7
 | cpu3 at mainbus0 apid 3: Intel(R) Core(TM) i5-2467M CPU @ 1.60GHz, id 0x206a7
 | 
 | [    17.081] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 3000
 | [    17.083] (**) intel(0): Relaxed fencing enabled
 | [    17.083] (**) intel(0): Wait on SwapBuffers? enabled
 | [    17.083] (**) intel(0): Triple buffering? enabled
 | [    17.083] (**) intel(0): Framebuffer tiled
 | [    17.083] (**) intel(0): Pixmaps tiled
 | [    17.083] (**) intel(0): 3D buffers tiled
 | [    17.083] (**) intel(0): SwapBuffers wait enabled
 | [    17.083] (==) intel(0): video overlay key set to 0x101fe
 | [    17.084] (II) intel(0): Output LVDS1 has no monitor section
 | [    17.087] (II) intel(0): Output VGA1 has no monitor section
 | [    17.090] (II) intel(0): Output HDMI1 has no monitor section
 | [    17.090] (II) intel(0): Output DP1 has no monitor section
 | [    17.090] (II) intel(0): EDID for output LVDS1
 | 
 
 I think that there are issues with both UXA and SNA that are causing
 different types of corruption depending on the exact model of the card.
 
 Are you using UXA or SNA?
 Does it display correctly if you turn noaccel on?
 What does the corruption look like?
 
 christos