From: Brian Gerst <bgerst@didntduck.org>
To: Paul <set@pobox.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos
Date: Tue, 21 Aug 2001 22:45:51 -0400 [thread overview]
Message-ID: <3B831CDF.4CC930A7@didntduck.org> (raw)
In-Reply-To: <20010819004703.A226@squish.home.loc>
Paul wrote:
>
> * Kernel oops, and locks up when I run xdos (dosemu)
>
> * Occuring in both 2.4.7-ac6 and 2.4.8-ac7. Run 'xdos' in X, and
> machine locks hard, only output to console is oops. (no sysrq)
> Tried once with strace, but no oops. (didnt wait long, though)
> Some oops before window is placed, some a little while after.
> (mouse movement?) Repeatable.
>
> * Kernels are virgin linus patched with ac. AMD-K6(tm) 3D
> processor
>
> * If anyone wants any more info or for me to do anything, just
> ask.
>
> Paul
> set@pobox.com
>
> (2.4.7-ac6 -- two captured, identitcal, first shown)
>
> ksymoops 2.4.1 on i586 2.4.7-ac6. Options used
> -V (default)
> -k /proc/ksyms (default)
> -l /proc/modules (default)
> -o /lib/modules/2.4.7-ac6/ (default)
> -m /boot/System.map-2.4.7-ac6 (specified)
>
> 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.
--
Brian Gerst
next prev parent reply other threads:[~2001-08-22 2:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 4:47 [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos 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-20 1:43 ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] " Paul
2001-08-20 6:09 ` Eric W. Biederman
2001-08-21 1:14 ` Paul
2001-08-21 6:08 ` Eric W. Biederman
2001-08-21 16:14 ` Wilfried Weissmann
[not found] ` <3B828898.BD98D4C4@gmx.at>
2001-08-21 16:20 ` Eric W. Biederman
2001-08-21 18:49 ` Wilfried Weissmann
2001-08-21 21:50 ` Wilfried Weissmann
2001-08-22 1:42 ` Paul
2001-08-22 7:56 ` Eric W. Biederman
2001-08-19 5:10 ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 " Jeff Chua
2001-08-22 2:45 ` Brian Gerst [this message]
[not found] ` <20010821232557.G218@squish.home.loc>
[not found] ` <3B832904.491AFE0E@didntduck.org>
2001-08-22 4:43 ` [OOPS] [resolution] Paul
[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 ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos Andi Kleen
2001-08-22 11:57 ` 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
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=3B831CDF.4CC930A7@didntduck.org \
--to=bgerst@didntduck.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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