Bug 168166
Summary: | ping prints nonsensical round-trip times on AMD64 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> | ||||
Component: | iputils | Assignee: | Radek Vokál <rvokal> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | Mike McLean <mikem> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | rawhide | CC: | notting | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | 20020927-28 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-09-30 08:22:42 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Alexandre Oliva
2005-09-13 04:28:40 UTC
I didn't manage to reproduce this issue on my AM64 box. Unfortunatelly I don't have rawhide installed on it but just FC4 with the latest kernel. Can you please retest ping on another kernel? Err... I wrote the problem wouldn't happen on FC4. What is it that you want me to retest, FC4 with rawhide kernel or rawhide with FC4 kernel? Aha, sorry, I've overlooked that you've already test it on FC4. I'll try to update my x86_64 box later this week and reproduce this issue. Is it only this specific kernel you see the above problem or is it happenning also with another FC5 kernels? I started noticing it about a week ago, and since we've pretty much had daily kernel updates in rawhide, several different kernels have exposed the issue. That said, yesterday's kernel wouldn't boot on my Athlon64 notebook, so I couldn't test that, so I'm still runing the kernel mentioned above. At least until today's rawhide kernel gets installed and a get a chance to reboot :-) I see this as well on recent rawhide. Created attachment 119163 [details]
memset message structure before using it
This fixes it for me. However, this does make me question why this never showed
up before. :)
Interesting... I was seeing this too, and it appears quite random too. Only 64-bit is affected, 32-bit ping works a-ok for me. I also saw similar things with tcpdump, it sometimes got timestamps in year 2142 or so. And sometimes the timestamps were just ok, same with ping. The behaviour changed some time between 1535 and 1582 (anything between that crash and burned all the time, so pinpointing the exact change is hard). There seem to have been some timestamp-related changes in the kernel networking code, but I think ping actually just uses a timestamp embedded in the packet data to do the measurements? (In reply to comment #6) > This fixes it for me. However, this does make me question why this never showed > up before. :) Thanks, patch checked in. |