From: Hermann Himmelbauer <dusty@violin.dyndns.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Interrupted sound with 2.4.4-ac6
Date: Tue, 15 May 2001 23:22:36 +0200 [thread overview]
Message-ID: <3B019E1C.9D9CE388@violin.dyndns.org> (raw)
Hi,
At first I have to apologize if you get this mail double, I sent it
yesterday once but I did not get it from the list and it seems it
vanished for some reason, so I try it a second time:
I built a nice mp3 player out of a AMD 486-DX133 and a soundblaster
es1371. I always used 2.2.16 and it worked properly. Due to several
reasons I want to switch to 2.4, so I tried my luck with 2.4.4-ac6.
Basically it works but the sound gets interrupted (around 0.5 - 5seconds
silence) from time to time although the system is around 44% idle. This
never happened with 2.2.16. These interrupts are not periodically,
sometimes there are none for a minute, sometimes there are even
interrupts around 5 seconds long.
I have to state that the data comes from an nfs-mounted directory -
perhaps this is a reason? (There is no network load).
Another interesting thing is that during those interrupts the processor
usage of mpg123 decreases from 53% to around 20%, so it looks as if
mpg123 can either not get data or not output data.
Do you have any clues? Are there perhaps some kernel parameters to tune
(buffer size, dma...)?
Best Regards,
Hermann
--
,_,
(O,O) "There is more to life than increasing its speed."
( ) -- Gandhi
-"-"--------------------------------------------------------------
next reply other threads:[~2001-05-15 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 21:22 Hermann Himmelbauer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-14 22:05 LANANA: To Pending Device Number Registrants Alexander Viro
2001-05-14 23:01 ` Interrupted sound with 2.4.4-ac6 Hermann Himmelbauer
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=3B019E1C.9D9CE388@violin.dyndns.org \
--to=dusty@violin.dyndns.org \
--cc=dusty@strike.wu-wien.ac.at \
--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
all inboxes | Powered by JetHome®