ignore SCD kernel warning about I2C communication ack errors#21959
Merged
StormLiangMS merged 1 commit intosonic-net:masterfrom Jan 20, 2026
Merged
Conversation
Signed-off-by: xulping <[email protected]>
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ZhaohuiS
approved these changes
Jan 19, 2026
Contributor
|
@lipxu why is it in draft? still not sure to ignore it yet? |
Contributor
Author
Contributor
Author
|
Hi, @StormLiangMS , Could you please help to review the PR and merge it if no more comments, thanks a lot. |
StormLiangMS
added
the
Request for 202511 branch
PriyanshTratiya
pushed a commit
to PriyanshTratiya/sonic-mgmt
that referenced
this pull request
Jan 21, 2026
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499 Signed-off-by: Priyansh Tratiya <[email protected]>
saravanan-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Jan 22, 2026
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499 Signed-off-by: Saravanan Sellappa <[email protected]>
justin-oliver
pushed a commit
to justin-oliver/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499 Signed-off-by: Yael Tzur <[email protected]>
abhishek-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Feb 6, 2026
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499
Anirudh-nokia
pushed a commit
to Anirudh-nokia/sonic-mgmt-fork
that referenced
this pull request
Feb 6, 2026
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499 Signed-off-by: ayya <[email protected]>
Contributor
Author
|
@vmittal-msft Could you please approve the request for 202511, thank you very much. |
nnelluri-cisco
pushed a commit
to nnelluri-cisco/sonic-mgmt
that referenced
this pull request
Feb 12, 2026
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499 Signed-off-by: nnelluri-cisco <[email protected]>
rraghav-cisco
pushed a commit
to rraghav-cisco/sonic-mgmt
that referenced
this pull request
Feb 13, 2026
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499 Signed-off-by: Raghavendran Ramanathan <[email protected]>
anilal-amd
pushed a commit
to anilal-amd/anilal-forked-sonic-mgmt
that referenced
this pull request
Feb 19, 2026
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499 Signed-off-by: Zhuohui Tan <[email protected]>
Collaborator
|
@lipxu PR conflicts with 202511 branch |
lipxu
added a commit
to lipxu/sonic-mgmt-lipxu-fork
that referenced
this pull request
Feb 22, 2026
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499
lipxu
added a commit
to lipxu/sonic-mgmt-lipxu-fork
that referenced
this pull request
Feb 22, 2026
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499 Signed-off-by: xuliping <[email protected]>
Contributor
Author
vmittal-msft
pushed a commit
that referenced
this pull request
Feb 23, 2026
…#22532) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499 Signed-off-by: xuliping <[email protected]>
Contributor
Author
abhishek-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Mar 17, 2026
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499 Signed-off-by: Abhishek <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
…et#21959) What is the motivation for this PR? In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors. How did you do it? It's a warning message, should not be failed in loganalyzer, ignore these messages. How did you verify/test it? https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3 https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0 https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1 https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499
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
6 participants
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.
Description of PR
Summary:
Fixes # (issue)
36327584
Type of change
Back port request
Approach
What is the motivation for this PR?
In the new testbed, the kernel outputs warning messages containing the word “error,” which causes LogAnalyzer to treat them as errors.
How did you do it?
It's a warning message, should not be failed in loganalyzer, ignore these messages.
How did you verify/test it?
https://elastictest.org/scheduler/testplan/696d71df4bbe3bd7ad16cdf3
https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436d
https://elastictest.org/scheduler/testplan/696d71dd4b8aa910b618436b
https://elastictest.org/scheduler/testplan/696d71dc15026fd4f746b8f0
https://elastictest.org/scheduler/testplan/696d71db4bbe3bd7ad16cdf1
https://elastictest.org/scheduler/testplan/696d71da5e4aaa3c28ac7499
Any platform specific information?
Arista
Supported testbed topology if it's a new test case?
Documentation