From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753909AbbIIQ0o (ORCPT ); Wed, 9 Sep 2015 12:26:44 -0400 Received: from mx2.suse.de ([195.135.220.15]:44861 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753272AbbIIQ0m (ORCPT ); Wed, 9 Sep 2015 12:26:42 -0400 Subject: Re: Kernel 4.1.6 Panic due to slab corruption To: Christoph Lameter , Nikolay Borisov References: <55ED4DAD.7080701@kyup.com> <55ED7186.7060503@kyup.com> <55EEEB6F.2090302@kyup.com> <55EEF3B1.9080104@kyup.com> <55F01AB0.6050409@kyup.com> Cc: "Linux-Kernel@Vger. Kernel. Org" , Marian Marinov , SiteGround Operations From: Vlastimil Babka Message-ID: <55F05DBF.5050907@suse.cz> Date: Wed, 9 Sep 2015 18:26:39 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/09/2015 04:01 PM, Christoph Lameter wrote: > On Wed, 9 Sep 2015, Nikolay Borisov wrote: > > What does: > > echo 1 >trace > > do? Could crash the sysem due to overload of messages. Yes I've seen that happen. Did you consider hooking it to trace_printk() instead of printk()?