Hi,
Running a 2.6.22 kernel and using the forcedeth driver with
my ethernet card, I noticed this one is not available from
the gigabit section but from the 10-100Mbit section as
__nForce Ethernet Support__.
[quote forcedeth.c]
0.27: 19 Jun 2004:
Gigabit support, new descriptor
-stable review patch. If anyone has any objections, please let us know.
--
From: Timo Jantunen <[EMAIL PROTECTED]>
If the forcedeth driver receives too much work in an interrupt, it
assumes it has a broken hardware with stuck IRQ. It works around the
problem by dis
Heip!
If the forcedeth driver receives too much work in an interrupt, it assumes
it has a broken hardware with stuck IRQ. It works around the problem by
disabling interrupts on the nic but makes a printk while holding device
spinlog - which isn't smart thing to do if you have netconsole o
e machine hangs after it. Since the same test was in
the previous kernel but I don't remember ever seeing it it is possible that
2.6.22 changed timings or something like that which made hitting the
default max_interrupt_work limit more likely.
I can try to get 2.6.21.x hang with forcedeth.m
sily.
>
Well. A Key piece of information would be: did that help?
>
> I have nForce3 board and Athlon 64 X2 CPU (but using 32-bit kernel). I'm
> using the built in ethernet with forcedeth driver. I also have ATI/AMD
> binary drivers loaded, and at least in some of the
uick fix for me is to increase max_interrupt_work value so it
doesn't get hit as easily.
I have nForce3 board and Athlon 64 X2 CPU (but using 32-bit kernel). I'm
using the built in ethernet with forcedeth driver. I also have ATI/AMD
binary drivers loaded, and at least in some of the case
ssage-
From: Lennart Sorensen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 25, 2007 10:06 PM
To: Peer Chen
Cc: linux-kernel@vger.kernel.org; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [PATCH] drivers/net: move the nvidia forcedeth driver from 100M
group to 1000M group
On Wed, A
On Wed, Apr 25, 2007 at 01:30:04PM +0800, Peer Chen wrote:
> nForce ehternet is a Gigabit NIC not 100M, move it to 1000M group to
> avoid the confusion.
The forcedeth on my nforce2 board is 100Mbit. I think the driver
handles both 100Mbit and GBit type devices. Makes for an interesting
categoriz
Peer Chen wrote:
> nForce ehternet is a Gigabit NIC not 100M, move it to 1000M group to
> avoid the confusion.
Overall, maybe the 100 Mbps vs 1000 Mbps distinction is getting less
useful and it would be better to have a single list. There are a *lot*
of chipsets on the market now which have the s
nForce ehternet is a Gigabit NIC not 100M, move it to 1000M group to
avoid the confusion.
Signed-off-by: Peer Chen <[EMAIL PROTECTED]>
--- linux-2.6.21-rc7/drivers/net/Kconfig.orig
+++ linux-2.6.21-rc7/drivers/net/Kconfig
@@ -1399,35 +1399,6 @@ config B44
. The mo
My x86-64 system has two network cards, a r8169 and a forcedeth, the r8169
works fine on my network,
but when I attempt to use the forcedeth card, I get the following errors in
dmesg:
NETDEV WATCHDOG: eth0: transmit timed out
nv_stop_tx: TransmitterStatus remained busy<7>eth0: tx_timeout: dead e
11 matches
Mail list logo
