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] [day] [month] [year] [list]

Message-ID: <CAM5Ud7OHKau65gmrDDpzGkv4vweAwP0xpDv2oMGaa3su5aAr8w@mail.gmail.com>
Date:   Tue, 20 Sep 2016 09:34:26 -0500
From:   NTU <neotheuser@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: Re: rcu_sched self-detected stall on CPU

Well this time I got a lot more symbols for you guys! I didn't change
anything except reboot a couple times. Log is attached. I don't debug
symbols often (never done it with kernel code before) but I'll give it
a shot with gdb and report back, I'll be glad to help solve this
issue.

Alec Ari

On Thu, Sep 15, 2016 at 12:15 PM, NTU <neotheuser@...il.com> wrote:
> Sorry!!
>
> Alec Ari
>
> On Thu, Sep 15, 2016 at 1:22 AM, Mike Galbraith
> <umgwanakikbuti@...il.com> wrote:
>> 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.

View attachment "stall_second.txt" of type "text/plain" (8886 bytes)