From: Eli Cohen <elic@nvidia.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>
Subject: RE: system hang on start-up (mlx5?)
Date: Wed, 3 May 2023 06:34:10 +0000 [thread overview]
Message-ID: <DM8PR12MB54003FBFCABCCB37EE807B45AB6C9@DM8PR12MB5400.namprd12.prod.outlook.com> (raw)
In-Reply-To: <A1E5B427-897B-409E-B8E3-E417678E81F6@oracle.com>
Hi Chuck,
Just verifying, could you make sure your server and card firmware are up to date?
Will try to see if I can reproduce this here.
> -----Original Message-----
> From: Chuck Lever III <chuck.lever@oracle.com>
> Sent: Wednesday, 3 May 2023 4:03
> To: Eli Cohen <elic@nvidia.com>
> Cc: Saeed Mahameed <saeedm@nvidia.com>; Leon Romanovsky
> <leon@kernel.org>; linux-rdma <linux-rdma@vger.kernel.org>; open
> list:NETWORKING [GENERAL] <netdev@vger.kernel.org>
> Subject: system hang on start-up (mlx5?)
>
> Hi-
>
> I have a Supermicro X10SRA-F/X10SRA-F with a ConnectX®-5 EN network
> interface card, 100GbE single-port QSFP28, PCIe3.0 x16, tall bracket;
> MCX515A-CCAT
>
> When booting a v6.3+ kernel, the boot process stops cold after a
> few seconds. The last message on the console is the MLX5 driver
> note about "PCIe slot advertised sufficient power (27W)".
>
> bisect reports that bbac70c74183 ("net/mlx5: Use newer affinity
> descriptor") is the first bad commit.
>
> I've trolled lore a couple of times and haven't found any discussion
> of this issue.
>
>
> --
> Chuck Lever
>
next prev parent reply other threads:[~2023-05-03 6:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 1:03 system hang on start-up (mlx5?) Chuck Lever III
2023-05-03 6:34 ` Eli Cohen [this message]
2023-05-03 14:02 ` Chuck Lever III
2023-05-04 7:29 ` Leon Romanovsky
2023-05-04 19:02 ` Chuck Lever III
2023-05-04 23:38 ` Jason Gunthorpe
2023-05-07 5:23 ` Eli Cohen
2023-05-07 5:31 ` Eli Cohen
2023-05-27 20:16 ` Chuck Lever III
2023-05-29 21:20 ` Thomas Gleixner
2023-05-30 13:09 ` Chuck Lever III
2023-05-30 13:28 ` Chuck Lever III
2023-05-30 13:48 ` Eli Cohen
2023-05-30 13:51 ` Chuck Lever III
2023-05-30 13:54 ` Eli Cohen
2023-05-30 15:08 ` Shay Drory
2023-05-31 14:15 ` Chuck Lever III
2023-05-30 19:46 ` Thomas Gleixner
2023-05-30 21:48 ` Chuck Lever III
2023-05-30 22:17 ` Thomas Gleixner
2023-05-31 14:43 ` Thomas Gleixner
2023-05-31 15:06 ` Chuck Lever III
[not found] ` <87leh4fmsg.ffs@tglx>
2023-05-31 18:52 ` Chuck Lever III
2023-05-31 19:19 ` Thomas Gleixner
2023-05-16 19:23 ` Chuck Lever III
2023-05-23 14:20 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-24 14:59 ` Chuck Lever III
2023-05-08 12:29 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-06-02 11:05 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-06-02 13:38 ` Chuck Lever III
2023-06-02 13:55 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-02 14:03 ` Chuck Lever III
2023-06-02 14:29 ` Jason Gunthorpe
2023-06-02 15:58 ` Thorsten Leemhuis
2023-06-02 16:54 ` Jakub Kicinski
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=DM8PR12MB54003FBFCABCCB37EE807B45AB6C9@DM8PR12MB5400.namprd12.prod.outlook.com \
--to=elic@nvidia.com \
--cc=chuck.lever@oracle.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
/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).