All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Intel-wired-lan] ice: Error setting promisc mode on VSI 6 (rc=-17) @ 5.18.x #forregzbot
Date: Thu, 25 Aug 2022 12:20:37 +0200	[thread overview]
Message-ID: <da420331-b160-6675-d638-8abbbbb7ce01@leemhuis.info> (raw)
In-Reply-To: <2596b2c6-71e4-543f-799f-b4b174c21f31@leemhuis.info>

TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.

On 19.06.22 13:50, Thorsten Leemhuis wrote:
> [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.]
> 
> 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)
>
> 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

#regzbot fixed-by: 79956b83ed4281c35561c39254558092d96a9ed1

      parent reply	other threads:[~2022-08-25 10:20 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
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   ` Thorsten Leemhuis [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=da420331-b160-6675-d638-8abbbbb7ce01@leemhuis.info \
    --to=regressions@leemhuis.info \
    --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.