Skip to content

Hard lockups using microcode releases 20191115, sig=0x806ec, on i5-8365U #24

Closed

Description

@vicamo
microcode: sig=0x806ec, pf=0x80, revision=0xc6 # good
microcode: sig=0x806ec, pf=0x80, revision=0xca # hang

This hangs Linux warm/cold boot for all versions with non-uniformed fail rate. With v5.2 or older, it's almost 100% reproducible; with v5.3 or above, it's much less likely. With kernel boot parameters initcall_debug ignore_loglevel=1 earlyprintk=efi earlycon=efifb, it shows it's mostly locked up inside lock access in console_init(), but it may also sometimes happen when early console is not even initialized. On Ubuntu Bionic, the first known failing version of intel-microcode package is 3.20191115.1ubuntu0.18.04.1. By reverting this package to any prior revision and such hard lockup is then gone. Another possible temporary work-around is to disable SMP by passing nosmp to kernel.

This is currently reproducible on Intel i5-8365U, model 142, stepping 12.

Activity

  1. vicamo commented on Feb 11, 2020

    @vicamo
    Author

    Also reported to Ubuntu Launchpad: https://bugs.launchpad.net/bugs/1862751

  2. esyr-rh commented on Feb 11, 2020

    @esyr-rh
    Contributor

    (from the linked launchpad bug)
    dmi.chassis.vendor: Dell Inc.
    dmi.product.name: Latitude 5410
    dmi.product.sku: 09C9
    dmi.bios.date: 01/29/2020
    dmi.bios.vendor: Dell Inc.
    dmi.bios.version: 0.0.7

  3. vicamo commented on Feb 12, 2020

    @vicamo
    Author

    Copy from launchpad: reverting intel-ucode/06-8e-0c to its prior revision 0xC6 would fix this issue.

  4. anthonywong commented on Feb 27, 2020

    @anthonywong

    @intel folks
    Just wondering if this issue has been received and acknowledged, and if a microcode fix will be coming?

  5. whpenner commented on Mar 18, 2020

    @whpenner

    We are looking into the issue. I'll send out an update as soon as I have more.

  6. hmh commented on Jun 10, 2020

    @hmh

    Another similar issue has been closed, with the update from 0xca to 0xd6 present in the newest release (20200609).

    @vicamo, can you please test if microcode revision 0xd6 (present on microcode 20200609) fixes your issue?

  7. paulmenzel commented on Jun 11, 2020

    @paulmenzel

    Instead of nosmp, maxcpus=1 or acpi=off or noapic worked for me in another case.

  8. vicamo commented on Jun 12, 2020

    @vicamo
    Author

    @vicamo, can you please test if microcode revision 0xd6 (present on microcode 20200609) fixes your issue?

    This can still be reproduced with 20200609 release.

    microcode: microcode updated early to revision 0xd6, date = 2020-04-23
    microcode: sig=0x806ec, pf=0x80, revision=0xd6
    microcode: Microcode Update Driver: v2.2.
    
  9. hmh commented on Jun 13, 2020

    @hmh

    There might be a separate issue on 20200609.

    report on Debian downstream:
    https://bugs.debian.org/962757

    From Debian butg report:
    2019115-20200520 works (rev 0xca), which is the opposite of the data on this report.
    20200609 (rev 0xd6) hangs on boot.

    There might be multiple issues causing hangs with recent Linux kernels and microcode 0x806ec.

  10. esyr-rh commented on Jun 16, 2020

    @esyr-rh
    Contributor

    There's also an observation that disabling Turbo helps with hangs during microcode update to revision 0xca on another Dell system (Dell M7720) with a 06-9e-0a/0x906ea CPU (Intel(R) Xeon(R) E-2186M): https://bugzilla.redhat.com/show_bug.cgi?id=1846097

  11. whpenner commented on Jun 16, 2020

    @whpenner

    An issue was identified with the microcode update 0xCA for cpuid 0x806Ex and 906Ex products. Please update to 0xD6 or later.

  12. paulmenzel commented on Jun 16, 2020

    @paulmenzel

    An issue was identified with the microcode update 0xCA for cpuid 0x806Ex and 906Ex products. Please update to 0xD6 or later.

    Where can 0xD6 be found?

  13. esyr-rh commented on Jun 16, 2020

    @esyr-rh
    Contributor
  14. hmh commented on Jun 16, 2020

    @hmh

    @whpenner: we have reports of update 0xd6 for signature 0x806ec also causing hangs, here:
    https://bugs.debian.org/962757

    Should we open a separate issue ?

  15. stevebeattie commented on Jun 16, 2020

    @stevebeattie

    @hmh I think so, I also have a privately received report of a failure with 0x806ec / WHL-U i5-8365U and 0xd6.

  16. whpenner commented on Jun 16, 2020

    @whpenner

    Yes, we should keep the 806Ex and 906Ex items separate from SKL, so a new issue would be better for tracking.

  17. changed the title [-]Hard lockups using microcode releases 20191115 on i5-8365U[/-] [+]Hard lockups using microcode releases 20191115, sig=0x806ec, on i5-8365U[/+] on Jun 25, 2020
  18. esyr-rh commented on Nov 11, 2020

    @esyr-rh
    Contributor

    06-8e-0c microcode has been updated to revision 0xde in the microcode-20201110 release, does the newer microcode revision help?

  19. hmh commented on Jan 24, 2021

    @hmh

    @vicamo, can you help us check if the microcode update in the latest microcode release fixes this issue ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions