Silvermont was announced to news media on May 6, 2013, at Intel's headquarters at Santa Clara, California.[3] Intel had repeatedly said the first Bay Trail devices would be available during the Holiday 2013 timeframe, while leaked slides showed that the release window for Bay Trail-T as August 28 – September 13, 2013.[4] Both Avoton and Rangeley were announced as being available in the second half of 2013. The first Merrifield devices were announced in 1H14.[5]
Intel revealed in its Q4 2016 quarterly report that there were quality issues in the C2000 product family, which had an effect on the financial performance of the company's Data Center Group that quarter.[12] An erratum named AVR54 published by Intel; state there is a defect in the chip's LPC clock, and affected systems "may experience inability to boot or may cease operation".[13][14][15] A workaround is available requiring platform hardware changes. The SoC failures are thought to have led to failures in Cisco and Synology products,[16] though discussion of the C2000 as the root cause of failure has been reported to be under a non-disclosure agreement for many vendors.[17]
Intel released a new C0 stepping of the C2000 series in April 2017 which corrected the bug.[18]
In July 2017 Intel published that a similar quality issue affects also Atom E3800 series embedded processors. The erratum named VLI89 published by Intel state, similar to issue with Atom C2000, that there is a defect in the chip's LPC clock and affected systems "may experience inability to boot or may cease operation".[19] Issues extend also to USB bus and SD card circuitry and should happen "under certain conditions where activity is high for several years". In April 2018 Intel announced it is releasing a new D1 stepping to fix the issue.[20]
The LPC, USB and SD Card buses circuitry degradation issues also apply to other Bay Trail processors such as Intel Celeron J1900 and N2800/N2900 series;[21] also to Pentium N3500, J2850, J2900 series; and Celeron J1800 and J1750 series—as those are based on the same affected silicon.
Cisco stated failures of Atom C2000 processors can occur as early as 18 months of use with higher failure rates occurring after 36 months.[22]
Mitigations were found to limit impact on systems. Firmware update for the LPC bus called LPC_CLKRUN# reduces the utilization of the LPC interface what in turn decreases (but not eliminates) LPC bus degradation - some systems are however not compatible with this new firmware. USB should have a maximum of 10% active time and there is a 50TB transmit traffic life expectancy over the lifetime of the port. It is recommended not to use SD card as a boot device and to remove the card from the system when not in use.
Bay Trail issues on Linux
It has been widely reported that Bay Trail CPUs (and possibly their derivatives including Airmont/Braswell/Cherry Trail) experience random freezes / lock-ups on various Linux kernels. Reference Linux bug report 109051 on Kernel.orgBugzilla, first reported Dec-2015. Workaround seems to be setting the Linux kernel flag intel_idle.max_cstate=1, which while eliminating the system freezes/lock-ups, results in increased CPU power/battery usage by preventing the CPU from entering higher power-saving C-states. Systems running Windows-OSes apparently do not experience these lockup/freeze issues.
Bay Trail issues on FreeBSD
A potential fix is to set hw.acpi.cpu.cx_lowest=C1 and dev.cpu.<n>.lowest via /etc/sysctl.conf.
Airmont issues
14 nm Airmont architecture processors are also affected by the design flaws as noted in the Braswell Specification Update under CHP49 errata.[23] In addition to LPC and SD Card circuitry degradation issues those 14 nm designs also have issues with Real Time Clock (RTC) circuitry degradation, their USB buses are however not affected. Unspecified firmware changes are required to mitigate RTC circuitry degradation. Intel does not plan to release a new stepping for Braswell. Intel admitted the issue stating the impact on consumers depends on use condition.[24]
Silvermont based processor cores have been used in Knights Landing versions of Intel's Xeon Phi multiprocessor HPC chips, with changes for HPC including AVX-512 vector units.[29][30]
