From: Bjorn Helgaas <helgaas@kernel.org>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
"Saarinen, Jani" <jani.saarinen@intel.com>
Subject: Re: Regression on linux-next (next-20250221)
Date: Wed, 26 Feb 2025 15:58:42 -0600 [thread overview]
Message-ID: <20250226215842.GA560520@bhelgaas> (raw)
In-Reply-To: <SJ1PR11MB6129B4B298158496F8BD36B0B9C22@SJ1PR11MB6129.namprd11.prod.outlook.com>
On Wed, Feb 26, 2025 at 07:36:19PM +0000, Borah, Chaitanya Kumar wrote:
> Hello Bjorn,
>
> Hope you are doing well. I am Chaitanya from the linux graphics team in Intel.
>
> This mail is regarding a regression we are seeing in our CI runs[1] on linux-next repository.
>
> Since the version next-20250221 [2], we are seeing that some of the machines in our CI are unable to connect through ssh (and therefore unable to participate).
> Looking at the logs we see this.
>
> `````````````````````````````````````````````````````````````````````````````````
> [ 5.838496] e1000e: Intel(R) PRO/1000 Network Driver
> [ 5.838515] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
> [ 5.838737] e1000e 0000:01:00.0: Disabling ASPM L1
> [ 5.840055] e1000e 0000:01:00.0: probe with driver e1000e failed with error -12
> `````````````````````````````````````````````````````````````````````````````````
> After bisecting the tree, the following patch [3] seems to be the first "bad"
> commit
>
> `````````````````````````````````````````````````````````````````````````````````````````````````````````
> commit 7d90d8d2bb1bfff8b33acbb6f815cba6f5250fad
> Author: Bjorn Helgaas mailto:bhelgaas@google.com
> Date: Fri Feb 14 18:03:00 2025 -0600
>
> PCI: Avoid pointless capability searches
>
> Many of the save/restore functions in the pci_save_state() and
> pci_restore_state() paths depend on both a PCI capability of the device and
> a pci_cap_saved_state structure to hold the configuration data, and they
> skip the operation if either is missing.
> `````````````````````````````````````````````````````````````````````````````````````````````````````````
>
> We verified that if we revert the patch the issue is not seen.
Sorry about this; this patch was dropped in next-20250224
Bjorn
next prev parent reply other threads:[~2025-02-26 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 19:36 Regression on linux-next (next-20250221) Borah, Chaitanya Kumar
2025-02-26 21:58 ` Bjorn Helgaas [this message]
2025-02-27 5:30 ` Borah, Chaitanya Kumar
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=20250226215842.GA560520@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=suresh.kumar.kurmi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox