From: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, intel-gfx@lists.freedesktop.org,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Andi Shyti <andi.shyti@linux.intel.com>,
Krzysztof Karas <krzysztof.karas@intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Krzysztof Niemiec <krzysztof.niemiec@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Disable not supported reset methods on DG1 0x4905
Date: Fri, 21 Aug 2026 11:50:07 +0200 [thread overview]
Message-ID: <4bd61f0e5667100e9773e06c8cefe25a9f9c00ad.camel@linux.intel.com> (raw)
In-Reply-To: <aogQ4fNchLVm9Pbg@zenone.zhora.eu>
Hi Andi,
On Fri, 2026-08-21 at 10:51 +0200, Andi Shyti wrote:
> Hi Janusz,
>
> On Wed, Aug 19, 2026 at 12:24:53PM +0200, Janusz Krzysztofik wrote:
> > DRM CI consequently reports failing device reset attempts on Intel DG1
>
> do you mean "consistently reports"?
Yeah, consistently is the right word.
@Bjorn: should I submit v2, or can you handle that correction?
Thanks,
Janusz
>
> > discrete graphics adapters. Manual reproduction attempts allowed to
> > narrow down the scope of that problem to a specific revision of that
> > hardware, SKU 8086:4905. It has been confirmed that both reset methods
> > claimed by the device, i.e., flr and bus, suffer from that issue.
> >
> > Since consecutively failing device resets may lead to system hangs,
> > disable both useless reset methods. A respective CI test will then be
> > skipped instead of aborting whole CI jobs.
> >
> > Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/work_items/11814
> > Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
>
> Thanks,
> Andi
prev parent reply other threads:[~2026-08-21 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 10:24 [PATCH] PCI: Disable not supported reset methods on DG1 0x4905 Janusz Krzysztofik
2026-08-19 10:30 ` sashiko-bot
2026-08-19 11:25 ` ✓ i915.CI.BAT: success for " Patchwork
2026-08-19 16:08 ` ✗ i915.CI.Full: failure " Patchwork
2026-08-20 11:01 ` [PATCH] " Krzysztof Karas
2026-08-21 8:51 ` Andi Shyti
2026-08-21 9:50 ` Janusz Krzysztofik [this message]
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=4bd61f0e5667100e9773e06c8cefe25a9f9c00ad.camel@linux.intel.com \
--to=janusz.krzysztofik@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=andi.shyti@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=krzysztof.niemiec@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sebastian.brzezinka@intel.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.