Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Per-crtc/connector DRRS debugfs (rev2)

2022-10-03 Thread Sarvela, Tomi P
> On Sat, Oct 01, 2022 at 11:23:17PM -, Patchwork wrote: > > * igt@gem_exec_balancer@parallel-balancer: > > - shard-iclb: [PASS][58] -> [SKIP][59] ([i915#4525]) > >[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12204/shard- > iclb2/igt@gem_exec_balan...@parallel-balanc

Re: [Intel-gfx] [CI] Maintenance: Intel-GFX-CI down on weekend 27.5.-29.5.

2022-05-27 Thread Sarvela, Tomi P
. If tests pass, partial functionality (DRM-Tip) is restored on Sunday and full functionality on Monday. Tomi From: Sarvela, Tomi P Sent: Friday, May 20, 2022 11:38 AM This is early warning about GFX-CI going down for maintenance on next week weekend Fri 27.5. to Sun 29.5. GFX-CI will be

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/edid: expand on struct drm_edid usage

2022-05-24 Thread Sarvela, Tomi P
> From: Nikula, Jani > > On Tue, 24 May 2022, Patchwork > wrote: > > == Series Details == > > > > Series: drm/edid: expand on struct drm_edid usage > > URL : https://patchwork.freedesktop.org/series/104309/ > > State : failure > > > > == Summary == > > > > > > Possible regressions >

[Intel-gfx] [CI] Maintenance: Intel-GFX-CI down on weekend 27.5.-29.5.

2022-05-20 Thread Sarvela, Tomi P
This is early warning about GFX-CI going down for maintenance on next week weekend Fri 27.5. to Sun 29.5. GFX-CI will be migrating to new hardware starting Friday 27.5. and estimated downtime is at least 48h (CIBuglog database dump/import). During downtime, no new builds are done and no testing is

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dmc: Load DMC on DG2 (rev4)

2022-04-16 Thread Sarvela, Tomi P
This week I've been working to get the Public CI work more reliably on bat-* machines which are hosted on a different site. The BAT for IGT, IGTPW, CI_DRM and Patchwork seems to be stabilized pretty well, and probably Trybot/TrybotIGT will be added soon enough. This isn't a promise that even one D

Re: [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [RESEND,1/3] drm/i915/dmc: abstract GPU error state dump

2022-03-31 Thread Sarvela, Tomi P
After the latest CI_DRM has been build, re-test should be enough. Tomi > From: De Marchi, Lucas > On Thu, Mar 31, 2022 at 08:28:09AM +, Tomi Sarvela wrote: > >The latest CI_DRM built is 11416; after that, there is build error: > >drivers/gpu/drm/amd/amdgpu/amdgpu_gtt_mgr.c: In function > 'am

Re: [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [RESEND,1/3] drm/i915/dmc: abstract GPU error state dump

2022-03-31 Thread Sarvela, Tomi P
The latest CI_DRM built is 11416; after that, there is build error: drivers/gpu/drm/amd/amdgpu/amdgpu_gtt_mgr.c: In function 'amdgpu_gtt_mgr_recover': drivers/gpu/drm/amd/amdgpu/amdgpu_gtt_mgr.c:200:31: error: 'struct ttm_range_mgr_node' has no member named 'tbo' amdgpu_ttm_recover_gart(node->

Re: [Intel-gfx] Intel-GFX-CI is halted due to power issue

2022-03-08 Thread Sarvela, Tomi P
The incident is over: power has been restored, but CI is still quiet. I'll check up the affected hosts and start re-testing the missed Patchwork series. Best Regards, Tomi Sarvela From: Sarvela, Tomi P Sent: Tuesday, March 8, 2022 11:26 AM To: intel-gfx@lists.freedesktop.org Intel-GFX-C

[Intel-gfx] Intel-GFX-CI is halted due to power issue

2022-03-08 Thread Sarvela, Tomi P
Intel-GFX-CI has ongoing issue, assumed AC power delivery. At around 21:00 EET yesterday, the power was lost to several parts of our CI lab, most notably to PDUs that control testhosts. As the PDUs cannot be reached or controlled, testhosts by and large are without power. There has been builds b

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/display/vrr: Reset VRR capable property on a long hpd (rev4)

2022-02-25 Thread Sarvela, Tomi P
> From: Saarinen, Jani > > From: Navare, Manasi D > > Subject: RE: ✗ Fi.CI.BAT: failure for drm/i915/display/vrr: Reset VRR > capable > > property on a long hpd (rev4) > > > > Hi, > > > > > > > > I fixed the regression in this patch and resent it, it still has BAT > > failures, I > wanted > > to

Re: [Intel-gfx] [PATCH v2 1/4] drm/i915/fbc: Parametrize FBC register offsets

2021-12-15 Thread Sarvela, Tomi P
> From: Sarvela, Tomi P > > From: Ville Syrjälä > > On Wed, Dec 15, 2021 at 09:05:03AM +, Sarvela, Tomi P wrote: > > > > From: Ville Syrjälä > > > > > > > > On Tue, Dec 14, 2021 at 06:25:43PM +0200, Ville Syrjälä wrote: > > > >

Re: [Intel-gfx] [PATCH v2 1/4] drm/i915/fbc: Parametrize FBC register offsets

2021-12-15 Thread Sarvela, Tomi P
> From: Ville Syrjälä > On Wed, Dec 15, 2021 at 09:05:03AM +, Sarvela, Tomi P wrote: > > > From: Ville Syrjälä > > > > > > On Tue, Dec 14, 2021 at 06:25:43PM +0200, Ville Syrjälä wrote: > > > > On Mon, Dec 13, 2021 at 09:54:04PM +0200, Jani Nikul

Re: [Intel-gfx] [PATCH v2 1/4] drm/i915/fbc: Parametrize FBC register offsets

2021-12-15 Thread Sarvela, Tomi P
> From: Ville Syrjälä > > On Tue, Dec 14, 2021 at 06:25:43PM +0200, Ville Syrjälä wrote: > > On Mon, Dec 13, 2021 at 09:54:04PM +0200, Jani Nikula wrote: > > > On Mon, 13 Dec 2021, Ville Syrjala wrote: > > > > > > This one is only used in gvt, anyway. And that actually makes me wonder > > > if t

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Fix DPT suspend/resume on !HAS_DISPLAY platforms

2021-11-26 Thread Sarvela, Tomi P
The trace is full of ext4, so I'm siding on -rc2 issue. You can try re-testing the series to see if same failure happens again. Tomi > From: Deak, Imre > > Hi, > > On Thu, Nov 25, 2021 at 10:38:35PM +, Patchwork wrote: > > == Series Details == > > > > Series: drm/i915: Fix DPT suspend/res

Re: [Intel-gfx] [PATCH 2/3] drm/i915/dg2: Add initial gt/ctx/engine workarounds

2021-11-12 Thread Sarvela, Tomi P
This issue was not catched by CI, because of series of unfortunate events. Before, CI has rebooted without module blocklist, and CI catched boot-time dmesg correctly and marked it as 'ci@boot' test with failure if there was a taint. I've been doing changes to make blocklisting i915 possible and

Re: [Intel-gfx] [PATCH 4/4] drm/i915: Fix oops on platforms w/o hpd support

2021-10-14 Thread Sarvela, Tomi P
> From: Ville Syrjälä > On Thu, Oct 14, 2021 at 09:31:40AM +, Sarvela, Tomi P wrote: > > > From: Ville Syrjälä > > > On Thu, Oct 14, 2021 at 12:18:23PM +0300, Jani Nikula wrote: > > > > On Thu, 14 Oct 2021, Ville Syrjala > > > > wrote: >

Re: [Intel-gfx] [PATCH 4/4] drm/i915: Fix oops on platforms w/o hpd support

2021-10-14 Thread Sarvela, Tomi P
> From: Ville Syrjälä > On Thu, Oct 14, 2021 at 12:18:23PM +0300, Jani Nikula wrote: > > On Thu, 14 Oct 2021, Ville Syrjala wrote: > > > From: Ville Syrjälä > > > > > > We don't have hpd support on i8xx/i915 which means > hotplug_funcs==NULL. > > > Let's not oops when loading the driver on one t

Re: [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/2] drm/dp: add drm_dp_phy_name() for getting DP PHY name

2021-10-05 Thread Sarvela, Tomi P
There was an issue with fd.o expired root cert, and that caused some issues during the weekend and yesterday, mostly with git fetches. I wonder if this is related. Can you re-test the patchset and see if the issue persists? Other patchsets nearby timewise seem to be unaffected by spurious sparses.

Re: [Intel-gfx] [PATCH 01/24] drm/i915/uncore: split the fw get function into separate vfunc

2021-10-04 Thread Sarvela, Tomi P
> From: Ville Syrjälä > On Wed, Sep 29, 2021 at 01:57:45AM +0300, Jani Nikula wrote: > > From: Dave Airlie > > > > constify it while here. drop the put function since it was never > > overloaded and always has done the same thing, no point in > > indirecting it for show. > > > > Reviewed-by: Jani

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/adlp: Add support for remapping CCS FBs (rev3)

2021-09-07 Thread Sarvela, Tomi P
This looks very much like SATA drive issue. I'll replace the drive for shard-iclb3 and we'll see if this happens again. Tomi > -Original Message- > From: Deak, Imre > Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915/adlp: Add support for > remapping CCS FBs (rev3) > > Hi Lakshmi, Tomi, >

Re: [Intel-gfx] Public i915 CI shardruns are disabled

2021-03-09 Thread Sarvela, Tomi P
It seems that the chops to be built has been re-defined several times in pipelines. Fixed. https://github.com/intel-innersource/drivers.gpu.i915.ci.pipelines/commit/89d2f8174a15585c082b2f714551225ba6cafe08 Tomi From: Sarvela, Tomi P Sent: Tuesday, March 2, 2021 7:27 PM To: 'inte

Re: [Intel-gfx] Public i915 CI shardruns are disabled

2021-03-02 Thread Sarvela, Tomi P
will be enabled again. Regards, Tomi Sarvela From: Sarvela, Tomi P More information (excuse my top-posting): - Issue happens in igt@gem_tiled_swapping@non-threaded Mlocking phase, before "starting subtest" appears. - Filesystem trashed is the one containing swapfile - If swap i

Re: [Intel-gfx] Public i915 CI shardruns are disabled

2021-03-02 Thread Sarvela, Tomi P
een CI_DRM_9817 and 9818 might work better Regards, Tomi Sarvela From: Sarvela, Tomi P Sent: Tuesday, March 2, 2021 1:38 PM To: intel-gfx@lists.freedesktop.org Cc: Szwichtenberg, Radoslaw Subject: Public i915 CI shardruns are disabled Hello, The linux i915 CI shardruns have been disabled.

[Intel-gfx] Public i915 CI shardruns are disabled

2021-03-02 Thread Sarvela, Tomi P
Hello, The linux i915 CI shardruns have been disabled. This is due to the unfortunate filesystem-corrupting bug first seen in linux-next 20210215, which now has been merged to linus 5.12-rc1 and further on to DRM-Tip, first instance seen in CI_DRM_9818. Last changes coming in were: fb3b93df7979 d

Re: [Intel-gfx] [PATCH] drm/i915/mst: fix pipe and vblank enable

2020-02-14 Thread Sarvela, Tomi P
> From: Jani Nikula > > On Mon, 10 Feb 2020, Arkadiusz Hiler wrote: > > As of the 3 days worth of queued shards: > > > > I agree that this is unacceptable, but we can do only so much from the > > CI/infra side. The time has been creeping up steadily over the last year > > or so and the machines

Re: [Intel-gfx] [PATCH 0/5] drm/i915/skl: drop pre-production stepping workarounds

2016-09-22 Thread Sarvela, Tomi P
> From: Zanoni, Paulo R > Em Sex, 2016-09-16 às 16:59 +0300, Jani Nikula escreveu: > > Only production steppings are supported, drop workarounds for > > anything > > else. The series is split by revision so we can bikeshed if there are > > steppings some people still need to use for some reason. >

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/skl: Add missing SKL GT3 id (rev2)

2016-02-01 Thread Sarvela, Tomi P
> From: Mika Kuoppala [mailto:mika.kuopp...@linux.intel.com] > > "Sarvela, Tomi P" writes: > > > > In the result box there is no SKL-I5K column at all. You're looking at HSW- > GT2? > > > > Yes I was looking at wrong column. My bad. I can see

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/skl: Add missing SKL GT3 id (rev2)

2016-02-01 Thread Sarvela, Tomi P
> From: Mika Kuoppala [mailto:mika.kuopp...@linux.intel.com] > > Ok. Then the rendering of the Patchwork_1328 report is somehow wrong as > in that picture the HANG box is in the nightly base column. In the result box there is no SKL-I5K column at all. You're looking at HSW-GT2? Tomi __

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/skl: Add missing SKL GT3 id (rev2)

2016-02-01 Thread Sarvela, Tomi P
> From: Mika Kuoppala [mailto:mika.kuopp...@linux.intel.com] > > Patchwork writes: > > > Series 2919v2 drm/i915/skl: Add missing SKL GT3 id > > http://patchwork.freedesktop.org/api/1.0/series/2919/revisions/2/mbox/ > > > > Test kms_pipe_crc_basic: > > Subgroup suspend-read-crc-pipe-a: > >