From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Networking <netdev@vger.kernel.org>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Linux Intel Wired LAN <intel-wired-lan@lists.osuosl.org>,
Linux Regressions <regressions@lists.linux.dev>,
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: Tue, 14 Nov 2023 16:54:33 -0800 [thread overview]
Message-ID: <32716.1700009673@famine> (raw)
In-Reply-To: <986716ed-f898-4a02-a8f6-94f85b355a05@gmail.com>
Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>Hi Thorsten and all,
>
>I come across LACP bonding regression on Bugzilla [1]. 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
>
>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.
Interestingly, we've been chasing internally an issue with
bonding LACP mode on ice (E810-XXV, I think) when running on the Ubuntu
kernel. That manifests as occasional TX timeouts, and doesn't happen if
the Intel OOT driver is used, so I wonder if that bugzilla reporter is
also seeing TX timeouts that correlate with their ping failures.
-J
>Thanks.
>
>[1]: https://bugzilla.kernel.org/show_bug.cgi?id=218139
>
>--
>An old man doll... just what I always wanted! - Clara
---
-Jay Vosburgh, jay.vosburgh@canonical.com
next prev parent reply other threads:[~2023-11-15 0:54 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 [this message]
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
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=32716.1700009673@famine \
--to=jay.vosburgh@canonical.com \
--cc=andy@greyhouse.net \
--cc=anilchabba@gmail.com \
--cc=anthony.l.nguyen@intel.com \
--cc=bagasdotme@gmail.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=regressions@leemhuis.info \
--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).