Skip to contentSkip to conversation

vm86 bugs in 2.5.30

RFC Kasper Dupont 1 participant 1 message Aug 10, 2002

lore
Share & tools
lore
#0 lore raw

I'm trying to port the vm86 bugfixes from 2.4.19 to 2.5.30. A premature patch is available at:
http://www.daimi.au.dk/~kasperd/linux_kernel/vm86.2.5.30.patch
The second chunk in mark_screen_rdonly had to be applied by hand, so I'd appreachiate if whoever made that bugfix would verify I got the patch applied correctly.

I am however currently fighting with another vm86 problem. I get this oops on 2.5.30:

<4> invalid operand: 0000
<4>CPU: 0
<4>EIP: 0000:[<00000000>] Not tainted
<4>EFLAGS: 00030282

<4>eax: 00000000   ebx: 00000000   ecx: 00000000   edx: 00000000
<4>esi: 00000000   edi: 00000000   ebp: 00000000   esp: cb5dbf24

<4>ds: 0000 es: 0000 ss: 0018
<4>Stack: 00007c00 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<4> 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<4> 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
<4>Call Trace: [<c0108c87>]
<4>Code: Bad EIP value.

Quoted 1 line
Quoted 1 line

EIP; 00000000 Before first symbol

Trace; c0108c87 <syscall_call+7/b>

It happens during the vm86 system call, but it is not fixed by any of the changes in vm86.c. Who remember which patch fixed this problem?

Signature · 3 lines
Kasper Dupont -- der bruger for meget tid på usenet.
For sending spam use mailto:[email protected]
or mailto:[email protected]