On Fri, Dec 5, 2014 at 10:48 AM, Dave Jones <da...@redhat.com> wrote:
>
> In the meantime, I rebooted into the same kernel, and ran trinity
> solely doing the lsetxattr syscalls.
Any particular reason for the lsetxattr guess? Just the last call
chain? I don't recognize it from the other traces, but maybe I just
didn't notice.
> The load was a bit lower, so I
> cranked up the number of child processes to 512, and then this
> happened..
Ugh. "dump_trace()" being broken and looping forever? I don't actually
believe it, because this isn't even on the exception stack (well, the
NMI dumper is, but that one worked fine - this is the "nested" dumping
of just the allocation call chain)
Smells like more random callchains to me. Unless this one is repeatable.
Limiting trinity to just lsetxattr is interesting. Did it make things
fail faster?
Linus
> [ 1611.747053] WARNING: CPU: 0 PID: 14810 at kernel/watchdog.c:265
> watchdog_overflow_callback+0xd5/0x120()
> [ 1611.747083] Watchdog detected hard LOCKUP on cpu 0
> [ 1611.747389] CPU: 0 PID: 14810 Comm: trinity-c304 Not tainted 3.16.0+ #114
> [ 1611.747544] Call Trace:
> [ remnoved NMI perf event stack trace ]
> [ 1611.753861] [<ffffffff810fee07>] is_module_text_address+0x17/0x50
> [ 1611.754734] [<ffffffff81092ab8>] __kernel_text_address+0x58/0x80
> [ 1611.755575] [<ffffffff81006b5f>] print_context_stack+0x8f/0x100
> [ 1611.756410] [<ffffffff81005540>] dump_trace+0x140/0x370
> [ 1611.758895] [<ffffffff810137cb>] save_stack_trace+0x2b/0x50
> [ 1611.759720] [<ffffffff811c29a0>] set_track+0x70/0x140
> [ 1611.760541] [<ffffffff8178d993>] alloc_debug_processing+0x92/0x118
> [ 1611.761366] [<ffffffff8178e5d6>] __slab_alloc+0x45f/0x56f
> [ 1611.765539] [<ffffffff811c6b26>] kmem_cache_alloc+0x1f6/0x270
> [ 1611.767183] [<ffffffff811e797f>] getname_flags+0x4f/0x1a0
> [ 1611.768004] [<ffffffff811ed7e5>] user_path_at_empty+0x45/0xc0
> [ 1611.772129] [<ffffffff811ed871>] user_path_at+0x11/0x20
> [ 1611.772959] [<ffffffff812040cb>] SyS_lsetxattr+0x4b/0xf0
> [ 1611.773783] [<ffffffff8179bc92>] system_call_fastpath+0x16/0x1b
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
