Hi, I finally got it working, but I don't like my solution! I noticed that after setup_mb_resource_map(); the board hang at outb and inl instructions. So I commented it out to see how far this will bring me. For my surprise the board booted right into Linux without further problems. Now my questions are:
- I now know that my resource map must be some kind of faulty. But why does it work on one CPU and doesn't on another, complete identical, one? - How do i manage to correct my resource map? Or how do I create a good resource map? - Since it seems to boot fine without resource map. Do I really need one? - And the last one, If I don't setup the res. map, who does it? Thanks and sorry for the whole bunch of questions, Knut Kujat. Knut Kujat escribió: > Marc Jones escribió: > >> On Sun, May 2, 2010 at 4:59 PM, Rudolf Marek <[email protected]> wrote: >> >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Hi, >>> >>> There is a plenty of bugs as in all modern CPUs ;) >>> >>> http://support.amd.com/us/Processor_TechDocs/41322.pdf >>> >>> Quick look to coreboot shows they are not handled? >>> >>> Some are easy to fix just to set some MSR, some are microcode fixes. >>> >>> >>> >> That Fam10 bugs should be handled in cpuSetAMDMSR as well as the microcode. >> >> If it is a race condition, it should pass CONFIG_LOGICAL_CPUS = 0. >> >> Marc >> >> >> > Hi, > > thx for your comments. > > I already set Config_Logical_CPUS = 0 and set physical and logical CPUs > to 1. This gets me a little further but still hangs before warm reset. > As I already set I have the exact same problem as Ward reported some > time ago. > > Thanks, > Knut Kujat. > > -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
