Re: 7.0_BETA on Ivy Bridge

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Fri, Jan 16, 2015 at 11:13:05AM +0000, Jaap Boender wrote:
> Hello,
> 
> I've compiled 7.0_BETA on this machine:
> NetBSD purcell.uni.mdx.ac.uk 7.0_BETA NetBSD 7.0_BETA (PURCELL) #1: 
> Tue Jan 13 16:19:01 GMT 2015  
> jaap1%purcell.uni.mdx.ac.uk@localhost:/usr/obj/sys/arch/amd64/compile/PURCELL 
> amd64
> 
> dmesg:
> [...]
> acpivga0 at acpi0 (VID): ACPI Display Adapter
> acpiout0 at acpivga0 (CRT, 0x0100): ACPI Display Output Device
> acpiout1 at acpivga0 (LCD, 0x0400): ACPI Display Output Device
> acpiout1: brightness levels: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 
> 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 
> 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 
> 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 
> 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
> acpiout2 at acpivga0 (DVI, 0x0302): ACPI Display Output Device
> acpiout3 at acpivga0 (DVI2, 0x0303): ACPI Display Output Device
> acpiout4 at acpivga0 (DVI3, 0x0304): ACPI Display Output Device
> acpiout5 at acpivga0 (DP, 0x0300): ACPI Display Output Device
> acpiout6 at acpivga0 (DP2, 0x0301): ACPI Display Output Device
> acpiout7 at acpivga0 (DP3, 0x0305): ACPI Display Output Device
> acpivga0: connected output devices:
> acpivga0:   0x0100 (acpiout0): Ext. Monitor, head 0
> acpivga0:   0x0400 (acpiout1): Unknown Output Device, head 0
> acpivga0:   0x0302 (acpiout2): Unknown Output Device, head 0
> acpivga0:   0x0303 (acpiout3): Unknown Output Device, head 0
> acpivga0:   0x0300 (acpiout5): Unknown Output Device, head 0
> acpivga0:   0x0301 (acpiout6): Unknown Output Device, head 0
> acpivga0:   0x0304 (acpiout4): Unknown Output Device, head 0
> acpivga0:   0x0305 (acpiout7): Unknown Output Device, head 0
> [...]
> i915drmkms0 at pci0 dev 2 function 0: Intel Ivy Bridge Integrated 
> Graphics Device (rev. 0x09)
> drm: Memory usable by graphics device = 2048M
> drm: Supports vblank timestamp caching Rev 2 (21.10.2013).
> drm: Driver supports precise vblank timestamp query.
> i915drmkms0: interrupting at ioapic0 pin 16 (i915)
> intelfb0 at i915drmkms0
> i915drmkms0: info: registered panic notifier
> intelfb0: framebuffer at 0xffff80008e616000, size 1366x768, depth 32, 
> stride 5504
> wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 emulation), 
> using wskbd0
> wsmux1: connecting to wsdisplay0
> 
> Acceleration works, and everything looks fine at first, but after a while I 
> start getting artifacts all over the place - up to the point where my 
> screen looks like the attached screenshot.
> 
> It's interesting that the system still remains vaguely usable: when I 
> maximise a window, for example, it will redraw well (no artifacts at least 
> in the contents; the KWin parts will remain garbled) but this doesn't 
> really last.
> 
> Anyone seeing this as well, and is there anything I can do to help 
> debug it?

It looks like what I'm seeing with opencpn running on a 965GM
(inside the opencpn window, not on the backgound, but this may be
dependant on the window manager - I'm using fvwm2)

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--