On 10/25/06, Michael Chan <[EMAIL PROTECTED]> wrote:
This confirms that it's some kind of interrupt problem as David had
suggested, at least on eth2. You can try booting with "noapic" to see
if it works if you haven't got the patch from Adrian Bunk yet.
No joy. Here's the dmesg after boot w/
On Wed, 2006-10-25 at 09:02 -0400, Richard Bollinger wrote:
> # ethtool -t eth2
> The test result is FAIL
> The test extra info:
> nvram test (online) 0
> link test (online) 1
> register test (offline) 0
> memory test(offline) 0
> loopback test (off
On 10/25/06, David Miller <[EMAIL PROTECTED]> wrote:
It's an interrupt routing problem for sure, Adrian Bunk
posted a potential fix to this poster an hour or so
ago.
I'm running with arch=i386 and the only related postings I see are for
x86_64 :-(.
-
To unsubscribe from this list: send the line
On 10/25/06, Michael Chan <[EMAIL PROTECTED]> wrote:
...
Can you cat /proc/interrupts a few times to see if the interrupt
counts on eth1 and eth2 are increasing?
# grep eth /proc/interrupts
9: 0 0 0 0IO-APIC-edge eth2
16: 177724 0 371238
From: "Michael Chan" <[EMAIL PROTECTED]>
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 ifconfi
Richard Bollinger wrote:
> GigaByte GA-7VCSV-RH motherboard w/two dual core Xeon's, 4gb RAM,
> Intel 5000v Chipset, dual Broadcom 5789 Gigabit Ethernet Controllers,
> connected to Dell GigE switch.
>
> Both interfaces work fine with vendor's drivers on Windows 2003, but
> using Linux 2.6.18.1 tg3
GigaByte GA-7VCSV-RH motherboard w/two dual core Xeon's, 4gb RAM,
Intel 5000v Chipset, dual Broadcom 5789 Gigabit Ethernet Controllers,
connected to Dell GigE switch.
Both interfaces work fine with vendor's drivers on Windows 2003, but
using Linux 2.6.18.1 tg3 or vendor's Linux driver, the first
