On 28.01.2008 20:38, ron minnich wrote:
> coreboot seems to by dying in VSM on some config access as well.
>> Carl-Daniel pointed out to me:
> "IIRC there is also a VSM stack which is located in a place differing
> from the one clobbered between 0x1000 and 0x2000.
>> Notice how it blows up exactly at the time where the first virtual PCI
> access happens. That means it blows up inside VSM."
>> So we need to get a complete idea of the needs of VSA/VSM for memory and stack.
>
For more context, here is a snippet from Ron's latest boot log with
stage2 at 0x2000. Ron, please correct me if I misstated something.
> It blow up here:
> PCI: devfn 0x8
> pci_scan_get_dev: list is 0x00087ea8, *list is 0x0000bd40
> pci_scan_get_dev: check dev device0_0
> pci_scan_get_dev: check dev device0_0 it has devfn 0x08
> PCI: pci_scan_bus pci_scan_get_dev returns dev device0_0
> find_constructor: find PCI: 1022:2080
> find_constructor: check all_constructors[i] 0x0000c720
> find_constructor: cons 0x0000c720, cons id PCI_DOMAIN: 1022:2080
>>> LinuxBIOS-3.0.0 Sun Jan 27 19:15:18 PST 2008 starting...
>> i.e. got through VSA, found dev 0:1.0, found it is a PCI device,
> running find_constructor, blowing up.
Regards,
Carl-Daniel