@zedei how often have you let it cycle?
Asus Boards love to reset multiple times, might actually be that everything is good and you just got spooked?
Happened to me and others before.
Yep. People who think they know things, like "asus codes are bonkers"?
To me, those lists of codes look exactly like those from previous Aptio 5 Days on for example X99.
If i have to speculate, Scaleable probably still uses those.
AMD on the other hand changed those for certain.
And the only things i have to come to that conclusion are experience on actual Hardware and leaks with juicy contents, hence the crystal ball.
So yes, i know actually pretty little. That does not keep me from using the little i have to try and be productive.
Additionally, i would like to have my questions answered to change the lack of knowledge if possible.
Onto the interpretation of Postcodes.
At this point, all we have are 2 figure Hex Numbers send on Port 0x80 that could be from anything including the PSP and Bios code.
You could take a random list and interpret the codes as a weather forecast and that it will be sunny tomorrow.
Comparing real-world behavior and codes with the expected and documented ones should show some huge discrepancies and issues.
Since i have already mentioned some of those issues, let me add ones about my crystal ball of postcodes.
Dell and Lenovo PSB Burned CPUs get stuck at Code 78 which "should" have something to do with the OEM sig not being found.
Which does not make any real sense to me.
Where as Code 0x7D is clearly labeled a PSB error code that would be way more reasonable.
On the List for the KRPA, 78 is "ACPI Module Init" and 7D is reserved.
What does that tell you?
So, amazingly, having access to actual unimpeachable and guaranteed correct documentation, I know what I'm interpreting.
Does that make any sense to you?
One thing i am certain about is that postcodes today are only of limited use in such matters.
Speed: codes only get visible when its an error and its stuck or the code isn't changed for a perceivable while.
There are likely hundreds of codes between those few observed.
Some of those might make a lot more sense if we could read them.
There are more then one two digit "Postcode".
Those additional ones could indicate a more general source for the port 80 code.
For instance if its a PSP BL, PEI or DXE Code.
And there is more then one list of interpretations for those codes.
Or at least, for the abbreviated 2 digit codes on just port 80.
Those codes were a good indicator for faults in the past.
I still can't discern what might be wrong in the OPs case.
System log from BMC:
ID: 18 October 25th 2021, 9:54:34 pm AMIF02F7496EBA0 spx_restservice: spx_restservice - - [4067 : 4067 CRITICAL][libipmi_AMIOEM.c:5987]Unable to get Current Active Image 1c1 -
- ID: 19 October 25th 2021, 9:54:34 pm AMIF02F7496EBA0 spx_restservice: spx_restservice - - [4067 : 4067 CRITICAL][misc.c:107]Error in getting dual image active image configuration::449 -
- ID: 16 October 25th 2021, 9:54:31 pm AMIF02F7496EBA0 spx_restservice: spx_restservice - - [4067 : 4067 CRITICAL][libipmi_AppDevice.c:764]Got invalid data field for SOl permissions eventhough userr is not disabled..adjust -
- ID: 17 October 25th 2021, 9:54:31 pm AMIF02F7496EBA0 spx_restservice: spx_restservice - - [4067 : 4067 CRITICAL][libipmi_AppDevice.c:764]Got invalid data field for SOl permissions eventhough userr is not disabled..adjust -
- ID: 14 October 25th 2021, 9:54:29 pm AMIF02F7496EBA0 spx_restservice: spx_restservice - - [4067 : 4067 CRITICAL][rest_default.c:359]ServiceRet 0 -
- ID: 15 October 25th 2021, 9:54:29 pm AMIF02F7496EBA0 spx_restservice: spx_restservice - - [4067 : 4067 CRITICAL][rest_default.c:393]channel no wRet 0 -
- ID: 13 October 25th 2021, 9:53:57 pm AMIF02F7496EBA0 dhcpmonitor: dhcpmonitor - - [3480 : 3480 CRITICAL][dhcpmonitor.c:357]Renewing DNS for eth0 interface. -
- ID: 12 October 25th 2021, 9:53:56 pm AMIF02F7496EBA0 dhcpmonitor: dhcpmonitor - - [3480 : 3480 CRITICAL][dhcpmonitor.c:200]DHCP monitor: Renewing eth0 interface for IPv6 -
- ID: 11 October 25th 2021, 9:53:55 pm AMIF02F7496EBA0 dhcpmonitor: dhcpmonitor - - [3480 : 3480 CRITICAL][dhcpmonitor.c:160]DHCP monitor: Renewing eth0 interface for IPv4 -
- ID: 9 October 25th 2021, 9:53:49 pm AMIF02F7496EBA0 dhcpmonitor: dhcpmonitor - - [3480 : 3480 CRITICAL][dhcpmonitor.c:189]DHCP monitor: Releasing eth0 interface for IPv4 -
- ID: 10 October 25th 2021, 9:53:49 pm AMIF02F7496EBA0 dhcpmonitor: dhcpmonitor - - [3480 : 3480 CRITICAL][dhcpmonitor.c:205]DHCP monitor: Releasing eth0 interface for IPv6 -
- ID: 8 October 25th 2021, 9:53:48 pm AMIF02F7496EBA0 dhcpmonitor: dhcpmonitor - - [3480 : 3480 CRITICAL][dhcpmonitor.c:357]Renewing DNS for eth0 interface. -
- ID: 7 October 25th 2021, 9:53:47 pm AMIF02F7496EBA0 dhcpmonitor: dhcpmonitor - - [3480 : 3480 CRITICAL][dhcpmonitor.c:200]DHCP monitor: Renewing eth0 interface for IPv6 -
- ID: 6 October 25th 2021, 9:53:46 pm AMIF02F7496EBA0 dhcpmonitor: dhcpmonitor - - [3480 : 3480 CRITICAL][dhcpmonitor.c:160]DHCP monitor: Renewing eth0 interface for IPv4 -
- ID: 4 October 25th 2021, 9:53:41 pm AMIF02F7496EBA0 dhcpmonitor: dhcpmonitor - - [3480 : 3480 CRITICAL][dhcpmonitor.c:189]DHCP monitor: Releasing eth0 interface for IPv4 -
- ID: 5 October 25th 2021, 9:53:41 pm AMIF02F7496EBA0 dhcpmonitor: dhcpmonitor - - [3480 : 3480 CRITICAL][dhcpmonitor.c:205]DHCP monitor: Releasing eth0 interface for IPv6 -
- ID: 2 October 25th 2021, 9:53:40 pm AMIF02F7496EBA0 dhcpmonitor: dhcpmonitor - - [3480 : 3480 CRITICAL][dhcpmonitor.c:200]DHCP monitor: Renewing eth0 interface for IPv6 -
- ID: 3 October 25th 2021, 9:53:40 pm AMIF02F7496EBA0 dhcpmonitor: dhcpmonitor - - [3480 : 3480 CRITICAL][dhcpmonitor.c:357]Renewing DNS for eth0 interface. -
- ID: 1 October 25th 2021, 9:53:39 pm AMIF02F7496EBA0 dhcpmonitor: dhcpmonitor - - [3480 : 3480 CRITICAL][dhcpmonitor.c:160]DHCP monitor: Renewing eth0 interface for IPv4 -
To me, all of those posted look more like BMC events that are unrelated to Platform and CPU Boot issues.
Are there any other Logs or entries?