From: David Miller <davem@davemloft.net>
To: andy@greyhouse.net
Cc: mchan@broadcom.com, netdev@vger.kernel.org
Subject: Re: [TG3]: Workaround MSI bug on 5714/5780.
Date: Thu, 06 Sep 2007 07:34:23 -0700 (PDT) [thread overview]
Message-ID: <20070906.073423.74747465.davem@davemloft.net> (raw)
In-Reply-To: <20070906134508.GA10317@gospo.rdu.redhat.com>
From: Andy Gospodarek <andy@greyhouse.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@greyhouse.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.
next prev parent reply other threads:[~2007-09-06 14:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 20:07 [TG3]: Workaround MSI bug on 5714/5780 Michael Chan
2007-09-05 19:38 ` Andy Gospodarek
2007-09-06 11:02 ` David Miller
2007-09-06 13:45 ` Andy Gospodarek
2007-09-06 14:34 ` David Miller [this message]
2007-09-06 14:40 ` Andy Gospodarek
2007-09-06 15:41 ` Andy Gospodarek
2007-09-06 19:05 ` Michael Chan
2007-09-06 18:26 ` Andy Gospodarek
2007-09-06 19:50 ` David Miller
2007-09-06 20:27 ` Andy Gospodarek
2007-09-08 2:26 ` Michael Chan
2007-09-08 21:25 ` David Miller
2007-09-14 22:33 ` David Miller
2007-09-06 15:11 ` Michael Chan
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=20070906.073423.74747465.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=mchan@broadcom.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;
as well as URLs for NNTP newsgroup(s).