I tracked this down to r4315. Here's a boot log with r4315:
http://ward.vandewege.net/coreboot/h8dme/minicom-20090618q.cap
And here's r4314, which works:
http://ward.vandewege.net/coreboot/h8dme/minicom-20090618q.cap
The URLs are the same,
I'm sorry, copy/paste error. This is (working) r4314:
No problem.
There's garbled text in all three logs. Shouldn't the APs be stopped at this point?
4314:
Enumerating buses... Show all devs...Before Phase 3. Root Device: enabled 1, 0 resources APIC_CLUSTER: 0: enabled 1, 0 resources APIC: 00: enabled 1, 0 resources PCI_DOMAIN: 0000: enabled 1, 0 resources PCI: 0i0m:a1g8e. 0l:e negntahb l=e d0 010,0 20a 6rceso uJrucmepsin gP CtIo: i0m0a:g0e0..0: enabled 1, 0 resources PCI: C0O0D:E0 1I.N0 :C AeCnHaEb lOeNd N1O,D E0: 0r1eso urces PNP: 002e.0: enabled 0, 3 resources PNP: 002e.1: enabled 0, 2 resources PNP: 002eT.r2a:i neDnQaSbRldeWdr P1o,s :2 bruefs_oau:r0c0e0sce bP3N0P: T0r0a2ien.D3Q:S Peonsa:b lMeudt u0a,l C2S PraesssoWu[r4c8e]s : 0P0N0Pc:e 90c082e .5: enabled 1, 4 resources PNP: 002e.6: enabled 0, 1 resources
I'm wondering if it is related to the garbling, and it becomes more serious because of the change in 4315.
If there's a good reason for the garbling, we could try to see what the other two logs are printing. It's not fun to decode it, but it looks like multiple CPUs trying to load the same stuff from CBFS.
Thanks, Myles