Asus F2A85M broken from version 4.10

[Balázs Vinarz]

Hello there!

I just recently started to work again on my port for Asus A88XM-E,
which is based on the F2A85-M:
https://review.coreboot.org/c/coreboot/+/30987.
The master build was broken for the A88XM-E and I though maybe some of
the differences between the sources have caused this, but it's broken
for the F2A85-M (LE) as well.
I built all the 4.9, 4.10 and 4.11 versions and 4.10 and 4.11 is
definitely broken. Right after the kernel loads it stops with a panic.
Where should I start a conversation about this? Bugtracker doesn't
seem to be too active.
I hope the mailing list can handle the attachment :)

Regards

[Kyösti Mälkki]

On Fri, Dec 13, 2019 at 9:42 PM Balázs Vinarz  wrote:
> Hello there!
>
> I just recently started to work again on my port for Asus A88XM-E,
> which is based on the F2A85-M:
> https://review.coreboot.org/c/coreboot/+/30987.
> The master build was broken for the A88XM-E and I though maybe some of
> the differences between the sources have caused this, but it's broken
> for the F2A85-M (LE) as well.
> I built all the 4.9, 4.10 and 4.11 versions and 4.10 and 4.11 is
> definitely broken. Right after the kernel loads it stops with a panic.

There are two board-status reports for 4.10 and 4.10-942 for
asus/f2a85m-pro you can try.
Or different kernel, I am not so sure about IOMMU in fam15tn, the
panic points to that direction.

Kyösti

[Github Hun]

Hi,

AFAIK your board is also AMD fam15h.  Then, it might be connected to commit: 0178760, as of Oct 25: 'Don't use both of _ADR and _HID' patch.  This commit removed the _HID object from src/northbridge/amd/agesa/family15tn/acpi/northbridge.asl. But Linux (Windows not tested) needs also an ID object together with the address (_ADR). You can give a try by putting back the commented out _HID object line and rename _HID to _CID (compatible ID).  It worked for me..(for Fam14h and Fam16h both _HID and _CID were there, so the patch in Oct only caused problems for Fam15h boards..).

Githubhun