lkml.org 
[lkml]   [2015]   [Apr]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: smp_call_function_single lockups
On Tue, Mar 31, 2015 at 04:07:32PM -0700, Linus Torvalds wrote:
> On Tue, Mar 31, 2015 at 3:23 PM, Chris J Arges
> <chris.j.arges@canonical.com> wrote:
> >
> > I had a few runs with your patch plus modifications, and got the following
> > results (modified patch inlined below):
>
> Ok, thanks.
>
> > [ 14.423916] ack_APIC_irq: vector = d1, irq = ffffffff
> > [ 176.060005] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [qemu-system-x86:1630]
> >
> > [ 17.995298] ack_APIC_irq: vector = d1, irq = ffffffff
> > [ 182.993828] ack_APIC_irq: vector = e1, irq = ffffffff
> > [ 202.919691] ack_APIC_irq: vector = 22, irq = ffffffff
> > [ 484.132006] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [qemu-system-x86:1586]
> >
> > [ 15.592032] ack_APIC_irq: vector = d1, irq = ffffffff
> > [ 304.993490] ack_APIC_irq: vector = e1, irq = ffffffff
> > [ 315.174755] ack_APIC_irq: vector = 22, irq = ffffffff
> > [ 360.108007] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [ksmd:26]
> .. snip snip ..
>
> So yeah, that's VECTOR_UNDEFINED, and while it could happen as part of
> irq setup, I'm not seeing that being something that your load should
> trigger.
>
> It could also obviously just be the vector being somehow corrupted,
> either due to crazy hardware or software.
>
> But quite frankly, the most likely reason is that whole irq vector movement.
>
> Especially since it sounds from your other email that when you apply
> Ingo's patches, the ack_APIC_irq warnings go away. Is that correct? Or
> did you just grep for "move" in the messages?
>
> If you do get both movement messages (from Info's patch) _and_ the
> ack_APIC_irq warnings (from mine), it would be interesting to see if
> the vectors line up somehow..
>
> Linus
>

Linus,

I included the full patch in reply to Ingo's email, and when running with that
I no longer get the ack_APIC_irq WARNs.

My next homework assignments are:
- Testing with irqbalance disabled
- Testing w/ the appropriate dump_stack() in Ingo's patch
- L0 testing

Thanks,
--chris




\
 
 \ /
  Last update: 2015-04-01 17:01    [W:0.098 / U:16.904 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site