[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+QYu4qtGSiC_vUFq3gynMWYbZQN=c7Bnp7HvpLJObg7ndcxNw@mail.gmail.com>
Date: Thu, 23 Feb 2023 16:16:19 +0100
From: Bruno Goncalves <bgoncalv@...hat.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Manish Chopra <manishc@...vell.com>,
Ariel Elior <aelior@...vell.com>,
LKML <linux-kernel@...r.kernel.org>,
Networking <netdev@...r.kernel.org>,
CKI Project <cki-project@...hat.com>,
Saurav Kashyap <skashyap@...vell.com>,
Javed Hasan <jhasan@...vell.com>,
Alok Prasad <palok@...vell.com>
Subject: Re: [EXT] Re: RIP: 0010:qede_load+0x128d/0x13b0 [qede] - 5.19.0
On Wed, 22 Feb 2023 at 22:34, Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Fri, 19 Aug 2022 09:36:54 +0200 Bruno Goncalves wrote:
> > We hit the panic by booting up the machine with a kernel 5.19.0 with
> > debug flags enabled.
>
> Hi Bruno,
>
> Was this ever fixed?
It looks like it got fixed, I haven't seen this failure on 6.2.0 kernels.
Bruno
Powered by blists - more mailing lists