No way, after the first int I have wait 5min and captured 5MB of ff. However, I have disabled the inb printf and all works fine for the rest :D
I'm afraid its the in's that I am interested in seeing. You have said earlier that the long delay is during the first couple of int10's. Thats where I want to see what its waiting on.
I know the log will be huge. Go ahead and run the user emu with the IO enabled for say 10 seconds and then quit. That should be enough to start with. It should compress down alot since its all text.
Also did you run the user emu with the if (port < 0x53) filter on the IO? I want to first rule out that its an issue with reading the system timer.
-- Richard A. Smith
Richard Smith schrieb:
No way, after the first int I have wait 5min and captured 5MB of ff. However, I have disabled the inb printf and all works fine for the rest :D
I'm afraid its the in's that I am interested in seeing. You have said earlier that the long delay is during the first couple of int10's. Thats where I want to see what its waiting on.
To clear this:
normally with disabled debug for the inTree emu there are three lines like
int10 vector at c000:xxxx short after each line normally the run_bios_int function is called.
the long delays are after the first call (20-30s) and after the second call (60-70s) The second delay is divided in two parts, because at the middle there is a flickering.
I know the log will be huge. Go ahead and run the user emu with the IO enabled for say 10 seconds and then quit. That should be enough to start with. It should compress down alot since its all text.
I have send the log to you, yesterday. Or not ??
Also did you run the user emu with the if (port < 0x53) filter on the IO? I want to first rule out that its an issue with reading the system timer.
I have tried this, but remember there was no debug outbut for port < 0x53 for the inTree emu.
However, I will do it for the userspace emu.
chris
-- Richard A. Smith
I know the log will be huge. Go ahead and run the user emu with the IO enabled for say 10 seconds and then quit. That should be enough to start with. It should compress down alot since its all text.
I have send the log to you, yesterday. Or not ??
The only thing I got yesterday was a 90k log that did not include any in statements.
-- Richard A. Smith
Also did you run the user emu with the if (port < 0x53) filter on the IO? I want to first rule out that its an issue with reading the system timer.
Here is the user emu output with enabled (port < 0x53) filter. as I say, no output for that ;)
chris
./testbios -s 32768 --abseg /dev/mem aw512n.bin -d 0x48 running file aw512n.bin No base specified. defaulting to 0xc0000 No initial code segment specified. defaulting to 0xc000 No initial instruction pointer specified. defaulting to 0x0003 Loading ax with BusDevFn = 48 updating int vector 0x10 updating int vector 0x10 updating int vector 0x42 updating int vector 0x42 updating int vector 0x43 updating int vector 0x43 updating int vector 0x1f updating int vector 0x1f updating int vector 0x1d updating int vector 0x1d updating int vector 0x1d updating int vector 0x1d updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 int10 vector at c41b4 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 run_bios_int: INT 10 CS:IP = c000:41b4 updating int vector 0x43 updating int vector 0x43 updating int vector 0x43 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 int10 vector at c41b4 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 run_bios_int: INT 10 CS:IP = c000:41b4 updating int vector 0x43 updating int vector 0x43 updating int vector 0x43 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 int10 vector at c41b4 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 updating int vector 0x10 run_bios_int: INT 10 CS:IP = c000:41b4 updating int vector 0x43 updating int vector 0x43 updating int vector 0x1d updating int vector 0x1d #
On 5/3/06, Christian Sühs chris@suehsi.de wrote:
Also did you run the user emu with the if (port < 0x53) filter on the IO? I want to first rule out that its an issue with reading the system timer.
Here is the user emu output with enabled (port < 0x53) filter. as I say, no output for that ;)
Ok. Thanks. Well then that rules out timer 1 or 2 issues. Very interesting that it does not use the timer for any delays.
-- Richard A. Smith
-
Christian Sühs -
Richard Smith