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

Bug#422271: this is not only an installation problem



retitle 422271 eth0 works not properly on B2000 because 
thanks

I have now tried to install debian 4.0 hppa with CD1 and without any
mirror,
installation ok but the same problems with eth0. Tulip is loaded but the
connections
are instable, TCP connection like ssh hangs often, but because this
protocol uses
an error correction it goes on after 10 or more seconds. ICPM show many
errors:

	# ping 192.168.1.5
	PING 192.168.1.5 (192.168.1.5) 56(84) bytes of data.
	64 bytes from 192.168.1.5: icmp_seq=1 ttl=64 time=4.05 ms
	64 bytes from 192.168.1.5: icmp_seq=2 ttl=64 time=0.249 ms
	wrong data byte #23 should be 0x17 but was 0x37
	#8      8 9 a b c d e f 10 11 12 13 14 15 16 37 18 19 1a 1b 1c
1d 1e 1f 20 21 22 23 24 25 26 27
	#40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37
	64 bytes from 192.168.1.5: icmp_seq=4 ttl=64 time=0.235 ms
	64 bytes from 192.168.1.5: icmp_seq=5 ttl=64 time=0.294 ms
	64 bytes from 192.168.1.5: icmp_seq=6 ttl=64 time=0.216 ms
	64 bytes from 192.168.1.5: icmp_seq=7 ttl=64 time=0.284 ms
	64 bytes from 192.168.1.5: icmp_seq=8 ttl=64 time=0.257 ms
	wrong data byte #23 should be 0x17 but was 0x37
	#8      8 9 a b c d e f 10 11 12 13 14 15 16 37 18 19 1a 1b 1c
1d 1e 1f 20 21 22 23 24 25 26 27
	#40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37
	64 bytes from 192.168.1.5: icmp_seq=9 ttl=64 time=0.268 ms
	wrong data byte #11 should be 0xb but was 0x2b
	#8      8 9 a 2b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c
1d 1e 1f 20 21 22 23 24 25 26 27
	#40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37
	64 bytes from 192.168.1.5: icmp_seq=13 ttl=64 time=0.169 ms
	64 bytes from 192.168.1.5: icmp_seq=14 ttl=64 time=0.295 ms
	64 bytes from 192.168.1.5: icmp_seq=15 ttl=64 time=0.153 ms
	64 bytes from 192.168.1.5: icmp_seq=16 ttl=64 time=0.282 ms
	64 bytes from 192.168.1.5: icmp_seq=49 ttl=64 time=0.337 ms
	wrong data byte #15 should be 0xf but was 0x2f
	#8      8 9 a b c d e 2f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c
1d 1e 3f 20 21 22 23 24 25 26 27
	#40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37
	64 bytes from 192.168.1.5: icmp_seq=18 ttl=64 time=0.196 ms
	64 bytes from 192.168.1.5: icmp_seq=51 ttl=64 time=0.248 ms
	wrong data byte #15 should be 0xf but was 0x2f
	#8      8 9 a b c d e 2f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c
1d 1e 1f 20 21 22 23 24 25 26 27
	#40     28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37
	64 bytes from 192.168.1.5: icmp_seq=20 ttl=64 time=0.178 ms
	64 bytes from 192.168.1.5: icmp_seq=21 ttl=64 time=0.315 ms
	
	--- 192.168.1.5 ping statistics ---
	21 packets transmitted, 17 received, 19% packet loss, time
20000ms
	rtt min/avg/max/mdev = 0.153/0.472/4.055/0.897 ms

There is no difference if 100baseTx-FD, 100baseTx-HD, 10baseT-FD or
10baseT-HD or an other
switch is used. IMO it is an interrupt problem, because both sites of
the cat5 cable does not
show any error on the link (or max one).

BR, Silvio

Attachment: mii-tool.log
Description: mii-tool.log

Attachment: dmsg.log
Description: dmsg.log

Attachment: lsmod.log
Description: lsmod.log

Attachment: lspci.log
Description: lspci.log


Reply to: