From: Leon Romanovsky <leon@kernel.org>
To: Haakon Bugge <haakon.bugge@oracle.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
OFED mailing list <linux-rdma@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH for-next] Revert "IB/mlx5: Don't return errors from poll_cq"
Date: Fri, 4 Mar 2022 19:24:01 +0200 [thread overview]
Message-ID: <YiJLMaPUzrTgsAPL@unreal> (raw)
In-Reply-To: <726B8D27-B7C7-4779-A56B-3AE9266BC208@oracle.com>
On Fri, Mar 04, 2022 at 10:53:34AM +0000, Haakon Bugge wrote:
>
>
> > On 3 Mar 2022, at 20:09, Leon Romanovsky <leon@kernel.org> wrote:
> >
> > On Thu, Mar 03, 2022 at 02:50:17PM +0100, Håkon Bugge wrote:
> >> This reverts commit dbdf7d4e7f911f79ceb08365a756bbf6eecac81c.
> >>
> >> Commit dbdf7d4e7f91 ("IB/mlx5: Don't return errors from poll_cq") is
> >> needed, when driver/fw communication gets wedged.
> >>
> >> With a large fleet of systems equipped with CX-5, we have observed the
> >> following mlx5 error message:
> >>
> >> wait_func:945:(pid xxx): ACCESS_REG(0x805) timeout. Will cause a
> >> leak of a command resource
> >
> > It is arguably FW issue. Please contact your Nvidia support representative.
>
> The RC for the whacked driver/fw communication has been raised with Nvidia support. This commit is to avoid the kernel to crash when this situation arises. And inevitable, it may happen.
I'm confident that support team will find best possible solution to the
raised issue.
Thanks
>
>
> Thxs, Håkon
prev parent reply other threads:[~2022-03-04 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 13:50 [PATCH for-next] Revert "IB/mlx5: Don't return errors from poll_cq" Håkon Bugge
2022-03-03 19:09 ` Leon Romanovsky
2022-03-04 10:53 ` Haakon Bugge
2022-03-04 17:24 ` Leon Romanovsky [this message]
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=YiJLMaPUzrTgsAPL@unreal \
--to=leon@kernel.org \
--cc=haakon.bugge@oracle.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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