Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    Some ping implementations use gettimeofday(3) to calculate round-trip times. As a result, ping may print incorrect results if your system time is not reliable. Commented Aug 15, 2013 at 23:35
  • @EvanTeitelman Indeed, my ping implementation does use gettimeofday. However, I checked those results with Wireshark and it shows the same behavior (2 ms decrements). Therefore, I don't think gettimeofday is the culprit... Commented Aug 16, 2013 at 11:41
  • 1
    And, I think it might be worthy of note, those two computers are connected with a direct short Ethernet cable, so I would expect latencies in the order of microseconds, not miliseconds.... Commented Aug 16, 2013 at 12:39
  • The nobody cared messages and the ping results are probably related. Is the 8139too the right driver? In the past there been some issue with the 8139cp. Have some option on insert? Some debug option maybe? On /proc/interrupts there's some other driver using 15? Commented Aug 17, 2013 at 23:14