[coreboot] H8QME-2+ boot problems on different machines.

Myles Watson mylesgw at gmail.com
Thu May 6 21:15:28 CEST 2010


>> And for the Not so good working CPU:
>> AFTER  setup_mb_resource
>> DRAM(40)0000000000-0000ffffff, ->(0), R, W, No interleave, 0
>> MMIO(80)0000000000-000000ffff, ->(0,0), , , CPU disable 0, Lock 0, Non
>> posted 0
>> MMIO(90)0000000000-000000ffff, ->(0,0), , , CPU disable 0, Lock 0, Non
>> posted 0
>> MMIO(98)0000000000-000000ffff, ->(0,0), , , CPU disable 0, Lock 0, Non
>> posted 0
>> MMIO(a0)0000000000-000000ffff, ->(0,0), , , CPU disable 0, Lock 0, Non
>> posted 0
>> MMIO(a8)0000000000-000000ffff, ->(0,0), , , CPU disable 0, Lock 0, Non
>> posted 0
>> MMIO(b0)0000000000-000000ffff, ->(0,0), , , CPU disable 0, Lock 0, Non
>> posted 0
> I wonder why all those registers show up.  They shouldn't print if they're
> zeroed.  Maybe you could print the raw register values, too.  The docs are
> available, and most of the meanings are copied into resourcemap.c.

It looks like your resourcemap.c is for k8, not fam10.  There's an
extra bit in fam10 that controls ganged links.  Since it's listed as
reserved in your resource map, it should never get cleared, which
could cause you problems, but only sporadically (depending on how that
bit floats).

That's probably the reason all the 0 registers show up.

Thanks,
Myles




More information about the coreboot mailing list