Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus

2010-02-15 Thread Marc Jones
2010/2/13 Zheng Bao fishb...@hotmail.com: Date: Sat, 13 Feb 2010 11:23:49 -0700 Subject: Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus From: marcj...@gmail.com To: fishb...@hotmail.com CC: coreboot@coreboot.org 2010/2/12 Zheng Bao fishb...@hotmail.com: Date

Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus

2010-02-13 Thread Marc Jones
2010/2/12 Zheng Bao fishb...@hotmail.com: Date: Fri, 12 Feb 2010 16:54:43 -0700 From: marcj...@gmail.com To: zheng@amd.com CC: coreboot@coreboot.org Subject: Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus On Fri, Feb 12, 2010 at 4:48 PM, Marc Jones marcj

Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus

2010-02-13 Thread Carl-Daniel Hailfinger
Zheng, can you try if the RS780 code works with a uniprocessor K8 (not Fam10) CPU? Maybe that gives us a better baseline for testing. Regards, Carl-Daniel -- Developer quote of the year: We are juggling too many chainsaws and flaming arrows and tigers. -- coreboot mailing list:

Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus

2010-02-13 Thread Zheng Bao
Date: Sat, 13 Feb 2010 11:23:49 -0700 Subject: Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus From: marcj...@gmail.com To: fishb...@hotmail.com CC: coreboot@coreboot.org 2010/2/12 Zheng Bao fishb...@hotmail.com: Date: Fri, 12 Feb 2010 16:54:43 -0700 From

Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus

2010-02-12 Thread Marc Jones
On Thu, Feb 11, 2010 at 6:54 PM, Bao, Zheng zheng@amd.com wrote: I kept on finding the problem. Now it is narrowed down to the line 108, src/arch/i386/coreboot_ram.ld. It is very, very, very, very confused. My CONFIG_RAMBASE should be 0x20, which is more than 0x10, but the location

Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus

2010-02-12 Thread Marc Jones
On Fri, Feb 12, 2010 at 4:48 PM, Marc Jones marcj...@gmail.com wrote: On Thu, Feb 11, 2010 at 6:54 PM, Bao, Zheng zheng@amd.com wrote: I kept on finding the problem. Now it is narrowed down to the line 108, src/arch/i386/coreboot_ram.ld. It is very, very, very, very confused. My

Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus

2010-02-12 Thread Zheng Bao
Date: Fri, 12 Feb 2010 16:54:43 -0700 From: marcj...@gmail.com To: zheng@amd.com CC: coreboot@coreboot.org Subject: Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus On Fri, Feb 12, 2010 at 4:48 PM, Marc Jones marcj...@gmail.com wrote: On Thu, Feb 11, 2010

Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus

2010-02-11 Thread Bao, Zheng
Chinese New Year. Oops. Zheng -Original Message- From: coreboot-boun...@coreboot.org [mailto:coreboot-boun...@coreboot.org] On Behalf Of Patrick Georgi Sent: Wednesday, February 10, 2010 6:52 PM To: coreboot@coreboot.org Subject: Re: [coreboot] Data in memory changes unexpectedly

Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus

2010-02-11 Thread Bao, Zheng
: Thursday, February 11, 2010 6:26 PM To: Patrick Georgi; coreboot@coreboot.org Subject: Re: [coreboot] Data in memory changes unexpectedly ininitialize_cpus I finally find out why. Your suggestion is quite usefull. The stack size is not set correctly. Each core should get 0x2000 bytes as its own stack