[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dff8729b-3ab6-4b54-a3b0-60fabf031d62@intel.com>
Date: Thu, 18 Apr 2024 06:44:25 +0300
From: Sasha Neftin <sasha.neftin@...el.com>
To: Jérôme Carretero <cJ@...gloub.eu>, Jesse Brandeburg
<jesse.brandeburg@...el.com>, Tony Nguyen <anthony.l.nguyen@...el.com>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, PaoloAbeni <pabeni@...hat.com>, "Thomas
Gleixner" <tglx@...utronix.de>, John Stultz <jstultz@...gle.com>, StephenBoyd
<sboyd@...nel.org>, "lifshits, Vitaly" <vitaly.lifshits@...el.com>,
"Ruinskiy, Dima" <dima.ruinskiy@...el.com>, Hui Wang <hui.wang@...onical.com>
CC: <netdev@...r.kernel.org>, <intel-wired-lan@...ts.osuosl.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [Intel-wired-lan] [BUG] e1000e, scheduling while atomic
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,
>
>
Powered by blists - more mailing lists