All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Fowler <linux-kernel@mlfowler.com>
To: ray-gmail@madrabbit.org
Cc: patrizio.bassi@gmail.com, "Kernel," <linux-kernel@vger.kernel.org>
Subject: Re: [BUG 2579] linux 2.6.* sound problems
Date: Mon, 31 Oct 2005 16:40:50 +0000	[thread overview]
Message-ID: <43664912.1060703@mlfowler.com> (raw)
In-Reply-To: <2c0942db0510310813p452b20b1q927e20376cd80ae0@mail.gmail.com>



Ray Lee wrote:
> On 10/31/05, Patrizio Bassi <patrizio.bassi@gmail.com> wrote:
> 
>>starting from 2.6.0 (2 years ago) i have the following bug.
> 
> 
> Well, the problem probably started before then.
> 
> 
>>link: http://bugzilla.kernel.org/show_bug.cgi?id=2579
> 
> 
>>Please fix that...2 years' bug!
> 
> 
> Speaking as a programmer, that's not a lot to go off of to find the
> bug. I think everyone would agree it's a bug, but we'll need more help
> from you.
> 
> 
>>fast summary:
>>when playing audio and using a bit the harddisk (i.e. md5sum of a 200mb
>>file) i hear noises, related to disk activity. more hd is used, more chicks
>>and ZZZZ noises happen.
> 

This to me sounds more like an interference issue, something I have seen 
on many laptops (I used to repair them in a previous incarnation). It is 
often referred to as "the 50Hz/60Hz hum" or the "ground loop" see any of 
these:

-http://www.pcmus.com/power-grounding.htm
-http://en.wikipedia.org/wiki/Ground_loop_%28electricity%29

-- 
Mike Fowler
Registered Linux user: 379787

"I could be a genius if I just put my mind to it, and I,
I could do anything, if only I could get 'round to it"
-PULP 'Glory Days'

  reply	other threads:[~2005-10-31 16:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 15:30 [BUG 2579] linux 2.6.* sound problems Patrizio Bassi
2005-10-31 16:13 ` Ray Lee
2005-10-31 16:40   ` Mike Fowler [this message]
2005-10-31 17:15 ` Lee Revell
2005-10-31 22:10 ` Tomasz Torcz
2005-11-02 11:20   ` Takashi Iwai
2005-11-02 11:36     ` Patrizio Bassi
     [not found] <53JVy-4yi-19@gated-at.bofh.it>
2005-10-31 16:43 ` Bodo Eggert
     [not found] ` <53Kyw-5Bt-53@gated-at.bofh.it>
     [not found]   ` <53L26-6dC-75@gated-at.bofh.it>
2005-10-31 16:59     ` Patrizio Bassi
2005-10-31 17:04   ` Patrizio Bassi
2005-10-31 17:27     ` Ray Lee
     [not found] ` <53Lus-73L-39@gated-at.bofh.it>
2005-10-31 19:38   ` Patrizio Bassi
     [not found] <53L1x-6dC-13@gated-at.bofh.it>
     [not found] ` <53L1x-6dC-11@gated-at.bofh.it>
2005-10-31 16:59   ` Patrizio Bassi
     [not found] ` <53LkE-6QU-5@gated-at.bofh.it>
     [not found]   ` <53LkW-6QU-49@gated-at.bofh.it>
     [not found]     ` <53LEq-7gr-7@gated-at.bofh.it>
2005-10-31 19:44       ` Patrizio Bassi
2005-10-31 23:12         ` Ondrej Zary
     [not found]         ` <4366A49F.3000101@rainbow-software.org>
2005-11-01  9:54           ` Patrizio Bassi
2005-11-23 16:22             ` Ard van Breemen
2005-11-23 19:46               ` Lee Revell
2005-11-23 20:05                 ` Patrizio Bassi
2005-11-23 20:22                   ` Lee Revell
2005-11-23 20:31                     ` Patrizio Bassi

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=43664912.1060703@mlfowler.com \
    --to=linux-kernel@mlfowler.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrizio.bassi@gmail.com \
    --cc=ray-gmail@madrabbit.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.