Skip to content

ci: earlycon enablement through command line for early bootup logs#1610

Closed
sampnimm2629 wants to merge 1 commit intoqualcomm-linux:masterfrom
sampnimm2629:master
Closed

ci: earlycon enablement through command line for early bootup logs#1610
sampnimm2629 wants to merge 1 commit intoqualcomm-linux:masterfrom
sampnimm2629:master

Conversation

@sampnimm2629
Copy link
Copy Markdown

Enable earlycon to get the early console logs to debug early bootup crashes in CI testing.

Enable earlycon to get the early console logs to debug early bootup crashes in CI testing.

Signed-off-by: sampnimm <sampnimm@qti.qualcomm.com>
@shashim-quic
Copy link
Copy Markdown

Enable earlycon to get the early console logs to debug early bootup crashes in CI testing.

+1 for this change. We need earlycon to debug early boot issue

Comment thread ci/base.yml
"
cmdline: |
KERNEL_CMDLINE_EXTRA:append = " qcom_scm.download_mode=1"
KERNEL_CMDLINE_EXTRA:append = " earlycon qcom_geni_serial.con_enabled=1 qcom_scm.download_mode=1"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this is likely not the right place to enable it. this would apply to all builds, all boards, every user.
If that's the case, then it should be explained why in the commit message.
what is the need here?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

this is likely not the right place to enable it. this would apply to all builds, all boards, every user. If that's the case, then it should be explained why in the commit message. what is the need here?

We need this to enable for all targets there in Lava CI, which will help us to get early console logs to debug early bootup crashes.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please point out the jobs that failed early enough to be debuggable only with the help of earlycon.

@lumag
Copy link
Copy Markdown
Contributor

lumag commented Feb 20, 2026

Please point out failed jobs which require this to be enabled.

Copy link
Copy Markdown
Contributor

@lumag lumag left a comment

Choose a reason for hiding this comment

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

No, earlycon is not a tool to debug production builds. By the time the kernel hits meta-qcom it should be stable enough to not require such debugging techniques.

@ricardosalveti
Copy link
Copy Markdown
Contributor

Yeah, please point out to the failed jobs so we can at least understand what happened here.

Also, this was removed before as part of #867.

@sampnimm2629
Copy link
Copy Markdown
Author

sampnimm2629 commented Feb 23, 2026

We have seen bootup crashes on Kaanapli, with earlycon disabled logs it was looking like device stuck in UEFI end and not able to get any useful data with respect to crash.
After that, we have tried with earlycon enabled and able to get kernel logs to debug the rpmh issue further. Attaching logs for the same.

earlycon_enabled.txt
earlycon_disbaled.txt

@lumag
Copy link
Copy Markdown
Contributor

lumag commented Feb 23, 2026

We have seen bootup crashes on Kaanapli, with earlycon disabled logs it was looking like device stuck in UEFI end

No, it doesn't. EBS (ExitBootServices) means that the UEFI has mostly ended.

and not able to get any useful data with respect to crash. After that, we have tried with earlycon enabled and able to get kernel logs to debug the rpmh issue further. Attaching logs for the same.

earlycon_enabled.txt earlycon_disbaled.txt

You've added boot logs. I've asked for the CI jobs. As I wrote earlier, the kernel must be stable enough before it reaches meta-qcom. Which means that you (or other kernel engineers) will be doing your own kernel builds. If you need, please enable earlycon as a part of your build.

@github-actions
Copy link
Copy Markdown

This pull request has been marked as stale due to 30 days of inactivity. To prevent automatic closure in 5 days, remove the stale label or add a comment. You can reopen a closed pull request at any time.

@github-actions github-actions Bot added the Stale label Mar 26, 2026
@github-actions github-actions Bot closed this Mar 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants