Skip to content

petri: use com3 for kmsg logs #1176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Conversation

tjones60
Copy link
Contributor

Using COM3 instead of diag_client allows us to get OpenHCL logs if it crashes early in boot

@tjones60 tjones60 requested a review from a team as a code owner April 10, 2025 22:57
Copy link
Member

@jstarks jstarks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tested this and although it configured the serial port successfully, it didn't seem to actually log any data from COM3 (I was able to connect to COM3 via hypestv while the test was running, which should not be possible, haha).

So it seems like something is missing.

@tjones60
Copy link
Contributor Author

tjones60 commented Apr 30, 2025

I tested this and although it configured the serial port successfully, it didn't seem to actually log any data from COM3 (I was able to connect to COM3 via hypestv while the test was running, which should not be possible, haha).

So it seems like something is missing.

Yeah I've been focusing on other things, but I did notice that the logs aren't actually coming through reliably (if you download the logs from the tdx/arm test runs on this PR which use com3, you can see that it sometimes gets some of the logs). I hope to get the time to investigate more soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants