On 08.04.21 10:19, Chen, Hongzhan via Xenomai wrote: >> From: Xenomai <xenomai-boun...@xenomai.org> On Behalf Of Wang, Rick Y via >> Xenomai >> Sent: Thursday, April 8, 2021 8:52 AM >> To: xenomai@xenomai.org >> Subject: Xenomai Community Call Minutes - April 7, 2021 >> >> Attendees: >> >> Jan Kiszka, Florian Bezdeka, Florent Pirou, Hongzhan Chen, >> Dao Zhang, Jianbo Cao, Yanfeng Pu, Rick Wang >> >> >> *Community update >> >> - No code change in the past two weeks >> - Greg is debugging jitter issue on ARM. >> - Siemens is testing WIP-Dovetail branch internally. Some issues were >> reported related to clock source or gdb crash. >> - Jan will log the issues to gitlab Xenomai hacker space: >> https://gitlab.com/Xenomai/xenomai-hacker-space/-/issues >> - For Xenomai 3.2, there are some submitted patches pending on Jan's review >> and merge. Also some patches in Philippe's private tree are pending on >> submission. >> - Florian and Song are working on Y2038 issue on Philippe's tree. It depends >> on some Dovetail codes to be merged first. >> - Hongzhan is working on latmus GPIO porting. 5.10 Dovetail-based Xenomai >> and EVL can't boot up on his dev board yet. 5.9 kernel can boot on the > > After further debug , when failure happen, actually system is wrong to use > pit instead of > LAPIC as clock event device because pit can not work with dovetail. After > check log , found > that there is abnormal info related to APIC reported "[ 2.812126] APIC: > ACPI MADT or MP tables are not detected" > It mentioned ACPI. So I traced ACPI related log suggested by Jan and Florian > and found that there is > ACPI related error reported earlier in log like " [ 0.013416] ACPI BIOS > Error (bug): A valid RSDP was not found (20200925/tbxfroot-210)". > I googled this error but all the solution related to it can not fix the > issue for example enabling ACPI in BIOS. > And then I captured kernel log for 5.9 and compare them with 5.10 and finally > found that there is log info related to ACPI missing with my 5.10 image like > " [ 0.000000] efi: ACPI 2.0=0x8c3ee000 ACPI=0x8c3ee000 > TPMFinalLog=0x8c4ad000 SMBIOS=0x8c9ca000 SMBIOS 3.0=0x8c9c9000 > MEMATTR=0x88059418" > After check kernel config, I found that my 5.10 config actually have not > enabled CONFIG_EFI. After enable it, evl successfully boot up on > my Rock PI X board now. > > Thanks for Jan and Florian's suggestions. >
Great to hear it works now! Yeah, CONFIG_EFI=y is part of x86_64_defconfig - that's why I suggested to retry starting from there. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux
