topic Re: Bay Trail Linux C-State bug in Mobile and Desktop Processors

Bay Trail Linux C-State bug

powerarmour — Wed, 04 Mar 2015 13:53:19 GMT

Is there any news on when (or if!) this pretty major bug will be addressed?

https://bugs.freedesktop.org/show_bug.cgi?id=88012 Bug 88012 – [bisected BYT] complete freeze after: drm/i915/vlv: WA for Turbo and RC6 to work together

Re: Bay Trail Linux C-State bug

Jose_H_Intel1 — Thu, 05 Mar 2015 19:17:49 GMT

You may want to check with the system or motherboard manufacturer in regards of possible fix through a BIOS update.

The following sites may also be of help:

Re: Bay Trail Linux C-State bug

powerarmour — Thu, 05 Mar 2015 20:38:30 GMT

Thanks, but it's not a current BIOS issue I believe (as it affects all BYT), it's more an issue with the commit at the moment.

Re: Bay Trail Linux C-State bug

tk7 — Tue, 10 Mar 2015 22:09:34 GMT

@Joe_intel, you are the motherboard manufacturer. This is a Bay Trail NUC I am having the problem with.

Re: Bay Trail Linux C-State bug

powerarmour — Wed, 03 Aug 2016 01:38:16 GMT

Interesting to see that this bug still remains...

https://bugzilla.kernel.org/show_bug.cgi?id=109051 https://bugzilla.kernel.org/show_bug.cgi?id=109051

Well over a year without a proper fix!

Re: Bay Trail Linux C-State bug

EstebanA_C_Intel — Wed, 03 Aug 2016 16:44:39 GMT

Hello, powerarmour :

I would like to check, have you posted this inquiry here: https://01.org/community Community | 01.org ?

This is a specialized communities support for Linux, peers over there are more aware of these reports and how they are being handled.

Regards,

Esteban C

Re: Bay Trail Linux C-State bug

powerarmour — Tue, 09 Aug 2016 12:22:49 GMT

Dear Esteban,

Yes it is also on 01.org, but you should ideally state more clearly that this is a 'Windows only' support community, as many people with Linux queries and questions will normally come here first.

Re: Bay Trail Linux C-State bug

EstebanA_C_Intel — Wed, 10 Aug 2016 18:01:53 GMT

Thank you for the feedback, powerarmour, I will take that to my upper management for review.

Regards,

Esteban C

Re: Bay Trail Linux C-State bug

VGerr — Sun, 21 Aug 2016 18:03:59 GMT

Hi Esteban,

Any news on this ? This is a HUGE issue for Linux users!

This bug hasn't been fixed for about 2 years and there are thousand if not hundreds of thousands affected.

Has this not hit intels radar?

They are quite under fire and the response to this is not considered appropriate.

It may be that this hasn't landed on the right plate, but if you just look at that bugzilla post:

https://bugzilla.kernel.org/show_bug.cgi?id=109051 https://bugzilla.kernel.org/show_bug.cgi?id=109051

you can see how serious this is.

Can you escalate this or let us know who we can contact?

Trust me, I will not invest in intel hardware if there is not proper support on it.

There are also businesses running on the Bay Trail platform and the successors, there.

Thank you for your time and please keep us posted.

Kind regards,

Vincent

Re: Bay Trail Linux C-State bug

idata — Tue, 23 Aug 2016 14:59:02 GMT

Hello, VGerris:

I can confirm this has been reported and is currently being reviewed by my upper management, as soon as I get instructions for you, I will let you know.

Regards,

Esteban C

Re: Bay Trail Linux C-State bug

VGerr — Tue, 23 Aug 2016 18:14:31 GMT

Hi Esteban,

Thank you for the reply.

It was suggested that a possible intel employee made a fix in the past that somehow did not make it to the kernel:

https://lkml.org/lkml/2015/3/24/271 https://lkml.org/lkml/2015/3/24/271

Maybe you can have a look and the fix may not be that difficult.

Thank you for your time and I am looking forward to any answer.

Kind regards,

Vincent

Re: Bay Trail Linux C-State bug

idata — Thu, 25 Aug 2016 16:13:04 GMT

Thank you for the additional information provided for this matter, VGerris.

This is to be reviewed and handled by the team in charge.

Regards,

Esteban C

Re: Bay Trail Linux C-State bug

VGerr — Wed, 14 Sep 2016 05:50:38 GMT

Hi Esteban,

I am getting the feeling we are kept busy here.

Can you give a concrete update of the matter?

How about a statement from management that you refer to?

Thank you and regards,

Vincent

Re: Bay Trail Linux C-State bug

idata — Wed, 21 Sep 2016 16:51:33 GMT

Hello, Peers:

I can assure the feedback about this matter has been placed, and it is to be reviewed as well; however, at the moment, there is no ETA for a resolution or outcome for the bug. It has to go through certain process which is required to get this done (reason why it takes a while).

Hope you can understand :)

Thanks,

Esteban C

Re: Bay Trail Linux C-State bug

VGerr — Mon, 28 Nov 2016 22:21:43 GMT

Hi Esteban,

Is there any reason why there is complete silence here?

Where are we in the process?

This is a known hardware bug that is likely to be circumvented or fixed in Windows drivers.

How difficult is it to get a response?

I hope intel will show that they care about their customers and fix bugs that are obvious faults.

I think everybody has been trying to be nice and push this and nothing happens.

Would a class action law suit be something that would get attention?

I would really like to see a reaction of any type of an indication.

I find it completely ununderstandable that the biggest PC chipmaker in the industry is unable to get an engineer to create a solution for a known hardware bug, especially not when it was already implemented for another platform.

Looking forward to you reaction,

Regards,

Vincent

Re: Bay Trail Linux C-State bug

idata — Tue, 29 Nov 2016 18:22:41 GMT

Sure I understand your concern, VGerris

There is a process required when handling these requests which take a while, but let me get an update and then let you know

Regards,

Esteban C

Re: Bay Trail Linux C-State bug

VGerr — Tue, 29 Nov 2016 19:54:55 GMT

Hi Esteban,

That seems like another message to hold things off and honestly, I am getting sick and tired of it.

This thread was started March 2015.

You started to be involved in the beginning of August 2016(!) and me half way.

You posted on the 23rd of August of 2016 that this was reported.

THAT IS OVER 3 MONTHS AGO.

How about you give an honest view of what is going on and stop trying to stall?

Do you not have the guts to admit we can all go screw ourselves with this hardware that is defect from the factory out?

I think everyone has been patient long enough.

Stop stalling and start answering please.

Thank you.

Re: Bay Trail Linux C-State bug

VGerr — Sat, 17 Dec 2016 00:46:45 GMT

Hi,

Just an update. Esteban seems to have crawled away somewhere after holding off and asking for my contact details.

Great progress has been made and it seemed very obvious that it was not due to efforts from him or whatever management he mentioned.

I have attacked the way of handling this per personal message and will not further elaborate on it here

A RedHat employee has created patched for the Cherry trail platform, the essential one can be found here:

https://patchwork.ozlabs.org/patch/704786/ https://patchwork.ozlabs.org/patch/704786/

If you go back to patch 1 and apply them in order, this should fix freeze issues.

Please help out testing and confirming.

I mentioned it in:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/comments/144 Comment # 144 : Bug # 1575467 : Bugs : linux package : Ubuntu

For Bay trail there was a patch posted that seems to deal with the errata in the proper way.

It's attached to the original bug, it was for 4.7, I added one for 4.8, please find it here:

https://bugzilla.kernel.org/show_bug.cgi?id=109051 Bug 109051 – intel_idle.max_cstate=1 required on baytrail to prevent crashes

For Ubuntu users like myself, I put up compiled kernels with the Bay trail freeze fix:

https://www.dropbox.com/sh/c39et4hr6tgp60q/AAC35c56aOEOwkmhjdvtG6dsa?dl=0 Dropbox - ubuntu x86_64 4.8 and 4.9 Bay trail freeze patched kernel packages

Arch Linux also has a patched 4.8 kernel.

I hope the terrible way intel dealth with these errata regarding Linux users will not happen again.

I also hope not too many people abandoned Linux on both server and desktop for this dumb reason of a zillion dollar company being unsupportive. The options for AMD and ARM get interesting by the day.you

Thanks to all people collaborating on the fix, please update the kernel bugzilla and ubuntu bug with your findings!

thank you

Re: Bay Trail Linux C-State bug

uk — Sun, 25 Dec 2016 14:02:13 GMT

Hello Vincent, just wanted to say thanks for following up on this. You may not have realised this yet, but you've helped a LOT of people ( including me ) suffering with this bug. Any idea when this patch will show up in the official linux kernel ?

Re: Bay Trail Linux C-State bug

VGerr — Mon, 26 Dec 2016 00:01:11 GMT

Hi,

Thank you for your feedback. I am very happy to read that it helped you. Can you share your hardware and software specifics that are applicable so we can get an idea of what is affected and fixed?

I asked the original creator (Jochen Hein) to post it on the kernel mailing list, which he did.

It may need some cleaning up, I am keeping an eye on it.

Looking forward to at least processor and kernel you tested and anything more relevant you can share.

Thanks for contributing!