Looking at one of your old logs, it looks like the VSA init code is *running* in the 0x1000 segment:
http://www.coreboot.org/pipermail/coreboot/2008-January/029736.html
(cs 0x1000)
That is probably smashing the region. The int18s are certainly bad, you should just have the normal two int15s, with cs 0x6000.
How do I get vsa into coreboot v3? I built an alix image, and I am able to boot it on a different lx platform, but it does not find vsa, since I didn't build it in. I'll look at the VSA load with FS2 if someone tells me how.
On Jan 28, 2008 7:07 PM, ron minnich rminnich@gmail.com wrote:
On Jan 28, 2008 3:58 PM, Marc Jones marc.jones@amd.com wrote:
I don't think so. It is coreboot that sets the stack for VSA initialization. The more I think about it, the stack shouldn't be moved. Just switch to real mode and VSA can use the same stack as LinuxBIOS (maybe pad it a little if you are worried about alignment). This is how it works in a standard BIOS.
Stack is at 8ffxx, which is way out of 64k area ... I am lazy and set %es to 0. It's really much easier to leave it on page 0 :-)
It is in the VSA memory area. It is setup by VSA during init.
Ron, can you provide us with logs of the last revision before VSA support went in and of your current local codebase? I hope to pinpoint the location of the explosion better.
I should be building shortly and be able to find what is blowing up.
Thanks
ron