public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David C. Hansen" <haveblue@us.ibm.com>
To: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] cs46xx: sound distortion after hours of use
Date: Tue, 15 Jan 2002 11:27:30 -0800	[thread overview]
Message-ID: <3C4482A2.8040903@us.ibm.com> (raw)
In-Reply-To: <200201151224.g0FCO8E06163@Port.imtp.ilyichevsk.odessa.ua> <20020115152000.GD13196@arthur.ubicom.tudelft.nl>

Erik Mouw wrote:

>On Tue, Jan 15, 2002 at 02:24:00PM -0200, Denis Vlasenko wrote:
>
>>I have noticed that after hours of palying mp3s thru my onboard audio
>>(I use cs46xx module) sound becomes distorted (high-pitch noise).
>>
>>Restarting xmms does not help.
>>
>>rmmod cs46xx; modprobe cs46xx fixes it.
>>
>Are you running a battery monitor or something similar? In that case it
>can cause the CPU to go into SMM with interrupts disabled to talk to
>the batteries and completely forget about servicing the audio IRQ
>thereby fscking up the sound. I had the same problems on my laptop and
>killing gnome_battery_applet fixed it.
>
I have the same problem, but very rarely.  I, too, use the 
rmmod/modprobe technique to fix it.  Have either of you found a way to 
excite the problem without waiting hours for it to happen?

--
Dave Hansen
haveblue@us.ibm.com


  reply	other threads:[~2002-01-15 19:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-15 16:24 [BUG] cs46xx: sound distortion after hours of use Denis Vlasenko
2002-01-15 15:20 ` Erik Mouw
2002-01-15 19:27   ` David C. Hansen [this message]
2002-01-15 20:24     ` Erik Mouw
     [not found]     ` <20020115153439.A413@davetop.uacdd.wvu.edu>
2002-01-15 20:42       ` David C. Hansen
2002-01-15 22:23         ` Bill Nottingham
2002-01-17  1:04         ` Andrew Kanaber
2002-01-24 15:27           ` Denis Vlasenko
2002-01-16  3:01     ` William Lee Irwin III

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=3C4482A2.8040903@us.ibm.com \
    --to=haveblue@us.ibm.com \
    --cc=J.A.K.Mouw@its.tudelft.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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