netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: "elic@nvidia.com" <elic@nvidia.com>,
	"saeedm@nvidia.com" <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: Fri, 2 Jun 2023 13:38:45 +0000	[thread overview]
Message-ID: <AAFDF38A-E59A-4D6A-8EC2-113861C8B5DB@oracle.com> (raw)
In-Reply-To: <5b235e0f-cd4c-a453-d648-5a4e9080ac19@leemhuis.info>

Hi Thorsten -

> On Jun 2, 2023, at 7:05 AM, Linux regression tracking #update (Thorsten Leemhuis) <regressions@leemhuis.info> wrote:
> 
> [TLDR: This mail in primarily relevant for Linux regression tracking. A
> change or fix related to the regression discussed in this thread was
> posted or applied, but it did not use a Link: tag to point to the
> report, as Linus and the documentation call for.

Linus recently stated he did not like Link: tags pointing to an
email thread on lore.

Also, checkpatch.pl is now complaining about Closes: tags instead
of Link: tags. A bug was never opened for this issue.

I did check the regzbot docs on how to mark this issue closed,
but didn't find a ready answer. Thank you for following up.


> Things happen, no
> worries -- but now the regression tracking bot needs to be told manually
> about the fix. See link in footer if these mails annoy you.]
> 
> On 08.05.23 14:29, Linux regression tracking #adding (Thorsten Leemhuis)
> wrote:
>> On 03.05.23 03:03, Chuck Lever III wrote:
>>> 
>>> 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.
>> 
>> #regzbot ^introduced bbac70c74183
>> #regzbot title system hang on start-up (irq or mlx5 problem?)
>> #regzbot ignore-activity
> 
> #regzbot fix: 368591995d010e6
> #regzbot ignore-activity
> 
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://linux-regtracking.leemhuis.info/about/#tldr
> That page also explains what to do if mails like this annoy you.

--
Chuck Lever



  reply	other threads:[~2023-06-02 13:39 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
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 [this message]
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=AAFDF38A-E59A-4D6A-8EC2-113861C8B5DB@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=elic@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --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).