[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141204145631.GA22794@redhat.com>
Date: Thu, 4 Dec 2014 09:56:31 -0500
From: Dave Jones <davej@...hat.com>
To: Will Deacon <will.deacon@....com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
"Kirill A. Shutemov" <kirill@...temov.name>,
Tejun Heo <tj@...nel.org>,
Andy Lutomirski <luto@...capital.net>,
Don Zickus <dzickus@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Linux Kernel <linux-kernel@...r.kernel.org>,
the arch/x86 maintainers <x86@...nel.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: frequent lockups in 3.18rc4
On Thu, Dec 04, 2014 at 10:51:03AM +0000, Will Deacon wrote:
> and, as before, it has a weird child process that I can't backtrace:
>
> trinity-c1 R running task 0 861 811 0x00000000
> Call trace:
When I get these, ftrace is a godsend.
cd /sys/kernel/debug/tracing/
echo 861 >> set_ftrace_pid
echo function_graph >> current_tracer
echo 1 >> tracing_on
wait a little while
cat trace > trace.txt
repeat last two steps if necessary
(assuming it's stuck in kernel space, which /proc/861/stack should
be able to confirm. Usually when I see this problem, that just shows
0xffffffffffffffff)
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists