public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Maximiliano Curia <maxy@rivero.com.ar>
To: linux-msdos@vger.kernel.org
Subject: Dosemu and clipper applications eating all CPU
Date: Mon, 08 Mar 2004 13:11:42 -0300	[thread overview]
Message-ID: <1078762302.15406.90.camel@peperina> (raw)

Hi!

I'm trying to run a clipper program inside dosemu.  It runs ok, but it
eats all the CPU cycles when it's idle. 

I've already tried changing the hogthreshold value, with no changes in
the result.

This is a snip of the strace of the process:

--- SIGALRM (Alarm clock) @ 0 (0) ---
<... vm86 resumed> )                    = -1 ENOSYS (Function not
implemented)
ioctl(4, FIONREAD, [0])                 = 0
select(7, [], NULL, NULL, {0, 0})       = 0 (Timeout)
select(7, [6], NULL, NULL, {0, 0})      = 0 (Timeout)
vm86(0x1, 0x81a2980, 0xa6, 0xfff8eff1, 0x8) = -1 ENOSYS (Function not
implemented)
vm86(0x1, 0x81a2980, 0xa6, 0xfff8eff1, 0xbffffa34) = -1 ENOSYS (Function
not implemented)
vm86(0x1, 0x81a2980, 0xa6, 0xfff8eff1, 0xbffffa34) = -1 ENOSYS (Function
not implemented)
--- SIGALRM (Alarm clock) @ 0 (0) ---
sigreturn()                             = ? (mask now [RTMIN])
ioctl(4, FIONREAD, [0])                 = 0
select(7, [], NULL, NULL, {0, 0})       = 0 (Timeout)
select(7, [6], NULL, NULL, {0, 0})      = 0 (Timeout)
vm86(0x1, 0x81a2980, 0xa6, 0xfff8eff1, 0xbffffa34 <unfinished ...>
--- SIGALRM (Alarm clock) @ 0 (0) ---
<... vm86 resumed> )                    = -1 ENOSYS (Function not
implemented)
ioctl(4, FIONREAD, [0])                 = 0
select(7, [], NULL, NULL, {0, 0})       = 0 (Timeout)
select(7, [6], NULL, NULL, {0, 0})      = 0 (Timeout)
vm86(0x1, 0x81a2980, 0xa6, 0xfff8eff1, 0xbffffa34 <unfinished ...>
--- SIGALRM (Alarm clock) @ 0 (0) ---

And it goes on like that.  While the user is doing nothing, this alarms
repeat themselves many times per second, turning the rest of the machine
into an unusable state.

When idle at the command prompt, the behaviour is notably different:

--- SIGALRM (Alarm clock) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
ioctl(4, FIONREAD, [0])                 = 0
gettimeofday({1078759812, 698914}, NULL) = 0
select(8, [], NULL, NULL, {0, 0})       = 0 (Timeout)
select(8, [7], NULL, NULL, {0, 0})      = 0 (Timeout)
gettimeofday({1078759812, 699517}, NULL) = 0
vm86(0x1, 0x81778a0, 0xa6, 0xfff8dff1, 0) = -1 ENOSYS (Function not
implemented)
vm86(0x1, 0x81778a0, 0xa6, 0xfff8dff1, 0) = -1 ENOSYS (Function not
implemented)
gettimeofday({1078759812, 700033}, NULL) = 0
vm86(0x1, 0x81778a0, 0xa6, 0xfff8dff1, 0) = -1 ENOSYS (Function not
implemented)
vm86(0x1, 0x81778a0, 0xa6, 0xfff8dff1, 0) = -1 ENOSYS (Function not
implemented)
(...) repeating gettimeofday+vm86+vm86 6 more times (...)
gettimeofday({1078759812, 703178}, NULL) = 0
vm86(0x1, 0x81778a0, 0xa6, 0xfff8dff1, 0) = -1 ENOSYS (Function not
implemented)
nanosleep({0, 80000000}, 0)             = ? ERESTART_RESTARTBLOCK (To be
restarted)
--- SIGALRM (Alarm clock) @ 0 (0) ---

I've been told this is a known problem, but I'm hoping it can be fixed
in some way.

-- 
Saludos
/\/\ /\ >< `/

             reply	other threads:[~2004-03-08 16:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-08 16:11 Maximiliano Curia [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-09 20:16 Dosemu and clipper applications eating all CPU Stas Sergeev
2004-03-10 15:29 ` Peter B. Steiger
2004-03-10 19:11 ` Maximiliano Curia
2004-03-10 18:36 Stas Sergeev
2004-03-10 19:36 Stas Sergeev
2004-03-10 22:55 ` Maurilio Longo
2004-03-11  8:29   ` Maurilio Longo
2004-03-11 18:44 Stas Sergeev
2004-03-12 22:33 Stas Sergeev
2004-03-15 11:53 ` Maurilio Longo
2004-03-15 17:50 Stas Sergeev
2004-03-15 18:07 ` Maurilio Longo
2004-03-15 19:17 Stas Sergeev
2004-04-28  5:55 Mgr. Peter Tuharsky
2004-04-28 19:52 ` Maximiliano Curia
2004-04-28 17:32 Stas Sergeev

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=1078762302.15406.90.camel@peperina \
    --to=maxy@rivero.com.ar \
    --cc=linux-msdos@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