From: "Jérôme Carretero" <cJ-ko@zougloub.eu>
To: Sasha Neftin <sasha.neftin@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [Intel-wired-lan] [BUG] e1000e, scheduling while atomic (stable)
Date: Fri, 19 Apr 2024 12:20:05 -0400 [thread overview]
Message-ID: <2259bbeb9a012548779e3bf09a393fdb7d62dd0c.camel@zougloub.eu> (raw)
In-Reply-To: <dff8729b-3ab6-4b54-a3b0-60fabf031d62@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
Hi Sasha,
Thank you, sorry for the delay but I coudln't reboot.
Adding Greg KH because I don't know if stable will receive my e-mail
(not subscribed) but the regression was integrated in stable:
commit 0a4e3c2d976aa4dd38951afd6267f74ef3fade0e
so they should get the fix ASAP too.
Tested-by: Jérôme Carretero <cJ-ko@zougloub.eu>
Best regards,
--
Jérôme
On Thu, 2024-04-18 at 06:44 +0300, Sasha Neftin wrote:
> 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,
> >
> >
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
next prev parent reply other threads:[~2024-04-19 16:20 UTC|newest]
Thread overview: 10+ 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-18 3:44 ` [Intel-wired-lan] " Sasha Neftin
2024-04-19 16:20 ` Jérôme Carretero [this message]
2024-04-20 16:17 ` [Intel-wired-lan] [BUG] e1000e, scheduling while atomic (stable) 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=2259bbeb9a012548779e3bf09a393fdb7d62dd0c.camel@zougloub.eu \
--to=cj-ko@zougloub.eu \
--cc=gregkh@linuxfoundation.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sasha.neftin@intel.com \
--cc=stable@vger.kernel.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).