netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: netdev@vger.kernel.org, andy@greyhouse.net
Subject: Re: [TG3]: Workaround MSI bug on 5714/5780.
Date: Thu, 06 Sep 2007 04:02:35 -0700 (PDT)	[thread overview]
Message-ID: <20070906.040235.71121480.davem@davemloft.net> (raw)
In-Reply-To: <1189022828.4960.2.camel@dell>

From: "Michael Chan" <mchan@broadcom.com>
Date: Wed, 05 Sep 2007 13:07:08 -0700

> [TG3]: Workaround MSI bug on 5714/5780.
> 
> A hardware bug was revealed after a recent PCI MSI patch was made to
> always disable legacy INTX when enabling MSI.  The 5714/5780 chips
> will not generate MSI when INTX is disabled, causing MSI failure
> messages to be reported, and another patch was made to workaround the
> problem by disabling MSI on ServerWorks HT1000 bridge chips commonly
> found with the 5714.
> 
> We workaround this chip bug by enabling INTX after we enable MSI and
> after we resume from suspend.
> 
> Update version to 3.81.
> 
> This problem was discovered by David Miller.
> 
> Signed-off-by: Michael Chan <mchan@broadcom.com>

Thanks a lot Michael, I'll apply this and work on reverting that
incorrect MSI chipset quirk too.

  parent reply	other threads:[~2007-09-06 11:02 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 [this message]
2007-09-06 13:45   ` Andy Gospodarek
2007-09-06 14:34     ` David Miller
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.040235.71121480.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).