[coreboot] unexpected exception errors loading vga rom

ron minnich rminnich at gmail.com
Fri Apr 24 17:15:58 CEST 2009

On Wed, Apr 22, 2009 at 8:58 PM, Joseph Smith <joe at settoplinux.org> wrote:
> YAHOO!!!!
> Well there is definitely something wacked out on x86emu and yabel. For the
> hell of it I tried VM86 and VGA comes right up with no errors. And VM86 is
> way faster x86emu and yabel. With my debug level still at 9 and a 5 second
> delay for filo, I am at the filo prompt in 15 seconds :-) This used to take
> about 25-30 seconds with x86emu.
> One question, is this normal for VM86?
> (from bootlog)
> PCI: 00:02.0 init
> On mainboard, rom address for PCI: 00:02.0 = fff00000
> PCI Expansion ROM, signature 0xaa55, INIT size 0x10000, data ptr 0x0040
> PCI ROM Image, Vendor 8086, Device 3577,
> PCI ROM Image,  Class Code 030000, Code Type 00
> copying VGA ROM Image from fff00000 to 0xc0000, 0x10000 bytes
> biosint: INT# 0xd
> biosint: eax 0x23fddfef ebx 0x0 ecx 0x2f6 edx 0x3b4
> biosint: ebp 0x10fac esp 0xc89 edi 0x4028 esi 0x24028
> biosint:  ip 0xffff   cs 0xc000  flags 0x813
> biosint: Oops, exception 13

this is really, really bad.

You don't want this to happen.

It's going to be way easier to debug if you run in linux, user more
x86emu, and turn on instruction tracing. Something's going very wrong.

Many of these vga bioses are very badly written and will fail on weird
ways. I think you've got one.


More information about the coreboot mailing list