netdev - Re: [TG3]: Workaround MSI bug on 5714/5780.

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070906.073423.74747465.davem@davemloft.net>
Date:	Thu, 06 Sep 2007 07:34:23 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	andy@...yhouse.net
Cc:	mchan@...adcom.com, netdev@...r.kernel.org
Subject: Re: [TG3]: Workaround MSI bug on 5714/5780.

From: Andy Gospodarek <andy@...yhouse.net>
Date: Thu, 6 Sep 2007 09:45:16 -0400

> Is is really necessary to get rid of the HT1000 patch?

Yes, absolutely and without a single doubt.

> commit e3008dedff4bdc96a5f67224cd3d8d12237082a0
> Author: Andy Gospodarek <andy@...yhouse.net>
> Date:   Thu May 10 22:58:57 2007 -0700
> 
>     PCI: disable MSI by default on systems with Serverworks HT1000 chips
> 
> This patch was designed to address tg3 and bnx2 messages printed on
> systems with HT1000 chips IIRC.  Are we going back to those messages on
> bnx2 or is there a workaround in that driver needed too?

Every report of that problem is with tg3 chips afflicted by this
INTX bug which is now worked around properly.

Even my Niagara T1000 box was hit by this absolutely stupid and
wrong MSI quirk, which is how I found this problem to begin with.

I'm reverting it.

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html