Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Apr 2012 08:43:30 +0930
From:      Matt Thyer <matt.thyer@gmail.com>
To:        Freddie Cash <fjwcash@gmail.com>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: 157k interrupts per second causing 60% CPU load on idle system
Message-ID:  <CACM2%2B-6o4D0=dohhHLONzF7_fs9tkgrC7vOFUcbA_RusMmZeBQ@mail.gmail.com>
In-Reply-To: <CACM2%2B-4_3p3-q74=PJMNbD65fiijf-9KYfzUTdEhsawwAQYRRw@mail.gmail.com>
References:  <CACM2%2B-46zHafjZo0O1dNNvEJm%2B2sUcYboBWwhJ8NxVhXyvpBZQ@mail.gmail.com> <4F6A67C0.7000909@sentex.net> <CACM2%2B-6BubOF1uWtXcBQyZqeiuqhvXazL9564CwN9uhJVNe2_w@mail.gmail.com> <4F6B3B46.4060105@sentex.net> <CACM2%2B-6J%2BkaV3aCudDNztDFefo602kTJZ-S99HB%2Bjhxe-tu5XA@mail.gmail.com> <CACM2%2B-7DrENh5ZBs-6vkSrH1szMqnYKi2acmzByAOgXdZvHZMg@mail.gmail.com> <CAOjFWZ5nhT5NPLnn_Bh7oDa0fC5KbfDE1aHA_e%2BX9iebxkLEaA@mail.gmail.com> <CACM2%2B-5ujs-kz9SNV7jwEU4Df5un5H=%2BqY%2B3Z0WSxj=7v8f8uQ@mail.gmail.com> <CACM2%2B-4_3p3-q74=PJMNbD65fiijf-9KYfzUTdEhsawwAQYRRw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 7, 2012 2:38 PM, "Matt Thyer" <matt.thyer@gmail.com> wrote:
>
> On 7 April 2012 14:31, Matt Thyer <matt.thyer@gmail.com> wrote:
>> Since moving the SATA 3 disk to the onboard Intel SATA 2 controller I'm
no longer having that disk evicted from the raidz2 pool with write errors
and I thought that the high interrupt rate issue had also been solved but
it's back again.
>>
>> This is on 8-STABLE at revision 230921 (before the new driver hit
8-STABLE).
>>
>> So now I need to go back to trying to determine what the cause is.
>>
> vmstat -i has shown that the issue was on irq 16.
>
> Unfortunately there seems to be a lot of things on irq 16:
>
> $  dmesg | grep "irq 16"
>
> pcib1: <PCI-PCI bridge> irq 16 at device 1.0 on pci0
> mps0: <LSI SAS2008> port 0xee00-0xeeff mem
0xfbdfc000-0xfbdfffff,0xfbd80000-0xfbdbffff irq 16 at device 0.0 on pci1
> vgapci0: <VGA-compatible display> port 0xff00-0xff07 mem
0xfb400000-0xfb7fffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
> uhci0: <UHCI (generic) USB controller> port 0xfe00-0xfe1f irq 16 at
device 26.0 on pci0
> pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
> pcib3: <ACPI PCI-PCI bridge> irq 16 at device 28.4 on pci0
> atapci0: <JMicron JMB368 UDMA133 controller> port
0xdf00-0xdf07,0xde00-0xde03,0xdd00-0xdd07,0xdc00-0xdc03,0xdb00-0xdb0f irq
16 at device 0.0 on pci3
>
> Any idea how to isolate which bit of hardware could be triggering the
interrupts ?
>
> Unfortunately the only device I could remove would be the SuperMicro
AOC-USAS2-L8i (so yes I could eliminate that).
>
> My biggest problem right now is not knowing how to trigger the issue.
>
> At this stage I'm going to upgrade to 9-STABLE and see if it returns.

The problem does not occur with 9-STABLE.

Who knows what the problem was ? USB maybe ?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACM2%2B-6o4D0=dohhHLONzF7_fs9tkgrC7vOFUcbA_RusMmZeBQ>