From: Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>
To: intel-wired-lan@lists.osuosl.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Subject: [Intel-wired-lan] ice: Error setting promisc mode on VSI 6 (rc=-17) @ 5.18.x
Date: Thu, 9 Jun 2022 08:58:41 +0200 [thread overview]
Message-ID: <CAK8fFZ7m-KR57M_rYX6xZN39K89O=LGooYkKsu6HKt0Bs+x6xQ@mail.gmail.com> (raw)
Hello,
I'm struggling with broken network connectivity at VMs using linux
bridge at host after update of kernel from 5.17.x to 5.18.x @ Dell
R750 server with E810-XXV NICs.
I noticed the kernel reports "Error setting promisc mode" in dmesg.
# dmesg | grep 'Error setting promisc'
[ 24.863557] ice 0000:31:00.0: Error setting promisc mode on VSI 6 (rc=-17)
[ 24.878369] ice 0000:31:00.0: Error setting promisc mode on VSI 6 (rc=-17)
[ 25.045834] ice 0000:31:00.0: Error setting promisc mode on VSI 6 (rc=-17)
[ 25.129840] ice 0000:b1:00.0: Error setting promisc mode on VSI 6 (rc=-17)
[ 25.144440] ice 0000:b1:00.0: Error setting promisc mode on VSI 6 (rc=-17)
# lspci -s 0000:31:00.0
31:00.0 Ethernet controller: Intel Corporation Ethernet Controller
E810-XXV for SFP (rev 02)
# lspci -s 0000:b1:00.0
b1:00.0 Ethernet controller: Intel Corporation Ethernet Controller
E810-XXV for SFP (rev 02)
It is easy to reproduce by:
# ip link set em1 promisc on
# dmesg -T | tail -n 1
[Thu Jun 9 08:48:19 2022] ice 0000:31:00.0: Error setting promisc
mode on VSI 6 (rc=-17)
Could it be an 'ice' driver bug introduced in the 5.18 kernel?
Best,
Jaroslav Pulhart
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2022-06-09 13:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 6:58 Jaroslav Pulchart [this message]
2022-06-18 15:36 ` [Intel-wired-lan] ice: Error setting promisc mode on VSI 6 (rc=-17) @ 5.18.x Jaroslav Pulchart
2022-06-19 11:50 ` Thorsten Leemhuis
2022-06-19 17:00 ` Jaroslav Pulchart
2022-07-05 9:43 ` Thorsten Leemhuis
2022-07-05 13:51 ` Wilczynski, Michal
2022-08-17 9:08 ` Thorsten Leemhuis
2022-08-17 15:59 ` Tony Nguyen
2022-08-17 16:07 ` Thorsten Leemhuis
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='CAK8fFZ7m-KR57M_rYX6xZN39K89O=LGooYkKsu6HKt0Bs+x6xQ@mail.gmail.com' \
--to=jaroslav.pulchart@gooddata.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@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;
as well as URLs for NNTP newsgroup(s).