Re: [Intel-gfx] Skylake graphics regression: projector failure with 4.8-rc3
On Mon, 19 Sep 2016, James Bottomley wrote: > On Mon, 2016-09-19 at 08:09 -0700, James Bottomley wrote: >> On Sun, 2016-09-18 at 13:35 +0200, Thorsten Leemhuis wrote: >> > Hi! James & Paulo: What's the current status of this? >> >> No, the only interaction has been the suggestion below for a revert, >> which didn't fix the problem. >> >> > Was this issue discussed elsewhere or even fixed in between? Just >> > asking, because this issue is on the list of regressions for 4.8. >> >> >> I'm just about to try out -rc7, but it's not fixed so far. > > OK, with -rc7 and the i915 fixes, there seems to be a marked > improvement. I can no longer crash the crtc by using lots of xrandr > switches, which was the principal problem. > > I've so far only got one of these in the logs > > [14858.635035] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* > CPU pipe B FIFO underrun > > And the only residual problem seems to be that the monitor goes blank > periodically, but this can be fixed by switching resolution a couple of > times. > > I haven't seen any of the link training errors so far and I've run > through my usual battery of be nasty to the external monitor tests. Thanks for the update. We still have fixes for the underruns in the pipeline. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Skylake graphics regression: projector failure with 4.8-rc3
On Mon, 2016-09-19 at 08:09 -0700, James Bottomley wrote: > On Sun, 2016-09-18 at 13:35 +0200, Thorsten Leemhuis wrote: > > Hi! James & Paulo: What's the current status of this? > > No, the only interaction has been the suggestion below for a revert, > which didn't fix the problem. > > > Was this issue discussed elsewhere or even fixed in between? Just > > asking, because this issue is on the list of regressions for 4.8. > > > I'm just about to try out -rc7, but it's not fixed so far. OK, with -rc7 and the i915 fixes, there seems to be a marked improvement. I can no longer crash the crtc by using lots of xrandr switches, which was the principal problem. I've so far only got one of these in the logs [14858.635035] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun And the only residual problem seems to be that the monitor goes blank periodically, but this can be fixed by switching resolution a couple of times. I haven't seen any of the link training errors so far and I've run through my usual battery of be nasty to the external monitor tests. James ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Skylake graphics regression: projector failure with 4.8-rc3
On Sun, 2016-09-18 at 13:35 +0200, Thorsten Leemhuis wrote: > Hi! James & Paulo: What's the current status of this? No, the only interaction has been the suggestion below for a revert, which didn't fix the problem. > Was this issue discussed elsewhere or even fixed in between? Just > asking, because this issue is on the list of regressions for 4.8. I'm just about to try out -rc7, but it's not fixed so far. James > Ciao, Thorsten > > On 01.09.2016 00:25, James Bottomley wrote: > > On Wed, 2016-08-31 at 21:51 +, Zanoni, Paulo R wrote: > > > Em Qua, 2016-08-31 às 14:43 -0700, James Bottomley escreveu: > > > > On Wed, 2016-08-31 at 11:23 -0700, James Bottomley wrote: > > > > > On Fri, 2016-08-26 at 09:10 -0400, James Bottomley wrote: > > > > > > We seem to have an xrandr regression with skylake now. > > > > > > What's > > > > > > happening is that I can get output on to a projector, but > > > > > > the > > > > > > system is losing video when I change the xrandr sessions > > > > > > (like > > > > > > going from a --above b to a --same-as b). The main screen > > > > > > goes > > > > > > blank, which is basically a reboot situation. > > > > > > Unfortunately, I > > > > > > can't seem to get the logs out of systemd to see if there > > > > > > was a > > > > > > dump to dmesg (the system was definitely responding). > > > > > > > > > > > > I fell back to 4.6.2 which worked perfectly, so this is > > > > > > definitely > > > > > > some sort of regression. I'll be able to debug more fully > > > > > > when > > > > > > I > > > > > > get back home from the Linux Security Summit. > > > > > > > > > > I'm home now. Unfortunately, my monitor isn't as problematic > > > > > as > > > > > the > > > > > projector, but by flipping between various modes and > > > > > separating > > > > > and > > > > > overlaying the panels with --above and --same-as (xrandr), I > > > > > can > > > > > eventually get it to the point where the main LCD panel goes > > > > > black > > > > > and can only be restarted by specifying a different mode. > > > > > > > > > > This seems to be associated with these lines in the X > > > > > > > > > > [ 14714.389] (EE) intel(0): failed to set mode: Invalid > > > > > argument > > > > > [22] > > > > > > > > > > But the curious thing is that even if this fails with the > > > > > error > > > > > message once, it may succeed a second time, so it looks to be > > > > > a > > > > > transient error translation problem from the kernel driver. > > > > > > > > > > I've attached the full log below. > > > > > > > > > > This is only with a VGA output. I currently don't have a > > > > > HDMI > > > > > dongle, but I'm in the process of acquiring one. > > > > > > > > After more playing around, I'm getting thousands of these in > > > > the > > > > kernel > > > > log (possibly millions: the log wraps very fast): > > > > > > > > [23504.873606] [drm:intel_dp_start_link_train [i915]] *ERROR* > > > > failed > > > > to train DP, aborting > > > > > > > > And then finally it gives up with > > > > > > > > [25023.770951] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] > > > > *ERROR* CPU pipe B FIFO underrun > > > > [25561.926075] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] > > > > *ERROR* CPU pipe A FIFO underrun > > > > > > > > And the crtc for the VGA output becomes non-responsive to any > > > > configuration command. This requires a reboot and sometimes a > > > > UEFI > > > > variable reset before it comes back. > > > > > > Please see this discussion: > > > https://patchwork.freedesktop.org/patch/103237/ > > > > > > Do you have this patch on your tree? Does the problem go away if > > > you > > > revert it? > > > > Yes, I've got it, it went in in 4.8-rc3 according to git: > > > > commit 58e311b09c319183254d9220c50a533e7157c9ab > > Author: Matt Roper > > Date: Thu Aug 4 14:08:00 2016 -0700 > > > > drm/i915/gen9: Give one extra block per line for SKL plane WM > > calculations > > > > Reverting it causes the secondary display not to sync pretty much > > at > > all. However, in the flickers I can see, it does work OK and > > doesn't > > now crash switching from --same-as to --above and back > > > > I also still get the logs filling up with the link training errors. > > > > On balance, although the behaviour is different, it's not an > > improvement because if I can't sync with the projector, I can't > > really > > use this as a fix. > > > > James > ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Skylake graphics regression: projector failure with 4.8-rc3
Hi! James & Paulo: What's the current status of this? Was this issue discussed elsewhere or even fixed in between? Just asking, because this issue is on the list of regressions for 4.8. Ciao, Thorsten On 01.09.2016 00:25, James Bottomley wrote: > On Wed, 2016-08-31 at 21:51 +, Zanoni, Paulo R wrote: >> Em Qua, 2016-08-31 às 14:43 -0700, James Bottomley escreveu: >>> On Wed, 2016-08-31 at 11:23 -0700, James Bottomley wrote: On Fri, 2016-08-26 at 09:10 -0400, James Bottomley wrote: > We seem to have an xrandr regression with skylake now. What's > happening is that I can get output on to a projector, but the > system is losing video when I change the xrandr sessions (like > going from a --above b to a --same-as b). The main screen goes > blank, which is basically a reboot situation. Unfortunately, I > can't seem to get the logs out of systemd to see if there was a > dump to dmesg (the system was definitely responding). > > I fell back to 4.6.2 which worked perfectly, so this is > definitely > some sort of regression. I'll be able to debug more fully when > I > get back home from the Linux Security Summit. I'm home now. Unfortunately, my monitor isn't as problematic as the projector, but by flipping between various modes and separating and overlaying the panels with --above and --same-as (xrandr), I can eventually get it to the point where the main LCD panel goes black and can only be restarted by specifying a different mode. This seems to be associated with these lines in the X [ 14714.389] (EE) intel(0): failed to set mode: Invalid argument [22] But the curious thing is that even if this fails with the error message once, it may succeed a second time, so it looks to be a transient error translation problem from the kernel driver. I've attached the full log below. This is only with a VGA output. I currently don't have a HDMI dongle, but I'm in the process of acquiring one. >>> >>> After more playing around, I'm getting thousands of these in the >>> kernel >>> log (possibly millions: the log wraps very fast): >>> >>> [23504.873606] [drm:intel_dp_start_link_train [i915]] *ERROR* >>> failed >>> to train DP, aborting >>> >>> And then finally it gives up with >>> >>> [25023.770951] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] >>> *ERROR* CPU pipe B FIFO underrun >>> [25561.926075] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] >>> *ERROR* CPU pipe A FIFO underrun >>> >>> And the crtc for the VGA output becomes non-responsive to any >>> configuration command. This requires a reboot and sometimes a UEFI >>> variable reset before it comes back. >> >> Please see this discussion: >> https://patchwork.freedesktop.org/patch/103237/ >> >> Do you have this patch on your tree? Does the problem go away if you >> revert it? > > Yes, I've got it, it went in in 4.8-rc3 according to git: > > commit 58e311b09c319183254d9220c50a533e7157c9ab > Author: Matt Roper > Date: Thu Aug 4 14:08:00 2016 -0700 > > drm/i915/gen9: Give one extra block per line for SKL plane WM > calculations > > Reverting it causes the secondary display not to sync pretty much at > all. However, in the flickers I can see, it does work OK and doesn't > now crash switching from --same-as to --above and back > > I also still get the logs filling up with the link training errors. > > On balance, although the behaviour is different, it's not an > improvement because if I can't sync with the projector, I can't really > use this as a fix. > > James ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Skylake graphics regression: projector failure with 4.8-rc3
On Wed, 2016-08-31 at 21:51 +, Zanoni, Paulo R wrote: > Hi > > Em Qua, 2016-08-31 às 14:43 -0700, James Bottomley escreveu: > > On Wed, 2016-08-31 at 11:23 -0700, James Bottomley wrote: > > > > > > On Fri, 2016-08-26 at 09:10 -0400, James Bottomley wrote: > > > > > > > > We seem to have an xrandr regression with skylake now. What's > > > > happening is that I can get output on to a projector, but the > > > > system is losing video when I change the xrandr sessions (like > > > > going from a --above b to a --same-as b). The main screen goes > > > > blank, which is basically a reboot situation. Unfortunately, I > > > > can't seem to get the logs out of systemd to see if there was a > > > > dump to dmesg (the system was definitely responding). > > > > > > > > I fell back to 4.6.2 which worked perfectly, so this is > > > > definitely > > > > some sort of regression. I'll be able to debug more fully when > > > > I > > > > get back home from the Linux Security Summit. > > > > > > I'm home now. Unfortunately, my monitor isn't as problematic as > > > the > > > projector, but by flipping between various modes and separating > > > and > > > overlaying the panels with --above and --same-as (xrandr), I can > > > eventually get it to the point where the main LCD panel goes > > > black > > > and can only be restarted by specifying a different mode. > > > > > > This seems to be associated with these lines in the X > > > > > > [ 14714.389] (EE) intel(0): failed to set mode: Invalid argument > > > [22] > > > > > > But the curious thing is that even if this fails with the error > > > message once, it may succeed a second time, so it looks to be a > > > transient error translation problem from the kernel driver. > > > > > > I've attached the full log below. > > > > > > This is only with a VGA output. I currently don't have a HDMI > > > dongle, but I'm in the process of acquiring one. > > > > After more playing around, I'm getting thousands of these in the > > kernel > > log (possibly millions: the log wraps very fast): > > > > [23504.873606] [drm:intel_dp_start_link_train [i915]] *ERROR* > > failed > > to train DP, aborting > > > > And then finally it gives up with > > > > [25023.770951] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] > > *ERROR* CPU pipe B FIFO underrun > > [25561.926075] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] > > *ERROR* CPU pipe A FIFO underrun > > > > And the crtc for the VGA output becomes non-responsive to any > > configuration command. This requires a reboot and sometimes a UEFI > > variable reset before it comes back. > > Please see this discussion: > https://patchwork.freedesktop.org/patch/103237/ > > Do you have this patch on your tree? Does the problem go away if you > revert it? Yes, I've got it, it went in in 4.8-rc3 according to git: commit 58e311b09c319183254d9220c50a533e7157c9ab Author: Matt Roper Date: Thu Aug 4 14:08:00 2016 -0700 drm/i915/gen9: Give one extra block per line for SKL plane WM calculations Reverting it causes the secondary display not to sync pretty much at all. However, in the flickers I can see, it does work OK and doesn't now crash switching from --same-as to --above and back I also still get the logs filling up with the link training errors. On balance, although the behaviour is different, it's not an improvement because if I can't sync with the projector, I can't really use this as a fix. James ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Skylake graphics regression: projector failure with 4.8-rc3
Hi Em Qua, 2016-08-31 às 14:43 -0700, James Bottomley escreveu: > On Wed, 2016-08-31 at 11:23 -0700, James Bottomley wrote: > > > > On Fri, 2016-08-26 at 09:10 -0400, James Bottomley wrote: > > > > > > We seem to have an xrandr regression with skylake now. What's > > > happening is that I can get output on to a projector, but the > > > system is losing video when I change the xrandr sessions (like > > > going from a --above b to a --same-as b). The main screen goes > > > blank, which is basically a reboot situation. Unfortunately, I > > > can't seem to get the logs out of systemd to see if there was a > > > dump to dmesg (the system was definitely responding). > > > > > > I fell back to 4.6.2 which worked perfectly, so this is > > > definitely > > > some sort of regression. I'll be able to debug more fully when > > > I > > > get back home from the Linux Security Summit. > > > > I'm home now. Unfortunately, my monitor isn't as problematic as > > the > > projector, but by flipping between various modes and separating and > > overlaying the panels with --above and --same-as (xrandr), I can > > eventually get it to the point where the main LCD panel goes black > > and can only be restarted by specifying a different mode. > > > > This seems to be associated with these lines in the X > > > > [ 14714.389] (EE) intel(0): failed to set mode: Invalid argument > > [22] > > > > But the curious thing is that even if this fails with the error > > message once, it may succeed a second time, so it looks to be a > > transient error translation problem from the kernel driver. > > > > I've attached the full log below. > > > > This is only with a VGA output. I currently don't have a HDMI > > dongle, but I'm in the process of acquiring one. > > After more playing around, I'm getting thousands of these in the > kernel > log (possibly millions: the log wraps very fast): > > [23504.873606] [drm:intel_dp_start_link_train [i915]] *ERROR* failed > to train DP, aborting > > And then finally it gives up with > > [25023.770951] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] > *ERROR* CPU pipe B FIFO underrun > [25561.926075] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] > *ERROR* CPU pipe A FIFO underrun > > And the crtc for the VGA output becomes non-responsive to any > configuration command. This requires a reboot and sometimes a UEFI > variable reset before it comes back. Please see this discussion: https://patchwork.freedesktop.org/patch/103237/ Do you have this patch on your tree? Does the problem go away if you revert it? Thanks, Paulo > > James > > ___ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Skylake graphics regression: projector failure with 4.8-rc3
On Wed, 2016-08-31 at 11:23 -0700, James Bottomley wrote: > On Fri, 2016-08-26 at 09:10 -0400, James Bottomley wrote: > > We seem to have an xrandr regression with skylake now. What's > > happening is that I can get output on to a projector, but the > > system is losing video when I change the xrandr sessions (like > > going from a --above b to a --same-as b). The main screen goes > > blank, which is basically a reboot situation. Unfortunately, I > > can't seem to get the logs out of systemd to see if there was a > > dump to dmesg (the system was definitely responding). > > > > I fell back to 4.6.2 which worked perfectly, so this is definitely > > some sort of regression. I'll be able to debug more fully when I > > get back home from the Linux Security Summit. > > I'm home now. Unfortunately, my monitor isn't as problematic as the > projector, but by flipping between various modes and separating and > overlaying the panels with --above and --same-as (xrandr), I can > eventually get it to the point where the main LCD panel goes black > and can only be restarted by specifying a different mode. > > This seems to be associated with these lines in the X > > [ 14714.389] (EE) intel(0): failed to set mode: Invalid argument [22] > > But the curious thing is that even if this fails with the error > message once, it may succeed a second time, so it looks to be a > transient error translation problem from the kernel driver. > > I've attached the full log below. > > This is only with a VGA output. I currently don't have a HDMI > dongle, but I'm in the process of acquiring one. After more playing around, I'm getting thousands of these in the kernel log (possibly millions: the log wraps very fast): [23504.873606] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to train DP, aborting And then finally it gives up with [25023.770951] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun [25561.926075] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun And the crtc for the VGA output becomes non-responsive to any configuration command. This requires a reboot and sometimes a UEFI variable reset before it comes back. James ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] Skylake graphics regression: projector failure with 4.8-rc3
On Fri, 2016-08-26 at 09:10 -0400, James Bottomley wrote: > We seem to have an xrandr regression with skylake now. What's > happening is that I can get output on to a projector, but the system > is losing video when I change the xrandr sessions (like going from a > --above b to a --same-as b). The main screen goes blank, which is > basically a reboot situation. Unfortunately, I can't seem to get the > logs out of systemd to see if there was a dump to dmesg (the system > was definitely responding). > > I fell back to 4.6.2 which worked perfectly, so this is definitely > some sort of regression. I'll be able to debug more fully when I get > back home from the Linux Security Summit. I'm home now. Unfortunately, my monitor isn't as problematic as the projector, but by flipping between various modes and separating and overlaying the panels with --above and --same-as (xrandr), I can eventually get it to the point where the main LCD panel goes black and can only be restarted by specifying a different mode. This seems to be associated with these lines in the X [ 14714.389] (EE) intel(0): failed to set mode: Invalid argument [22] But the curious thing is that even if this fails with the error message once, it may succeed a second time, so it looks to be a transient error translation problem from the kernel driver. I've attached the full log below. This is only with a VGA output. I currently don't have a HDMI dongle, but I'm in the process of acquiring one. James [30.672] X.Org X Server 1.17.2 Release Date: 2015-06-16 [30.672] X Protocol Version 11, Revision 0 [30.672] Build Operating System: openSUSE SUSE LINUX [30.672] Current Operating System: Linux jarvis 4.8.0-rc3+ #12 SMP PREEMPT Mon Aug 22 08:16:45 EDT 2016 x86_64 [30.672] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-test root=UUID=994363fd-c12c-4c6c-92e9-85e8ac695cf9 ro resume=/dev/nvme0n1p2 splash=silent quiet showopts pcie_aspm=force [30.672] Build Date: 07 March 2016 08:22:28AM [30.672] [30.672] Current version of pixman: 0.32.6 [30.672] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [30.672] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [30.673] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Aug 31 07:10:56 2016 [30.673] (==) Using config directory: "/etc/X11/xorg.conf.d" [30.673] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [30.673] (==) No Layout section. Using the first Screen section. [30.673] (==) No screen section available. Using defaults. [30.673] (**) |-->Screen "Default Screen Section" (0) [30.673] (**) | |-->Monitor "" [30.673] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [30.673] (==) Automatically adding devices [30.673] (==) Automatically enabling devices [30.673] (==) Automatically adding GPU devices [30.674] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist. [30.674] Entry deleted from font path. [30.674] (==) FontPath set to: /usr/share/fonts/misc:unscaled, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi:unscaled, /usr/share/fonts/75dpi:unscaled, /usr/share/fonts/ghostscript/, /usr/share/fonts/cyrillic:unscaled, /usr/share/fonts/truetype/, built-ins [30.674] (==) ModulePath set to "/usr/lib64/xorg/modules" [30.674] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [30.674] (II) Loader magic: 0x80dd00 [30.674] (II) Module ABI versions: [30.674] X.Org ANSI C Emulation: 0.4 [30.674] X.Org Video Driver: 19.0 [30.674] X.Org XInput driver : 21.0 [30.674] X.Org Server Extension : 9.0 [30.675] (++) using VT number 7 [30.675] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [30.675] (II) xfree86: Adding drm device (/dev/dri/card0) [30.688] (--) PCI:*(0:0:2:0) 8086:1916:1028:0704 rev 7, Mem @ 0xdb00/16777216, 0x9000/268435456, I/O @ 0xf000/64, BIOS @ 0x/131072 [30.688] (II) LoadModule: "glx" [30.689] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [30.691] (II) Module glx: vendor="X.Org Foundation" [30.691] compiled for 1.17.2, module version = 1.0.0 [30.691] ABI class: X.Org Server Extension, version 9.0 [30.691] (==) AIGLX enabled [30.691] (==) Matched intel as autoconfigured driver 0 [30.691] (==) Matched intel as autoconfigured driver 1 [30.691] (==) Matched modesetting as autoconfigured driver 2 [30.691] (==) Matched fbdev as autoconfigured driver 3 [30.691] (==) Matched vesa as autoconfigured driver 4 [30.691] (==) Assigned the driver to t
Re: [Intel-gfx] Skylake graphics regression: projector failure with 4.8-rc3
On Fri, 2016-08-26 at 09:10 -0400, James Bottomley wrote: > We seem to have an xrandr regression with skylake now. What's > happening is that I can get output on to a projector, but the system > is losing video when I change the xrandr sessions (like going from a > --above b to a --same-as b). The main screen goes blank, which is > basically a reboot situation. Unfortunately, I can't seem to get the > logs out of systemd to see if there was a dump to dmesg (the system > was definitely responding). > > I fell back to 4.6.2 which worked perfectly, so this is definitely > some sort of regression. I'll be able to debug more fully when I get > back home from the Linux Security Summit. Sorry, ignore the logs: they're from a previous bug; as I said I'll try to gather logs when I get back to a more controlled environment over the weekend. James ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
