Amidst all the noise here, I thought it might be good to summarize some
things and perhaps get them confirmed.
Affected distros:
* Ubuntu
* Antergos
and if the kernel bug attached is the same as this one:
* Arch
* Fedora
Note: every distro with the right kernel has the potential for the
problem, even though they do not display the symptoms. They may have
turned it off, but the problem lies waiting in the kernel, not unlike
some recessive genetic disease.
The kernels:
* 4.10 is ok
* highest version is in zesty-proposed: 4.10.0-43.47
* 4.11-4.13.0-17 is not ok
* highest version is in artful main: 4.13.0-22.25
* 4.13.0-21.24 avoids creating the problem by refusing to compile the kernel
with CONFIG_SPI_INTEL_SPI_PLATFORM set
* highest version is in artful-proposed: 4.13.0-22.25
* bionic main is still 4.13.0-17.20!
* 4.14.9 Ubuntu mainline fixes the problem, it seems
* this includes the following relevant commits:
* don't touch SPI-NOR write protection bit
d9018976cdb6eefc62a7ba79a405f6c9661b08a7 (see kernel bug report)
* this is for the LPC bridge of the Intel I/O Controller hub
(southbridge) which provides access to, e.g. BIOS ROM
* note this only seems to affect Intel Haswell and Broadwell, see
drivers/mfd/lpc_ich.c for PCI IDs
* off-by-one fix 9d63f17661e25fd28714dac94bdebc4ff5b75f09
* this DOES NOT include the kernel compilation config change found in
4.13.0-21.24
* for some reason this doesn't work for everyone, so perhaps there's another
issue at play
Affected serial flash devices by manufacturer part number, JEDEC ID
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
/* ESMT */
f25l32pa, 0x8c2016
f25l32qa, 0x8c4116
f25l64qa, 0x8c4117
/* GigaDevice */
gd25q16, 0xc84015
gd25q32, 0xc84016
gd25lq32, 0xc86016
gd25q64, 0xc84017
gd25lq64c, 0xc86017
gd25q128, 0xc84018
gd25q256, 0xc84019
/* Winbond */
w25q16dw, 0xef6015
w25q32dw, 0xef6016
w25q64dw, 0xef6017
w25q128fw, 0xef6018
Note: considering the author of intel-spi the device driver feels that
these are the problem children, based on a characteristic they have, the
fact that there's Insyde BIOS or not probably has no bearing on whether
or not a device is affected.
Finally, a question: any way to figure out the JEDEC ID of the serial
flash without having to load the module?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1734147
Title:
Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in linux-hwe-edge source package in Xenial:
Fix Released
Status in linux-oem source package in Xenial:
Fix Released
Status in linux source package in Artful:
Fix Released
Bug description:
Description: An update to linux kernel on Ubuntu 17.10 that enabled
the intel-spi-* drivers made Insyde BIOS unusable. Main issues were
Settings being not stored, USB Boot impossible and EFI entries read-
only.
Fix: The issue was fixed in Kernel Version 4.13.0-21. But previous
affected machines still suffered from a broken BIOS.
Repair: Boot Linux and Install Kernel Version 4.14.9. Reboot into
Linux and BIOS should be restored to a working state.
---
Test Case: Fix has been verified by our HWE team on affected hardware.
Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.
---
Affected Machines:
Lenovo B40-70
Lenovo B50-70
Lenovo B50-80
Lenovo Flex-3
Lenovo Flex-10
Lenovo G40-30
Lenovo G50-30
Lenovo G50-70
Lenovo G50-80
Lenovo S20-30
Lenovo U31-70
Lenovo Y50-70
Lenovo Y70-70
Lenovo Yoga Thinkpad (20C0)
Lenovo Yoga 2 11" - 20332
Lenovo Z50-70
Lenovo Z51-70
Lenovo ideapad 100-15IBY
Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE (not fixed by 4.14.9 and 4.14.10)
Acer TravelMate B113
Toshiba Satellite S55T-B5233
Toshiba Satellite L50-B-1R7
Toshiba Satellite S50-B-13G
Dell Inspiron 15-3531 (not fixed by 4.14.9)
Mediacom Smartbook 14 Ultra M-SB14UC
Acer Aspire E3-111-C0UM
---
Original Description:
Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
reported a corrupted BIOS.
It's not possible to save new settings in BIOS anymore and after
rebooting, the system starts with the old settings.
Moreover (and most important) USB booting is not possible anymore
since USB is not recognized. It's very serious, since our machines do
not have a CDROM.
Lenovo forums at the moment are full of topics regading this issue.
Thank you!!
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
