From: Kasper Dupont <kasperd@daimi.au.dk>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: [RFC] vm86 bugs in 2.5.30
Date: Sat, 10 Aug 2002 10:49:05 +0200 [thread overview]
Message-ID: <3D54D381.793D796C@daimi.au.dk> (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.
>>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?
--
Kasper Dupont -- der bruger for meget tid på usenet.
For sending spam use mailto:razrep@daimi.au.dk
or mailto:mcxumhvenwblvtl@skrammel.yaboo.dk
next reply other threads:[~2002-08-10 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-10 8:49 Kasper Dupont [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-10 19:52 [RFC] vm86 bugs in 2.5.30 Stas Sergeev
2002-08-10 20:10 ` Kasper Dupont
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D54D381.793D796C@daimi.au.dk \
--to=kasperd@daimi.au.dk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox