From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel panic on Lenovo X60 with tracing enabled
Date: Thu, 09 Mar 2017 21:43:47 +0100 [thread overview]
Message-ID: <2b0704a6a3cd8a97890340c7fa0133a9@molgen.mpg.de> (raw)
In-Reply-To: <20170309112936.7e220f61@gandalf.local.home>
On 2017-03-09 17:29, Steven Rostedt wrote:
> On Thu, 9 Mar 2017 10:16:02 -0600
> Josh Poimboeuf 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 wrote:
>> > > 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?
As far as I can see, the Debian Linux kernel is built with
`CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y`.
So it might be a different problem?
Kind regards,
Paul
next prev parent reply other threads:[~2017-03-09 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 12:12 Paul Menzel
2017-03-09 14:36 ` Steven Rostedt
2017-03-09 16:16 ` Josh Poimboeuf
2017-03-09 16:29 ` Steven Rostedt
2017-03-09 20:43 ` Paul Menzel [this message]
2017-03-09 23:04 ` Josh Poimboeuf
2017-03-10 8:53 ` Paul Menzel
2017-03-10 18:18 ` Josh Poimboeuf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2b0704a6a3cd8a97890340c7fa0133a9@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®