From: Stan Hoeppner <stan@hardwarefreak.com>
To: Stirling Westrup <swestrup@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: IRQ issues with multiple SiI3114's on Kernel 3.2
Date: Fri, 27 Jul 2012 12:24:52 -0500 [thread overview]
Message-ID: <5012CEE4.8040306@hardwarefreak.com> (raw)
In-Reply-To: <CAJt7KB8-yPm7RX8doKw1WjYwxfvVQ8Af7GNmu=QVsM_sAtYKiQ@mail.gmail.com>
On 7/27/2012 11:40 AM, Stirling Westrup wrote:
> I recently purchased a large system for use as a backup server for a
> pair of small businesses. It contains a boot drive plus 10 more
> storage drives. Despite having three onboard SATA controllers, the
> motherboard didn't have enough SATA connectors for all the drives, so
> I installed a pair of identical SiI3114 raid cards to handle the extra
> connections. It has a Sandy Bridge chipset, so I installed a 3.2
> kernel.
>
> # uname -a
> Linux ttt 3.2.0-0.bpo.2-amd64 #1 SMP Fri Jun 29 20:42:29 UTC 2012
> x86_64 GNU/Linux
...
> Okay, enough background. Here's the issue: I had no trouble building
> and sync'ing the first array, but when I try to sync the second array,
> I always get the following dmesg an hour or so into the process:
>
> irq 19: nobody cared (try booting with the "irqpoll" option)
> [ 346.120572] Pid: 1100, comm: md1_resync Not tainted
3.2.0-0.bpo.2-amd64 #1
> [ 346.120573] Call Trace:
> ...
> [ 346.120697] handlers:
> [ 346.120699] [<ffffffffa00479e0>] ahci_interrupt
> [ 346.120702] [<ffffffffa02f17ec>] sil_interrupt
> [ 346.120703] Disabling IRQ #19
> [ 346.122145] sched: RT throttling activated
...
> From this point onward syncing drops to a tiny fraction of its
> previous speed. I've tried booting with 'irqpoll' as the error message
> suggests, but it has had no effect. I'm really not sure if there is a
> conflict between my two SiI3114's or between the SiI's and the Marvell
> controller (although I've never had an issue with Marvell in the
> past), nor how to go about diagnosing or fixing this. I'll include a
> full dmesg dump below, as well as my currently loaded modules. If
> anyone wants any further info, just ask.
Have you tried irqbalance to spread the interrupts across cores/cache
domains? https://irqbalance.org/documentation.html
Dual/quad socket machines benefit more than a single socket machine, but
the latter can still benefit if the cache hierarchy is appropriate.
~$ aptitude install irqbalance
No guarantees this will fix your problem but it's worth a shot. Takes a
few seconds to install, and it won't cause any negative effects, even if
it yields no positive effects.
--
Stan
next prev parent reply other threads:[~2012-07-27 17:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 16:40 IRQ issues with multiple SiI3114's on Kernel 3.2 Stirling Westrup
2012-07-27 17:24 ` Stan Hoeppner [this message]
2012-07-27 22:14 ` Stirling Westrup
2012-07-28 2:20 ` Stirling Westrup
2012-07-28 9:10 ` Stan Hoeppner
2012-07-28 17:48 ` Stirling Westrup
2012-07-28 23:41 ` Stirling Westrup
2012-07-29 9:24 ` Stan Hoeppner
2012-07-29 19:00 ` Stirling Westrup
2012-07-29 20:17 ` Stan Hoeppner
2012-08-01 23:43 ` Stirling Westrup
2012-08-02 1:08 ` Stan Hoeppner
2012-07-28 18:19 ` Stirling Westrup
2012-07-28 18:45 ` Stirling Westrup
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=5012CEE4.8040306@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-ide@vger.kernel.org \
--cc=swestrup@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).