Xenomai Community Call Minutes - April 7, 2021

Xenomai Community Call Minutes - April 7, 2021

[Wang, Rick Y]

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
same board. It could be related to clock source and ACPI changes in kernel.



Thanks,
Rick

Re: Xenomai Community Call Minutes - April 7, 2021

[Philippe Gerum]

Hello Rick,

At what time did that meeting take place yesterday? I tried to connect
several times to the usual 'teams' room from 7:55 to 8:10, but nobody
was there.

Wang, Rick Y via Xenomai <xenomai@xenomai.org> writes:

> 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
> same board. It could be related to clock source and ACPI changes in kernel.
>
>
>
> Thanks,
> Rick


-- 
Philippe.

Re: Xenomai Community Call Minutes - April 7, 2021

[Jan Kiszka]

On 08.04.21 08:57, Philippe Gerum via Xenomai wrote:
> 
> Hello Rick,
> 
> At what time did that meeting take place yesterday? I tried to connect
> several times to the usual 'teams' room from 7:55 to 8:10, but nobody
> was there.

CEST mess: The meeting moved to 9am our time due to daylight saving.

Jan

> 
> Wang, Rick Y via Xenomai <xenomai@xenomai.org> writes:
> 
>> 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
>> same board. It could be related to clock source and ACPI changes in kernel.
>>
>>
>>
>> Thanks,
>> Rick
> 
> 

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

Re: Xenomai Community Call Minutes - April 7, 2021

[Philippe Gerum]

Jan Kiszka <jan.kiszka@siemens.com> writes:

> On 08.04.21 08:57, Philippe Gerum via Xenomai wrote:
>> 
>> Hello Rick,
>> 
>> At what time did that meeting take place yesterday? I tried to connect
>> several times to the usual 'teams' room from 7:55 to 8:10, but nobody
>> was there.
>
> CEST mess: The meeting moved to 9am our time due to daylight saving.
>

Mmf, ok.

> Jan
>
>> 
>> Wang, Rick Y via Xenomai <xenomai@xenomai.org> writes:
>> 
>>> 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
>>> same board. It could be related to clock source and ACPI changes in kernel.
>>>
>>>
>>>
>>> Thanks,
>>> Rick
>> 
>> 


-- 
Philippe.

Re: Xenomai Community Call Minutes - April 7, 2021

[Philippe Gerum]

Philippe Gerum <rpm@xenomai.org> writes:

> Jan Kiszka <jan.kiszka@siemens.com> writes:
>
>> On 08.04.21 08:57, Philippe Gerum via Xenomai wrote:
>>> 
>>> Hello Rick,
>>> 
>>> At what time did that meeting take place yesterday? I tried to connect
>>> several times to the usual 'teams' room from 7:55 to 8:10, but nobody
>>> was there.
>>
>> CEST mess: The meeting moved to 9am our time due to daylight saving.
>>
>
> Mmf, ok.
>

Btw, maybe there could be an automatic reminder sent to the list about
this recurring meeting a couple of days before it takes place? This
might decide (a few) other people to join in out of curiosity, who
knows.

-- 
Philippe.

RE: Xenomai Community Call Minutes - April 7, 2021

[Chen, Hongzhan]

>From: Xenomai <xenomai-bounces@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.

Regards

Hongzhan Chen

>same board. It could be related to clock source and ACPI changes in kernel.
>
>
>
>Thanks,
>Rick

Re: Xenomai Community Call Minutes - April 7, 2021

[Jan Kiszka]

On 08.04.21 10:19, Chen, Hongzhan via Xenomai wrote:
>> From: Xenomai <xenomai-bounces@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

Re: Xenomai Community Call Minutes - April 7, 2021

[Antoine Hoarau]

I ran into the same issue. Using default config too. Had to enable EFI
manually.

Le jeu. 8 avr. 2021 à 10:28, Jan Kiszka via Xenomai <xenomai@xenomai.org> a
écrit :

> On 08.04.21 10:19, Chen, Hongzhan via Xenomai wrote:
> >> From: Xenomai <xenomai-bounces@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
>
>

RE: Xenomai Community Call Minutes - April 7, 2021

[Chen, Hongzhan]

>-----Original Message-----
>From: Jan Kiszka <jan.kiszka@siemens.com> 
>Sent: Thursday, April 8, 2021 4:28 PM
>To: Chen, Hongzhan <hongzhan.chen@intel.com>; xenomai@xenomai.org
>Subject: Re: Xenomai Community Call Minutes - April 7, 2021
>
>On 08.04.21 10:19, Chen, Hongzhan via Xenomai wrote:
>>> From: Xenomai <xenomai-bounces@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.

My problem is that the same image that had not enabled efi successfully boot up  from the beginning on Maxtang board which I 
already setup lava for it  at first so that I had not suspected config thing for my Rock PI X board that I have got recently.
But after further check log on Maxtang,  it seems that it use mptable to examine MPS so that it still can cover APIC.

Regards

Hongzhan Chen

>
>Jan
>
>-- 
>Siemens AG, T RDA IOT
>Corporate Competence Center Embedded Linux