@Mika After seeing the logs in your post I checked the logs on my Lenovo Yoga (20C0) for similar entries as yours: [ 19.724288] intel-spi intel-spi: wrote SSFSTS_CTL=0x0045020c [ 19.724301] intel-spi intel-spi: wrote FDATA(0)=00 00 [ 19.724304] intel-spi intel-spi: wrote SSFSTS_CTL=0x0041360c [ 19.736538] intel-spi intel-spi: wrote SSFSTS_CTL=0x0040520c [ 19.736542] intel-spi intel-spi: Both SR/CR cleared
My logs do not show anything link this. Could it be, that the fix dows not work for the 20C0? Any ideas on this? [ 18.936164] calling intel_spi_platform_driver_init+0x0/0x1000 [intel_spi_platform] @ 571 [ 18.936215] intel-spi intel-spi: BFPREG=0x0bff0800 [ 18.936218] intel-spi intel-spi: HSFSTS_CTL=0x0004e008 [ 18.936219] intel-spi intel-spi: -> Locked [ 18.936221] intel-spi intel-spi: FADDR=0x00ae86ec [ 18.936222] intel-spi intel-spi: DLOCK=0x00000000 [ 18.936224] intel-spi intel-spi: FDATA(0)=0x00000083 [ 18.936226] intel-spi intel-spi: FDATA(1)=0x00000000 [ 18.936228] intel-spi intel-spi: FDATA(2)=0x00000000 [ 18.936230] intel-spi intel-spi: FDATA(3)=0x00000000 [ 18.936232] intel-spi intel-spi: FDATA(4)=0x00000000 [ 18.936233] intel-spi intel-spi: FDATA(5)=0x00000000 [ 18.936235] intel-spi intel-spi: FDATA(6)=0x00000000 [ 18.936237] intel-spi intel-spi: FDATA(7)=0x00000000 [ 18.936239] intel-spi intel-spi: FDATA(8)=0x00000000 [ 18.936241] intel-spi intel-spi: FDATA(9)=0x00000000 [ 18.936242] intel-spi intel-spi: FDATA(10)=0x00000000 [ 18.936244] intel-spi intel-spi: FDATA(11)=0x00000000 [ 18.936246] intel-spi intel-spi: FDATA(12)=0x00000000 [ 18.936248] intel-spi intel-spi: FDATA(13)=0x00000000 [ 18.936250] intel-spi intel-spi: FDATA(14)=0x00000000 [ 18.936252] intel-spi intel-spi: FDATA(15)=0x00000000 [ 18.936254] intel-spi intel-spi: FRACC=0x00004a4b [ 18.936256] intel-spi intel-spi: FREG(0)=0x00000000 [ 18.936257] intel-spi intel-spi: FREG(1)=0x0bff0800 [ 18.936260] intel-spi intel-spi: FREG(2)=0x07ff0001 [ 18.936262] intel-spi intel-spi: FREG(3)=0x00007fff [ 18.936263] intel-spi intel-spi: FREG(4)=0x00007fff [ 18.936265] intel-spi intel-spi: PR(0)=0x00000000 [ 18.936267] intel-spi intel-spi: PR(1)=0x8bff0b30 [ 18.936269] intel-spi intel-spi: PR(2)=0x8acf0aa1 [ 18.936271] intel-spi intel-spi: PR(3)=0x8aa00aa0 [ 18.936273] intel-spi intel-spi: PR(4)=0x8a9f0800 [ 18.936274] intel-spi intel-spi: SSFSTS_CTL=0xf94010c0 [ 18.936276] intel-spi intel-spi: PREOP_OPTYPE=0xfe400606 [ 18.936278] intel-spi intel-spi: OPMENU0=0x0135059f [ 18.936280] intel-spi intel-spi: OPMENU1=0x20d80203 [ 18.936282] intel-spi intel-spi: LVSCC=0x80802025 [ 18.936283] intel-spi intel-spi: UVSCC=0x80002025 [ 18.936284] intel-spi intel-spi: Protected regions: [ 18.936287] intel-spi intel-spi: 01 base: 0x00b30000 limit: 0x00bfffff [W.] [ 18.936290] intel-spi intel-spi: 02 base: 0x00aa1000 limit: 0x00acffff [W.] [ 18.936292] intel-spi intel-spi: 03 base: 0x00aa0000 limit: 0x00aa0fff [W.] [ 18.936294] intel-spi intel-spi: 04 base: 0x00800000 limit: 0x00a9ffff [W.] [ 18.936295] intel-spi intel-spi: Flash regions: [ 18.936297] intel-spi intel-spi: 00 disabled [ 18.936299] intel-spi intel-spi: 01 base: 0x00800000 limit: 0x00bfffff [ 18.936301] intel-spi intel-spi: 02 base: 0x00001000 limit: 0x007fffff [ 18.936303] intel-spi intel-spi: 03 disabled [ 18.936304] intel-spi intel-spi: 04 disabled [ 18.936306] intel-spi intel-spi: Using SW sequencer for register access [ 18.936307] intel-spi intel-spi: Using HW sequencer for erase operation [ 18.936309] intel-spi intel-spi: wrote SSFSTS_CTL=0x0045020c [ 18.936318] intel-spi intel-spi: s25fl064k (8192 Kbytes) [ 18.938965] calling rapl_init+0x0/0x1000 [intel_rapl] @ 589 [ 18.939493] intel_rapl: Found RAPL domain package [ 18.939494] intel_rapl: Found RAPL domain core [ 18.939495] intel_rapl: Found RAPL domain uncore [ 18.939496] intel_rapl: Found RAPL domain dram [ 18.943692] initcall rapl_init+0x0/0x1000 [intel_rapl] returned 0 after 4608 usecs [ 18.946463] calling cmdline_parser_init+0x0/0x1000 [cmdlinepart] @ 813 [ 18.946466] initcall cmdline_parser_init+0x0/0x1000 [cmdlinepart] returned 0 after 0 usecs [ 18.951039] Creating 1 MTD partitions on "intel-spi": [ 18.951043] 0x000000000000-0x000000c00000 : "BIOS" [ 18.951044] mtd: partition "BIOS" extends beyond the end of device "intel-spi" -- size truncated to 0x800000 [ 18.951192] initcall intel_spi_platform_driver_init+0x0/0x1000 [intel_spi_platform] returned 0 after 14669 usecs -- 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: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Committed 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: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. --- 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 (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- 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 --- 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 : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
