From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Regressions <regressions@lists.linux.dev>,
Jay Vosburgh <jay.vosburgh@canonical.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Networking <netdev@vger.kernel.org>,
Linux Intel Wired LAN <intel-wired-lan@lists.osuosl.org>,
Andy Gospodarek <andy@greyhouse.net>,
Ivan Vecera <ivecera@redhat.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Anil Choudhary <anilchabba@gmail.com>
Subject: Re: sr-iov related bonding regression (two regressions in one report)
Date: Wed, 15 Nov 2023 20:04:08 +0700 [thread overview]
Message-ID: <ZVTByHx1HfYds_v-@archie.me> (raw)
In-Reply-To: <0f97acf9-012d-4bb2-a766-0c2737e32b2c@leemhuis.info>
[-- Attachment #1: Type: text/plain, Size: 2069 bytes --]
On Wed, Nov 15, 2023 at 06:50:26AM +0100, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 15.11.23 01:54, Jay Vosburgh wrote:
> > Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> >
> >> I come across LACP bonding regression on Bugzilla [1].
>
> Side note: Stephen forwards some (all?) network regressions to the right
> people:
> https://lore.kernel.org/all/20231113083746.5e02f8b0@hermes.local/
>
> Would be best to check for that, no need to forward things twice, that
> just results in a mess.
>
> >> The reporter
> >> (Cc'ed) has two regressions. The first is actual LACP bonding
> >> regression (but terse):
> >>
> >>> Till linkx kernel 6.5.7 it is working fine, but after upgrading to 6.6.1 ping stop working with LACP bonding.
> >>> When we disable SR-IOV from bios , everything working fine
>
> Makes me wonder if things have been working with or without the OOT
> module on 6.5.7, as strictly speaking it's only considered a kernel
> regression if thing worked with a vanilla kernel (e.g. without OOT
> modules) beforehand and broke when switching to a newer vanilla kernel.
> If that's the case it would be okay to add to regzbot.
>
> >> And the second is out-of-tree module FTBFS:
> > [... skip OOT stuff ...]
> >
> >> Should I add the first regression to regzbot (since the second one
> >> is obviously out-of-tree problem), or should I asked detailed regression
> >> info to the reporter?
> >
> > My vote is to get additional information. Given the nature of
> > the workaround ("When we disable SR-IOV from bios , everything working
> > fine"), it's plausible that the underlying cause is something
> > platform-specific.
>
> Maybe, but when it comes to the "no regressions" rule that likely makes
> no difference from Linus perspective.
>
> But I guess unless the intel folks or someone else has an idea what
> might be wrong here we likely need a bisection (with vanilla kernels of
> course) to get anywhere.
>
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-11-15 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 23:59 sr-iov related bonding regression (two regressions in one report) Bagas Sanjaya
2023-11-15 0:54 ` Jay Vosburgh
2023-11-15 5:50 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-15 6:13 ` Anil Choudhary
2023-11-15 13:08 ` Bagas Sanjaya
2023-11-15 6:19 ` Anil Choudhary
2023-11-15 13:11 ` Bagas Sanjaya
2023-11-15 20:48 ` Anil Choudhary
2023-11-16 10:53 ` Bagas Sanjaya
2023-11-15 13:04 ` Bagas Sanjaya [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=ZVTByHx1HfYds_v-@archie.me \
--to=bagasdotme@gmail.com \
--cc=andy@greyhouse.net \
--cc=anilchabba@gmail.com \
--cc=anthony.l.nguyen@intel.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=jay.vosburgh@canonical.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).