kernel(-64k): add patch to revert new UART change #12883
Merged
Conversation
This file contains 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
christopherco
changed the title
christopherco
changed the title
microsoft-github-policy-service
bot
added
Packaging
3.0-dev
Starting in kernel v6.6.76, our automated testing encountered failures on specific bare-metal systems where, after a kernel panic, sometimes the kernel's panic message was not seen in the system's IPMI SEL. After bisecting the changes between v6.6.75 to v6.6.76, we isolated the offending commit to: serial: 8250: Adjust the timeout for FIFO mode To restore functionality, revert the offending commit. We will continue investigating the issue separately. Apply to both kernel and kernel-64k. Signed-off-by: Chris Co <[email protected]>
Signed-off-by: Chris Co <[email protected]>
christopherco
force-pushed
the
chrco/revert-serial
branch
from
99d2c7f to
50ab50a
Compare
jslobodzian
approved these changes
Mar 11, 2025
jslobodzian
pushed a commit
that referenced
this pull request
Mar 11, 2025
Starting in kernel v6.6.76, our automated testing encountered failures
on specific bare-metal systems where, after a kernel panic, sometimes
the kernel's panic message was not seen in the system's IPMI SEL.
After bisecting the changes between v6.6.75 to v6.6.76, we isolated the
offending commit to:
serial: 8250: Adjust the timeout for FIFO mode
To restore functionality, revert the offending commit. We will continue
investigating the issue separately.
Apply to both kernel and kernel-64k.
Signed-off-by: Chris Co <[email protected]>
binujp
pushed a commit
that referenced
this pull request
Mar 12, 2025
Starting in kernel v6.6.76, our automated testing encountered failures
on specific bare-metal systems where, after a kernel panic, sometimes
the kernel's panic message was not seen in the system's IPMI SEL.
After bisecting the changes between v6.6.75 to v6.6.76, we isolated the
offending commit to:
serial: 8250: Adjust the timeout for FIFO mode
To restore functionality, revert the offending commit. We will continue
investigating the issue separately.
Apply to both kernel and kernel-64k.
Signed-off-by: Chris Co <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-staticsubpackages, etc.) have had theirReleasetag incremented../cgmanifest.json,./toolkit/scripts/toolchain/cgmanifest.json,.github/workflows/cgmanifest.json)./LICENSES-AND-NOTICES/SPECS/data/licenses.json,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)*.signatures.jsonfilessudo make go-tidy-allandsudo make go-test-coveragepassSummary
Starting in kernel v6.6.76, our automated testing encountered failures
on specific bare-metal systems where, after a kernel panic, sometimes
the kernel's panic message was not seen in the system's IPMI SEL.
After bisecting the changes between v6.6.75 to v6.6.76, we isolated the
offending commit to:
To restore functionality, revert the offending commit. We will continue
investigating the issue separately.
Apply to both kernel and kernel-64k.
Signed-off-by: Chris Co [email protected]
Does this affect the toolchain?
YES
Associated issues
Test Methodology