Bug 61111
Summary: | tcpdump and ping granularity for > 40 ms rtt's | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <rodger_pape> |
Component: | tcpdump | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | gharris |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-03-25 11:31:38 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: |
Description
Need Real Name
2002-03-13 20:00:40 UTC
This is a result of something done to the kernel. Compiling a vanilla 2.4.7 kernel from kernel.org results in tcpdump timestamp resolutions of 1us. Compiling 2.4.7-10 with an identical configuration (as close as possible) results in 10ms resolution on tcpdump timestamps. I suspect somebody has done something shakey to arch/i386/kernel/time.c What network driver is this ? (it works fine here) Also does this happen with the errata kernel (2.4.9-31) ? Upgrading to the 2.4.9-31 kernel fixed the problem. Thanks Since you asked, I got the same behavior (10ms granulatiry under 2.4.7-10) with 3c59x (two machines), eepro100 (two machines), and lance (one machine). |