[Bug 1742696] Re: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash
*WORKING* Ok, was on -36 hence thought -37 would be the next one. Tested with linux-image-4.13.0-38-generic/artful-proposed linux-image-extra-4.13.0-38-generic/artful-proposed and fix worked. BIOS is writable after applying fix kernel. Stays writable after returning to 4.13.0-38. ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742696 Title: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742696] Re: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash
*NOT WORKING* So checked to install from artful-proposed the following packages: linux-image-4.13.0-37-generic/artful-proposed linux-image-extra-4.13.0-37-generic/artful-proposed Following sequence: 1. Install fix kernel from bug #1734147 2. Reboot with fix kernel 3. Reboot into BIOS, doing some changes 4. Continue reboot with fix kernel (BIOS reset message disappeared) 5. Reboot into BIOS, check if changes have been retained, result: YES) 6. Continue reboot with fix kernel 7. Install artful-proposed kernel (by sudo apt-get install linux-image-4.13.0-37-generic/artful-proposed and sudo apt-get install linux-image-extra-4.13.0-37-generic/artful-proposed) 8. Reboot artful-proposed kernel 9. Reboot artful-proposed Kernel (BIOS reset message reappears) To make sure, I checked to install Josephs Kernel (from #5) in Step 7. Result after 3 reboots: BIOS reset message is still gone. Hence something is not working correctly in the artful-proposed kernel (or my tests). Any ideas? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742696 Title: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742696] Re: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash
@ Joseph (Or anyone who knows), can you help me our here. As I am not developer, I am not getting on how Ubuntu versioning and Kernel updates work. Why is there an artful-proposed needed? Is the 4.13 Kernel versioned under artful, but still used in Xenial? Then I would need to add the artful-proposed to my Xenial sources? Sounds weird, but I am ok with trying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742696 Title: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742696] Re: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash
#5 Using the test kernel I can confirm, that the BIOS is writable, keeps settings over reboot and the bios changed message has disappeared. Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742696 Title: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742696] Re: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash
So how are we going on with this? As it seems I am the only one so far in this unique combination. Hence it might be too much asked to cherry pick the 4.13 kernels just for me? I could try to build by current kernel (4.13.0-26) with patches and then stay on that one until 4.14 gets available? (never done that but would be worth a try?) If more people show up here with the issue the cherry pick is still an option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742696 Title: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
#524, #525 Created Bug #1742696 "Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug" Let's continue discussion over there -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742696] [NEW] Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash
Public bug reported: New bug forked out of Bug #1734147 "corrupted BIOS due to Intel SPI bug in kernel Edit" When trying to apply the proposed fix in Bug #1734147 to a Lenovo Yoga with Serial Flash s25fl064k, the actual fix works, however reverting back to original available Kernel <4.14.x again locks the BIOS for write. How to identify chip: Using the Fix Kernel from Bug #1734147 the kernel log will show intel-spi entries. In lower part serial is shown as below: intel-spi intel-spi: s25fl064k (8192 Kbytes) Additional Information: Lenovo Yoga running Linux Mint 18.3 (based on Xenial 16.04) Bug #1734147 occured when trying Ubuntu 17.10 Explanation by Mika Westerberg (Bug #1734147, Comment #524) "commit d9018976cdb6 is missing with this particular BIOS/system because every time you boot the system, the BIOS resets to default when it finds BCR register is changed. This is different issue than the CMP=1 issue most of the users have reported. This one also is not permanent so everything is fine as long as you don't touch that BCR register. In this case you either need to always boot to a kernel where that fix (d9018976cdb6) is included or blacklist lpc_ich.ko. Ubuntu v4.14.x kernels have that fix included so you might want to take one of them or build your own." New bug requested to discuss this separate from main Bug #1734147 Anthony Wong (Bug #1734147, Comment #525) "Looks like we need to cherry-pick it to 4.13 after all. Christian, do you mind opening a new bug for your issue? We should continue the discussion and fix over there." ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1742696/+attachment/5035109/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742696 Title: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742696] Re: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742696/+attachment/5035110/+files/lspci-vnvn.log ** Summary changed: - Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug + Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742696 Title: Commit d9018976cdb6 missing in Kernels <4.14.x preventing lasting fix of Intel SPI bug on certain serial flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
#519 no, I did not compile the kernel yet. So far only used the one provided in the fix description. As for repairing -like with the fix kernel- this won't help, right? It would just be an option to go away from the repository kernels and compile my own one until the commit is included in the repository kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
#516, #517 no change in 4.13.0-26. as soon as I booted once, BIOS is back to ro. If the commit d9018976cdb6 is missing, what to do? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
#511, 512, 513 I switched to 4.13.0-21, which was stated to have fixed the problem and should be safe as in multiple posts above (e.g. #350, #484, ...). I cannot say, if mint need to do something as well, but it comes right off the ubuntu repos (see below). linux-image-4.13.0-21-generic: Installiert: 4.13.0-21.24~16.04.1 Installationskandidat: 4.13.0-21.24~16.04.1 Versionstabelle: *** 4.13.0-21.24~16.04.1 500 500 http://ftp.fau.de/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status #515 Sadly I have Windows only in a VM. What are you looking for? Can I get information otherwise? 4.13.0-26 is just available for me, will install it, try that, try the fix again and see what happens, then report back -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
#509 At least my BIOS is read only. I can't change a single setting without it reverting on next boot. It just says "Configuration changed - restarting system." and I have the old settings again. :-( When using the patched kernel, that message is gone and I can edit and save BIOS changes over reboot. As soon as I use the unpatched kernel. I am back on the symptom above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
@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=0x [ 18.936224] intel-spi intel-spi: FDATA(0)=0x0083 [ 18.936226] intel-spi intel-spi: FDATA(1)=0x [ 18.936228] intel-spi intel-spi: FDATA(2)=0x [ 18.936230] intel-spi intel-spi: FDATA(3)=0x [ 18.936232] intel-spi intel-spi: FDATA(4)=0x [ 18.936233] intel-spi intel-spi: FDATA(5)=0x [ 18.936235] intel-spi intel-spi: FDATA(6)=0x [ 18.936237] intel-spi intel-spi: FDATA(7)=0x [ 18.936239] intel-spi intel-spi: FDATA(8)=0x [ 18.936241] intel-spi intel-spi: FDATA(9)=0x [ 18.936242] intel-spi intel-spi: FDATA(10)=0x [ 18.936244] intel-spi intel-spi: FDATA(11)=0x [ 18.936246] intel-spi intel-spi: FDATA(12)=0x [ 18.936248] intel-spi intel-spi: FDATA(13)=0x [ 18.936250] intel-spi intel-spi: FDATA(14)=0x [ 18.936252] intel-spi intel-spi: FDATA(15)=0x [ 18.936254] intel-spi intel-spi: FRACC=0x4a4b [ 18.936256] intel-spi intel-spi: FREG(0)=0x [ 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)=0x7fff [ 18.936263] intel-spi intel-spi: FREG(4)=0x7fff [ 18.936265] intel-spi intel-spi: PR(0)=0x [ 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: 0x00b3 limit: 0x00bf [W.] [ 18.936290] intel-spi intel-spi: 02 base: 0x00aa1000 limit: 0x00ac [W.] [ 18.936292] intel-spi intel-spi: 03 base: 0x00aa limit: 0x00aa0fff [W.] [ 18.936294] intel-spi intel-spi: 04 base: 0x0080 limit: 0x00a9 [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: 0x0080 limit: 0x00bf [ 18.936301] intel-spi intel-spi: 02 base: 0x1000 limit: 0x007f [ 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] 0x-0x00c0 : "BIOS" [ 18.951044] mtd: partition "BIOS" extends beyond the end of device "intel-spi" -- size truncated to 0x80 [ 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubunt
[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
NOT WORKING I tried it on my Lenovo Yoga Thinkpad (20C0) with Linux Mint 18.3 (The one I managed to use the 17.10 USB on to mess up the BIOS). When installing the Kernels provided above, I can again do changes in BIOS and they stay over reboot. However as soon as I revert back to 4.13.0-21 Kernel, the Problem is back. Any ideas? Regards Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Hi there, so it feels I am a special case of this. I am running Linux Mint 18.3 as my main distro. However to check a problem with standby based on Ubuntu I tried to run Ubuntu 17.10 from USB. Since then I have the same trouble to save my BIOS, etc. However Linux Mint is starting from hard disk without problems. I read the possible repair solution and before trying to do anything, I wanted to check, if it is likely that this kernel will work with Linux Mint 18.3, which is based on Ubuntu 16.04? Highest available Kernel by package manager is 4.13.0-21 right now. Regards Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520965] Re: Lenovo Helix does not wake up from suspend
Hi Christopher, not sure if I understand. Do you have a definition page of the different kinds of kernels you mentioned? With repository kernel I would understand an available kernel via repository sources. However would Linux Mint be considered as a 3rd party? Next question would be which version is preferred? The latest available one? (In my case 4.13.0-16.19, running right now 4.10.0-38.42) Regards Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520965 Title: Lenovo Helix does not wake up from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520965] Re: Lenovo Helix does not wake up from suspend
I disagree to move this to invalid (Not only still I have that bug as well), as it was already on triaged, hence a problem to be looked in. Would it make sense, that I check with the latest kernel? Regards Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520965 Title: Lenovo Helix does not wake up from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520965] Re: Lenovo Helix does not wake up from suspend
Hi there, I have the same behaviour on a Lenovo Thinkpad Yoga, running - Linux Mint 18.2 (hence Ubuntu 16.04) - 4.10.0-38-generic - Lenovo BIOS Version: GQET52WW (1.32), Release Date: 05/04/2017 - intel-microcode 3.20170707.1~ubuntu16.04.0 Only difference is, that standby randomly works (maybe 4 out of 10 times) What is the status of this? It seems abandoned for a year now without a solution. Can I help somehow with debug information? Regards Chris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520965 Title: Lenovo Helix does not wake up from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
