netdev - RE: system hang on start-up (mlx5?)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <DM8PR12MB54004679C6E1D72E0960FFE8AB709@DM8PR12MB5400.namprd12.prod.outlook.com>
Date: Sun, 7 May 2023 05:23:08 +0000
From: Eli Cohen <elic@...dia.com>
To: Jason Gunthorpe <jgg@...pe.ca>, Chuck Lever III <chuck.lever@...cle.com>
CC: Leon Romanovsky <leon@...nel.org>, Saeed Mahameed <saeedm@...dia.com>,
	linux-rdma <linux-rdma@...r.kernel.org>, "open list:NETWORKING [GENERAL]"
	<netdev@...r.kernel.org>
Subject: RE: system hang on start-up (mlx5?)

Maybe. And maybe the problem is triggered due to the usage we make of that infrastructure. If I am not mistaken, mlx5_core is the first and only driver to make use of this infrastructure.
 
> -----Original Message-----
> From: Jason Gunthorpe <jgg@...pe.ca>
> Sent: Friday, 5 May 2023 2:38
> To: Chuck Lever III <chuck.lever@...cle.com>
> Cc: Leon Romanovsky <leon@...nel.org>; Eli Cohen <elic@...dia.com>; Saeed
> Mahameed <saeedm@...dia.com>; linux-rdma <linux-
> rdma@...r.kernel.org>; open list:NETWORKING [GENERAL]
> <netdev@...r.kernel.org>
> Subject: Re: system hang on start-up (mlx5?)
> 
> On Thu, May 04, 2023 at 07:02:48PM +0000, Chuck Lever III wrote:
> >
> >
> > > On May 4, 2023, at 3:29 AM, Leon Romanovsky <leon@...nel.org> wrote:
> > >
> > > On Wed, May 03, 2023 at 02:02:33PM +0000, Chuck Lever III wrote:
> > >>
> > >>
> > >>> On May 3, 2023, at 2:34 AM, Eli Cohen <elic@...dia.com> wrote:
> > >>>
> > >>> Hi Chuck,
> > >>>
> > >>> Just verifying, could you make sure your server and card firmware are
> up to date?
> > >>
> > >> Device firmware updated to 16.35.2000; no change.
> > >>
> > >> System firmware is dated September 2016. I'll see if I can get
> > >> something more recent installed.
> > >
> > > We are trying to reproduce this issue internally.
> >
> > More information. I captured the serial console during boot.
> > Here are the last messages:
> 
> Oh I wonder if this is connected to Thomas's recent interrupt and MSI
> rework? Might need to bisection search around those big series
> 
> Jason