linux-kernel - Re: rcu_sched self-detected stall on CPU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1473920558.8231.3.camel@gmail.com>
Date:   Thu, 15 Sep 2016 08:22:38 +0200
From:   Mike Galbraith <umgwanakikbuti@...il.com>
To:     NTU <neotheuser@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: rcu_sched self-detected stall on CPU

On Wed, 2016-09-14 at 23:02 -0500, NTU wrote:
> [   26.542980] Call Trace:
> [   26.542983]  [<ffffffffa7fbd7c1>] ? 0xffffffffa7fbd7c1
> [   26.542985]  [<ffffffffa7f17d35>] ? 0xffffffffa7f17d35
> [   26.542986]  [<ffffffffa796c115>] ? 0xffffffffa796c115
> [   26.542988]  [<ffffffffa7633d86>] ? 0xffffffffa7633d86
> [   26.542989]  [<ffffffffa796c0a6>] ? 0xffffffffa796c0a6
...

The stack trace is useless without symbols.