[coreboot] H8QME 128GB RAM not Booting

Knut Kujat knuku at gap.upv.es
Tue May 18 15:16:12 CEST 2010


Myles Watson escribió:
>> I steal one of the 8GB dimms and put it on one of my test machines I
>> configured coreboot to only initialize one CPU/CORE and therefore only
>> the 8GB. Booting with this configuration leads to the same result as on
>> the 128GB machine it hangs at the first memcopy it finds so the problem
>> seem to be the dimm itself but it is still DDR 2.
>>     
>
> I'm glad you could narrow it down.  I would expect that no one had tested
> the code with 8GB dimms, so maybe you should be looking for a math/logic
> error (or just missing code) in the sizing or initialization?
>
>   
>> I attached the showroutes and dumpmem outputs.
>>
>> raminit_amdmct()
>> DRAM(40)0000000000-0000ffffff, ->(0), R, W, No interleave, 0
>> MMIO(90)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(b8)00fc000000-00ffffffff, ->(0,0), , , CPU disable 0, Lock 0, Non
>> posted 0
>>     
> This is wrong, but shouldn't affect this problem.  Your buses and I/O are on
> node 0 link 2, but your MMIO is on node 0 link 0.
>
>   
>> PCIIO(c0)0000000-1ffffff, ->(0,2), , ,VGA 0 ISA 0
>> PCIIO(c8)0000000-0000fff, ->(0,0), , ,VGA 0 ISA 0
>> PCIIO(d0)0000000-0000fff, ->(0,0), , ,VGA 0 ISA 0
>> CONFIG(e0)00-ff ->(0,2),R W (bus numbers)
>>     
>
>   
>> raminit_amdmct begin:
>>         DCTInit_D: mct_DIMMPresence Done
>>         DCTInit_D: mct_SPDCalcWidth Done
>>         DCTInit_D: mct_DIMMPresence Done
>>         DCTInit_D: mct_SPDCalcWidth Done
>>         DCTInit_D: AutoCycTiming_D Done
>>         DCTInit_D: AutoConfig_D Done
>>         DCTInit_D: PlatformSpec_D Done
>>         DCTInit_D: StartupDCT_D
>> Node: 00  base: 00  limit: 7fffff  BottomIO: e00000
>>     
> limit 7fffff = 2 GB of RAM.
>
>   
>> raminit_amdmct end:
>>
>> *** Yes, the copy/decompress is taking a while, FIXME!
>> v_esp=000cbf18
>> testx = 5a5a5a5a
>> dump_mem:
>> 000c8000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>>     
> I think the other end of the stack would be more interesting.  Something
> like 0xcbf00-0xcc000 (CAR).  Then you could dump the RAM for the stack too.
> I guess since you know it's not working, seeing the values wouldn't really
> help.  I'd try looking at the values you see in raminit, and why the dimm
> isn't getting initialized correctly.
>
> Thanks,
> Myles

Hello,

I tested the ram and got:

aminit_amdmct end:
Testing DRAM : 00100000 - 07ffffff
DRAM fill: 0x00100000-0x07ffffff
00100000 00200000 00300000 00400000 00500000 00600000 00700000 00800000
00900000 00a00000 00b00000 00c00000 00d00000 00e00000 00f00000 01000000
01100000 01200000 01300000 01400000 01500000 01600000 01700000 01800000
01900000 01a00000 01b00000 01c00000 01d00000 01e00000 01f00000 02000000
02100000 02200000 02300000 02400000 02500000 02600000 02700000 02800000
02900000 02a00000 02b00000 02c00000 02d00000 02e00000 02f00000 03000000
03100000 03200000 03300000 03400000 03500000 03600000 03700000 03800000
03900000 03a00000 03b00000 03c00000 03d00000 03e00000 03f00000 04000000
04100000 04200000 04300000 04400000 04500000 04600000 04700000 04800000
04900000 04a00000 04b00000 04c00000 04d00000 04e00000 04f00000 05000000
05100000 05200000 05300000 05400000 05500000 05600000 05700000 05800000
05900000 05a00000 05b00000 05c00000 05d00000 05e00000 05f00000 06000000
06100000 06200000 06300000 06400000 06500000 06600000 06700000 06800000
06900000 06a00000 06b00000 06c00000 06d00000 06e00000 06f00000 07000000
07100000 07200000 07300000 07400000 07500000 07600000 07700000 07800000
07900000 07a00000 07b00000 07c00000 07d00000 07e00000 07f00000 08000000
DRAM filled
DRAM verify: 0x00100000-0x07ffffff
00100000 Fail: @0x00100040 Read value=0x00114040
Fail: @0x00100044 Read value=0x00114044
Fail: @0x00100048 Read value=0x00114048
Fail: @0x0010004c Read value=0x0011404c
Fail: @0x00100050 Read value=0x00114050
...
Fail: @0x00100434 Read value=0x00114434
Fail: @0x00100438 Read value=0x00114438
Fail: @0x0010043c Read value=0x0011443c
Fail: @0x00100440 Read value=0x00114440
Aborting.
00100440
DRAM did _NOT_ verify!
DRAM ERROR

is anyone able to interpret something out of this which could help me :P
because I can't except for the fact that it's failing.

Thanks and bye,
Knut Kujat.





More information about the coreboot mailing list