From: "Georg Nikodym" <georgn@somanetworks.com>
To: "Michael B. Trausch" <fd0man@crosswinds.net>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@redhat.com>,
Zack Brown <zab@redhat.com>
Subject: Re: Possible Bug: drivers/sound/maestro.c
Date: Fri, 26 Jan 2001 10:26:53 -0500 (EST) [thread overview]
Message-ID: <14961.38717.250220.501376@somanetworks.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101260220430.11818-100000@fd0man.accesstoledo.com>
In-Reply-To: <Pine.LNX.4.21.0101260220430.11818-100000@fd0man.accesstoledo.com>
>>>>> "MBT" == Michael B Trausch <fd0man@crosswinds.net> writes:
MBT> I've been using this driver and this hardware since I started
MBT> running Kernel 2.2.16. It _works_, however, whenever I have a
MBT> program that I compile that's especially large (the kernel,
MBT> glibc, etc.), or copy/move lots of files around, the driver
MBT> starts to fuzz lots of the sound going to the card - even after
MBT> the activity causing the load has stopped. It happens in both
MBT> the left and the right channel, and the only way to resolve it
MBT> is to kill the process with /dev/dsp open (typically mpg123),
MBT> and then start it again.
FWIW, I too was having this kind of problem. When I starting living
on 2.4.x kernels the problem went away. Also gone were sound dropping
out when I busied my machine with compiles things.
Of course, I'm omitting the irrelevant detail of the absence of the
pci_enable_dev() call 2.4.0-testX where X<12 which caused the driver
to not work at all.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-26 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 7:34 Michael B. Trausch
2001-01-26 15:26 ` Georg Nikodym [this message]
2001-01-26 17:47 ` Michael B. Trausch
2001-01-26 20:57 ` Barry K. Nathan
2001-01-26 21:11 ` Tom Sightler
2001-01-30 8:31 ` Zach Brown
2001-01-26 23:43 ` Michael B. Trausch
2001-01-26 23:47 ` Alan Cox
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=14961.38717.250220.501376@somanetworks.com \
--to=georgn@somanetworks.com \
--cc=alan@redhat.com \
--cc=fd0man@crosswinds.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zab@redhat.com \
/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®