From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Leon Romanovsky' <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
'Olga Kornievskaia'
<aglo-63aXycvo3TyHXe+LvDLADg@public.gmane.org>
Cc: 'Doug Ledford' <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
'linux-rdma' <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: RE: krping problem on 4.15-rc4
Date: Fri, 19 Jan 2018 09:53:40 -0600 [thread overview]
Message-ID: <00c601d3913d$acfef920$06fceb60$@opengridcomputing.com> (raw)
In-Reply-To: <20180119110852.GB1393-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
> > >>> > > Not sure. But it does seem to be tied to that specific machine.
> Question: Is an IOMMU enabled on that system?
> > >>> >
> > >>> > IOMMU (Inter's VT-d) is enabled in BIOS (on both machines).
> > >>> >
> > >>> > > Perhaps that is exposing a dma mapping problem with krping?
> > >>>
> > >>> I have replaces the CX-5 card with another one and I no longer see
the
> > >>> krping problem. I think it speaks that it's a card issue...
> > >>
> > >> Check the firmware on the bad card. Lots of issues disappear if you
> > >> have older firmware and update to the latest.
> > >
> > > That's a valid point. A check of firmware versions is needed. At the
> > > time of the problem, I believe I had two machines that each had same
> > > firmware versions. After card replacement, the replacement card
> > > displays newer firmware.
> >
> > I have upgraded the firmware on both machines involved to the latest
> > available firmware for the card and now I'm in the situation where
> > krping does not work on either machine --- when either of them is a
> > server it fails with the same information in the var log messages:
>
> Doesn't it mean that the issue in FW?
>
Is still possible that krping has some dma mapping bug that wasn't detected
by older FW, and now is being detected by the new FW?
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-01-19 15:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 15:30 krping problem on 4.15-rc4 Olga Kornievskaia
[not found] ` <CAN-5tyH1HO7yzzQLyb5z5Pq=OrHnKzmCrR2MffLguqsEA-mwWg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-10 20:10 ` Steve Wise
2018-01-11 18:18 ` Olga Kornievskaia
2018-01-11 19:45 ` Steve Wise
2018-01-12 22:06 ` Olga Kornievskaia
[not found] ` <CAN-5tyGq=hmXY9HZYXpfaytOUV=gb0fri69gj69WKbbYtW3nTQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-13 0:07 ` Steve Wise
2018-01-16 19:50 ` Olga Kornievskaia
[not found] ` <CAN-5tyG9ZsaKZs3ayfFfuy7o25DrXR2yWmwUvLdNutJ1SbEg1w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-16 21:14 ` Olga Kornievskaia
[not found] ` <CAN-5tyFSYWaTPVdq=99Yr9XwnULyf4tw06roZys=rtR0F3x03g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-17 21:03 ` Doug Ledford
[not found] ` <1516223013.3403.285.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-17 22:03 ` Olga Kornievskaia
[not found] ` <CAN-5tyFM_Noj5n-BW+BMa-0VXBWnUVWU2JkiP2f5JBpZoA6YcQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-18 16:13 ` Olga Kornievskaia
[not found] ` <CAN-5tyGxnd0WnvgxEpNpZ5fG6u2JZs=Wg0fEvt8EaNLHckvx0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-19 11:08 ` Leon Romanovsky
[not found] ` <20180119110852.GB1393-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-19 12:21 ` Majd Dibbiny
[not found] ` <14B966CB-B883-4431-A2A3-9DDE6B88B9AB-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-01-19 13:57 ` Olga Kornievskaia
[not found] ` <CAN-5tyGiuuvzxru+aeeCahukrbm_aivN+HfLx=X1d8txxL4A9w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-19 21:07 ` Olga Kornievskaia
2018-01-19 15:53 ` Steve Wise [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='00c601d3913d$acfef920$06fceb60$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=aglo-63aXycvo3TyHXe+LvDLADg@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matanb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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 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.