game "Knights and Merchants" deadlocks

[Joris Huizer]

Hello,

I have this question: I have a game called "Knights and Merchants" which 
  I sometimes play; I find it deadlocks each time after playing for an 
hour or so
it seems it isn't a complete deadlock, sometimes some of sound comes 
through between intervals of minutes or so; harddisk activity seems 
extreme - the light is burning constantly.
I then usually decide to kill the program; as it opens fullscreen I 
can't get to the xterm that launched it, so I try to get to a console;
The system is so slow that it takes some time to get to a console 
<ctrl-alt-f1>, and login in may time out a few times before finaly 
getting in (the cure to that one is simple: login before starting the 
game...) - then it takes another minute or so to run ps and kill the 
wine process

is there a way to find what is causing the deadlock? I can log the 
output wine gives using `script`, but as deadlocks only occur after a 
lot of time running the game with lots of logging active would be a pain

will log the output at least next time I play; for now, has somebody 
ideas how to log without getting major slowdown (otherwise there's no 
playing in it)?

thanks,

Joris

[Jesse Allen]

On 2/4/06, Joris Huizer  wrote:
> Hello,
>
> I have this question: I have a game called "Knights and Merchants" which
>   I sometimes play; I find it deadlocks each time after playing for an
> hour or so
> it seems it isn't a complete deadlock, sometimes some of sound comes
> through between intervals of minutes or so; harddisk activity seems
> extreme - the light is burning constantly.
> I then usually decide to kill the program; as it opens fullscreen I
> can't get to the xterm that launched it, so I try to get to a console;
> The system is so slow that it takes some time to get to a console
> <ctrl-alt-f1>, and login in may time out a few times before finaly
> getting in (the cure to that one is simple: login before starting the
> game...) - then it takes another minute or so to run ps and kill the
> wine process
>
> is there a way to find what is causing the deadlock? I can log the
> output wine gives using `script`, but as deadlocks only occur after a
> lot of time running the game with lots of logging active would be a pain
>
> will log the output at least next time I play; for now, has somebody
> ideas how to log without getting major slowdown (otherwise there's no
> playing in it)?
>
> thanks,
>
> Joris

If you could tell us your sound module name and which wine sound
driver you use that could be helpful.  There are a variety of sound
problems out there.

Jesse

[Joris Huizer]

Jesse Allen wrote:
> On 2/4/06, Joris Huizer  wrote:
>
> If you could tell us your sound module name and which wine sound
> driver you use that could be helpful.  There are a variety of sound
> problems out there.
>
> Jesse

I'm running alsa with oss emulation - I think wine is using the oss 
interface (just ran winecfg, it says no audio driver is selected in 
registry, and it assumes it should run oss)

[Jesse Allen]

On 2/5/06, Joris Huizer  wrote:
> I'm running alsa with oss emulation - I think wine is using the oss
> interface (just ran winecfg, it says no audio driver is selected in
> registry, and it assumes it should run oss)

And what sound module?  (snd_intel8x0, snd_cmipci...)

[Joris Huizer]

Jesse Allen wrote:
> On 2/5/06, Joris Huizer  wrote:
> > I'm running alsa with oss emulation - I think wine is using the oss
> > interface (just ran winecfg, it says no audio driver is selected in
> > registry, and it assumes it should run oss)
>
> And what sound module?  (snd_intel8x0, snd_cmipci...)

Sorry I don't really know what specs you need;
the sound module is 'snd_emu10k1'
[12:28:27]jorishuizer@debian:~$ lsmod|grep snd
snd_emu10k1            76616  0
snd_rawmidi            18628  1 snd_emu10k1
snd_pcm_oss            44264  0
snd_mixer_oss          14336  1 snd_pcm_oss
snd_pcm                75880  2 snd_emu10k1,snd_pcm_oss
snd_timer              19268  1 snd_pcm
snd_seq_device          5928  2 snd_emu10k1,snd_rawmidi
snd_ac97_codec         57604  1 snd_emu10k1
snd_page_alloc          8264  2 snd_emu10k1,snd_pcm
snd_util_mem            3008  1 snd_emu10k1
snd_hwdep               6436  1 snd_emu10k1
snd                    41732  10 
snd_emu10k1,snd_rawmidi,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_seq_device,snd_ac97_codec,snd_util_mem,snd_hwdep
soundcore               6656  1 snd

/usr/bin/lspci gives these lines on the sound card:
0000:00:07.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 
(rev 08)
0000:00:07.1 Input device controller: Creative Labs SB Live! MIDI/Game 
Port (rev 08)

are there more commands to run to get additional information?

regards,

Joris