From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751372AbbCTUBo (ORCPT ); Fri, 20 Mar 2015 16:01:44 -0400 Received: from mga03.intel.com ([134.134.136.65]:33137 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750925AbbCTUBk (ORCPT ); Fri, 20 Mar 2015 16:01:40 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,438,1422950400"; d="scan'208";a="543981207" Message-ID: <550C7C8C.2020309@intel.com> Date: Fri, 20 Mar 2015 13:01:16 -0700 From: Dave Hansen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Linus Torvalds , David Ahern CC: "David S. Miller" , linux-mm , LKML , sparclinux@vger.kernel.org Subject: Re: 4.0.0-rc4: panic in free_block References: <550C37C9.2060200@oracle.com> <550C5078.8040402@oracle.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/20/2015 09:58 AM, Linus Torvalds wrote: > 128 cpu's is still "unusual", of course, but by no means unheard of, > and I'f have expected others to report it too if it was wasy to > trigger on x86-64. FWIW, I configured a kernel with SLAB and kicked off a bunch of compiles on a 160-thread x86_64 system. It definitely doesn't die _quickly_. It's been running for an hour or two.