linux-kernel - Re: perf sw_event related lockup

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: <CABPqkBRe0xK_mf4JE+0e-UDs92Os_3dreHfh-wnG78fquTCRHQ@mail.gmail.com>
Date:	Mon, 18 Nov 2013 16:18:34 +0100
From:	Stephane Eranian <eranian@...gle.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Vince Weaver <vincent.weaver@...ne.edu>,
	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Paul Mackerras <paulus@...ba.org>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Subject: Re: perf sw_event related lockup

Peter,

I missed the beginning of this thread somehow.
What's the initial problem?


On Mon, Nov 18, 2013 at 9:54 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Fri, Nov 15, 2013 at 12:26:16PM -0500, Vince Weaver wrote:
>> On Fri, 15 Nov 2013, Peter Zijlstra wrote:
>> >
>> > Please enable CONFIG_FRAME_POINTER to get better backtraces, but the
>> > above suggests the pagefault swevent, will have a look.
>>
>> here it is again I think.  I compiled with CONFIG_FRAME_POINTER but the
>> backtraces don't look that different.
>
> Looks to be that other one -- the one where the intel constraints thing
> goes belly up. I was hoping Stephane would look at that since I know
> he's been rewriting that code.
--
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/