All of lore.kernel.org
 help / color / mirror / Atom feed
From: Victor Julien <v.p.p.julien@let.rug.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.3+ sound distortion
Date: Sat, 21 Apr 2001 23:07:23 +0200	[thread overview]
Message-ID: <01042123072300.00453@victor> (raw)
In-Reply-To: <Pine.LNX.4.05.10104211159030.5218-100000@cosmic.nrg.org> <01042121403000.00436@victor> <20010421225205.B2615@arthur.ubicom.tudelft.nl>
In-Reply-To: <20010421225205.B2615@arthur.ubicom.tudelft.nl>

I don't use APM monitors. The noise is more frequent than once every few 
seconds. I've tried to reproduce the noise using cpu-intensive programs other 
than seti@home and i failed. I tried compiling a kernel together with heavy 
calculations in The Gimp, but it didn't produce the noise. Could it be a 
problem only triggerd by seti? Is there something special about seti?


Victor Julien


Please enter my email-adress in the CC.


> On Sat, Apr 21, 2001 at 09:40:30PM +0200, Victor Julien wrote:
> > That did not help. The distortion is no stuttering, but noise in the
> > music. It's not specific to xmms, freeamp and xine also have the noise.
> > The noise reminds me of years ago when my father used a electric shaver
> > witch gave noise in the sound of my radio. Maybe that can give you an
> > idea about the sort of noise.
> >
> > The changelog of 2.4.3 said that there were via-chipset-fixes undone,
> > could this be a problem of my chipset?
>
> Possible. Another thing to check is if you started using an APM
> monitoring program, like the GNOME battery_applet which reads /proc/apm
> every couple of seconds. With every read of /proc/apm the APM driver
> calls the APM BIOS, which on some systems runs quite long with
> interrupts disabled. On my laptop this results in exactly the noise you
> described.
>
>
> Erik

  reply	other threads:[~2001-04-21 21:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-21 16:04 2.4.3+ sound distortion Victor Julien
2001-04-21 19:05 ` Nigel Gamble
2001-04-21 19:40   ` Victor Julien
2001-04-21 20:52     ` Erik Mouw
2001-04-21 21:07       ` Victor Julien [this message]
2001-04-21 23:05       ` 2.4.3-pre3+ " Victor Julien
2001-04-21 23:15 ` 2.4.3+ " Alan Cox
2001-04-21 23:31   ` Victor Julien
2001-04-22  7:55   ` Marcel J.E. Mol
2001-04-22 12:17     ` Alan Cox
2001-04-22 13:46 ` Mike Castle
2001-04-23  3:08   ` David
  -- strict thread matches above, loose matches on Subject: below --
2001-04-22 17:47 Victor Julien
     [not found] ` <20010422110902.C1093@ulthar.internal.mclure.org>
2001-04-22 18:37   ` Victor Julien
2001-04-22 18:55     ` Alan Cox
2001-04-22 18:53 ` Alan Cox
2001-04-23 15:01 Woller, Thomas
2002-03-06  5:08 David Ford
2002-03-06 16:43 Woller, Thomas

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=01042123072300.00453@victor \
    --to=v.p.p.julien@let.rug.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.