[GTALUG] Intel Bay Trail bug fixed in 5.3!

D. Hugh Redelmeier hugh at mimosa.com
Tue May 28 12:02:04 EDT 2019


Bay Trail is a family of processors/SoCs introduced in 2013.  They were 
ubiquitous.  And they suffered hangs under Linux.
<https://ark.intel.com/content/www/us/en/ark/products/codename/55844/bay-trail.html>

The work-around has been to turn off some power-saving capabilities, 
crippling the usefulness of these "low-power" chips.  (I suspect most 
users never found the magic incantation to do this and so have just given 
up on running Linux on these systems.)

I'm subscribed to the bugzilla entries.  I just got a notification of
the thousandth comment added to one.  A kernel patch has been
submitted by Intel and accepted for 5.3 (months away).  The whole
useful life of this SoC has been impaired.

This patch is work-around code for a chip bug.  The patch itself is
restricted to "Valleyview" which is a name for something that covers
all Bay Trail chips, and only Bay Trail chips.

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

--- Comment #1000 from w2q at arcor.de ---

I may cite Hans de Goede from this site: 
https://www.phoronix.com/forums/forum/software/mobile-linux/1096936-intel-baytrail-cherrytrail-systems-can-now-correctly-hibernate-again-under-linux?p=1096999#post1096999

"

Actually the Intel open-source devs have been working on fixing this and a
patch-series which should improve things wrt this has been queued for merging
into 5.3 (it just missed the 5.2 merge window), see: 

https://cgit.freedesktop.org/drm-intel/commit/?id=a75d035fedbdecf83f86767aa2e4d05c8c4ffd95

"



Yeah, comment 1000!


More information about the talk mailing list