,
Ramya
From: l4-hackers [l4-hackers-boun...@os.inf.tu-dresden.de] on behalf of Adam
Lackorzynski [a...@os.inf.tu-dresden.de]
Sent: 09 September 2014 22:46
To: l4-hackers@os.inf.tu-dresden.de
Subject: Re: Aborted L4linux due to CLI/STI
Hi,
On Mon Sep 08
Hi,
On Mon Sep 08, 2014 at 07:10:00 +, Masti Ramya Jayaram wrote:
That's ok as long it's also ok for native Linux.
I am not sure what they did with native Linux but I know from the SCC
forums that these instructions do not exist. So I guess that is ok.
I'm wondering how did you end
From: l4-hackers [l4-hackers-boun...@os.inf.tu-dresden.de] on behalf of Adam
Lackorzynski [a...@os.inf.tu-dresden.de]
Sent: 08 September 2014 00:29
To: l4-hackers@os.inf.tu-dresden.de
Subject: Re: Aborted L4linux due to CLI/STI
On Fri Sep 05, 2014 at 16:21:34 +
Jayaram rma...@inf.ethz.ch wrote:
Dear all,
I get an error during L4linux boot when I enter the debugger (using ESC)
and resume:
Aborted L4linux due to CLI/STI at 0x534911.
When I disassemble this using gdb:
(gdb) disassemble 0x534911
Dump of assembler code for function
Dear all,
I get an error during L4linux boot when I enter the debugger (using ESC) and
resume:
Aborted L4linux due to CLI/STI at 0x534911.
When I disassemble this using gdb:
(gdb) disassemble 0x534911
Dump of assembler code for function cmpxchg8b_emu:
0x00534910 +0: pushf
an error during L4linux boot when I enter the debugger (using ESC) and
resume:
Aborted L4linux due to CLI/STI at 0x534911.
When I disassemble this using gdb:
(gdb) disassemble 0x534911
Dump of assembler code for function cmpxchg8b_emu:
0x00534910 +0:pushf
0x00534911 +1:cli
