From: Andi Kleen <ak@suse.de>
To: Brian Gerst <bgerst@didntduck.org>
Cc: linux-kernel@vger.kernel.org, set@pobox.com,
alan@lxorguk.ukuu.org.uk, Wilfried.Weissmann@gmx.at
Subject: Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos
Date: 22 Aug 2001 13:16:16 +0200 [thread overview]
Message-ID: <oupn14sny4f.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <20010819004703.A226@squish.home.loc.suse.lists.linux.kernel> <3B831CDF.4CC930A7@didntduck.org.suse.lists.linux.kernel>
In-Reply-To: Brian Gerst's message of "22 Aug 2001 04:54:51 +0200"
Brian Gerst <bgerst@didntduck.org> writes:
> >
> > CPU: 0
> > EIP: 0010:[<c0180a18>]
> > Using defaults from ksymoops -t elf32-i386 -a i386
> > EFLAGS: 00010002
> > eax: 00001000 ebx: c4562368 ecx: 00000000 edx: 00000001
> > esi: c4562368 edi: c4a954d4 ebp: 00000001 esp: c6887d88
> > ds: 008 es: 0000 ss: 0018
> ^^^^
> Here is your problem. %es is set to the null segment. I had my
> suspicions about the segment reload optimisation in the -ac kernels, and
> this proves it. Try backing out the changes to arch/i386/kernel/entry.S
> and include/asm-i386/hw_irq.h and see if that fixes the problem.
This patch should fix the problem. One assumption coded into the reload
optimization is violated by vm86 mode. Please test.
--- linux-2.4.8-ac7-work/include/asm-i386/hw_irq.h-SEG2 Mon Aug 20 02:54:53 2001
+++ linux-2.4.8-ac7-work/include/asm-i386/hw_irq.h Wed Aug 22 13:02:16 2001
@@ -114,8 +114,10 @@
"cmpl %eax,7*4(%esp)\n\t" \
"je 1f\n\t" \
"movl %eax,%ds\n\t" \
+ "1: cmpl %eax,8*4(%esp)\n\t" \
+ "je 2f\n\t" \
"movl %eax,%es\n\t" \
- "1:\n\t"
+ "2:\n\t"
#define IRQ_NAME2(nr) nr##_interrupt(void)
#define IRQ_NAME(nr) IRQ_NAME2(IRQ##nr)
-Andi
next parent reply other threads:[~2001-08-22 11:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010819004703.A226@squish.home.loc.suse.lists.linux.kernel>
[not found] ` <3B831CDF.4CC930A7@didntduck.org.suse.lists.linux.kernel>
2001-08-22 11:16 ` Andi Kleen [this message]
2001-08-22 11:57 ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos Brian Gerst
2001-08-22 12:10 ` Andi Kleen
2001-08-22 12:11 ` Brian Gerst
2001-08-22 13:22 ` Andi Kleen
2001-08-22 19:52 ` Paul
2001-08-23 13:34 ` Andi Kleen
2001-08-23 18:05 ` Paul
2001-08-23 18:20 ` Wayne Whitney
2001-08-19 4:47 Paul
2001-08-19 5:09 ` Jeff Chua
2001-08-19 5:40 ` Paul
2001-08-19 8:04 ` Jeff Chua
2001-08-19 20:30 ` Eric W. Biederman
2001-08-19 5:10 ` Jeff Chua
2001-08-22 2:45 ` Brian Gerst
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=oupn14sny4f.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=Wilfried.Weissmann@gmx.at \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=set@pobox.com \
/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