linux-kernel - Re: Kernel stability on baytrail machines

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: <864e7ac7-8041-9a81-819c-d6b60b59dd0f@feix.cz>
Date:	Wed, 13 Jul 2016 12:05:51 +0200
From:	Michal Feix <michal@...x.cz>
To:	Pavel Machek <pavel@....cz>,
	Ezequiel Garcia <ezequiel@...guardiasur.com.ar>
Cc:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
	dri-devel@...ts.freedesktop.org, intel-gfx@...ts.freedesktop.org
Subject: Re: Kernel stability on baytrail machines

On Tue 2016-07-12 16:41:58, Ezequiel Garcia wrote:
>> Hi Alan,
>>
>> (Adding interested people to this thread)
>>
>> On 09 Apr 08:14 PM, One Thousand Gnomes wrote:
>>>>> I do feel that the importance of the mentioned bug is currently
>>>>> underestimated. Can anyone here give a note, how much current linux
>>>>> kernel is supposed to be stable on general baytrail machines?
>>>> If you did not get any replies... you might want to check MAINTAINERS file, and
>>>> put Intel x86 maintainers on Cc list.
>>>>
>>>> I'm sure someone cares :-).
>>> Yes we care, and there are people looking at the various reports.
>>>
>> Are there any updates on the status of this issue?
>>
>> The current bugzilla report [1] marks this as a power management
>> issue. However, many reports indicate that it would only freeze
>> when running X, so it's not completely clear if it's related to
>> the gfx driver too.
> Does
>
> "intel_idle.max_cstate=1"
>
> fix it for you?
Yes, it does.
> If you feel it is X-only problem, you may want to provide details
> about your graphics subsystem (DRM enabled? framebuffer only?) and
> probably cc.
It's not X-only problem. Happens even in console mode, which is KMS 
switched during boot though.
> ...actually... you may want to verify if it happens in unaccelerated X.
As it happens even in console mode, is this relevant test?

Michal