linux-kernel - Re: Kernel panic on Lenovo X60 with tracing enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bea1b2d8-6cd6-28b1-7214-a3ed7da2eb1e@molgen.mpg.de>
Date:   Fri, 10 Mar 2017 09:53:29 +0100
From:   Paul Menzel <pmenzel@...gen.mpg.de>
To:     Josh Poimboeuf <jpoimboe@...hat.com>
Cc:     Steven Rostedt <rostedt@...dmis.org>,
        Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: Kernel panic on Lenovo X60 with tracing enabled

Dear Josh,


On 03/10/17 00:04, Josh Poimboeuf wrote:
> On Thu, Mar 09, 2017 at 09:43:47PM +0100, Paul Menzel wrote:
>> 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?
>
> Is it a stock Debian kernel?  If so, do you have a link where it can be
> downloaded?

Sure, hopefully [3] works for you.

```
dpkg -x 
linux-image-4.9.0-0.bpo.2-686-pae-unsigned_4.9.13-1~bpo8+1_i386.deb 
target-directory
```


Kind regards,

Paul


[1] 
https://packages.debian.org/jessie-backports/linux-image-4.9.0-0.bpo.2-686-pae-unsigned
[2] 
https://packages.debian.org/jessie-backports/i386/linux-image-4.9.0-0.bpo.2-686-pae-unsigned/download
[3] 
http://ftp.us.debian.org/debian/pool/main/l/linux/linux-image-4.9.0-0.bpo.2-686-pae-unsigned_4.9.13-1~bpo8+1_i386.deb
[4] https://linux.die.net/man/1/dpkg