All,
I am bringing up a Software model which simulates 48 ARM A72 Cores.
I noticed the following assertion with UEFI in GICv3 mode.
add-symbol-file /home/supven01/ashbrook_test/uefi/edk2/Build/Ashbrook_DevPlatform/DEBUG_GCC49/AARCH64/ArmPkg/Drivers/TimerDxe/TimerDxe/DEBUG/ArmTimerDxe.dll 0xFF438240 Loading driver at 0x000FF438000 EntryPoint=0x000FF438280 ArmTimerDxe.efi ASSERT /home/supven01/ashbrook_test/uefi/edk2/MdePkg/Library/BaseLib/LinkedList.c(61): List->ForwardLink != ((void *) 0)
gEmbeddedTokenSpaceGuid.PcdTimerPeriod was set to "100000".
However, after increasing gEmbeddedTokenSpaceGuid.PcdTimerPeriod, the assertion goes away and UEFI proceeds to load the Shell and OS.
Any pointers/analysis is appreciated.
Thanks, Supreeth
________________________________
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On 17 November 2015 at 18:21, Supreeth Venkatesh Supreeth.Venkatesh@arm.com wrote:
All,
I am bringing up a Software model which simulates 48 ARM A72 Cores.
I noticed the following assertion with UEFI in GICv3 mode.
add-symbol-file /home/supven01/ashbrook_test/uefi/edk2/Build/Ashbrook_DevPlatform/DEBUG_GCC49/AARCH64/ArmPkg/Drivers/TimerDxe/TimerDxe/DEBUG/ArmTimerDxe.dll 0xFF438240
Loading driver at 0x000FF438000 EntryPoint=0x000FF438280 ArmTimerDxe.efi
ASSERT /home/supven01/ashbrook_test/uefi/edk2/MdePkg/Library/BaseLib/LinkedList.c(61): List->ForwardLink != ((void *) 0)
gEmbeddedTokenSpaceGuid.PcdTimerPeriod was set to “100000”.
However, after increasing gEmbeddedTokenSpaceGuid.PcdTimerPeriod, the assertion goes away and UEFI proceeds to load the Shell and OS.
Any pointers/analysis is appreciated.
Not a clue, unfortunately. This could be lots of things, I suppose, including memory corruption or the timer interrupt firing before the data structures have been set up
If the issue is related with timer period, you can check if you have applied below patch to your code:
http://article.gmane.org/gmane.comp.bios.edk2.devel/1199/
Regards,
Heyi
On 11/18/2015 01:21 AM, Supreeth Venkatesh wrote:
All,
I am bringing up a Software model which simulates 48 ARM A72 Cores.
I noticed the following assertion with UEFI in GICv3 mode.
add-symbol-file /home/supven01/ashbrook_test/uefi/edk2/Build/Ashbrook_DevPlatform/DEBUG_GCC49/AARCH64/ArmPkg/Drivers/TimerDxe/TimerDxe/DEBUG/ArmTimerDxe.dll 0xFF438240
Loading driver at 0x000FF438000 EntryPoint=0x000FF438280 ArmTimerDxe.efi
ASSERT /home/supven01/ashbrook_test/uefi/edk2/MdePkg/Library/BaseLib/LinkedList.c(61): List->ForwardLink != ((void *) 0)
gEmbeddedTokenSpaceGuid.PcdTimerPeriod was set to “100000”.
However, after increasing gEmbeddedTokenSpaceGuid.PcdTimerPeriod, the assertion goes away and UEFI proceeds to load the Shell and OS.
Any pointers/analysis is appreciated.
Thanks,
Supreeth
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Linaro-uefi mailing list Linaro-uefi@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-uefi
-
Ard Biesheuvel -
Heyi Guo -
Supreeth Venkatesh