From: "Jérôme Carretero" <cJ@zougloub.eu>
To: 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>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [BUG] e1000e, scheduling while atomic
Date: Wed, 17 Apr 2024 14:46:52 -0400 [thread overview]
Message-ID: <a7eb665c74b5efb5140e6979759ed243072cb24a.camel@zougloub.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
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.
I just verified that this happens on the latest master.
Let me know if I can (quickly) help,
--
Jérôme
PS: Sorry if I'm sending this to too many people, I did a
get_maintainer timer and e1000e code.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
next reply other threads:[~2024-04-17 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 18:46 Jérôme Carretero [this message]
2024-04-18 3:44 ` [Intel-wired-lan] [BUG] e1000e, scheduling while atomic 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-23 16:23 ` Greg Kroah-Hartman
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
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=a7eb665c74b5efb5140e6979759ed243072cb24a.camel@zougloub.eu \
--to=cj@zougloub.eu \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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 \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).