netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: Tariq Toukan <ttoukan.linux@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Jay Vosburgh <j.vosburgh@gmail.com>,
	Veaceslav Falico <vfalico@gmail.com>,
	Andy Gospodarek <andy@greyhouse.net>,
	Moshe Shemesh <moshe@nvidia.com>,
	Itay Aveksis <itayav@nvidia.com>,
	Ran Rozenstein <ranro@nvidia.com>,
	tariqt@nvidia.com
Subject: Re: bug report: WARNING in bonding
Date: Thu, 12 Nov 2020 17:46:27 +0200	[thread overview]
Message-ID: <20201112154627.GA2138135@shredder> (raw)
In-Reply-To: <fb299ee2-4cf0-31d8-70f4-874da43e0021@gmail.com>

On Thu, Nov 12, 2020 at 05:38:44PM +0200, Tariq Toukan wrote:
> Hi all,
> 
> In the past ~2-3 weeks, we started seeing the following WARNING and traces
> in our regression testing systems, almost every day.
> 
> Reproduction is not stable, and not isolated to a specific test, so it's
> hard to bisect.
> 
> Any idea what could this be?
> Or what is the suspected offending patch?

Do you have commit f8e48a3dca06 ("lockdep: Fix preemption WARN for spurious
IRQ-enable")? I think it fixed the issue for me

  reply	other threads:[~2020-11-12 15:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 15:38 bug report: WARNING in bonding Tariq Toukan
2020-11-12 15:46 ` Ido Schimmel [this message]
2020-11-12 15:54   ` Tariq Toukan
2020-11-12 16:33     ` Ido Schimmel
2021-02-18 17:10       ` Tariq Toukan
2021-02-25 15:24         ` Tariq Toukan
2021-04-06 18:02           ` Steven Rostedt

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=20201112154627.GA2138135@shredder \
    --to=idosch@idosch.org \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=itayav@nvidia.com \
    --cc=j.vosburgh@gmail.com \
    --cc=kuba@kernel.org \
    --cc=moshe@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=ranro@nvidia.com \
    --cc=tariqt@nvidia.com \
    --cc=ttoukan.linux@gmail.com \
    --cc=vfalico@gmail.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).