Bug 108732 - ping(8) reports 14 digit time on sparc64
Summary: ping(8) reports 14 digit time on sparc64
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: sparc64 (show other bugs)
Version: 6.2-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-sparc64 (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-03 21:00 UTC by andrew
Modified: 2011-12-12 19:06 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description andrew 2007-02-03 21:00:34 UTC 
From a Sun AXI 440MHz, type 
# ping google.com
see result like
ping 63 bytes from 192.168.2.20 icmp_seq=n ttl=64 time=257698753776000.000

result simliar with local and remote destinations.

Fix: 

not known
How-To-Repeat: type ping anytime
Comment 1 Pietro Cerutti freebsd_committer freebsd_triage 2008-06-02 13:52:13 UTC 
State Changed
From-To: open->feedback

I can't reproduce it on 7.0-RELEASE.
Comment 2 Daniel Austin MBCS 2008-06-23 17:25:11 UTC 
Hi,

ultra60# ping www.google.com
PING www.l.google.com (66.249.93.99): 56 data bytes
64 bytes from 66.249.93.99: icmp_seq=0 ttl=247 time=44.676 ms
64 bytes from 66.249.93.99: icmp_seq=1 ttl=247 time=42.746 ms
64 bytes from 66.249.93.99: icmp_seq=2 ttl=247 time=44.050 ms

Could this be specific to a certain NIC?  If you can let me know what 
NIC is in the machine, I will happily try via the same if I have one 
here.  I have em, fxp, gem and hme NICs available in sparc64 machines.


Thanks,

Daniel.
Comment 3 Marius Strobl freebsd_committer freebsd_triage 2011-12-12 19:04:59 UTC 
State Changed
From-To: feedback->closed

Close; the problem isn't reproducible and requested feedback was never 
received.