linux-kernel - Re: perf-related lockup on 3.11

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]

Date:	Thu, 19 Sep 2013 01:24:05 -0700
From:	Andi Kleen <andi@...stfloor.org>
To:	Vince Weaver <vincent.weaver@...ne.edu>
Cc:	linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Dave Jones <davej@...hat.com>
Subject: Re: perf-related lockup on 3.11

Vince Weaver <vincent.weaver@...ne.edu> writes:

> On Wed, 11 Sep 2013, Vince Weaver wrote:
>
>> 
>> I got this hard lockup running my perf_fuzzer on 3.11 on a core2.
>> I guess I should try to reproduce it on linus-git but was hoping
>> I could wait until -rc1 before trying that.
>
> OK, I can also lock up 3.12-rc1 using the perf_fuzzer.  Last message
> logged is below.

If it's easily reproducible and a regression, could you perhaps bisect it?

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only
--
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/