public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Sound-related hard-locking
Date: Thu, 12 Dec 2002 20:56:56 +0300	[thread overview]
Message-ID: <3DF8CDE8.4030306@yahoo.com> (raw)

Hello.

J. Solomon Kostelnik wrote:
> But last night the same thing happened when I was playing an
> MP3 with XMMS and then booted XDOS (without midid running). 
> As soon as the XDOS window opened, my machine hard-locked.
Hmm, doesn't look dosemu-related at a
first glance.

> vanilla 2.4.18 kernel
This may be a problem. Try 2.4.20 as
all the older kernels were easy to
lock up by dosemu, which is now fixed.

> Maestro 2E.
And what about video? It was reported
that xdos crashes X sometimes on some
video boards. Try running console
dosemu and see if the problem is still
there (apply the post-less video patch
at first).

> Is there a way I can log this before it crashes and get any meaningful
> data before it happens?
Try ALSA drivers with OSS emulation.
Maybe it is just an ESS OSS driver buggy
and the current dosemu sound code is
extremely evil to the underlaying drivers
and exposes all of their hidden bugs.
It locks up the Aureal drivers on my
machine after some minutes of playing,
but as that drivers are proprietary, this
can't be fixed.
Another usefull test would be to try
dosemu with a pc-speaker OSS driver. If
the problem goes away by this, then it
is definitely a problem of your OSS driver.
Because even if the dosemu sound code
is buggy, this doesn't excuse a kernel
lock-ups.


             reply	other threads:[~2002-12-12 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12 17:56 Stas Sergeev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-12 16:12 Sound-related hard-locking J. Solomon Kostelnik

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=3DF8CDE8.4030306@yahoo.com \
    --to=stssppnn@yahoo.com \
    --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