Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jarek Poplawski wrote:
On Sat, Dec 30, 2006 at 02:21:15AM +0000, Sid Boyce wrote:
Jarek Poplawski wrote:
On 28-12-2006 04:23, Sid Boyce wrote:
I first saw the problem on the 64x2 box after upgrading to 2.6.19. The
network appeared OK with ifconfig and route -n, but I had no network
access. Pinging any other box, the box was responding, but no response
...
barrabas:/usr/src/linux-2.6.20-rc1-git5 # ssh Boycie ifconfig
Password:
eth0      Link encap:Ethernet  HWaddr 00:0A:E4:4E:A1:42
inet addr:192.168.10.5 Bcast:255.255.255.255 Mask:255.255.255.0
This Bcast isn't probably what you need.

Regards,
Jarek P.


Corrected on the one box where it was not correct, problem is still there.

There are many things to suspect yet:
- firewall,
- switch,
- routing,
- ifconfig,
- other misonfigured box,
- connecting
and so on.

I think you should try with some linux networking group
at first and if you really think it's driver then
[email protected] (instead of linux-kernel@).

If you could send full ifconfig, route -n (or ip route
if you use additional tables) and tcpdump (all packets)
from both boxes while pinging each other and a few words
how it is connected (other cards, other active boxes in
the network?) maybe something more could be found.

Cheers,
Jarek P.
PS: Sorry for late responding.


I have a problem with posting to linux-kernel and netdev, my mail got
returned as SPAM, now it just gets dropped. postmaster says the filter
is seeing a sub-string of something that is filtered. I shall try under my other email address.

Everything is fine with a eepro100 on the 64x2 box that gave the same
problem with a nVidia Corporation MCP51 Ethernet Controller (rev a1)
using the forcedeth module. On the x86_64 laptop the problem is with a
Broadcom NetXtreme BCM5788 using the tg3 module. Switching back to a
2.6.18.2 kernel, there is no problem.
With all configurations of cards on both, route -n is the same on all
kernels and instantly reports back. With >=2.6.19 on the laptop, netstat
-r takes a very long time before returning the information ~30 seconds,
instantly on 2.6.18.2.
Boycie:~ # netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
192.168.10.0    *               255.255.255.0   U         0 0          0
eth0
loopback        *               255.0.0.0       U         0 0          0 lo
default         Smoothie.site   0.0.0.0         UG        0 0          0
eth0
Boycie:~ # route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.10.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         192.168.10.102  0.0.0.0         UG    0      0        0 eth0


--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux