Content-Type: text/plain; charset=US-ASCII
From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
To: "Carlos Fernandez Sanz" <cfs-lk@nisupu.com>,
       <linux-kernel@vger.kernel.org>
Subject: Re: Network issues in 2.6
Date: Mon, 5 Apr 2004 14:53:47 +0300
References: <002101c41b00$3f0f8c30$1530a8c0@HUSH>
In-Reply-To: <002101c41b00$3f0f8c30$1530a8c0@HUSH>
MIME-Version: 1.0
Content-Transfer-Encoding: 7BIT
Message-Id: <200404051453.47023.vda@port.imtp.ilyichevsk.odessa.ua>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1450
Lines: 31

On Monday 05 April 2004 14:21, Carlos Fernandez Sanz wrote:
> I upgraded from 2.4.22 to 2.6.5 (to test HPT374' support, which BTW, works
> fine).
>
> However, I'm having serious network issues now. The NIC is a 3com 3c905B.
> ifconfig shows this:
>
> eth0      Link encap:Ethernet  HWaddr 00:01:03:27:81:75
>           inet addr:192.168.20.1  Bcast:192.168.20.255  Mask:255.255.255.0
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:11241 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:9739 errors:0 dropped:0 overruns:0 carrier:9732
>           collisions:0 txqueuelen:1000
>           RX bytes:2994485 (2.8 Mb)  TX bytes:835146 (815.5 Kb)
>           Interrupt:9 Base address:0xd800
>
> Note that for TX packets, the carrier number is almost the same as the
> total packets.... booting in 2.4.22, there are zero problems.  The only
> difference in the ifconfig, other than that, is that in 2.4.22, I have
> "RUNNING" in the options (but I didn't find how to force that).

Hm. Thats strange. Your interface is not UP. It's not supposed to
do any tx/rx at all. Try to up it. If it does not work, 
strace 'ifconfig eth0 up' under both kernels and compare.
-- 
vda
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/