From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Andrzej Siewior Subject: Re: BUG: unable to handle kernel NULL pointer dereference on 3.18.13-rt10 Date: Mon, 13 Jul 2015 09:55:28 +0200 Message-ID: <55A36EF0.7020404@linutronix.de> References: <453aa7881ded41e7a843795863ac1712@FE-MBX1012.de.bosch.com> <20150710132318.GA27402@linutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Thomas Gleixner , "linux-rt-users@vger.kernel.org" To: "Koehrer Mathias (ETAS/ESW5)" Return-path: Received: from www.linutronix.de ([62.245.132.108]:52435 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751139AbbGMHzb (ORCPT ); Mon, 13 Jul 2015 03:55:31 -0400 In-Reply-To: Sender: linux-rt-users-owner@vger.kernel.org List-ID: On 07/13/2015 09:39 AM, Koehrer Mathias (ETAS/ESW5) wrote: > Hi Sebastian, hi Thomas, Hi Mathias, >> if you managed to trigger it that reliably, could you revert >> slub_delay_ctor_on_rt.patch in the queue and try again? >> > > on another PC we got the kernel BUG during normal operation (not at reboot) and with this one ftrace was enabled. > Please see the output of the serial console in the attachment. > I hope this helps to identify the issue! Was this with or without the ctor patch I mentioned? > > Regards > > Mathias Sebastian