From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752392AbdCIUnw (ORCPT ); Thu, 9 Mar 2017 15:43:52 -0500 Received: from mx3.molgen.mpg.de ([141.14.17.11]:38302 "EHLO mx1.molgen.mpg.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750913AbdCIUnv (ORCPT ); Thu, 9 Mar 2017 15:43:51 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 09 Mar 2017 21:43:47 +0100 From: Paul Menzel To: Steven Rostedt Cc: Josh Poimboeuf , Ingo Molnar , linux-kernel@vger.kernel.org Subject: Re: Kernel panic on Lenovo X60 with tracing enabled Organization: =?UTF-8?Q?Max-Planck-Institut_f=C3=BCr_molekulare_Genetik?= In-Reply-To: <20170309112936.7e220f61@gandalf.local.home> References: <20170309093630.69d02d7e@gandalf.local.home> <20170309161602.blwj36l6ckg3yh5g@treble> <20170309112936.7e220f61@gandalf.local.home> Message-ID: <2b0704a6a3cd8a97890340c7fa0133a9@molgen.mpg.de> User-Agent: Roundcube Webmail/1.1.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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