| Summary: | [QA 5.2_M3.rc1] Image not booting on Arrowlake target (ARL) genericx86-64 only | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [QA/Testing] Runtime Testing | Reporter: | Jing Hui <jing.hui.tham> | ||||
| Component: | oeqa/runtime | Assignee: | Yogesh Tyagi <yogesh.tyagi> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | High | CC: | anuj.mittal, bruce.ashfield, chee.yang.lee, jing.hui.tham, randy.macleod, richard.purdie, ross.burton | ||||
| Version: | 5.2 | ||||||
| Target Milestone: | 5.2 M4 | ||||||
| Hardware: | All | ||||||
| OS: | x86_64 | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | Don't know | |||||
| Attachments: |
|
||||||
|
Description
Jing Hui
2025-03-18 07:17:32 UTC
Created attachment 5108 [details]
Image not able to boot up.
image tested on Arrowlake platform: genericx86-64 core-image-sato-sdk To save people having to download the attachment, it shows the system hanging at "Booting 'boot'". Can you try booting with "debug earlycon" added to the kernel arguments please. linux-yocto 6.12.13 is booting with two additional configs: CONFIG_DRM_ACCEL=y CONFIG_DRM_ACCEL_IVPU=m Yogesh: will you be sending a patch? Yes, I will be sending a patch. Arrowlake is booting with latest meta (kernel 6.12.19). same issue occurred on Arrowlake platform. Reopening this ticket. Image tested on Arrowlake platform: genericx86-64 core-image-sato-sdk Observed same behavior during boot: System hanging at "Booting 'boot'". [QA 5.2.rc1] same issue occurred on Arrowlake platform. Reopening this ticket. Image tested on Arrowlake platform: genericx86-64 core-image-sato-sdk Observed same behavior during boot: System hanging at "Booting 'boot'". I previously reported that linux-yocto 6.12.19 booted on Arrow Lake, but this was inaccurate. The issue was specific to the genericx86-64 image failing to boot on Arrow Lake, whereas the intel-corei7-64 image worked without issues. After further investigation, I found that enabling CONFIG_DMAR_TABLE (which is automatically enabled when CONFIG_INTEL_IOMMU is set) in the kernel configuration resolves the boot failure for the genericx86-64 image on Arrow Lake. But since CONFIG_INTEL_IOMMU has been a part of only Intel machine's configurations, I want to do further debugging to find out where exactly the boot process is stuck. I tried following kernel command line options earlycon=EARLY early_ioremap_debug=EARLY earlyprintk=EARLY earlyprintk=bios but none of them help to generate any boot logs. Yogsesh is working on this so -> Accepted state. patch is sent to mailing list https://lists.yoctoproject.org/g/linux-yocto/message/15029 Tested and fixed in yocto-5.2.rc2. Image is booting up on Arrowlake. |