From: "Samium Gromoff" <_deepfire@mail.ru>
To: chrisp@newmail.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: sound crashes in 2.4
Date: Fri, 24 Aug 2001 16:49:22 +0400 [thread overview]
Message-ID: <E15aGOo-00093V-00@f12.port.ru> (raw)
> Both 2.4.8 and 2.4.9 have this problem (these are the ones I tried).
> Btw on 2.2.x i get DMA (output) timeout errors (and broken sound).
just to clarify: does 2.4.7 hangs?
(for me it doesnt, but everything >= 2.4.8 does)
also as i already said, the sound isn`t clear:
there are little clicks here and there...
but i have an infinite trace(*). you - don`t.
(*) - in fact there are 3 traces.
first - quite short (1-1.5 screen)
second - 3-4 screens, and
third - infinite...
---
cheers,
Samium Gromoff
next reply other threads:[~2001-08-24 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-24 12:49 Samium Gromoff [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-24 11:42 sound crashes in 2.4 Samium Gromoff
2001-08-24 18:17 ` Chris Pockele
[not found] <no.id>
2001-08-20 16:33 ` Alan Cox
2001-08-20 19:24 ` Chris Pockele
2001-08-20 23:08 ` Frank Davis
2001-08-24 11:01 ` Chris Pockele
2001-08-20 16:17 Chris Pockele
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=E15aGOo-00093V-00@f12.port.ru \
--to=_deepfire@mail.ru \
--cc=chrisp@newmail.net \
--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).