Launchpad has imported 20 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=195951.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2017-06-01T06:33:34+00:00 abdo.roig wrote: Created attachment 256825 early boot log with kernel 4.11.2 My machine boots fine with kernel 4.11.3. However, on the next boot, the firmware says: "Configuration Changed - Requires restart", and the firmware settings are reset to defaults. There was no such issue with the 4.10 kernels. My machine is a Lenovo Thinkpad Yoga (first generation) with the latest firmware revision. I attach a piece of logs I gathered booting kernel 4.11.2 with efi=debug. Is there any other piece of data I can provide? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/0 ------------------------------------------------------------------------ On 2017-06-04T10:13:53+00:00 julius.bullinger+kernelorg wrote: I can confirm this bug on the same hardware for all current kernel versions from 4.11 on. I tested on Fedora: * kernel-4.11.2-200.vanilla.knurd.1.fc25.x86_64 * kernel-4.11.3-200.fc25.x86_64 * kernel-4.12.0-0.rc2.git0.1.vanilla.knurd.1.fc25.x86_64 All of them suffer from the issue, while 4.10 does not. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/1 ------------------------------------------------------------------------ On 2017-06-04T10:15:41+00:00 julius.bullinger+kernelorg wrote: *** Bug 195975 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/2 ------------------------------------------------------------------------ On 2017-06-15T21:27:16+00:00 matt wrote: Could you try doing a git bisect to track down which commit introduced the issue? I looked at the EFI changes between v4.10 and v4.11 but nothing obvious stood out. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/3 ------------------------------------------------------------------------ On 2017-07-09T00:00:44+00:00 abdo.roig wrote: I bisected the issue to commit ff00d7a32a1b88b772981a13fc198e0d29300666: "mfd: lpc_ich: Add support for SPI serial flash host controller". Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/4 ------------------------------------------------------------------------ On 2017-07-14T09:20:37+00:00 matt wrote: Thanks for bisecting. Re-assigning since this doesn't look like an EFI issue per se. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/5 ------------------------------------------------------------------------ On 2017-07-14T09:21:15+00:00 matt wrote: Mika, can you take a look? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/6 ------------------------------------------------------------------------ On 2017-07-24T09:08:51+00:00 mika.westerberg wrote: Can you attach full dmesg to the bug and then revert ff00d7a32a1b88b772981a13fc198e0d29300666 and attach dmesg of that boot as well? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/7 ------------------------------------------------------------------------ On 2017-07-26T14:01:57+00:00 abdo.roig wrote: Created attachment 257711 dmesg log at 8afda8b2 (good) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/8 ------------------------------------------------------------------------ On 2017-07-26T14:03:09+00:00 abdo.roig wrote: Created attachment 257713 dmesg log at ff00d7a3 (bad) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/9 ------------------------------------------------------------------------ On 2017-07-26T14:05:39+00:00 abdo.roig wrote: I attached the logs you requested. The git hashes in the logs do not match the hash in the kernel version because in order to work-around a gcc7 build problem I cherry-picked 474c9015 on top. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/10 ------------------------------------------------------------------------ On 2017-07-26T14:10:47+00:00 mika.westerberg wrote: Both logs say kernel v4.10 is that expected? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/11 ------------------------------------------------------------------------ On 2017-07-26T14:13:43+00:00 abdo.roig wrote: Yes, this is what git-describe reports. The bug was introduced in the 4.11 merge windows, so git describe reports 4.10-blah-blah. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/12 ------------------------------------------------------------------------ On 2017-07-26T14:32:30+00:00 mika.westerberg wrote: Created attachment 257715 Prevent touching BCR register from lpc_ich.c Can you try the attached patch and see if it makes a difference? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/13 ------------------------------------------------------------------------ On 2017-07-26T14:59:00+00:00 abdo.roig wrote: Yes, it does. With your patch on top of the bad commit, the problem disappears. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/14 ------------------------------------------------------------------------ On 2017-07-27T15:34:28+00:00 mika.westerberg wrote: OK, thanks for testing. I'll prepare proper patch and send it upstream tomorrow. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/15 ------------------------------------------------------------------------ On 2017-10-20T12:18:29+00:00 keigh.rim wrote: I upgraded Ubuntu on my thinkpad yoga machine (1st gen) from 17.04 (kernel 4.10) to 17.10 (kernel 4.13) and this issue is introduced. I also tried Fedora 26 (kernel 4.11) live cd, and noticed the same problem. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/16 ------------------------------------------------------------------------ On 2017-11-11T03:59:39+00:00 josh_bell7 wrote: Hi Mika, this bug also affects me. Has your patch been committed? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/17 ------------------------------------------------------------------------ On 2017-11-11T08:25:32+00:00 mika.westerberg wrote: Yes, it should be included in v4.14-rc1+ Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/18 ------------------------------------------------------------------------ On 2022-12-27T11:08:33+00:00 gecam59 wrote: Whoever is responsible for this should provide a fix or buy me a new laptop. I can't change any BIOS settings. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/668 ** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => Medium -- 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 Boot-Repair: Fix Released Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released 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. Warning: 32bit iso on sourceforge for boot-repair-disk still contains unpatched Kernel. This is especially dangerous if boot-repair fails to repair the system to a bootable state, as there will be no way of applying the Fix detailed below. 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. If you have applied updates, and find that you can not boot the above fixed kernel because of Secure Boot and that the kernel is unsigned, but can still boot another kernel for your system; here's what you can do: 1) Download http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed: $ wget http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed 2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi: $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi 3) Reboot; you should now be able to load the new unsigned kernel that allows fixing firmware / SPI. 4) Once you're satisfied that things work; boot to Ubuntu with a standard, signed kernel, and re-install the right GRUB version for your system: $ sudo grub-install --- 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 Yoga 3 11" 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 Toshiba Satellite L70-A-13M Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix) Acer Aspire E3-111-C0UM HP 14-r012la Fujitsu Q584 (unable to fix due to non booting OS on the tablet) --- 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 regarding this issue. Thank you!! To manage notifications about this bug go to: https://bugs.launchpad.net/boot-repair/+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
