Re: Kernel panic on Lenovo X60 with tracing enabled

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Josh Poimboeuf <jpoimboe@redhat.com>
Newsgroups	linux.kernel
Subject	Re: Kernel panic on Lenovo X60 with tracing enabled
Date	Thu, 09 Mar 2017 17:20:01 +0100
Message-ID	<tj8Xf-7Er-5@gated-at.bofh.it> (permalink)
References	<tj5wm-5a0-33@gated-at.bofh.it> <tj7ya-6vj-19@gated-at.bofh.it>
MIME-Version	1.0
Content-Type	text/plain; charset=utf-8
Content-Disposition	inline
User-Agent	Mutt/1.6.0.1 (2016-04-01)
X-Scanned-By	MIMEDefang 2.68 on 10.5.11.24
X-Greylist	Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Thu, 09 Mar 2017 16:16:05 +0000 (UTC)
Sender	robomod@news.nic.it
List-ID	<linux-kernel.vger.kernel.org>
X-Mailing-List	linux-kernel@vger.kernel.org
Approved	robomod@news.nic.it
Lines	29
Organization	linux.* mail to news gateway
X-Original-Cc	Paul Menzel <pmenzel@molgen.mpg.de>, Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org
X-Original-Date	Thu, 9 Mar 2017 10:16:02 -0600
X-Original-Message-ID	<20170309161602.blwj36l6ckg3yh5g@treble>
X-Original-References	<cf5ccae5-cf53-224d-ab14-e79766f4392f@molgen.mpg.de> <20170309093630.69d02d7e@gandalf.local.home>
X-Original-Sender	linux-kernel-owner@vger.kernel.org
Xref	csiph.com linux.kernel:1596177

Show key headers only | View raw

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.

-- 
Josh

Thread

Kernel panic on Lenovo X60 with tracing enabled Paul Menzel <pmenzel@molgen.mpg.de> - 2017-03-09 13:40 +0100
  Re: Kernel panic on Lenovo X60 with tracing enabled Steven Rostedt <rostedt@goodmis.org> - 2017-03-09 15:50 +0100
    Re: Kernel panic on Lenovo X60 with tracing enabled Josh Poimboeuf <jpoimboe@redhat.com> - 2017-03-09 17:20 +0100
      Re: Kernel panic on Lenovo X60 with tracing enabled Steven Rostedt <rostedt@goodmis.org> - 2017-03-09 18:10 +0100
        Re: Kernel panic on Lenovo X60 with tracing enabled Paul Menzel <pmenzel@molgen.mpg.de> - 2017-03-09 21:50 +0100
          Re: Kernel panic on Lenovo X60 with tracing enabled Josh Poimboeuf <jpoimboe@redhat.com> - 2017-03-10 00:10 +0100
            Re: Kernel panic on Lenovo X60 with tracing enabled Paul Menzel <pmenzel@molgen.mpg.de> - 2017-03-10 10:00 +0100
              Re: Kernel panic on Lenovo X60 with tracing enabled Josh Poimboeuf <jpoimboe@redhat.com> - 2017-03-10 19:20 +0100

csiph-web