From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S932795AbdCIRGj (ORCPT <rfc822;w@1wt.eu>);
        Thu, 9 Mar 2017 12:06:39 -0500
Received: from mail.kernel.org ([198.145.29.136]:48150 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S932669AbdCIRGU (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 9 Mar 2017 12:06:20 -0500
Date: Thu, 9 Mar 2017 11:29:36 -0500
From: Steven Rostedt <rostedt@goodmis.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>, Ingo Molnar <mingo@redhat.com>,
        linux-kernel@vger.kernel.org
Subject: Re: Kernel panic on Lenovo X60 with tracing enabled
Message-ID: <20170309112936.7e220f61@gandalf.local.home>
In-Reply-To: <20170309161602.blwj36l6ckg3yh5g@treble>
References: <cf5ccae5-cf53-224d-ab14-e79766f4392f@molgen.mpg.de>
        <20170309093630.69d02d7e@gandalf.local.home>
        <20170309161602.blwj36l6ckg3yh5g@treble>
X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, 9 Mar 2017 10:16:02 -0600
Josh Poimboeuf <jpoimboe@redhat.com> wrote:

> On Thu, Mar 09, 2017 at 09:36:30AM -0500, Steven Rostedt wrote:
> > On Thu, 9 Mar 2017 13:12:28 +0100
> > Paul Menzel <pmenzel@molgen.mpg.de> wrote:
> > 
> > > Dear Steven, dear Ingo,
> > > 
> > > 
> > > Hopefully, I am contacting the right people for my issue.
> > > 
> > > Suspending a system with Linux 4.9.13 with tracing enabled, it fails 
> > > with the screen still enabled, and the LED blinking. Attaching a serial 
> > > console to the dock, shows the messages below.
> > 
> > I'm betting this is a compiler bug, as that bug that printed is the
> > internal ftrace check for it. (note the bug is only in x86-32 not
> > x86-64)
> > 
> > Funny, we are just talking about this bug in another thread, but with a
> > different symptom.
> > 
> > Josh, did you say this goes away if you disable optimize for size or
> > does it need to be enabled?
> 
> Yeah, assuming it's the same problem, then this is caused by
> CONFIG_CC_OPTIMIZE_FOR_SIZE.  It would be fixed by changing it to
> CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE.
> 

Paul, do you have CONFIG_CC_OPTIMIZE_FOR_SIZE enabled? Can you set it
to PERFORMANCE and see if the problem goes away?

-- Steve