Re: [coreboot] coreboot hangs on my AMD fam10 board (updatedebugmessage).

[Bao, Zheng]

Ping. What is the way to solve this?

I can NOT merge the CBFS to our code for a long time.

Zheng
-----Original Message-----
From: [e-mail]
[mailto:[e-mail]] On Behalf Of Bao, Zheng
Sent: Saturday, October 10, 2009 10:12 AM
To: [e-mail]; Carl-Daniel Hailfinger
Subject: Re: [coreboot] coreboot hangs on my AMD fam10 board (update
debugmessage).

I update the code. It hangs at somewhere else. It seems to be what
Carl-Daniel said. Is there any workaround way to skip this and let do my
own job?

Zheng

-----Original Message-----
From: Carl-Daniel Hailfinger [mailto:[e-mail]] 
Sent: Saturday, October 10, 2009 9:16 AM
To: Bao, Zheng
Cc: [e-mail]
Subject: Re: [coreboot] coreboot hangs on my AMD fam10 board.

On 09.10.2009 08:10, Bao, Zheng wrote:
> Current coreboot seems to hang somewhere. Before the 60th anniversary

of
> People's Republic of China, I always disable the CBFS when I worked on
> my fam10 board, otherwise it would be error. But now, I can not find
> where I can disable it. It seems to stop at waiting AP cores.
>
> I am wondering if it is caused by CBFS and if it happens on other

board.
> If any one can test it, I will be appreciating.

We have not solved the SMP startup printk locking yet. That explains the
mangled log messages.
Unless I'm mistaken we still decompress some parts multiple times
concurrently to the same address and that can crash the code.
Overlapping stack might also crash the code during lzma decompression.
Decompression of AP code should happen on the BSP or on exactly one AP,
but not on all APs.
> coreboot-2.0.0-r623M_tilapia_fam10_Fallback Fri Oct  9 13:15:49 CST

2009
> starting...
> [...]
> Start other core - nodeid: 00  cores: 03
> started ap apicid:    cccooorrreeexxx:::      ---------   {{{
> AAAPPPIIICCC
> IIIDDD   ===   000312   NNNOOODDDEEEIIIDDD   ===   000000
> CCCOOORRREEEIIIDDD   ===   000321}}
> }   ---------

Regards,
Carl-Daniel

coreboot hangs on my AMD fam10 board (updatedebugmessage).

[Myles Watson]

On Sun, Oct 11, 2009 at 7:44 PM, Bao, Zheng  wrote:
> Ping. What is the way to solve this?

Could you test a few things to make sure we understand what's broken?
1. Try a single-processor build and see if it still fails.
2. Try not compressing your coreboot_ram.
...
Is your log level set to 9?

Thanks,
Myles

coreboot hangs on my AMD fam10 board (updatedebugmessage).

[Carl-Daniel Hailfinger]

On 12.10.2009 16:28, Myles Watson wrote:
> On Sun, Oct 11, 2009 at 7:44 PM, Bao, Zheng  wrote:
> > Ping. What is the way to solve this?
>
> Could you test a few things to make sure we understand what's broken?
> Try a single-processor build and see if it still fails.
> Try not compressing your coreboot_ram.

IIRC the problem ist not coreboot_ram, but coreboot_apc, so please do
not compress coreboot_apc and use a dualcore processor (more cores may
contribute to the problem). That could serve as a hack to get things going.

Regards,
Carl-Daniel

coreboot hangs on my AMD fam10 board (updatedebugmessage).

[Myles Watson]

> > Try not compressing your coreboot_ram.
>
> IIRC the problem ist not coreboot_ram, but coreboot_apc, so please do
> not compress coreboot_apc and use a dualcore processor (more cores may
> contribute to the problem). That could serve as a hack to get things going.

The fam10 code doesn't use coreboot_apc by default.

Thanks,
Myles

coreboot hangs on my AMD fam10 board (updatedebugmessage).

[Myles Watson]

On Mon, Oct 12, 2009 at 8:28 AM, Myles Watson  wrote:
> On Sun, Oct 11, 2009 at 7:44 PM, Bao, Zheng  wrote:
> > Ping. What is the way to solve this?
>
> Could you test a few things to make sure we understand what's broken?
> Try a single-processor build and see if it still fails.
> Try not compressing your coreboot_ram.
>
> ...
> Is your log level set to 9?

I just downloaded the latest SimNOW and got the latest Coreboot.  It
"just worked" for me.  In the past I've had trouble when there's a
major change and config.py doesn't get updated.  Could you try:

rm -rf targets/amd/serengeti_cheetah_fam10/serengeti_cheetah_fam10/
./buildtarget amd/serengeti_cheetah_fam10
make -C amd/serengeti_cheetah_fam10/serengeti_cheetah_fam10

It booted to SeaBIOS for me.

Thanks,
Myles

coreboot hangs on my AMD fam10 board(updatedebugmessage).

[Bao, Zheng]

Now I found that the system doesn't hang. It just decompresses the
image. It is unbearably slow. Do you guys know why it does so slowly?

Zheng

-----Original Message-----
From: coreboot-bounces+zheng.bao=[e-mail]
[mailto:coreboot-bounces+zheng.bao=[e-mail]] On Behalf Of
Bao, Zheng
Sent: Monday, October 12, 2009 9:45 AM
To: [e-mail]
Subject: Re: [coreboot] coreboot hangs on my AMD fam10
board(updatedebugmessage).

Ping. What is the way to solve this?

I can NOT merge the CBFS to our code for a long time.

Zheng
-----Original Message-----
From: [e-mail]
[mailto:[e-mail]] On Behalf Of Bao, Zheng
Sent: Saturday, October 10, 2009 10:12 AM
To: [e-mail]; Carl-Daniel Hailfinger
Subject: Re: [coreboot] coreboot hangs on my AMD fam10 board (update
debugmessage).

I update the code. It hangs at somewhere else. It seems to be what
Carl-Daniel said. Is there any workaround way to skip this and let do my
own job?

Zheng

-----Original Message-----
From: Carl-Daniel Hailfinger [mailto:[e-mail]] 
Sent: Saturday, October 10, 2009 9:16 AM
To: Bao, Zheng
Cc: [e-mail]
Subject: Re: [coreboot] coreboot hangs on my AMD fam10 board.

On 09.10.2009 08:10, Bao, Zheng wrote:
> Current coreboot seems to hang somewhere. Before the 60th anniversary

of
> People's Republic of China, I always disable the CBFS when I worked on
> my fam10 board, otherwise it would be error. But now, I can not find
> where I can disable it. It seems to stop at waiting AP cores.
>
> I am wondering if it is caused by CBFS and if it happens on other

board.
> If any one can test it, I will be appreciating.

We have not solved the SMP startup printk locking yet. That explains the
mangled log messages.
Unless I'm mistaken we still decompress some parts multiple times
concurrently to the same address and that can crash the code.
Overlapping stack might also crash the code during lzma decompression.
Decompression of AP code should happen on the BSP or on exactly one AP,
but not on all APs.
> coreboot-2.0.0-r623M_tilapia_fam10_Fallback Fri Oct  9 13:15:49 CST

2009
> starting...
> [...]
> Start other core - nodeid: 00  cores: 03
> started ap apicid:    cccooorrreeexxx:::      ---------   {{{
> AAAPPPIIICCC
> IIIDDD   ===   000312   NNNOOODDDEEEIIIDDD   ===   000000
> CCCOOORRREEEIIIDDD   ===   000321}}
> }   ---------

Regards,
Carl-Daniel

coreboot hangs on my AMD fam10 board(updatedebugmessage).

[Ward Vandewege]

On Mon, Nov 02, 2009 at 02:25:23PM +0800, Bao, Zheng wrote:
> Now I found that the system doesn't hang. It just decompresses the
> image. It is unbearably slow. Do you guys know why it does so slowly?

Ah! I saw that too on Fam10. Mansoor suggested setting

CONFIG_XIP_ROM_BASE

to solve this. Does that help?

Thanks,
Ward.