From: Sasha Neftin <sasha.neftin@intel.com>
To: "Jérôme Carretero" <cJ@zougloub.eu>,
"Jesse Brandeburg" <jesse.brandeburg@intel.com>,
"Tony Nguyen" <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
PaoloAbeni <pabeni@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"John Stultz" <jstultz@google.com>,
StephenBoyd <sboyd@kernel.org>,
"lifshits, Vitaly" <vitaly.lifshits@intel.com>,
"Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
"Hui Wang" <hui.wang@canonical.com>
Cc: <netdev@vger.kernel.org>, <intel-wired-lan@lists.osuosl.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [BUG] e1000e, scheduling while atomic
Date: Thu, 18 Apr 2024 06:44:25 +0300 [thread overview]
Message-ID: <dff8729b-3ab6-4b54-a3b0-60fabf031d62@intel.com> (raw)
In-Reply-To: <a7eb665c74b5efb5140e6979759ed243072cb24a.camel@zougloub.eu>
On 17/04/2024 21:46, Jérôme Carretero wrote:
> Hi,
>
>
> I opened https://bugzilla.kernel.org/show_bug.cgi?id=218740 because I'm
> not quite sure the culprit is e1000e or some timer stuff.
Hello Jérôme,
You hit on regression introduced by 6dbdd4de0362 (used the wrong timer
during code running in atomic contexts)
Please, incorporate
https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20240417190320.3159360-1-vitaly.lifshits@intel.com/
in your latest kernel.
Thanks,
sasha
>
> I just verified that this happens on the latest master.
>
>
> Let me know if I can (quickly) help,
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Neftin <sasha.neftin@intel.com>
To: "Jérôme Carretero" <cJ@zougloub.eu>,
"Jesse Brandeburg" <jesse.brandeburg@intel.com>,
"Tony Nguyen" <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
PaoloAbeni <pabeni@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"John Stultz" <jstultz@google.com>,
StephenBoyd <sboyd@kernel.org>,
"lifshits, Vitaly" <vitaly.lifshits@intel.com>,
"Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
"Hui Wang" <hui.wang@canonical.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] [BUG] e1000e, scheduling while atomic
Date: Thu, 18 Apr 2024 06:44:25 +0300 [thread overview]
Message-ID: <dff8729b-3ab6-4b54-a3b0-60fabf031d62@intel.com> (raw)
In-Reply-To: <a7eb665c74b5efb5140e6979759ed243072cb24a.camel@zougloub.eu>
On 17/04/2024 21:46, Jérôme Carretero wrote:
> Hi,
>
>
> I opened https://bugzilla.kernel.org/show_bug.cgi?id=218740 because I'm
> not quite sure the culprit is e1000e or some timer stuff.
Hello Jérôme,
You hit on regression introduced by 6dbdd4de0362 (used the wrong timer
during code running in atomic contexts)
Please, incorporate
https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20240417190320.3159360-1-vitaly.lifshits@intel.com/
in your latest kernel.
Thanks,
sasha
>
> I just verified that this happens on the latest master.
>
>
> Let me know if I can (quickly) help,
>
>
next prev parent reply other threads:[~2024-04-18 3:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 18:46 [BUG] e1000e, scheduling while atomic Jérôme Carretero
2024-04-17 18:46 ` [Intel-wired-lan] " Jérôme Carretero
2024-04-18 3:44 ` Sasha Neftin [this message]
2024-04-18 3:44 ` Sasha Neftin
2024-04-19 16:20 ` [Intel-wired-lan] [BUG] e1000e, scheduling while atomic (stable) Jérôme Carretero
2024-04-20 16:17 ` Sasha Neftin
2024-04-20 16:17 ` Sasha Neftin
2024-04-23 16:23 ` Greg Kroah-Hartman
2024-04-23 16:23 ` Greg Kroah-Hartman
2024-04-25 6:06 ` Sasha Neftin
2024-04-25 6:06 ` Sasha Neftin
2024-04-27 10:54 ` Artem S. Tashkinov
2024-04-27 11:14 ` Greg KH
2024-04-28 8:01 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-29 17:13 ` Tony Nguyen
2024-04-29 17:13 ` Tony Nguyen
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=dff8729b-3ab6-4b54-a3b0-60fabf031d62@intel.com \
--to=sasha.neftin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=cJ@zougloub.eu \
--cc=davem@davemloft.net \
--cc=dima.ruinskiy@intel.com \
--cc=edumazet@google.com \
--cc=hui.wang@canonical.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=jstultz@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=vitaly.lifshits@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 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.