All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrizio Bassi <patrizio.bassi@gmail.com>
To: Ray Lee <ray-lk@madrabbit.org>,
	"Kernel, " <linux-kernel@vger.kernel.org>
Subject: Re: [BUG 2579] linux 2.6.* sound problems
Date: Mon, 31 Oct 2005 20:44:06 +0100	[thread overview]
Message-ID: <43667406.9070104@gmail.com> (raw)
In-Reply-To: <53LEq-7gr-7@gated-at.bofh.it>

Ray Lee ha scritto:
> On Mon, 2005-10-31 at 18:04 +0100, Patrizio Bassi 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.
>>>>link: http://bugzilla.kernel.org/show_bug.cgi?id=2579
> 
> 
>>>>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
>>
>>actually i don't have any more 2.4 kernels due to some problems with
>>other devices.
> 
> 
> I'd suggest installing one and at minimum booting it to single user mode
> to run some tests. If 2.4 works great, then it's worthwhile to find out
> what it's getting right that 2.6 is getting wrong. The only way to find
> that out is to compare the two.
> 
> 
>>however i remember i checked that and it was pretty the same
> 
> 
> Well, I barely trust my own memory in general, so I'd suggest that we
> check. Humor me. This is the standard way to find out where a problem
> is. Check the good, check the bad, compare the two.
> 
> 
>>kernel is perfectly tuned.
> 
> 
> <?> How do you know?
> 
> 
>>i notice that with dma disabled it works much better.
>>problem happens with hda/hdc, so both ide channels.
> 
> 
>>hdparm -i /dev/hda
> 
> 
> It'd be more useful to see hdparm 2.4 versus 2.6, so we can see if
> there's any difference. If we don't see the 2.4 version, then we can't
> tell if this is something worthwhile to tweak. Does that make sense? If
> they are set the same between both 2.4 and 2.6, then we know we can rule
> the hard drive settings out as the source of the problem.
> 
> 
>> BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=off
>> BuffType=DualPortCache, BuffSize=1821kB, MaxMultSect=16, MultSect=off
> 
> 
> MultiSect is off on both, can you turn that on and see if that makes a
> difference? Without multisect set on (and set to 16), your hard drives
> are transferring one sector per interrupt, instead of a max of 16. This
> makes for a lot more interrupts on the system, and might be the source
> of the problem.
> 
> If that doesn't change anything, you may also try what Mike Fowler
> hinted at, and recompile your kernel with Hz set to 100 instead of the
> default 250. As well as trying the RT patchset and seeing if that shows
> any sources of problems.
> 
> Ray
> 

2.4 is hard to try for me....i'll try if i can...

i set 16 to sectors setting, but nothing changed, no real changes.

i'll recompile tomorrow -git4 with 100Hz option to check if timer can
help me



  parent reply	other threads:[~2005-10-31 19:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53L1x-6dC-13@gated-at.bofh.it>
     [not found] ` <53L1x-6dC-11@gated-at.bofh.it>
2005-10-31 16:59   ` [BUG 2579] linux 2.6.* sound problems 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 [this message]
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
     [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
2005-10-31 15:30 Patrizio Bassi
2005-10-31 16:13 ` Ray Lee
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

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