From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] just run xdos
Date: Tue, 21 Aug 2001 18:14:18 +0200 [thread overview]
Message-ID: <3B8288DA.D5E52766@gmx.at> (raw)
In-Reply-To: <Pine.LNX.4.33.0108191600580.10914-100000@boston.corp.fedex.com> <m166bjokre.fsf@frodo.biederman.org> <20010819214322.D1315@squish.home.loc> <m1snenmfe0.fsf@frodo.biederman.org> <20010820211410.B218@squish.home.loc> <m1g0amlzcm.fsf@frodo.biederman.org>
"Eric W. Biederman" wrote:
>
> Paul <set@pobox.com> writes:
>
> > "Eric W. Biederman" <ebiederm@xmission.com>, on Mon Aug 20, 2001 [12:09:27 AM]
> > said:
> >
> >
> > > If you can rule out X stracing dosemu might be of some help. The
> > > challenge now is to track down what dosemu is doing that is triggering
> > > the problem.
> > >
> > > As an interrupt handler is where the oops is occuring. Finding an
> > > immediate cause and effect could be tricky.
> > >
> > > Eric
> >
> > Dear Eric;
> >
> > Ok. I oopsed/locked the machine running 'dos' in a vt,
> > without X in single user mode. Then I did it again, stracing the
> > session. Unfortunately, the fs was left in such a state, that
> > fsck completely chucked the logfile out. Then I booted 2.2.18, and
> > tried. I could not make it oops.
> > I need to setup a test machine to persue this farther, as
> > locking and fscking my main box is no fun:) Ill try to get that
> > strace...
>
> O.k. That rules out all kinds of things. What is interesting at first
> glance is that a) Every oops has been in an interrupt handler. and
> b) It is never remotely at the same location.
>
> I'm beginning to suspect there is some kind of hardware problem. But it
> is very weird. I wonder if dos 6.2 somehow tickles a bug in the media GX
> processor. Though my top canidate is probably the lazy state switching
> introduced in 2.4. I know there were some problems with the ldt that were
> fixed, and there might be another case out there. But I'm just guessing
> in the dark.
>
> If you can reproduce this on a second machine that would definentily help.
>
> Eric
I have the same problem on a K7-800. My kernel is 2.4.7-ac3 (with K7
optimization!). Everything else seems to work fine, but dosemu locks up
the computer when running certain games.
Sometimes I can play for quite some time (1/2 hour or more) without
problems. Eventually it will freeze. It feels like it is triggered by
mouse activity.
Wilfried
next prev parent reply other threads:[~2001-08-21 16:14 UTC|newest]
Thread overview: 18+ 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 [this message]
[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
[not found] ` <20010821232557.G218@squish.home.loc>
[not found] ` <3B832904.491AFE0E@didntduck.org>
2001-08-22 4:43 ` [OOPS] [resolution] Paul
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=3B8288DA.D5E52766@gmx.at \
--to=wilfried.weissmann@gmx.at \
--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