mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ray Lee <madrabbit@gmail.com>
To: patrizio.bassi@gmail.com
Cc: "Kernel," <linux-kernel@vger.kernel.org>
Subject: Re: [BUG 2579] linux 2.6.* sound problems
Date: Mon, 31 Oct 2005 08:13:12 -0800	[thread overview]
Message-ID: <2c0942db0510310813p452b20b1q927e20376cd80ae0@mail.gmail.com> (raw)
In-Reply-To: <436638A8.3000604@gmail.com>

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.

Does hdparm -i (or -I) show differences between the 2.4 kernels and
2.6? 2.6 has new IDE drivers, and so perhaps your system isn't using
the best driver any more.

You may also want to compare lspci -vv of your IDE controller and
sound card between 2.4 and 2.6, and see if there are any differences.

No guarantees, but this is where you'd start.

> Ready to test any patch/solution.

Try that. If nothing obvious appears in the examination, you may want
to try the 2.6.14-rt1 patchset from Ingo Molnar. It's designed to
reduce latency in the kernel, but also has a latency tracer that may
be particularly useful for your problem. (Assuming it's a latency
issue, and not a hardware misconfiguration due to 2.6 doing something
wrong.)

Ray

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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 15:30 Patrizio Bassi
2005-10-31 16:13 ` Ray Lee [this message]
2005-10-31 16:40   ` Mike Fowler
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=2c0942db0510310813p452b20b1q927e20376cd80ae0@mail.gmail.com \
    --to=madrabbit@gmail.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 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®