intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Sarvela, Tomi P" <tomi.p.sarvela@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] Public i915 CI shardruns are disabled
Date: Tue, 2 Mar 2021 13:50:58 +0000	[thread overview]
Message-ID: <51946a94b1154605bd7dda2c77ab12fc@intel.com> (raw)
In-Reply-To: <e12dfaac0aa242f4a10d8c5b920a98db@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 2361 bytes --]

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 is partition, it seems that the swap signature is correct even
after running the test, so for now I'm assuming that the issue has to do
with swapfile

- Bisection between 20210129 and 20210215 proved to be challenging,
because the kernels have pre-init hang, don't leave dmesg and I don't
have console on testing host. Petri's suggestion to bisect between
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 <radoslaw.szwichtenberg@intel.com>
Subject: Public i915 CI shardruns are disabled

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 drm-tip: 2021y-03m-01d-09h-36m-57s UTC integration manifest
3b3c4086295b drm-tip: 2021y-03m-01d-08h-49m-06s UTC integration manifest
fe07bfda2fb9 Linux 5.12-rc1

More information can be seen at:
https://phoronix.com/scan.php?page=news_item&px=Linux-5.12-Early-Buggy-Issue

I've seen this bug happen regularly with (but not limited to) IGT test:
igt@gem_tiled_swapping@non-threaded

The range for bisection is linux-next 20210215 to 20210129 because the kernels
in-between taint the kernel and our i915 testing was not done. Hitting the bug
corrupts the underlying filesystem very thoroughly, wiping out large amount of
data from the beginning of the partition which leaves fsck sad with thousands of
items lost. Bisection of the IGT testlist was done with two root filesystems, where
testable kernel booted from 2. partition, and copy of the 2. partition was stored
on 1. partition and could be restored at will.

I'll continue bisecting this bug on the linux-next tree again. If someone has more
information where this issue originates from, help would be appreciated.

Regards,

Tomi Sarvela

--
Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo


[-- Attachment #1.2: Type: text/html, Size: 16013 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2021-03-02 13:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 11:37 Sarvela, Tomi P
2021-03-02 13:50 ` Sarvela, Tomi P [this message]
2021-03-02 17:26   ` Sarvela, Tomi P
2021-03-02 19:31     ` Dave Airlie
2021-03-02 23:27       ` Linus Torvalds
2021-03-02 23:38         ` Dave Airlie
2021-03-02 23:56           ` Linus Torvalds
2021-03-03  0:15             ` Jens Axboe
2021-03-03  0:36               ` Jens Axboe
2021-03-03  1:01                 ` Linus Torvalds
2021-03-03  1:18                   ` Jens Axboe
2021-03-03  2:48                     ` Linus Torvalds
2021-03-09  8:31     ` Sarvela, Tomi P
2021-03-03 18:28 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51946a94b1154605bd7dda2c77ab12fc@intel.com \
    --to=tomi.p.sarvela@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --subject='Re: [Intel-gfx] Public i915 CI shardruns are disabled' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).