Hello,
since very early in the 2.6.14 process ping or traceroute gives very
strange timestamps. eg
64 bytes from 192.168.0.1: icmp_seq=1 ttl=127 time=4294971590970 ms
Translating the time to hex gives something like 0x03e8 xxxx xxxx which
make me wonder a little. This was introduced by the patch:
[NET]: Store skb->timestamp as offset to a base timestamp
Reduces skb size by 8 bytes on 64-bit.
Signed-off-by: Patrick McHardy <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
---
commit a61bbcf28a8cb0ba56f8193d512f7222e711a294
tree 33ae1976ab3b08aac516debb2742d2c6696d5436
parent 25ed891019b84498c83903ecf53df7ce35e9cff6
I checked this on two machines. Both where equipped with Opteron processors
in 64bit mode. Using gcc 3.4.3, 4.0.1 and 4.0.2 gives exactly the same reults.
Reverting that patch restores the correct timestamping
Bye
Joachim
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
-
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]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |