[SeaBIOS] SeaVGABIOS crash on FC13 X11

Julian Pidancet julian.pidancet at gmail.com
Sun Mar 10 03:04:02 CET 2013


On Sun, Mar 10, 2013 at 1:15 AM, Kevin O'Connor <kevin at koconnor.net> wrote:
> On Sun, Mar 10, 2013 at 01:09:35AM +0000, Julian Pidancet wrote:
>> On Sun, Mar 10, 2013 at 12:09 AM, Kevin O'Connor <kevin at koconnor.net> wrote:
>
> Yeah - I thought the same thing and looked into that.  The assembler
> translation is still being performed and I don't see anything that
> looks suspicious.
>

I managed to get set up with qemu and SeaBIOS and I'm seeing
interesting results:
First of all, I'm not able to access the Xorg logs, because it looks
like the VM crashes completely. (Maybe I need to ask Fedora to boot in
text mode ?)

I compiled SeaBIOS with DEBUG_LEVEL=3 and CONFIG_DEBUG_SERIAL_PORT, so
I can see what's going on. It looks like that when Xorg is about to
start in the VM, we're receiving a lot of corrupted data on the serial
port.

It reminds me a lot what I used to see with the Windows 16bit code
emulator, which was unable to dereference pointers using the %sp
register, which was leading the print function to display corrupted
strings. Could we have something similar here ?

It is printing the same sequence of bytes over and over again:

0002d160  30 30 33 0d 0a ff 55 aa  48 e9 ed 4e 93 55 aa 48  |003...U.H..N.U.H|
0002d170  ec ed 4e 93 55 aa 48 e9  ed 4e 93 55 aa 48 e9 ed  |..N.U.H..N.U.H..|
0002d180  4e 93 55 aa 48 e9 ed 4e  93 55 aa 48 e9 ed 4e 93  |N.U.H..N.U.H..N.|
0002d190  55 aa 48 e9 ed 4e 93 55  aa 48 e9 ed 4e 93 55 aa  |U.H..N.U.H..N.U.|
0002d1a0  48 e9 ed 4e 93 55 aa 48  e9 ed 4e 93 55 aa 48 e9  |H..N.U.H..N.U.H.|


-- 
Julian



More information about the SeaBIOS mailing list