Sadly it turned out that didn't help to Jonathan: I'm skeptical this will address my issue on msi/ms7135, as it's a Socket 754 board that only single-core CPU packages are available for. Nevertheless, I'll give this change a try.
Indeed, it does not fix the issue I'm having. 2018-05-06 8:22 GMT+03:00 Kyösti Mälkki <[email protected]>: > On Fri, May 4, 2018 at 7:25 PM, Aaron Durbin via coreboot > <[email protected]> wrote: >> On Fri, May 4, 2018 at 10:01 AM, Jonathan A. Kollasch >> <[email protected]> wrote: >>> On Fri, May 04, 2018 at 05:23:40PM +0200, Piotr Król wrote: >>>> Hi Aaron, >>>> I tried to boot PC Engines apu2 on recent master branch and discovered >>>> that it not boot. Bisection points to: >>>> >>>> 60320182d011 console: only allow console messages after initialization >>>> >>>> It is hard to believe that this change cause AGESA reset loop, but I >>>> checked 3 times. After applying above commit I end up with loop: >>> >>> I see a similar romstage boot loop starting with this commit on >>> msi/ms7135 (K8N Neo3), a DDR1 K8 board. >> >> I think it's the AMD boards and their weird config. CAR_GLOBAL is >> used, but apparently these boards fail if accessing CAR_GLOBAL at the >> wrong time? If you have log diffs w/ and w/o the patch it'd help with >> root cause. >> > > Jonathan, try this: https://review.coreboot.org/c/coreboot/+/26120 > > Kyösti > > -- > coreboot mailing list: [email protected] > https://mail.coreboot.org/mailman/listinfo/coreboot -- coreboot mailing list: [email protected] https://mail.coreboot.org/mailman/listinfo/coreboot
