run away pci scan

[Marc Jones]

I'm working with amd/mahogany_fam10 mainboard and having problems in
ramstage. It is going through pci device scanning when it starts
finding the same devices again and malloc memory until it dies. It
also looks like it never goes down a bridge, always staying on bus0.
The problem starts at CPU: APIC: 03, it starts scanning bus0 again.

Enumerating buses...
Show all devs...Before Device Enumeration.
Root Device: enabled 1, 0 resources
APIC_CLUSTER: 0: enabled 1, 0 resources
APIC: 00: enabled 1, 0 resources
PCI_DOMAIN: 0000: enabled 1, 0 resources

... normal device init happens.....

CPU: APIC: 00 enabled
malloc Enter, size 1092, free_mem_ptr 00270000
malloc 00270000
CPU: APIC: 01 enabled
malloc Enter, size 1092, free_mem_ptr 00270444
malloc 00270444
CPU: APIC: 02 enabled
malloc Enter, size 1092, free_mem_ptr 00270888
malloc 00270888
CPU: APIC: 03 enabled
PCI_DOMAIN: 0000 scanning...

Anyone have  thoughts on what is happening here? Attached complete serial log.

Thanks!
Marc

[Myles Watson]

> I'm working with amd/mahogany_fam10 mainboard and having problems in
> ramstage. It is going through pci device scanning when it starts
> finding the same devices again and malloc memory until it dies. It
> also looks like it never goes down a bridge, always staying on bus0.
> The problem starts at CPU: APIC: 03, it starts scanning bus0 again.
>
> Anyone have  thoughts on what is happening here?

Have you tried increasing the stack size?  That's been a problem in the past
with this type of failure.
> Attached complete serial
> log.

I didn't get it.

Thanks,
Myles

[Marc Jones]

On Fri, Apr 30, 2010 at 4:21 PM, Myles Watson  wrote:
> > Anyone have  thoughts on what is happening here?
>
> Have you tried increasing the stack size?  That's been a problem in the past
> with this type of failure.

Thanks, I tried increasing the stack size from 0x8000 to 0x10000, but
that didn't seem to help.

[Patrick Georgi]

Am Freitag, den 30.04.2010, 16:15 -0600 schrieb Marc Jones:
> I'm working with amd/mahogany_fam10 mainboard and having problems in
> ramstage. It is going through pci device scanning when it starts
> finding the same devices again and malloc memory until it dies. It
> also looks like it never goes down a bridge, always staying on bus0.
> The problem starts at CPU: APIC: 03, it starts scanning bus0 again.

We had that case happen when a bridge had a secondary bus ID of 0.
coreboot then enters the bridge, and starts again with the root bus.

This could also happen with other bus ids, but I guess 0 is the most
obvious contender for misbehaviour.

Patrick

[ron minnich]

On Sat, May 1, 2010 at 6:09 AM, Patrick Georgi  wrote:
> We had that case happen when a bridge had a secondary bus ID of 0.
> coreboot then enters the bridge, and starts again with the root bus.
>
> This could also happen with other bus ids, but I guess 0 is the most
> obvious contender for misbehaviour.

I saw that too once but can not remember the fix save printing "this
bridge is broken" and refusing to proceed.

ron