From: Guenter Roeck <linux@roeck-us.net>
To: Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, slade@sladewatkins.com
Subject: Re: [PATCH 5.18 000/343] 5.18.4-rc2 review
Date: Tue, 14 Jun 2022 08:33:56 -0700 [thread overview]
Message-ID: <d993bbb6-e583-5d91-76c0-841cc5da86af@roeck-us.net> (raw)
In-Reply-To: <CAK8fFZ4JnhA3s8e4YDp_+GOq5+p4YzRtKdEFzjogtXc3EBttzw@mail.gmail.com>
On 6/14/22 08:03, Jaroslav Pulchart wrote:
> út 14. 6. 2022 v 16:56 odesílatel Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> napsal:
>>
>> On Tue, Jun 14, 2022 at 04:41:31PM +0200, Jaroslav Pulchart wrote:
>>> út 14. 6. 2022 v 8:34 odesílatel Greg Kroah-Hartman
>>> <gregkh@linuxfoundation.org> napsal:
>>>>
>>>> On Tue, Jun 14, 2022 at 07:56:36AM +0200, Jaroslav Pulchart wrote:
>>>>> Hello,
>>>>>
>>>>> I would like to report that the ethernet ice driver is not capable of
>>>>> setting promisc mode on at E810-XXV physical interface in the whole
>>>>> 5.18.y kernel line.
>>>>>
>>>>> Reproducer:
>>>>> $ ip link set promisc on dev em1
>>>>> Dmesg error message:
>>>>> Error setting promisc mode on VSI 6 (rc=-17)
>>>>>
>>>>> the problem was not observed with 5.17.y
>>>>
>>>> Any chance you can use 'git bisect' to track down the problem commit and
>>>> let the developers of it know?
>>>>
>>>> thanks,
>>>
>>> I tried it, but it makes the system unbootable. I expect the reason is
>>> that it happened somewhere between 5.17->5.18 so I'm using an
>>> "unstable" kernel.
>>>
>>> Is there some way I could bisect just one driver, not a full kernel
>>> between 5.17->5.18?
>>
>> How do you know it is just "one driver"?
>
> Just a quess based on "git grep". The error message was introduced in
> the driver in 5.18-rc*.
>
The message was introduced with commit 1273f89578f26 ("ice: Fix broken
IFF_ALLMULTI handling"). Given that commit message, it appears to be
at least somewhat likely that reverting this commit will fix your problem.
I would suggest to give it a try.
Guenter
next prev parent reply other threads:[~2022-06-14 15:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 18:18 [PATCH 5.18 000/343] 5.18.4-rc2 review Greg Kroah-Hartman
2022-06-13 21:50 ` Florian Fainelli
2022-06-13 22:16 ` Justin Forbes
2022-06-14 1:50 ` Ron Economos
2022-06-14 3:04 ` Shuah Khan
2022-06-14 5:56 ` Jaroslav Pulchart
2022-06-14 6:34 ` Greg Kroah-Hartman
2022-06-14 14:41 ` Jaroslav Pulchart
2022-06-14 14:56 ` Greg Kroah-Hartman
2022-06-14 15:03 ` Jaroslav Pulchart
2022-06-14 15:33 ` Guenter Roeck [this message]
2022-06-14 9:10 ` Jiri Slaby
2022-06-14 11:47 ` Rudi Heitbaum
2022-06-14 14:35 ` Fenil Jain
2022-06-14 15:48 ` Guenter Roeck
2022-06-14 18:18 ` Naresh Kamboju
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=d993bbb6-e583-5d91-76c0-841cc5da86af@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jaroslav.pulchart@gooddata.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=slade@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/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).