From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Lamparter Subject: Re: mlx4 w/ IOMMU broken, kernel 3.12.6 -- resolved Date: Thu, 9 Jan 2014 13:46:19 +0100 Message-ID: <20140109124619.GD351037@jupiter.n2.diac24.net> References: <20140108134917.GC351037@jupiter.n2.diac24.net> <20140109075411.GA27750@mtl-eit-vdi-22.mtl.labs.mlnx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: David Lamparter , netdev@vger.kernel.org To: Amir Vadai Return-path: Received: from spaceboyz.net ([87.106.131.203]:59801 "EHLO spaceboyz.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751060AbaAIMqe (ORCPT ); Thu, 9 Jan 2014 07:46:34 -0500 Content-Disposition: inline In-Reply-To: <20140109075411.GA27750@mtl-eit-vdi-22.mtl.labs.mlnx> Sender: netdev-owner@vger.kernel.org List-ID: 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 ' > > 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