[coreboot] Problems porting H8dmr_fam10 to H8qme-2+

Knut Kujat knuku at gap.upv.es
Mon Dec 21 11:27:58 CET 2009


Myles Watson escribió:
>
>
> On Fri, Dec 18, 2009 at 8:41 AM, Knut Kujat <knuku at gap.upv.es
> <mailto:knuku at gap.upv.es>> wrote:
>
>>     Never mind about the memory corruption.  PNP: 002e.3 has some
>>     resources that aren't "fixed", so the allocator is trying to
>>     allocate them.  In the SuperIO code where those resources are
>>     declared, set the flags to match the other resources.
>     Problem solved I killed it :) means I disabled it in the device
>     tree. The H9DMR board has two serials and my board H8QME has only
>     one.
>
> Great.
>  
>
>     Now, I've got till the MTRR initialization and here is my reward:
>
>     POST: 0x93
>     Setting up local apic... apic_id: 0x0a done.
>     POST: 0x9b
>     CPU model: Quad-Core AMD Opteron(tm) Processor 8350
>     siblings = 03, CPU #10 initialized
>     All AP CPUs stopped
>     PCI: 00:18.0 init
>     PCI: 00:02.0 init
>     Unexpected Exception: 6 @ 10:00207ff1 - Halting
>     Code: 0 eflags: 00010046
>     eax: 00000000 ebx: 00226358 ecx: 0021ea74 edx: 00000001
>     edi: 0021ea74 esi: 00000001 ebp: 0023fff4 esp: 0023ff50
>     POST: 0xff
>
>     the strange thing is that it seems to work for like 11 other
>     cores. And this log is from my last try but before it always
>     starts rebooting with SOFT RESET after:
>
>
> Somebody else will probably know how to help you better.  The first
> thing I would do is disable siblings (LOGICAL_PROCESSORS=0) and see if
> you can get past it or not.
>
> Thanks,
> Myles
>
Hello,

I now getting this:
Setting fixed MTRRs(0-88) type: UC
After Startup.
Initializing CPU #0
DONE fixed MTRRs
C


INIT detected from  --- {     APICID = 00 NODEID = 00 COREID = 00} ---

Issuing SOFT_RESET...


coreboot-2.0.0-r_Fallback lun dic 21 11:02:38 CET 2009 starting...

BSP Family_Model: 00100f22
*sysinfo range: [000cc000,000cdfa0]
bsp_apicid = 00
cpu_init_detectedx = 00000000
microcode: equivalent rev id  = 0x1022, current patch id = 0x00000000
microcode: rev id (1062) does not match this patch.
microcode: Not updated! Fix microcode_updates[]
cpuSetAMDMSR  done
...blablabla

but I haven't changed anything but inserting some printk_spew into "void
dev_initialize(void)" to see where exactly jumps the exception out.

I'm confused :(.

THX,
Knut Kujat.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20091221/da0b503b/attachment.html>


More information about the coreboot mailing list