Hi again,
I just found some more info that may (or may not) help to identify the
source of the problem outlined in my previous post (quoted below).
I just typed "dmesg" and saw the following at the end of the listing:
ping(776): unaligned trap at 0000000120002b04: 0000000120118c24 29 1
ping(776): unaligned trap at 0000000120002b2c: 0000000120118c1c 29 2
ping(776): unaligned trap at 0000000120002b04: 0000000120118c24 29 1
ping(776): unaligned trap at 0000000120002b2c: 0000000120118c1c 29 2
ping(777): unaligned trap at 0000000120002b04: 0000000120118c24 29 1
ping(777): unaligned trap at 0000000120002b2c: 0000000120118c1c 29 2
ping(777): unaligned trap at 0000000120002b04: 0000000120118c24 29 1
ping(777): unaligned trap at 0000000120002b2c: 0000000120118c1c 29 2
ping(781): unaligned trap at 0000000120002b04: 0000000120118c24 29 1
ping(781): unaligned trap at 0000000120002b2c: 0000000120118c1c 29 2
ping(781): unaligned trap at 0000000120002b04: 0000000120118c24 29 1
ping(781): unaligned trap at 0000000120002b2c: 0000000120118c1c 29 2
traceroute(784): unaligned trap at 0000000120002a9c: 000000012010613c 2d 6
traceroute(784): unaligned trap at 0000000120002aa0: 0000000120106134 2d 5
traceroute(784): unaligned trap at 0000000120002a9c: 000000012010613c 2d 6
traceroute(784): unaligned trap at 0000000120002aa0: 0000000120106134 2d 5
traceroute(785): unaligned trap at 0000000120002a9c: 000000012010613c 2d 6
traceroute(785): unaligned trap at 0000000120002aa0: 0000000120106134 2d 5
traceroute(785): unaligned trap at 0000000120002a9c: 000000012010613c 2d 6
traceroute(785): unaligned trap at 0000000120002aa0: 0000000120106134 2d 5
ping(860): unaligned trap at 0000000120002b04: 0000000120117324 29 1
ping(860): unaligned trap at 0000000120002b2c: 000000012011731c 29 2
ping(860): unaligned trap at 0000000120002b04: 0000000120117324 29 1
ping(860): unaligned trap at 0000000120002b2c: 000000012011731c 29 2
I guess the above is related to the problem, but I don't know what it means.
/Jesper juhl
> Hi,
>
> I'm not quite sure if this is a kernel related problem or a
> problem with the
> ping program that ships with Red Hat 6.0 (Alpha), but every
> time I try to
> ping a host from my AlphaServer 800 5/500 I get output like the sample
> below. It does not seem to disrupt anything - the server is
> acting like both
> a HTTP and FTP server, and there is aparently no data corruption when
> retrieving files from the server (but the output below is
> still troubling
> me).
> I recently upgraded to the 2.2.14 kernel instead of the stock
> Red Hat one to
> see if that fixed things, but the result is the same.
>
> Could someone please tell me what's wrong and how to fix it?
> If you have patches I should try, or need more information
> then just let me
> know (a few more details about the system is below the sample data).
>
> BTW: I thought that this might be becourse I was at first
> pinging a WinNT
> server (maybe it returned an invalid reply), but the result
> is the same if I
> ping a Linux or AIX server.
>
>
> Sample of output from running ping :
>
> PING 10.227.136.1 (10.227.136.1): 56 data bytes
> 64 bytes from 10.227.136.1: icmp_seq=0 ttl=255 time=0.3 ms
> wrong data byte #8 should be 0x8 but was 0xff
> 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 2
> 5 26 27 28 29 2a 2b
> 2c 2d 2e 2f 0 0 0 0 0 0 0 0 0 0 0 0
> 64 bytes from 10.227.136.1: icmp_seq=1 ttl=255 time=0.2 ms
> wrong data byte #8 should be 0x8 but was 0xd2
> 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 2
> 5 26 27 28 29 2a 2b
> 2c 2d 2e 2f 0 0 0 0 0 0 0 0 0 0 0 0
> 64 bytes from 10.227.136.1: icmp_seq=2 ttl=255 time=0.2 ms
> wrong data byte #8 should be 0x8 but was 0xb6
> 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 2
> 5 26 27 28 29 2a 2b
> 2c 2d 2e 2f 0 0 0 0 0 0 0 0 0 0 0 0
> 64 bytes from 10.227.136.1: icmp_seq=3 ttl=255 time=0.2 ms
> wrong data byte #8 should be 0x8 but was 0x93
> 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 2
> 5 26 27 28 29 2a 2b
> 2c 2d 2e 2f 0 0 0 0 0 0 0 0 0 0 0 0
> 64 bytes from 10.227.136.1: icmp_seq=4 ttl=255 time=0.2 ms
> wrong data byte #8 should be 0x8 but was 0x7a
> 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 2
> 5 26 27 28 29 2a 2b
> 2c 2d 2e 2f 0 0 0 0 0 0 0 0 0 0 0 0
> 64 bytes from 10.227.136.1: icmp_seq=5 ttl=255 time=0.2 ms
> wrong data byte #8 should be 0x8 but was 0x7c
> 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 2
> 5 26 27 28 29 2a 2b
> 2c 2d 2e 2f 0 0 0 0 0 0 0 0 0 0 0 0
> 64 bytes from 10.227.136.1: icmp_seq=6 ttl=255 time=0.2 ms
> wrong data byte #8 should be 0x8 but was 0x45
> 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 2
> 5 26 27 28 29 2a 2b
> 2c 2d 2e 2f 0 0 0 0 0 0 0 0 0 0 0 0
> 64 bytes from 10.227.136.1: icmp_seq=7 ttl=255 time=0.2 ms
> wrong data byte #8 should be 0x8 but was 0x26
> 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 2
> 5 26 27 28 29 2a 2b
> 2c 2d 2e 2f 0 0 0 0 0 0 0 0 0 0 0 0
> 64 bytes from 10.227.136.1: icmp_seq=8 ttl=255 time=0.2 ms
> wrong data byte #8 should be 0x8 but was 0xe
> 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 2
> 5 26 27 28 29 2a 2b
> 2c 2d 2e 2f 0 0 0 0 0 0 0 0 0 0 0 0
>
> --- 10.227.136.1 ping statistics ---
> 9 packets transmitted, 9 packets received, 0% packet loss
> round-trip min/avg/max = 0.2/0.2/0.3 ms
>
>
> Hardware info:
>
> AlphaServer 800 5/500
> 256MB RAM (+ 369MB swap partition)
> 3 DE-500BA NIC's installed (using a tulip driver build into
> the kernel, not
> as a module).
>
>
> Software info:
>
> Linux fenris 2.2.14 #1 Wed Feb 5 16:36:53 CET 2048 alpha unknown
> Kernel modules 2.1.121
> Gnu C egcs-2.91.66
> Binutils 2.9.1.0.24
> Linux C Library 2.1.1
> Dynamic linker ldd (GNU libc) 2.1.1
> Procps 2.0.2
> Mount 2.9o
> Net-tools 1.51
> Console-tools 1999.03.02
> Sh-utils 1.16
> Modules Loaded
>
> Output from "cat /proc/cpuinfo"
>
> cpu : Alpha
> cpu model : EV56
> cpu variation : 7
> cpu revision : 0
> cpu serial number :
> system type : Noritake
> system variation : 0
> system revision : 0
> system serial number : AY84657188
> cycle frequency [Hz] : 500000000
> timer frequency [Hz] : 1024.00
> page size [bytes] : 8192
> phys. address bits : 40
> max. addr. space # : 127
> BogoMIPS : 497.02
> kernel unaligned acc : 0 (pc=0,va=0)
> user unaligned acc : 102 (pc=120002b2c,va=12011731c)
> platform string : AlphaServer 800 5/500
> cpus detected : 1
>
>
> I hope the above is enough info :-)
>
> Best regards
> Jesper Juhl
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 21:00:22 EST