linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: gaxt <gaxt@rogers.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org
Subject: 260test2+O10int breaks : Re: WINE + Galciv + Con Kolivar's 09 patch to  2.6.0-test1-mm2
Date: Mon, 28 Jul 2003 01:17:34 -0400	[thread overview]
Message-ID: <3F24B1EE.9080900@rogers.com> (raw)
In-Reply-To: <200307271205.59230.kernel@kolivas.org>

Update: 260-test2 with O10int has returned wine+galciv to freezing the 
whole computer on starting the game. The intro avi plays less than 1 
second and the machine freezes up. I can swtich from virtual terminals 
but not enter any input.

Con Kolivas wrote:
> On Sun, 27 Jul 2003 07:49, gaxt wrote:
> 
>>Kudos to CK
> 
> 
> Thanks.
> 
> 
>>In 2.4.21 galciv + wine was fine.
>>
>>In 2.4.21 + CK patches, galvic + wine would pause every 15 seconds or so
>>(maybe it was when little animations played).
>>
>>In 2.6.0-test1-mm2 (vanilla, or + 08) Galciv would stutter horribly and
>>freeze my machine in wine. It might run smoothly until I loaded a
>>nautilus window or something then stutters and loss of control of the
>>system.
>>
>>With 09, it is smooth as silk until I do something and then the video
>>playbacks can be choppy but the game (turn based strategy) seems to run
>>without the long pauses of 2.4.21 CK or 2.6.0 vanilla. I can switch
>>between apps and go back without any problem.
>>
>>09 seems to be a big improvement for whatever caused the stutter & die
>>problems in wine+galciv.
> 
> 
> Therein lies the problem with large MAX_SLEEP_AVG values. It may prevent 
> interactive tasks from becoming non interactive (which is the point), but if 
> an interactive task turns into a true cpu hog it can literally stall the 
> machine for seconds. Which is why the workaround in O*int that allow small 
> MSAs help.
> 
> Con
> 
> 



  reply	other threads:[~2003-07-28  4:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-26 21:49 WINE + Galciv + Con Kolivar's 09 patch to 2.6.0-test1-mm2 gaxt
2003-07-27  2:05 ` Con Kolivas
2003-07-28  5:17   ` gaxt [this message]
2003-07-28 21:40   ` gaxt
2003-07-28 21:39     ` Con Kolivas
2003-07-29  2:30       ` gaxt
2003-07-29  3:25         ` Con Kolivas
2003-07-29 12:48           ` WINE + Galciv + Con Kolivas's 011 patch to 2.6.0-test2 gaxt
2003-07-29 12:46             ` Con Kolivas
2003-07-29 20:59               ` gaxt
2003-07-29 21:09                 ` gaxt
2003-07-29 21:13                   ` gaxt
2003-08-08 20:04               ` 2.6.0-test2-mm5 + July Wine + Galciv gaxt
2003-08-12 14:42               ` WINE + Galciv + 2.6.0-test3-mm1-O15 gaxt
2003-08-12 14:40                 ` Con Kolivas
2003-08-12 18:24                   ` Mike Galbraith
2003-08-12 18:44                     ` Timothy Miller
2003-08-12 18:48                       ` Mike Galbraith
2003-08-13  3:34                     ` Con Kolivas
2003-08-13 12:47                       ` Mike Galbraith

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=3F24B1EE.9080900@rogers.com \
    --to=gaxt@rogers.com \
    --cc=kernel@kolivas.org \
    --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;
as well as URLs for NNTP newsgroup(s).