netdev - Re: mlx4 fails ("go bit not cleared") without MSI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAErSpo7RKHE-vopDYh8P83Wb_5_-Fj8SSn7_Z=9cqYgBOejpxw@mail.gmail.com>
Date:	Wed, 20 Jan 2016 11:00:49 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Yishai Hadas <yishaih@...lanox.com>
Cc:	"helgaas@...nel.org" <helgaas@...nel.org>,
	Majd Dibbiny <majd@...lanox.com>,
	Tal Alon <talal@...lanox.com>,
	"Or Gerlitz (gerlitz.or@...il.com)" <gerlitz.or@...il.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: mlx4 fails ("go bit not cleared") without MSI

On Wed, Jan 20, 2016 at 3:42 AM, Yishai Hadas <yishaih@...lanox.com> wrote:
>> From: Bjorn Helgaas [mailto:bhelgaas@...gle.com]
>> I assume you're tried booting with "pci=nomsi" or "mlx_core.msi_x=0"
>> and it works for you?  Note that my board might be an internal design,
>> not a Mellanox board, so if it works for you, we can probably just
>> ignore this as being an artifact of the internal design.
>
> Yes, it works for me (module parameter msi_x=0), as you pointed out above
> you are not using Mellanox board but some internal design and
> it might be some artifact of.

OK, let's assume that's the case.  I haven't seen the actual board, so
I can't be certain what I'm using.  Thanks for checking into it.

Bjorn