Workaround for "PHC time jumps ~4 seconds there and back on AQC107"#63
Open
peci1 wants to merge 1 commit intoAquantia:masterfrom
Open
Workaround for "PHC time jumps ~4 seconds there and back on AQC107"#63peci1 wants to merge 1 commit intoAquantia:masterfrom
peci1 wants to merge 1 commit intoAquantia:masterfrom
Conversation
Signed-off-by: Martin Pecka <peckama2@fel.cvut.cz>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Workarouds issue https://www.spinics.net/lists/netdev/msg1013570.html .
Summary: PHC time jumps ~4 seconds there and back on AQC107
I'm testing on multiple copper-PHY NICs with AQC107 and the problem is always the same:
I run the tests on multiple PCs with different CPU archs and the problem is always the same:
When I enable PTP on the card (e.g.
hwstamp_ctl -i eth2 -t 1) and run phc2sys from linuxptpto sync the card's PHC to another clock (AQ107 is time sink), I get time jumps of the PHC clock
of ~4 secs in the future and then back (after ~5 secs). These jumps happen in random intervals
and I haven't found a pattern. Usually, it happens every 20-100 secs, but there have been even
much longer intervals. These time jumps are corrected by phc2sys quite quickly (within ~10 seconds),
but during this interval, the time is wrong.
As concluded in the discussion on netdev, this PR brings in a workaround that seems to work and seems to have no side-effects. But it doesn't solve the root cause.