Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm: Handle connector tile support only for modes that match tile size

On 12/17/19 1:59 AM, Manasi Navare wrote: On Fri, Dec 13, 2019 at 10:54:55AM +0200, Tomi Sarvela wrote: On 12/12/19 11:28 PM, Manasi Navare wrote: The KBL failure does not look related to the changes in this patch series. Tomi, could you confirm if this is a false negative? Manasi

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm: Handle connector tile support only for modes that match tile size

On 12/12/19 11:28 PM, Manasi Navare wrote: The KBL failure does not look related to the changes in this patch series. Tomi, could you confirm if this is a false negative? Manasi The failures with the patchset seem same as all the other results from live_gt_pm: just that kbl-x1275 hasn't been

Re: [Intel-gfx] [PATCH i-g-t] intel-ci: Relegate gem_exec_reloc to the shards

overall -- and hopefully without losing any of the predictive failure coverage in BAT. This stagnant bit of uAPI/uABI will remain checked by the irregular idle runs. Signed-off-by: Chris Wilson Cc: Joonas Lahtinen Cc: Tomi Sarvela Cc: Petri Latvala Cc: Martin Peres Before Joonas went fishing

Re: [Intel-gfx] [PATCH] drm/i915: Enable refcount debugging for default debug levels

On 6/13/19 3:46 PM, Rodrigo Vivi wrote: On Thu, Jun 13, 2019 at 01:28:42PM +0100, Chris Wilson wrote: refcount_t is our first line of defence against use-after-free, so let's enable it for debugging. It seems a nice thing to have on debug by default and they promise no performance impact.

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/icl: Set GCP_COLOR_INDICATION only for 10/12 bit deep color (rev8)

On 5/4/19 8:55 AM, Saarinen, Jani wrote: Hi, -Original Message- From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of Aditya Swarup Sent: lauantai 4. toukokuuta 2019 2.04 To: intel-gfx@lists.freedesktop.org Cc: Peres, Martin Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT:

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for IRQ initialization debloat and conversion to uncore (rev2)

On 4/12/19 11:57 PM, Paulo Zanoni wrote: Em qui, 2019-04-11 às 01:08 +, Patchwork escreveu: == Series Details == Series: IRQ initialization debloat and conversion to uncore (rev2) URL : https://patchwork.freedesktop.org/series/59202/ State : success So, this is the BAT email I got

Re: [Intel-gfx] [PATCH] firmware/dmc/icl: load v1.07 on icelake.

On 08/02/2018 10:15 AM, Tomi Sarvela wrote: On 08/02/2018 08:11 AM, Rodrigo Vivi wrote: On Wed, Aug 01, 2018 at 05:30:49PM -0700, Paulo Zanoni wrote: Em Qua, 2018-08-01 às 17:07 -0700, Anusha Srivatsa escreveu: Add Support to load DMC on Icelake. While at it, also add support to load

Re: [Intel-gfx] [PATCH] firmware/dmc/icl: load v1.07 on icelake.

On 08/02/2018 08:11 AM, Rodrigo Vivi wrote: On Wed, Aug 01, 2018 at 05:30:49PM -0700, Paulo Zanoni wrote: Em Qua, 2018-08-01 às 17:07 -0700, Anusha Srivatsa escreveu: Add Support to load DMC on Icelake. While at it, also add support to load the firmware during system resume. v2: load

Re: [Intel-gfx] [PATCH i-g-t 1/2] intel-ci: Unblacklist selftests

On 07/17/2018 03:52 PM, Chris Wilson wrote: The CI infrastructure is ready and is already running the kernel selftests in BAT, so there is no reason to blacklist them from the shards. Signed-off-by: Chris Wilson Cc: Tomi Sarvela Cc: Petri Latvala Cc: Martin Peres --- tests/intel-ci

Re: [Intel-gfx] [PATCH] usb/icl: Work around ACPI boottime crash

On 07/03/2018 08:12 PM, Paulo Zanoni wrote: Em Seg, 2018-07-02 às 16:57 +0300, Imre Deak escreveu: Work around the following boot time crash: I worked around a very similar boot time crash by disabling CONFIG_SLAB_FREELIST_HARDENED. Can you please verify if this helps? From the CI kernel

Re: [Intel-gfx] [PATCH] usb/icl: Work around ACPI boottime crash

] ? acpi_ds_delete_walk_state+0x113/0x131 ... Cc: Chris Wilson Signed-off-by: Imre Deak T-b Tomi? -Chris Tested with pre-release ICL hardware, and the patch helps with this particular boot-time crash. Tested-by: Tomi Sarvela Tomi -- Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gvt: Enable KVMGT for BXT

On 06/13/2018 09:30 AM, Chris Wilson wrote: Quoting Zhenyu Wang (2018-06-13 04:44:12) On 2018.06.11 10:09:52 +0100, Chris Wilson wrote: Quoting Patchwork (2018-06-11 10:05:46) == Series Details == Series: drm/i915/gvt: Enable KVMGT for BXT URL :

Re: [Intel-gfx] [PATCH 2/3] drm/i915/huc: Load HuC v03.00.2555 for Geminilake.

On 05/23/2018 09:15 AM, Anusha Srivatsa wrote: load the v03.00.2555 huC on geminilake. v2: - rebased. - Load the correct the version. (John Spotswood) Cc: John Spotswood <john.a.spotsw...@intel.com> Cc: Tomi Sarvela <tomi.p.sarv...@intel.com> Cc: Jani Saarinen <jani.saari...@in

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t] tests/perf_pmu: Handle CPU hotplug failures better

On 02/26/2018 12:03 PM, Petri Latvala wrote: On Fri, Feb 23, 2018 at 02:20:59PM +, Tvrtko Ursulin wrote: On 23/02/2018 11:58, Petri Latvala wrote: We have IGT_HANG and IGT_HANG_WITHOUT_RESET so the users can opt in/out of some fatal behaviour already. I'm fine with auto-rebooting, even as

Re: [Intel-gfx] ✗ Fi.CI.BAT: warning for ICL display initialization, selected patches (rev3)

On 02/08/18 15:34, Paulo Zanoni wrote: Em Ter, 2018-02-06 às 19:54 +, Patchwork escreveu: == Series Details == Series: ICL display initialization, selected patches (rev3) URL : https://patchwork.freedesktop.org/series/37668/ State : warning == Summary == Series 37668v3 ICL display

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/guc: Don't enable GuC when vGPU is active

On 15/01/18 12:28, Zhenyu Wang wrote: On 2018.01.15 12:07:28 +0200, Joonas Lahtinen wrote: On Fri, 2018-01-12 at 14:08 +0800, Du, Changbin wrote: On Fri, Jan 12, 2018 at 11:32:30AM +0530, Sagar Arun Kamble wrote: Is skl-gvtdvm not having vGPU active? It has flag X86_FEATURE_HYPERVISOR set

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,1/9] drm/i915: Extract intel_get_cagf

On 22/11/17 13:31, Tvrtko Ursulin wrote: On 21/11/2017 18:40, Patchwork wrote: == Series Details == Series: series starting with [CI,1/9] drm/i915: Extract intel_get_cagf URL   : https://patchwork.freedesktop.org/series/34186/ State : success [...] Pushed, but only then noticed this failed

Re: [Intel-gfx] [PATCH i-g-t] tests: Regenerate testlist when Makefile is changed

On 21/11/17 17:06, Maarten Lankhorst wrote: This fixes the testlist keeping the out-of-date reference to chamelium on last run. Signed-off-by: Maarten Lankhorst <maarten.lankho...@linux.intel.com> Reported-by: Tomi Sarvela <tomi.p.sarv...@intel.com> Cc: Tomi Sarvela <tomi.p.sa

Re: [Intel-gfx] [PATCH] Skylake DMC v1.27

the SKL_DMC now, and I re-ran the Patchwork series https://patchwork.freedesktop.org/series/33568/ Please include branch information in the future pull requests. Best regards, Tomi Sarvela -- Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo

Re: [Intel-gfx] [PATCH] HAX: WARN_ON(crtc->crc.opened during disable)

On 08/11/17 17:59, Jani Nikula wrote: On Wed, 08 Nov 2017, Tomi Sarvela <tomi.p.sarv...@intel.com> wrote: On 08/11/17 17:27, Jani Nikula wrote: On Wed, 08 Nov 2017, Chris Wilson <ch...@chris-wilson.co.uk> wrote: Quoting Jani Nikula (2017-11-08 13:06:39) Please use trybot (i.e.

Re: [Intel-gfx] [PATCH] HAX: WARN_ON(crtc->crc.opened during disable)

On 08/11/17 17:27, Jani Nikula wrote: On Wed, 08 Nov 2017, Chris Wilson wrote: Quoting Jani Nikula (2017-11-08 13:06:39) Please use trybot (i.e. send patches to intel-gfx-try...@lists.freedesktop.org) for hacks that aren't intended for upstream. Then they can be

[Intel-gfx] [CI][Patchwork] Bug fixed when using vetted tests/hosts in result comparison

, and not tested properly because there was no blacklists in that time. I'll re-run couple days worth of newest patchset results, so there will be duplicate (but more green) result emails to the mailing list and authors. Sorry for the noise. Best regards, Tomi Sarvela -- Intel Finland Oy - BIC 0357606-4

Re: [Intel-gfx] ✗ Fi.CI.IGT: warning for series starting with [1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not

On 03/11/17 13:33, Tomi Sarvela wrote: On 03/11/17 12:43, Petri Latvala wrote: On Fri, Nov 03, 2017 at 10:18:32AM +0200, Tomi Sarvela wrote: On 02/11/17 19:08, Ville Syrjälä wrote: On Thu, Nov 02, 2017 at 04:34:26PM -, Patchwork wrote: == Series Details == Series: series starting

Re: [Intel-gfx] ✗ Fi.CI.IGT: warning for series starting with [1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not

On 03/11/17 12:43, Petri Latvala wrote: On Fri, Nov 03, 2017 at 10:18:32AM +0200, Tomi Sarvela wrote: On 02/11/17 19:08, Ville Syrjälä wrote: On Thu, Nov 02, 2017 at 04:34:26PM -, Patchwork wrote: == Series Details == Series: series starting with [1/3] drm/i915: Check if the stolen

Re: [Intel-gfx] ✗ Fi.CI.IGT: warning for series starting with [1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not

On 03/11/17 12:41, Ville Syrjälä wrote: On Fri, Nov 03, 2017 at 10:18:32AM +0200, Tomi Sarvela wrote: On 02/11/17 19:08, Ville Syrjälä wrote: On Thu, Nov 02, 2017 at 04:34:26PM -, Patchwork wrote: Test kms_busy: Subgroup extended-modeset-hang-oldfb-with-reset-render

Re: [Intel-gfx] ✗ Fi.CI.IGT: warning for series starting with [1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not

On 02/11/17 19:08, Ville Syrjälä wrote: On Thu, Nov 02, 2017 at 04:34:26PM -, Patchwork wrote: == Series Details == Series: series starting with [1/3] drm/i915: Check if the stolen memory "reserved" area is enabled or not URL : https://patchwork.freedesktop.org/series/33060/ State :

Re: [Intel-gfx] [PATCH i-g-t] run-tests.sh: Use piglit names when listing available tests

rectly consume run-tests.sh -l output. The piglit format is directly consumable by piglit --test-list, and thus by run-tests.sh -T. Signed-off-by: Petri Latvala <petri.latv...@intel.com> Cc: Tomi Sarvela <tomi.p.sarv...@intel.com> Cc: Arkadiusz Hiler <arkadiusz.hi...@intel.com> --- Thi

Re: [Intel-gfx] [CI] drm/i915: Use a cached mapping for the physical HWS

On 11/10/17 14:43, Chris Wilson wrote: Quoting Chris Wilson (2017-10-11 12:21:06) Older gen use a physical address for the hardware status page, for which we use cache-coherent writes. As the writes are into the cpu cache, we use a normal WB mapped page to read the HWS, used for our seqno

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Redo old gmch irq handling (rev2)

On 21/08/17 15:09, Ville Syrjälä wrote: On Fri, Aug 18, 2017 at 09:19:23PM +0100, Chris Wilson wrote: Quoting Patchwork (2017-08-18 20:41:45) == Series Details == Series: drm/i915: Redo old gmch irq handling (rev2) URL : https://patchwork.freedesktop.org/series/26215/ State : success ==

Re: [Intel-gfx] [PATCH i-g-t] tests: delete extended.testlist

On 03/08/17 18:34, Daniel Vetter wrote: This approach died, we just run everything there is (and use that to apply some serious darwinian pressure onto testcase to prove themselves). Cc: Martin Peres <martin.pe...@linux.intel.com> Cc: Arkadiusz Hiler <arkadiusz.hi...@intel.com> Cc:

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: DMC 1.02 for Kabylake

On Friday, 10 February 2017 13:57:47 EET Ander Conselvan De Oliveira wrote: > Seems like neither of the versions of DMC are being tested by CI. Added kbl_dmc_ver1_01.bin to fi-kbl-7500u. Can't see kbl_dmc_ver1_02 in the firmware repo. Tomi > > [1]: > > [3.466858]

Re: [Intel-gfx] [PATCH] drm/i915/guc: Make sure vma containing firmware is GuC mappable

7y-01m-05d-16h-48m-32s UTC integration manifest) get into infinite suspend with following options turned on: i915.enable_guc_submission=1 i915.enable_guc_loading=1 With this patch the testhost i6700K survived dozen rounds of igt@gem_exec_suspend@basic-s3, without it the first run han

Re: [Intel-gfx] ✗ Fi.CI.BAT: warning for drm/i915: Suppress underrun reporting around DP link retraining

On Monday, 17 October 2016 14:33:28 EEST Ville Syrjälä wrote: > On Fri, Oct 14, 2016 at 06:51:37PM -, Patchwork wrote: > > == Series Details == > > > > Series: drm/i915: Suppress underrun reporting around DP link retraining > > URL : https://patchwork.freedesktop.org/series/13805/ > > State

Re: [Intel-gfx] [PATCH] drm/i915: Unify VLV/CHV DPOunit clock gating disable/enable

On Wednesday 27 April 2016 17:49:26 Ville Syrjälä wrote: > On Mon, Apr 18, 2016 at 07:18:25PM +0300, ville.syrj...@linux.intel.com wrote: > > From: Ville Syrjälä > > > > Check for VLV/CHV instead if !BXT when re-enabling DPOunit clock gating > > after DSI disable.

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Unduplicate CHV phy code (rev5)

Hello, On Wednesday 27 April 2016 16:36:13 Ander Conselvan De Oliveira wrote: > > Subgroup suspend-read-crc-pipe-a: > > pass -> INCOMPLETE (hsw-gt2) > > dmesg ends with > > [ 505.669959] kms_pipe_crc_basic: starting subtest suspend-read-crc-pipe-A > > Seems very

Re: [Intel-gfx] [PATCH i-g-t 1/2] lib/igt_aux: Half the timeout for suspend to RAM and a third for suspend to disk.

Fi CI has ran with this patch approx 2 weeks at January. All platforms acted the same with or without patch. Tomi On Wednesday 20 April 2016 20:49:56 Marius Vlad wrote: > Signed-off-by: Marius Vlad > --- > lib/igt_aux.c | 8 > 1 file changed, 4

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Fix eDP low vswing for Broadwell (rev3)

On Thursday 14 April 2016 19:20:22 Ville Syrjälä wrote: > On Wed, Apr 13, 2016 at 05:07:04PM -, Patchwork wrote: > > == Series Details == > > > > Series: drm/i915: Fix eDP low vswing for Broadwell (rev3) > > URL : https://patchwork.freedesktop.org/series/4499/ > > State : failure > > > >

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Rest of my DSI and DPLL stuff

On Thursday 14 April 2016 11:46:12 Ville Syrjälä wrote: > On Thu, Apr 14, 2016 at 10:24:23AM +0300, Tomi Sarvela wrote: > > On Wednesday 13 April 2016 19:29:25 Ville Syrjälä wrote: > > [ILK-hp8440p problems] > > > > > ... > > > > > > [ 265

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Rest of my DSI and DPLL stuff

On Wednesday 13 April 2016 19:29:25 Ville Syrjälä wrote: [ILK-hp8440p problems] > ... > > [ 265.316531] drm/i915: Resetting chip after gpu hang > [ 265.316585] [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -110 > > Looks like the GPU died for some reason. > > > Test

Re: [Intel-gfx] [CI-ping 1/9] drm/i915: Include engine->last_submitted_seqno in GPU error state

Yesterday CI got lagged for a bit while I was tuning timeouts in host connectivity. We're now using nmap (instead of ping) to get better results over firewalls and long distances. Change sparked from connecting French DUT to our Jenkins. The results for this series were run, but not posted for

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915: Sharing the pixel_format_from_vbt to whole i915

On Thursday 07 April 2016 15:58:12 Jani Nikula wrote: > > *sigh*, there's pretty much no way the patches could cause any of > this. :( > > BR, > Jani. I'm guessing that the IGT randomized testing order is hiding problems ... can't really reproduce easily. I kind of liked the old system

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: BXT DDI PHY sequence BUN (rev3)

Temporary fluke, they are there now. Nothing special, just dellxps not deciding which suspend-read-crc-pipe it hangs this time. Tomi On Friday 01 April 2016 13:12:41 Imre Deak wrote: > On pe, 2016-04-01 at 08:33 +, Patchwork wrote: > > BOOT FAILED for snb-dellxps > > > > Results at

Re: [Intel-gfx] [REGRESSION] system hang on ILK/SNB/IVB

not familiar with the driver innards, it might take a while. Tomi On Thursday 31 March 2016 22:35:17 Lukas Wunner wrote: > Hi Tomi, > > On Thu, Mar 31, 2016 at 10:21:16AM +0300, Tomi Sarvela wrote: > > The problem with the results in your link is that there is no HSW, ILK, > > I

Re: [Intel-gfx] [REGRESSION] system hang on ILK/SNB/IVB

x by waiting for the asynchronous thread to finish. > > > > v2: > > An async_synchronize_full() was also added to > > intel_fbdev_set_suspend() > > in v1 which turned out to be entirely gratuitous. It caused a deadlock > > on suspend

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/bxt: Fix off-by-one error in Broxton PLL IDs (rev3)

On Thursday 17 March 2016 18:00:52 Takashi Iwai wrote: ... > > CI_DRM_1147 git://anongit.freedesktop.org/drm-intel > > dbbc6d276864d7b7a3a1edb04f0511153f9c3852 > > > > Note that drm-intel-nightly history changes, so the exact commits might > > not be there any more. > > Well, I have no internal

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/bxt: Fix off-by-one error in Broxton PLL IDs (rev3)

On Wednesday 16 March 2016 16:40:24 Takashi Iwai wrote: > On Wed, 16 Mar 2016 16:37:06 +0100, Daniel Vetter wrote: > > On Wed, Mar 16, 2016 at 02:37:24PM +0200, Tomi Sarvela wrote: > > > > > > SND is recurring problem. I'd like to see drm-intel-nightly not breaki

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/bxt: Fix off-by-one error in Broxton PLL IDs (rev3)

On Wednesday 16 March 2016 10:48:43 Imre Deak wrote: > Tomi, noticed two things that maybe infrastructure related, see below: > > > Test drv_module_reload_basic: > > skip -> PASS (bdw-nuci7) > > Test gem_ringfill: > > Subgroup basic-default-s3: > >

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/bxt: Fix off-by-one error in Broxton PLL IDs (rev3)

On Friday 18 March 2016 09:00:13 Takashi Iwai wrote: > On Fri, 18 Mar 2016 08:36:27 +0100, > > Do you have the commit of the last working kernel? > > > The unit tests that hang quite reliably on first run are > > igt@gem_ringfill_basic-default-s3 > > igt@drv_module_reload_basic > >

Re: [Intel-gfx] [PATCH v8 1/1] drm/i915/bxt: Check BIOS RC6 setup before enabling RC6

On Tuesday 16 February 2016 16:28:43 Daniel Vetter wrote: > On Tue, Feb 16, 2016 at 09:52:49AM +0200, Tomi Sarvela wrote: > > What kind of status dashboard would be good? As mentioned, CI itself was > > all good and well, and status board would reflect that. > > Well sta

Re: [Intel-gfx] [PATCH v8 1/1] drm/i915/bxt: Check BIOS RC6 setup before enabling RC6

On Monday 15 February 2016 18:07:47 Daniel Vetter wrote: > On Mon, Feb 08, 2016 at 05:08:03PM +0200, Jani Nikula wrote: > > On Mon, 08 Feb 2016, Imre Deak wrote: > > >> > Thanks for the patch, I pushed it to -dinq. > > >> > > >> The rule is, we should wait for the CI results