public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: 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 20:49:29 +0200	[thread overview]
Message-ID: <3B82AD39.1268A6F0@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> <3B828898.BD98D4C4@gmx.at> <m1ae0tmll8.fsf@frodo.biederman.org>

"Eric W. Biederman" wrote:
> 
> Wilfried Weissmann <Wilfried.Weissmann@gmx.at> writes:
> >
> > 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.
> 
> Hmm.  There are some similiar conditions.  And it may be the same bug.
> 
> Is your dosemu not suid root?  And running in X when you are playing those
> games?  You don't have any ports lines in your dosemu.conf?
> 
> It is very important to rule out dosemu doing direct hardware access, before investigating
> something else like the kernel.

I set $_videoportaccess = (0)
This should not change anything since $_graphics=(0) too. However I
experienced no more crashes. (???)

> 
> Eric

thanks,
Wilfried

  reply	other threads:[~2001-08-21 18:49 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
     [not found]                 ` <3B828898.BD98D4C4@gmx.at>
2001-08-21 16:20                   ` Eric W. Biederman
2001-08-21 18:49                     ` Wilfried Weissmann [this message]
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=3B82AD39.1268A6F0@gmx.at \
    --to=wilfried.weissmann@gmx.at \
    --cc=ebiederm@xmission.com \
    --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