From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Anil Choudhary <anilchabba@gmail.com>,
Linux Regressions <regressions@lists.linux.dev>
Cc: Jay Vosburgh <jay.vosburgh@canonical.com>,
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>
Subject: Re: sr-iov related bonding regression (two regressions in one report)
Date: Wed, 15 Nov 2023 20:08:49 +0700 [thread overview]
Message-ID: <ZVTC4WYHVdXpMlGj@archie.me> (raw)
In-Reply-To: <EFC5ADF4-1EE4-4900-B250-AC35656DC68B@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
On Tue, Nov 14, 2023 at 10:13:20PM -0800, Anil Choudhary wrote:
> Its not hardware issue when I do rmmod iavf ping started working .
> So issue is certainly in this kernel and with sriov only
> Iavf id Nic driver for VF(sriovnic)
>
>
Please don't top-post; reply inline with appropriate context instead.
So you have this regression on vanilla kernel, right? If so, please
bisect (see Documentation/admin-guide/bug-bisect.rst in the kernel
sources for reference).
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-15 13:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 23:59 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 [this message]
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=ZVTC4WYHVdXpMlGj@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
all inboxes | Powered by JetHome®