On Sat, May 1, 2010 at 6:09 AM, Patrick Georgi patrick@georgi-clan.de 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