Netdev List
 help / color / mirror / Atom feed
From: David Lamparter <equinox@diac24.net>
To: Amir Vadai <amirv@mellanox.com>
Cc: David Lamparter <equinox@diac24.net>, netdev@vger.kernel.org
Subject: Re: mlx4 w/ IOMMU broken, kernel 3.12.6 -- resolved
Date: Thu, 9 Jan 2014 13:46:19 +0100	[thread overview]
Message-ID: <20140109124619.GD351037@jupiter.n2.diac24.net> (raw)
In-Reply-To: <20140109075411.GA27750@mtl-eit-vdi-22.mtl.labs.mlnx>

On Thu, Jan 09, 2014 at 09:54:15AM +0200, Amir Vadai wrote:
> What is the firmware version?
> You can get it by issuing 'ethtool -i <interface>'
> 
> Please make sure you're using the latest FW from mellanox.com.

Ah, indeed updating from 2.11.500 to 2.30.8000 has fixed the issue.
(The driver could print a warning for this?)

(Note: updating the firmware has been rather annoying due to the complex
and complicated way the OEM branding [this is an IBM card] is designed.
If you have some way of passing up user experience feedback, please put
a note down on this.)

> We still don't have MLNX_OFED package that supports this kernel.

I noticed, the kernel driver from the external package is referencing
things that have disappeared from the kernel around version 3.8.  Though
I don't see why there is both an in-kernel driver and a separate
package...

Thanks for the firmware pointer,


David

  reply	other threads:[~2014-01-09 12:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 13:49 mlx4 w/ IOMMU broken, kernel 3.12.6 David Lamparter
2014-01-09  7:54 ` Amir Vadai
2014-01-09 12:46   ` David Lamparter [this message]
2014-01-09 13:24     ` mlx4 w/ IOMMU broken, kernel 3.12.6 -- resolved Amir Vadai

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=20140109124619.GD351037@jupiter.n2.diac24.net \
    --to=equinox@diac24.net \
    --cc=amirv@mellanox.com \
    --cc=netdev@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