From: Anton Brekhov <anton.brekhov@rsc-tech.ru>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Max Gurtovoy <maxg@mellanox.com>,
linux-nvme@lists.infradead.org,
Konstantin Ponomarev <k.ponomarev@rsc-tech.ru>
Subject: Re: NVMe Over Fabrics Disconnect Kernel error
Date: Mon, 30 Mar 2020 11:26:51 +0300 [thread overview]
Message-ID: <CABY-YC4sWPNjZcwdZQtq_QR8iSbWZtyaAZTj8vCLL2pkdPfiZA@mail.gmail.com> (raw)
In-Reply-To: <a82f314f-f294-3cc9-5b94-f550c0538297@grimberg.me>
Ok, thank you!
By the way I found this thread https://lkml.org/lkml/2019/7/18/832
It seems to me like our problem. Maybe I'm wrong.
пн, 30 мар. 2020 г. в 07:39, Sagi Grimberg <sagi@grimberg.me>:
>
>
> > Then I'm afraid that we can't reproduce this, cause we use Intel omni
> > path drivers that is not compatible with the latest version of the
> > kernel.
> > Today we've tried to install new version of kernel, upgrade to Centos
> > 8 and 8.1. However nothing is compatible with our technologies in our
> > HPC cluster.
> > If there is any other workarounds or ideas we would be happy to hear
> > it from you.
> > If no, we'll stay in touch when will be upgrading whole cluster.
>
> Given that this is 1 RH issue, then probably you should open a ticket to
> RH asking to backport a fix or report a bug if it still exists upstream.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-03-30 8:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 6:12 NVMe Over Fabrics Disconnect Kernel error Anton Brekhov
2020-03-29 4:14 ` Sagi Grimberg
2020-03-29 8:50 ` Max Gurtovoy
2020-03-29 11:38 ` Anton Brekhov
2020-03-29 11:56 ` Max Gurtovoy
2020-03-29 14:40 ` Anton Brekhov
2020-03-30 4:38 ` Sagi Grimberg
2020-03-30 8:26 ` Anton Brekhov [this message]
2020-03-31 13:26 ` Christoph Hellwig
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=CABY-YC4sWPNjZcwdZQtq_QR8iSbWZtyaAZTj8vCLL2pkdPfiZA@mail.gmail.com \
--to=anton.brekhov@rsc-tech.ru \
--cc=k.ponomarev@rsc-tech.ru \
--cc=linux-nvme@lists.infradead.org \
--cc=maxg@mellanox.com \
--cc=sagi@grimberg.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.