update Mesa to 17.2.6

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

update Mesa to 17.2.6

Jonathan Gray-11
cd /usr/xenocara/lib
ftp https://mesa.freedesktop.org/archive/mesa-17.2.6.tar.gz
ftp http://jsg.id.au/mesa-update/mesa.diff.gz
tar zxf mesa-17.2.6.tar.gz
gunzip mesa.diff.gz
patch -p0 < mesa.diff

sed -i 's/mesa$/mesa-17.2.6/' Makefile

build xenocara as normal

Builds on at least amd64, i386, sparc64, armv7 and arm64.

I'm interested in reports from people who saw corruption on Intel
graphics during the brief period when Mesa 17.1.6 was in the tree.

Reply | Threaded
Open this post in threaded view
|

Re: update Mesa to 17.2.6

Matthieu Herrb-7
On Mon, Nov 27, 2017 at 08:22:30PM +1100, Jonathan Gray wrote:

> cd /usr/xenocara/lib
> ftp https://mesa.freedesktop.org/archive/mesa-17.2.6.tar.gz
> ftp http://jsg.id.au/mesa-update/mesa.diff.gz
> tar zxf mesa-17.2.6.tar.gz
> gunzip mesa.diff.gz
> patch -p0 < mesa.diff
>
> sed -i 's/mesa$/mesa-17.2.6/' Makefile
>
> build xenocara as normal
>
> Builds on at least amd64, i386, sparc64, armv7 and arm64.
>
> I'm interested in reports from people who saw corruption on Intel
> graphics during the brief period when Mesa 17.1.6 was in the tree.

Hi,

Works for me on my various intel and radeon based machines, including
macppc (with r300). I wasn't seeing the corruption with 17.1.6 though.

I've also checked the it builds and that glxgears works (slowly as
expected) on loongson.
--
Matthieu Herrb

Reply | Threaded
Open this post in threaded view
|

Re: update Mesa to 17.2.6

Bryan Steele-2
On Wed, Dec 13, 2017 at 09:56:32PM +0100, Matthieu Herrb wrote:

> On Mon, Nov 27, 2017 at 08:22:30PM +1100, Jonathan Gray wrote:
> > cd /usr/xenocara/lib
> > ftp https://mesa.freedesktop.org/archive/mesa-17.2.6.tar.gz
> > ftp http://jsg.id.au/mesa-update/mesa.diff.gz
> > tar zxf mesa-17.2.6.tar.gz
> > gunzip mesa.diff.gz
> > patch -p0 < mesa.diff
> >
> > sed -i 's/mesa$/mesa-17.2.6/' Makefile
> >
> > build xenocara as normal
> >
> > Builds on at least amd64, i386, sparc64, armv7 and arm64.
> >
> > I'm interested in reports from people who saw corruption on Intel
> > graphics during the brief period when Mesa 17.1.6 was in the tree.
>
> Hi,
>
> Works for me on my various intel and radeon based machines, including
> macppc (with r300). I wasn't seeing the corruption with 17.1.6 though.
>
> I've also checked the it builds and that glxgears works (slowly as
> expected) on loongson.
> --
> Matthieu Herrb
>

Hi,

The last time the Mesa 17 update came up there was also an issue with
the newly introduced GLSL shader cache with pledge(2), which broke 3d
Accel/WebGL in chromium, at least on radeondrm(4).

Is this still an issue?

On Thu, Aug 24, 2017 at 09:14:53PM -0400, Bryan Steele wrote:

> It's the GPU Process that crashses, not chrome totally, so stuff
> doesn't feel as fast but otherwise works.. except WebGL.
>
> With MESA_GLSL_CACHE_DISABLE
>
> Canvas: Hardware accelerated
> CheckerImaging: Disabled
> Flash: Hardware accelerated
> Flash Stage3D: Hardware accelerated
> Flash Stage3D Baseline profile: Hardware accelerated
> Compositing: Hardware accelerated
> Multiple Raster Threads: Enabled
> Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
> Rasterization: Software only. Hardware acceleration disabled
> Video Decode: Hardware accelerated
> WebGL: Hardware accelerated
> WebGL2: Hardware accelerated
>
> Without MESA_GLSL_CACHE_DISABLE
>
> Canvas: Software only, hardware acceleration unavailable
> CheckerImaging: Disabled
> Flash: Software only, hardware acceleration unavailable
> Flash Stage3D: Software only, hardware acceleration unavailable
> Flash Stage3D Baseline profile: Software only, hardware acceleration
unavailable

> Compositing: Software only, hardware acceleration unavailable
> Multiple Raster Threads: Enabled
> Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
> Rasterization: Software only, hardware acceleration unavailable
> Video Decode: Software only, hardware acceleration unavailable
> WebGL: Hardware accelerated but at reduced performance
> WebGL2: Unavailable
>
> $ ktrace -di
>  73674 chrome   CALL  open(0x178f67579a80,0x10000<O_RDONLY|O_CLOEXEC>)
>  73674 chrome   NAMI
> "/home/brynet/.cache/mesa/de/4387ec406a27454794d3b16d24e\
>  73674 chrome   PLDG  open, "rpath", errno 1 Operation not permitted
>  98110 chrome   CALL  kill(73674,SIGKILL)
>
> -Bryan.

Reply | Threaded
Open this post in threaded view
|

Re: update Mesa to 17.2.6

Bryan Steele-2
On Wed, Dec 13, 2017 at 04:19:03PM -0500, Bryan Steele wrote:

> On Wed, Dec 13, 2017 at 09:56:32PM +0100, Matthieu Herrb wrote:
> > On Mon, Nov 27, 2017 at 08:22:30PM +1100, Jonathan Gray wrote:
> > > cd /usr/xenocara/lib
> > > ftp https://mesa.freedesktop.org/archive/mesa-17.2.6.tar.gz
> > > ftp http://jsg.id.au/mesa-update/mesa.diff.gz
> > > tar zxf mesa-17.2.6.tar.gz
> > > gunzip mesa.diff.gz
> > > patch -p0 < mesa.diff
> > >
> > > sed -i 's/mesa$/mesa-17.2.6/' Makefile
> > >
> > > build xenocara as normal
> > >
> > > Builds on at least amd64, i386, sparc64, armv7 and arm64.
> > >
> > > I'm interested in reports from people who saw corruption on Intel
> > > graphics during the brief period when Mesa 17.1.6 was in the tree.
> >
> > Hi,
> >
> > Works for me on my various intel and radeon based machines, including
> > macppc (with r300). I wasn't seeing the corruption with 17.1.6 though.
> >
> > I've also checked the it builds and that glxgears works (slowly as
> > expected) on loongson.
> > --
> > Matthieu Herrb
> >
>
> Hi,
>
> The last time the Mesa 17 update came up there was also an issue with
> the newly introduced GLSL shader cache with pledge(2), which broke 3d
> Accel/WebGL in chromium, at least on radeondrm(4).
>
> Is this still an issue?

Note; this is similar to the issue we had with ~/.drirc configurations.

https://marc.info/?l=openbsd-cvs&m=145221017502166&w=2
https://marc.info/?l=openbsd-ports-cvs&m=145211683609002&w=2

Reply | Threaded
Open this post in threaded view
|

Re: update Mesa to 17.2.6

Jonathan Gray-11
In reply to this post by Bryan Steele-2
On Wed, Dec 13, 2017 at 04:19:03PM -0500, Bryan Steele wrote:

> On Wed, Dec 13, 2017 at 09:56:32PM +0100, Matthieu Herrb wrote:
> > On Mon, Nov 27, 2017 at 08:22:30PM +1100, Jonathan Gray wrote:
> > > cd /usr/xenocara/lib
> > > ftp https://mesa.freedesktop.org/archive/mesa-17.2.6.tar.gz
> > > ftp http://jsg.id.au/mesa-update/mesa.diff.gz
> > > tar zxf mesa-17.2.6.tar.gz
> > > gunzip mesa.diff.gz
> > > patch -p0 < mesa.diff
> > >
> > > sed -i 's/mesa$/mesa-17.2.6/' Makefile
> > >
> > > build xenocara as normal
> > >
> > > Builds on at least amd64, i386, sparc64, armv7 and arm64.
> > >
> > > I'm interested in reports from people who saw corruption on Intel
> > > graphics during the brief period when Mesa 17.1.6 was in the tree.
> >
> > Hi,
> >
> > Works for me on my various intel and radeon based machines, including
> > macppc (with r300). I wasn't seeing the corruption with 17.1.6 though.
> >
> > I've also checked the it builds and that glxgears works (slowly as
> > expected) on loongson.
> > --
> > Matthieu Herrb
> >
>
> Hi,
>
> The last time the Mesa 17 update came up there was also an issue with
> the newly introduced GLSL shader cache with pledge(2), which broke 3d
> Accel/WebGL in chromium, at least on radeondrm(4).
>
> Is this still an issue?

In Mesa 17.1/17.2 the disk shader cache is not used on Intel graphics
which is why I didn't notice the problem at the time.

Mesa 17.2.8 is now in the tree and unconditionally disables the disk
shader cache on OpenBSD with the same result as setting the disable
environment variable.

Reply | Threaded
Open this post in threaded view
|

Re: update Mesa to 17.2.6

Lauri Tirkkonen-2
In reply to this post by Jonathan Gray-11
Hi,

On Mon, Nov 27 2017 20:22:30 +1100, Jonathan Gray wrote:
> I'm interested in reports from people who saw corruption on Intel
> graphics during the brief period when Mesa 17.1.6 was in the tree.

Sorry for not testing this sooner; I had forgotten about seeing this
corruption previously. Updating to a snapshot just now (from OpenBSD
6.2-current (GENERIC.MP) #305: Thu Dec 21 14:53:41 MST 2017 to OpenBSD
6.2-current (GENERIC.MP) #314: Wed Jan  3 13:14:26 MST 2018) did
result in corruption on my X220 and jogged my memory that I've seen this
problem in the past... dmesg follows.

OpenBSD 6.2-current (GENERIC.MP) #314: Wed Jan  3 13:14:26 MST 2018
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8451125248 (8059MB)
avail mem = 8188076032 (7808MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (64 entries)
bios0: vendor LENOVO version "8DET73WW (1.43 )" date 10/12/2016
bios0: LENOVO 42915CG
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT SSDT DMAR UEFI UEFI UEFI
acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) EHC1(S3) EHC2(S3) HDEF(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2492.26 MHz
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
acpihpet0: recalibrated TSC frequency 2491918253 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.92 MHz
cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.92 MHz
cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2491.92 MHz
cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 2 (EXP1)
acpiprt3 at acpi0: bus 3 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP4)
acpiprt5 at acpi0: bus 13 (EXP5)
acpiprt6 at acpi0: bus -1 (EXP7)
acpicpu0 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu1 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu2 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpicpu3 at acpi0: C3(350@104 io@0x415), C1(1000@1 halt), PSS
acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2
acpitz0 at acpi0: critical temperature is 99 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
"LEN0020" at acpi0 not configured
"SMO1200" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "45N1172" serial   403 type LION oem "SANYO"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
acpidock0 at acpi0: GDCK not docked (0)
acpivideo0 at acpi0: VID_
acpivout at acpivideo0 not configured
acpivideo1 at acpi0: VID_
cpu0: Enhanced SpeedStep 2492 MHz: speeds: 2501, 2500, 2200, 2000, 1800, 1600, 1400, 1200, 1000, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 2G Host" rev 0x09
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 3000" rev 0x09
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1366x768, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel 6 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address f0:de:f1:bc:2d:42
ehci0 at pci0 dev 26 function 0 "Intel 6 Series USB" rev 0x04: apic 2 int 16
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
azalia0 at pci0 dev 27 function 0 "Intel 6 Series HD Audio" rev 0x04: msi
azalia0: codecs: Conexant CX20590, Intel/0x2805, using Conexant CX20590
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 6 Series PCIE" rev 0xb4: msi
pci1 at ppb0 bus 2
ppb1 at pci0 dev 28 function 1 "Intel 6 Series PCIE" rev 0xb4: msi
pci2 at ppb1 bus 3
iwn0 at pci2 dev 0 function 0 "Intel Centrino Advanced-N 6205" rev 0x34: msi, MIMO 2T2R, MoW, address 10:0b:a9:49:23:68
ppb2 at pci0 dev 28 function 4 "Intel 6 Series PCIE" rev 0xb4: msi
pci3 at ppb2 bus 13
sdhc0 at pci3 dev 0 function 0 "Ricoh 5U822 SD/MMC" rev 0x07: apic 2 int 16
sdhc0: SDHC 3.0, 50 MHz base clock
sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed, dma
ehci1 at pci0 dev 29 function 0 "Intel 6 Series USB" rev 0x04: apic 2 int 23
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
pcib0 at pci0 dev 31 function 0 "Intel QM67 LPC" rev 0x04
ahci0 at pci0 dev 31 function 2 "Intel 6 Series AHCI" rev 0x04: msi, AHCI 1.3
ahci0: port 2: 3.0Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 2 lun 0: <ATA, INTEL SSDMCEAC03, LLLi> SCSI3 0/direct fixed naa.55cd2e404bc780d4
sd0: 28626MB, 512 bytes/sector, 58626288 sectors, thin
ichiic0 at pci0 dev 31 function 3 "Intel 6 Series SMBus" rev 0x04: apic 2 int 18
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 4GB DDR3 SDRAM PC3-10600 SO-DIMM
spdmem1 at iic0 addr 0x51: 4GB DDR3 SDRAM PC3-10600 SO-DIMM
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
wsmouse1 at pms0 mux 0
pms0: Synaptics clickpad, firmware 8.0, 0x1e2b1 0x940300
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
aps0 at isa0 port 0x1600/31
vmm0 at mainbus0: VMX/EPT
uhub2 at uhub0 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 2.00/0.00 addr 2
uhub3 at uhub1 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 2.00/0.00 addr 2
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
sd1 at scsibus3 targ 1 lun 0: <OPENBSD, SR CRYPTO, 006> SCSI2 0/direct fixed
sd1: 28623MB, 512 bytes/sector, 58620593 sectors
root on sd1a (1e3f2d2fd0a15e70.a) swap on sd1b dump on sd1b

--
Lauri Tirkkonen | lotheac @ IRCnet

Reply | Threaded
Open this post in threaded view
|

Re: update Mesa to 17.2.6

Jonathan Gray-11
On Fri, Jan 05, 2018 at 12:38:27AM +0200, Lauri Tirkkonen wrote:

> Hi,
>
> On Mon, Nov 27 2017 20:22:30 +1100, Jonathan Gray wrote:
> > I'm interested in reports from people who saw corruption on Intel
> > graphics during the brief period when Mesa 17.1.6 was in the tree.
>
> Sorry for not testing this sooner; I had forgotten about seeing this
> corruption previously. Updating to a snapshot just now (from OpenBSD
> 6.2-current (GENERIC.MP) #305: Thu Dec 21 14:53:41 MST 2017 to OpenBSD
> 6.2-current (GENERIC.MP) #314: Wed Jan  3 13:14:26 MST 2018) did
> result in corruption on my X220 and jogged my memory that I've seen this
> problem in the past... dmesg follows.

I wonder if this is exposing an inteldrm problem.

Does switching to the intel driver with xorg.conf or the below
diff change anything?

Index: xserver/hw/xfree86/common/xf86pciBus.c
===================================================================
RCS file: /cvs/xenocara/xserver/hw/xfree86/common/xf86pciBus.c,v
retrieving revision 1.15
diff -u -p -r1.15 xf86pciBus.c
--- xserver/hw/xfree86/common/xf86pciBus.c 8 Dec 2017 15:02:00 -0000 1.15
+++ xserver/hw/xfree86/common/xf86pciBus.c 4 Jan 2018 22:57:20 -0000
@@ -1192,11 +1192,26 @@ xf86VideoPtrToDriverList(struct pci_devi
  case 0xa011:
  case 0x0042: /* XXX Ironlake is unstable with modesetting */
  case 0x0046:
- /* Use intel driver on 2nd and 3rd generation */
+ /* Sandy Bridge */
+ case 0x0102:
+ case 0x0112:
+ case 0x0122:
+ case 0x010a:
+ case 0x0106:
+ case 0x0116:
+ case 0x0126:
+ /* Ivy Bridge */
+ case 0x0156:
+ case 0x0166:
+ case 0x0152:
+ case 0x0162:
+ case 0x015a:
+ case 0x016a:
+ /* Use intel driver until Ivy Bridge */
  driverList[0] = "intel";
  break;
  default:
- /* Use modesetting driver on 4th generation and up */
+ /* Use modesetting driver on Haswell and up */
  driverList[0] = "modesetting";
  break;
         }

Reply | Threaded
Open this post in threaded view
|

Re: update Mesa to 17.2.6

Theo de Raadt-2
> > On Mon, Nov 27 2017 20:22:30 +1100, Jonathan Gray wrote:
> > > I'm interested in reports from people who saw corruption on Intel
> > > graphics during the brief period when Mesa 17.1.6 was in the tree.

The issue is back.

x230.

run xpdf on a document which large regions of black and white, and
flip between pages.

It looks like something is cached and not being
pushed/invalidated/writethrough.  so it does not make it onto the
screen correctly.  there are cache-streaks which don't update on an
idle machine.

If the machine is very busy, it is hard to see these because the cache
lines get pushed earlier.

But on an idle machine, documents are unreadable.

Reply | Threaded
Open this post in threaded view
|

Re: update Mesa to 17.2.6

Theo de Raadt-2
In reply to this post by Jonathan Gray-11
The diff below helps, and will be in snaps until the situation is
resolved.

> On Fri, Jan 05, 2018 at 12:38:27AM +0200, Lauri Tirkkonen wrote:
> > Hi,
> >
> > On Mon, Nov 27 2017 20:22:30 +1100, Jonathan Gray wrote:
> > > I'm interested in reports from people who saw corruption on Intel
> > > graphics during the brief period when Mesa 17.1.6 was in the tree.
> >
> > Sorry for not testing this sooner; I had forgotten about seeing this
> > corruption previously. Updating to a snapshot just now (from OpenBSD
> > 6.2-current (GENERIC.MP) #305: Thu Dec 21 14:53:41 MST 2017 to OpenBSD
> > 6.2-current (GENERIC.MP) #314: Wed Jan  3 13:14:26 MST 2018) did
> > result in corruption on my X220 and jogged my memory that I've seen this
> > problem in the past... dmesg follows.
>
> I wonder if this is exposing an inteldrm problem.
>
> Does switching to the intel driver with xorg.conf or the below
> diff change anything?
>
> Index: xserver/hw/xfree86/common/xf86pciBus.c
> ===================================================================
> RCS file: /cvs/xenocara/xserver/hw/xfree86/common/xf86pciBus.c,v
> retrieving revision 1.15
> diff -u -p -r1.15 xf86pciBus.c
> --- xserver/hw/xfree86/common/xf86pciBus.c 8 Dec 2017 15:02:00 -0000 1.15
> +++ xserver/hw/xfree86/common/xf86pciBus.c 4 Jan 2018 22:57:20 -0000
> @@ -1192,11 +1192,26 @@ xf86VideoPtrToDriverList(struct pci_devi
>   case 0xa011:
>   case 0x0042: /* XXX Ironlake is unstable with modesetting */
>   case 0x0046:
> - /* Use intel driver on 2nd and 3rd generation */
> + /* Sandy Bridge */
> + case 0x0102:
> + case 0x0112:
> + case 0x0122:
> + case 0x010a:
> + case 0x0106:
> + case 0x0116:
> + case 0x0126:
> + /* Ivy Bridge */
> + case 0x0156:
> + case 0x0166:
> + case 0x0152:
> + case 0x0162:
> + case 0x015a:
> + case 0x016a:
> + /* Use intel driver until Ivy Bridge */
>   driverList[0] = "intel";
>   break;
>   default:
> - /* Use modesetting driver on 4th generation and up */
> + /* Use modesetting driver on Haswell and up */
>   driverList[0] = "modesetting";
>   break;
>          }
>

Reply | Threaded
Open this post in threaded view
|

Re: update Mesa to 17.2.6

Lauri Tirkkonen-2
In reply to this post by Jonathan Gray-11
Hi,

On Fri, Jan 05 2018 10:09:08 +1100, Jonathan Gray wrote:
> Does switching to the intel driver with xorg.conf or the below
> diff change anything?

Yes, with the intel driver the corruption is gone.

However, I updated my work Haswell laptop (x240; cpu0: Intel(R) Core(TM)
i7-4600U CPU @ 2.10GHz, 1995.72 MHz; inteldrm0 at pci0 dev 2 function 0
"Intel HD Graphics" rev 0x0b) and it does exhibit similar corruption;
it's more difficult to notice as it seems to clear away faster but it's
there, at least if you know to look for it (I can provide a shaky-cam
video if you like). It too goes away when switching to intel driver, so
perhaps your diff isn't quite sufficient (although granted, with Haswell
the effect is so much less noticeable, it may not be a problem).

--
Lauri Tirkkonen | lotheac @ IRCnet