All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>,
	intel-wired-lan@lists.osuosl.org,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [Intel-wired-lan] ice: Error setting promisc mode on VSI 6 (rc=-17) @ 5.18.x
Date: Sun, 19 Jun 2022 13:50:55 +0200	[thread overview]
Message-ID: <2596b2c6-71e4-543f-799f-b4b174c21f31@leemhuis.info> (raw)
In-Reply-To: <CAK8fFZ7m-KR57M_rYX6xZN39K89O=LGooYkKsu6HKt0Bs+x6xQ@mail.gmail.com>

[TLDR: I'm adding this regression report to the list of tracked
regressions; all text from me you find below is based on a few templates
paragraphs you might have encountered already already in similar form.]

Hi, this is your Linux kernel regression tracker.

On 09.06.22 08:58, Jaroslav Pulchart wrote:
> 
> 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?

CCing the regression mailing list, as it should be in the loop for all
regressions, as explained here:
https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html

Jaroslav, did you try to revert the change that was suggested to you in
https://lore.kernel.org/all/d993bbb6-e583-5d91-76c0-841cc5da86af@roeck-us.net/
Did it help?

Anyway: To be sure below issue doesn't fall through the cracks
unnoticed, I'm adding it to regzbot, my Linux kernel regression tracking
bot:

#regzbot ^introduced v5.17 to v5.18
#regzbot title net: ice: Error setting promisc mode on VSI 6 (rc=-17) @
5.18.x
#regzbot monitor
https://lore.kernel.org/all/CAK8fFZ68+xZ2Z0vDWnihF8PeJKEmEwCyyF-8W9PCZJTd8zfp-A@mail.gmail.com/
#regzbot monitor
https://lore.kernel.org/all/CAK8fFZ61mQ3AYpdWjWtyUXzrs-RVMW61mBLrjRDXBxB-F9GzbA@mail.gmail.com/
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply -- ideally with also
telling regzbot about it, as explained here:
https://linux-regtracking.leemhuis.info/tracked-regression/

Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report (the mail this one replied to), as the kernel's
documentation call for; above page explains why this is important for
tracked regressions.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

WARNING: multiple messages have this Message-ID (diff)
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>,
	intel-wired-lan@lists.osuosl.org,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [Intel-wired-lan] ice: Error setting promisc mode on VSI 6 (rc=-17) @ 5.18.x
Date: Sun, 19 Jun 2022 13:50:55 +0200	[thread overview]
Message-ID: <2596b2c6-71e4-543f-799f-b4b174c21f31@leemhuis.info> (raw)
In-Reply-To: <CAK8fFZ7m-KR57M_rYX6xZN39K89O=LGooYkKsu6HKt0Bs+x6xQ@mail.gmail.com>

[TLDR: I'm adding this regression report to the list of tracked
regressions; all text from me you find below is based on a few templates
paragraphs you might have encountered already already in similar form.]

Hi, this is your Linux kernel regression tracker.

On 09.06.22 08:58, Jaroslav Pulchart wrote:
> 
> 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?

CCing the regression mailing list, as it should be in the loop for all
regressions, as explained here:
https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html

Jaroslav, did you try to revert the change that was suggested to you in
https://lore.kernel.org/all/d993bbb6-e583-5d91-76c0-841cc5da86af@roeck-us.net/
Did it help?

Anyway: To be sure below issue doesn't fall through the cracks
unnoticed, I'm adding it to regzbot, my Linux kernel regression tracking
bot:

#regzbot ^introduced v5.17 to v5.18
#regzbot title net: ice: Error setting promisc mode on VSI 6 (rc=-17) @
5.18.x
#regzbot monitor
https://lore.kernel.org/all/CAK8fFZ68+xZ2Z0vDWnihF8PeJKEmEwCyyF-8W9PCZJTd8zfp-A@mail.gmail.com/
#regzbot monitor
https://lore.kernel.org/all/CAK8fFZ61mQ3AYpdWjWtyUXzrs-RVMW61mBLrjRDXBxB-F9GzbA@mail.gmail.com/
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply -- ideally with also
telling regzbot about it, as explained here:
https://linux-regtracking.leemhuis.info/tracked-regression/

Reminder for developers: When fixing the issue, add 'Link:' tags
pointing to the report (the mail this one replied to), as the kernel's
documentation call for; above page explains why this is important for
tracked regressions.

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  parent reply	other threads:[~2022-06-19 11:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09  6:58 [Intel-wired-lan] ice: Error setting promisc mode on VSI 6 (rc=-17) @ 5.18.x Jaroslav Pulchart
2022-06-18 15:36 ` Jaroslav Pulchart
2022-06-19 11:50 ` Thorsten Leemhuis [this message]
2022-06-19 11:50   ` Thorsten Leemhuis
2022-06-19 17:00   ` Jaroslav Pulchart
2022-06-19 17:00     ` Jaroslav Pulchart
2022-07-05  9:43     ` Thorsten Leemhuis
2022-07-05  9:43       ` Thorsten Leemhuis
2022-07-05 13:51       ` Wilczynski, Michal
2022-07-05 13:51         ` Wilczynski, Michal
2022-08-17  9:08         ` Thorsten Leemhuis
2022-08-17  9:08           ` Thorsten Leemhuis
2022-08-17 15:59           ` Tony Nguyen
2022-08-17 15:59             ` Tony Nguyen
2022-08-17 16:07             ` Thorsten Leemhuis
2022-08-17 16:07               ` Thorsten Leemhuis
2022-08-25 10:20   ` [Intel-wired-lan] ice: Error setting promisc mode on VSI 6 (rc=-17) @ 5.18.x #forregzbot 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=2596b2c6-71e4-543f-799f-b4b174c21f31@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jaroslav.pulchart@gooddata.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.