lkml.org 
[lkml]   [2017]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Kernel panic on Lenovo X60 with tracing enabled
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

\
 
 \ /
  Last update: 2017-03-09 21:44    [W:0.090 / U:0.588 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site