public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "Robert M. Stockmann" <stock@stokkie.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata, Sound on same IRQ : flaky sound
Date: Wed, 27 Aug 2008 20:59:35 -0400	[thread overview]
Message-ID: <48B5F877.8030506@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0808280147230.1242-100000@hubble.stokkie.net>

Robert M. Stockmann wrote:
> Hi,
> 
> I have a couple of AMD64 machines with onboard sound devices running 
> and they all have one thing in common : flaky sound when one is 
> doing some heavy disk I/O on the SATA disks. Interesting enough 
> /proc/interrupts shows that libata is using the same IRQ as the sound 
> devices :
> 
> model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 6000+
> stepping        : 3
> cpu MHz         : 3014.679
> cache size      : 1024 KB
> 
> # cat /proc/interrupts 
>            CPU0       CPU1       
>   0:      55869  154467838    IO-APIC-edge  timer
>   8:          0          0    IO-APIC-edge  rtc
>   9:          0          0   IO-APIC-level  acpi
>  16:       1453     499686   IO-APIC-level  libata, NVidia CK8S
>  17:          0          0   IO-APIC-level  ehci_hcd:usb1
>  18:      27633   69978987   IO-APIC-level  eth0
> NMI:      10718      12112 
> LOC:  154533874  154533852 
> ERR:          0
> MIS:          0

What is the behavior of a recent kernel?

Is your SATA interface set to legacy mode in BIOS?

	Jeff



  reply	other threads:[~2008-08-28  0:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  0:06 libata, Sound on same IRQ : flaky sound Robert M. Stockmann
2008-08-28  0:59 ` Jeff Garzik [this message]
2008-08-28  1:30   ` Robert M. Stockmann
2008-08-28  7:57     ` el es
2008-08-28 16:33     ` James Ausmus
     [not found] <fa.t59JCw5e/IAg/3vXyG2sheD1AnE@ifi.uio.no>
2008-08-28 14:41 ` Robert Hancock
2008-08-28 17:27   ` Robert M. Stockmann
2008-08-29 12:57     ` Clemens Ladisch

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=48B5F877.8030506@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stock@stokkie.net \
    /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