On Friday, May 06, 2011 11:36:52 am Jack Vogel wrote:
> I don't see why you are blaming em, you can see its on MSIX vectors
> that are NOT storming, its something with USB as noted. Trying to
> disable em from using MSIX is in exactly the wrong direction IMHO.
In the past Intel host bridges have e
Hi Jack,
On Friday 06 May 2011 17:36:52 Jack Vogel wrote:
> On Fri, May 6, 2011 at 8:32 AM, Daan Vreeken wrote:
> > Hi Steven,
> >
> > On Friday 06 May 2011 17:20:15 Steven Hartland wrote:
> > > From: "Daan Vreeken"
> > >
> > > > # vmstat -i
> > > > interrupt total
On 5/6/2011 11:02 AM, Daan Vreeken wrote:
> One core is spending half it's time handling interrupts.
> /var/log/messages doesn't show any new message since the storm
> started. "vmstat -i" now shows :
>
> # vmstat -i
> interrupt total rate
> irq3:
I don't see why you are blaming em, you can see its on MSIX vectors
that are NOT storming, its something with USB as noted. Trying to
disable em from using MSIX is in exactly the wrong direction IMHO.
Jack
On Fri, May 6, 2011 at 8:32 AM, Daan Vreeken wrote:
> Hi Steven,
>
> On Friday 06 May 20
Hi Steven,
On Friday 06 May 2011 17:20:15 Steven Hartland wrote:
> From: "Daan Vreeken"
>
> > # vmstat -i
> > interrupt total rate
> > irq3: uart1 917384 63
> > --> irq16: ehci0 809547235 55608
>
> Have you tried
- Original Message -
From: "Daan Vreeken"
# vmstat -i
interrupt total rate
irq3: uart1 917384 63
--> irq16: ehci0 809547235 55608
Have you tried removing USB from the kernel?
USB seems to be a common
On Thursday 05 May 2011 22:22:15 Jack Vogel wrote:
> On Thu, May 5, 2011 at 1:17 PM, Daan Vreeken wrote:
> > Hi Peter,
> >
> > On Thursday 05 May 2011 21:28:02 Peter Jeremy wrote:
> > > On 2011-May-05 13:22:59 +0200, Daan Vreeken wrote:
> > > >Not yet. I'll reboot the machine later today when I h
On 2011-May-05 13:22:59 +0200, Daan Vreeken wrote:
>Not yet. I'll reboot the machine later today when I have physical access to it
>to check the BIOS version. I'll keep you informed as soon as I get another
>storm going.
Depending on the quality of your BIOS (competence of the vendor), you
migh
Cool, thanks for the update! Good luck.
Jack
On Thu, May 5, 2011 at 1:17 PM, Daan Vreeken wrote:
> Hi Peter,
>
> On Thursday 05 May 2011 21:28:02 Peter Jeremy wrote:
> > On 2011-May-05 13:22:59 +0200, Daan Vreeken wrote:
> > >Not yet. I'll reboot the machine later today when I have physical a
Hi Peter,
On Thursday 05 May 2011 21:28:02 Peter Jeremy wrote:
> On 2011-May-05 13:22:59 +0200, Daan Vreeken wrote:
> >Not yet. I'll reboot the machine later today when I have physical access
> > to it to check the BIOS version. I'll keep you informed as soon as I get
> > another storm going.
>
>
Hi Jack,
On Thursday 05 May 2011 02:25:39 Jack Vogel wrote:
> OK, but the reason you see the multiple cases of irq 16 is that's the
> bridge,
> once you are using MSIX, as vmstat shows, its using other vectors.
>
> Can you capture the messages file with the actual storm happening?
I'll do that as
OK, but the reason you see the multiple cases of irq 16 is that's the
bridge,
once you are using MSIX, as vmstat shows, its using other vectors.
Can you capture the messages file with the actual storm happening?
I noticed some complaints about checksums in the dmesg, have you
checked on BIOS upgr
On Thursday 05 May 2011 00:15:43 you wrote:
> This all looks completely kosher, what IRQ is the storm on??
IRQ 16. Further down this email there is a list of devices that share the IRQ
according to 'dmesg'.
> On Wed, May 4, 2011 at 3:04 PM, Daan Vreeken wrote:
> > Hi,
> >
> > On Wednesday 04
2011/5/4 Jack Vogel :
> This is the second report in a matter of a week perhaps about a problematic
> motherboard, I would like to know who makes them.
Just for the record, the motherboard with which I had problems (I
guess my problem is here referred) is VIA EPIA SN1. It's nothing
new, and pr
Right, it was you Wiktor :) Oh, so yours is sort of a special case.
Thanks,
Jack
On Wed, May 4, 2011 at 3:27 PM, Wiktor Niesiobedzki wrote:
> 2011/5/4 Jack Vogel :
> > This is the second report in a matter of a week perhaps about a
> problematic
> > motherboard, I would like to know who make
This all looks completely kosher, what IRQ is the storm on??
Jack
On Wed, May 4, 2011 at 3:04 PM, Daan Vreeken wrote:
> Hi,
>
> On Wednesday 04 May 2011 20:47:32 Jack Vogel wrote:
> > Will you please set it back to a default and then boot and capture the
> > message for me?
>
> No problem. He
Hi,
On Wednesday 04 May 2011 20:47:32 Jack Vogel wrote:
> Will you please set it back to a default and then boot and capture the
> message for me?
No problem. Here's the output with MSI/MSIX enabled :
http://vehosting.nl/pub_diffs/dmesg_plantje2_with_msix_2011_05_04.txt
I've also added t
Will you please set it back to a default and then boot and capture the
message for me?
Thank you,
Jack
On Wed, May 4, 2011 at 11:19 AM, Daan Vreeken wrote:
> Hi Jack,
>
> Wednesday 04 May 2011 19:46:05 Jack Vogel wrote:
> > Who makes your motherboard? The problem you are having is that MSIX A
Hi Jack,
Wednesday 04 May 2011 19:46:05 Jack Vogel wrote:
> Who makes your motherboard? The problem you are having is that MSIX AND
> MSI are both failing as em0 comes up, so it falls back to Legacy interrupt
> mode,
> and must be having some issue with sharing the line, causing the storm.
The mo
Who makes your motherboard? The problem you are having is that MSIX AND
MSI are both failing as em0 comes up, so it falls back to Legacy interrupt
mode,
and must be having some issue with sharing the line, causing the storm.
This is the second report in a matter of a week perhaps about a problemat
Hi All,
I've just updated a machine to -current (r221321) and since then I'm seeing an
interrupt storm on irq 16. The storm goes away when I disable MSI/MSIX with
the following lines in "loader.conf" :
hw.pci.enable_msix="0"
hw.pci.enable_msi="0"
According to "dmesg" the follow
21 matches
Mail list logo
