From: Nicholas Knight <tegeran@home.com>
To: "Samium Gromoff" <_deepfire@mail.ru>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.8/2.4.8-ac7 sound crashes
Date: Mon, 20 Aug 2001 06:40:58 -0700 [thread overview]
Message-ID: <01082006405800.00227@c779218-a> (raw)
In-Reply-To: <E15YlfQ-000EZS-00@f5.mail.ru>
In-Reply-To: <E15YlfQ-000EZS-00@f5.mail.ru>
On Monday 20 August 2001 02:48 am, Samium Gromoff wrote:
> I do not know if this problem is reported already,
> since i read lkml thru web-archive, with accompanying
> update delays.
>
> 2.4.8 dies after ~1/2 minute of mpg123 playback,
> with tty switching freeze, and typing out
> continuously (i`d say infinitely) call trace.
>
> ac7 acts this way too, but before death
> sound stalls *some* times, i then each time restart
> the proggie which emits it. This pattern survives
> 4-5 stalls, after which - final trace dump.
>
> gcc-2.95.3, sb16 - genuine, vanilla ac7, vanilla
> 2.4.8.
no problems like this for me.
GCC 2.95.3, SB16 "Value" (don't ask me why they named it that, it's just
like a regular SB16 ISA as far as I can tell), vanilla 2.4.8, mpg123 is
version 0.59r, says june 15th 1999, I'll see if there's a newer version.
I also use XMMS and it works fine.
What motherboard are you using? is the SB16 PCI or ISA? if it's ISA do
you have persistant DMA buffers enabled in the kernel? (not sure if that
would cause this or not)
next prev parent reply other threads:[~2001-08-20 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-20 9:48 2.4.8/2.4.8-ac7 sound crashes Samium Gromoff
2001-08-20 13:40 ` Nicholas Knight [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-20 14:28 Samium Gromoff
2001-08-20 14:32 ` Oleg Drokin
2001-08-20 14:49 ` Justin A
2001-08-20 15:27 Samium Gromoff
2001-08-21 13:17 Samium Gromoff
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=01082006405800.00227@c779218-a \
--to=tegeran@home.com \
--cc=_deepfire@mail.ru \
--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