From: Jason Gunthorpe <jgg@ziepe.ca>
To: rug@usm.lmu.de
Cc: linux-rdma@vger.kernel.org
Subject: Re: Infiniband crash
Date: Fri, 14 Oct 2022 16:21:51 -0300 [thread overview]
Message-ID: <Y0m2z+d3T/fnRW/Z@ziepe.ca> (raw)
In-Reply-To: <20221014181651.Horde.p1jZxomAX1Dlqme6qIvYwJa@www.usm.uni-muenchen.de>
On Fri, Oct 14, 2022 at 06:16:51PM +0000, rug@usm.lmu.de wrote:
> Hi to whom it may concern,
>
> We are getting on a 6.0.0 (and also on 5.10 up) the following Mellanox
> infiniband problem (see below).
> Can you please help (this is on a running ia64 cluster).
The fastest/simplest way to get help on something so obscure would be
to bisection search to the problematic commit
You might be the only user left in the world of this combination :)
Jason
next prev parent reply other threads:[~2022-10-14 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 18:16 Infiniband crash rug
2022-10-14 19:21 ` Jason Gunthorpe [this message]
2022-10-17 10:13 ` Christoph Lameter
2022-10-17 11:24 ` Rudolf Gabler
-- strict thread matches above, loose matches on Subject: below --
2024-12-16 18:05 tpearson
2024-12-17 8:10 ` Thomas Bogendoerfer
2024-12-17 19:42 ` Timothy Pearson
2024-12-16 18:06 tpearson
[not found] ` <420F7218-5193-44B3-AD7F-ACED38C206AE@usm.lmu.de>
2024-12-16 20:10 ` Timothy Pearson
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=Y0m2z+d3T/fnRW/Z@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=rug@usm.lmu.de \
/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