Skip to contentSkip to conversation

intel_idle.max_cstate=1 required on baytrail to prevent crashes

DISCUSSION Michal Feix 3 participants 4 messages Mar 17, 2016 – Mar 18, 2016

lore
Share & tools
lore
#0 lore raw

Hello everyone,

for the past few months, I'm fighting random hard lock-ups on my Baytrail machine with different linux kernels. Freezes are quite frequent, between few minutes to few hours of uptime. According to other reporters, this was pinpointed as an intel_idle problem on Baytrail. The bug report originally started as i915 regression at
https://bugs.freedesktop.org/show_bug.cgi?id=88012 and was moved to kernel Bugzilla few months ago -
https://bugzilla.kernel.org/show_bug.cgi?id=109051

This bug seems to be a serious showstopper for Baytrail users and was already confirmed by many, but there is no obvious progress on this bug report for last few months. Meny reporters have confirmed intel_idle.max_cstate=1 or intel_idle.max_cstate=2 as a half-working workaround, which makes the interval between freezes on Baytrail longer.

Could someone here please confirm if this is in or out of anyone's current focus? I strongly believe this is not a minority issue and maybe this just slipped through meny other important bug reports.

Thank you,

--
Michael

#1 lore raw
Quoted 1 line · Michal Feix

Hello everyone,

Hi,

Quoted 15 lines

for the past few months, I'm fighting random hard lock-ups on my Baytrail machine with different linux kernels. Freezes are quite frequent, between few minutes to few hours of uptime. According to other reporters, this was pinpointed as an intel_idle problem on Baytrail. The bug report originally started as i915 regression at
https://bugs.freedesktop.org/show_bug.cgi?id=88012 and was moved to kernel Bugzilla few months ago -
https://bugzilla.kernel.org/show_bug.cgi?id=109051

This bug seems to be a serious showstopper for Baytrail users and was already confirmed by many, but there is no obvious progress on this bug report for last few months. Meny reporters have confirmed intel_idle.max_cstate=1 or intel_idle.max_cstate=2 as a half-working workaround, which makes the interval between freezes on Baytrail longer.

Quoted 3 lines

Could someone here please confirm if this is in or out of anyone's current focus? I strongly believe this is not a minority issue and maybe this just slipped through meny other important bug reports.

No, it hasn't, but it turns out difficult to root-cause.

Tell me one thing: does disabling intel_idle entirely on the affected systems make the problem go away?

That is, does intel_idle.max_cstate=0 in the kernel command line help?

Or does idle=nomwait in the kernel command line help?

Thanks,
Rafael

#2 lore raw
Quoted 14 lines
Quoted 9 lines

for the past few months, I'm fighting random hard lock-ups on my Baytrail machine with different linux kernels. Freezes are quite frequent, between few minutes to few hours of uptime. According to other reporters, this was pinpointed as an intel_idle problem on Baytrail. The bug report originally started as i915 regression at
https://bugs.freedesktop.org/show_bug.cgi?id=88012 and was moved to kernel Bugzilla few months ago -
https://bugzilla.kernel.org/show_bug.cgi?id=109051

Quoted 5 lines

This bug seems to be a serious showstopper for Baytrail users and was already confirmed by many, but there is no obvious progress on this bug report for last few months. Meny reporters have confirmed intel_idle.max_cstate=1 or intel_idle.max_cstate=2 as a half-working workaround, which makes the interval between freezes on Baytrail longer.

Quoted 8 lines

No, it hasn't, but it turns out difficult to root-cause.

Tell me one thing: does disabling intel_idle entirely on the affected systems make the problem go away?

That is, does intel_idle.max_cstate=0 in the kernel command line help?

Or does idle=nomwait in the kernel command line help?

intel_idle.max_cstate=1 - no hard-lockups
intel_idle.max_cstate=0 - no hard-lockups
idle=nomwait - with hard-lockups

Someone on Bugzilla suggested to try latest 4.5 kernel, as he believes it's fixed already on his BYT laptop. I'm running on the longterm branch so I just upgraded to 4.1.19 LTS which is the latest in Arch distro for the moment. And yes - my uptime is 4 hours and still counting! :-) I'll see during next few days but maybe it's fixed.

intel_idle would then be probably out of suspision, as it haven't been touched for last few months..

Michael

#3 lore raw
Quoted 27 lines · Michal Feix
Quoted 14 lines
Quoted 9 lines

for the past few months, I'm fighting random hard lock-ups on my Baytrail machine with different linux kernels. Freezes are quite frequent, between few minutes to few hours of uptime. According to other reporters, this was pinpointed as an intel_idle problem on Baytrail. The bug report originally started as i915 regression at
https://bugs.freedesktop.org/show_bug.cgi?id=88012 and was moved to kernel Bugzilla few months ago -
https://bugzilla.kernel.org/show_bug.cgi?id=109051

Quoted 5 lines

This bug seems to be a serious showstopper for Baytrail users and was already confirmed by many, but there is no obvious progress on this bug report for last few months. Meny reporters have confirmed intel_idle.max_cstate=1 or intel_idle.max_cstate=2 as a half-working workaround, which makes the interval between freezes on Baytrail longer.

Quoted 8 lines

No, it hasn't, but it turns out difficult to root-cause.

Tell me one thing: does disabling intel_idle entirely on the affected systems make the problem go away?

That is, does intel_idle.max_cstate=0 in the kernel command line help?

Or does idle=nomwait in the kernel command line help?

intel_idle.max_cstate=1 - no hard-lockups
intel_idle.max_cstate=0 - no hard-lockups
idle=nomwait - with hard-lockups

Quoted 8 lines

Someone on Bugzilla suggested to try latest 4.5 kernel, as he believes it's fixed already on his BYT laptop. I'm running on the longterm branch so I just upgraded to 4.1.19 LTS which is the latest in Arch distro for the moment. And yes - my uptime is 4 hours and still counting! :-) I'll see during next few days but maybe it's fixed.

intel_idle would then be probably out of suspision, as it haven't been touched for last few months..

This is not an intel_idle problem in any case. If anything, there might be a way to work around it in that driver.