From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: rabollinger@gmail.com, netdev@vger.kernel.org
Subject: Re: tg3 driver fails with on-board BCM95789 NICS (GigaByte GA-7VCSV)
Date: Tue, 24 Oct 2006 21:33:50 -0700 (PDT) [thread overview]
Message-ID: <20061024.213350.74746920.davem@davemloft.net> (raw)
In-Reply-To: <1551EAE59135BE47B544934E30FC4FC093FC6D@NT-IRVA-0751.brcm.ad.broadcom.com>
From: "Michael Chan" <mchan@broadcom.com>
Date: Tue, 24 Oct 2006 21:31:56 -0700
> Can you cat /proc/interrupts a few times to see if the interrupt
> counts on eth1 and eth2 are increasing?
>
> You can also run ethtool -t [eth1 | eth2] to run a basic selftest
> on the 2 devices. Be sure to ifconfig up first before the selftest.
It's an interrupt routing problem for sure, Adrian Bunk
posted a potential fix to this poster an hour or so
ago.
next prev parent reply other threads:[~2006-10-25 4:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 21:32 tg3 driver fails with on-board BCM95789 NICS (GigaByte GA-7VCSV) Richard Bollinger
2006-10-25 4:31 ` Michael Chan
2006-10-25 4:33 ` David Miller [this message]
2006-10-25 13:36 ` Richard Bollinger
2006-10-25 13:02 ` Richard Bollinger
2006-10-25 16:39 ` Michael Chan
2006-10-25 19:29 ` Richard Bollinger
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=20061024.213350.74746920.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=rabollinger@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.