|
Bugzilla – Full Text Bug Listing |
| Summary: | ucode-intel update in TW snapshot 0629 breaks system start-up | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Robby Engelmann <robby.engelmann> |
| Component: | Basesystem | Assignee: | Cristian Rodríguez <crrodriguez> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P1 - Urgent | CC: | crrodriguez, dimstar, dmueller, forgotten__FQzTs08vU, jeffm, mmarek, robby.engelmann, tiwai, trenn |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
hwinfo
dracut output dmidecode |
||
|
Description
Robby Engelmann
2016-07-01 12:53:56 UTC
Created attachment 682820 [details]
hwinfo
some more infos: I am using a crypt-lvm setup on skylake. Zaitor mentioned that he already updated two intel machines without issue. He did not use crypt-lvm setup on both. This is an autogenerated message for OBS integration: This bug (987358) was mentioned in https://build.opensuse.org/request/show/405914 Factory / ucode-intel Well.. unless it is a problem in the kernel side that loads the microcrode..or a problem in dracut that creates a microcode blob that makes the kernel choke..there is nothing we can do about it other than reverting it. it is closed source.. BTW.. I updated skylake box with CPU Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz With no problem whatsoever.. what CPU on which motherboard breaks ? Is the BIOS of the machine up2date as well ? I bought a Tuxedo InfinityBook v2 in April this year. Thus, I would think the BIOS is up-to-date. I do not know how to check this. Did anybody try to update it on an crypt-lvm setup machine? And will add the dracut output from the update here. Created attachment 682889 [details]
dracut output
(In reply to Robby Engelmann from comment #6) > I bought a Tuxedo InfinityBook v2 in April this year. Thus, I would think > the BIOS is up-to-date. I do not know how to check this. > Did anybody try to update it on an crypt-lvm setup machine? > And will add the dracut output from the update here. Tuxedo should supply firmware updates.. crypt-lvm is not involved in your issue..your system fails to load the initrd in the first place.. Is there a way to figure out what goes wrong here? As far as I know I am the only one hit by this bug. I would expect that the bios is up to date on a newly bought notebook. the BIOS is quite fresh: BIOS Information Vendor: American Megatrends Inc. Version: 5.11 Release Date: 04/08/2016 Created attachment 682937 [details]
dmidecode
Hi Michal.. do you know how to debug a hang during the initrd loading or the early microcode stuff ? (In reply to Cristian Rodríguez from comment #12) > Hi Michal.. do you know how to debug a hang during the initrd loading or the > early microcode stuff ? Try to pass dis_ucode_ldr boot option. This will disable the early microcode loading. If this helps, it implies that the ucode is the culprit. You can try to downgrade the ucode-intel package. Try booting with ignore_loglevel on the kernel command line. (In reply to Takashi Iwai from comment #13) > (In reply to Cristian Rodríguez from comment #12) > > Hi Michal.. do you know how to debug a hang during the initrd loading or the > > early microcode stuff ? > > Try to pass dis_ucode_ldr boot option. This will disable the early > microcode loading. > > If this helps, it implies that the ucode is the culprit. You can try to > downgrade the ucode-intel package. I updated to the snapshot containing the updated ucode-intel package --> boot hang I updated to the snapshot containing the updated ucode-intel package but this time updated all packages except for ucode-intel --> no boot hang --> thus, it should be clear that the ucode package was the culprit. There is a new version: 20160714 which should fix the issue. I pushed it into Base:System and submitted it against openSUSE:Factory. Please give it a try. I already close this one fixed, please re-open if you see issues. two questions: 1. I only need to pick the rpm and install it via rpm -i ? 2. how can I recover the system, if it still does not work (without reinstalling my whole system) then I will give it a try.... (In reply to Robby Engelmann from comment #17) > two questions: > > 1. I only need to pick the rpm and install it via rpm -i ? Usually yes. In doubt, rebuild initrd manually (e.g. call mkinitrd). > 2. how can I recover the system, if it still does not work (without > reinstalling my whole system) You can skip ucode loading by passing dis_ucode_ldr boot option, as mentioned in comment 13. > then I will give it a try.... This is an autogenerated message for OBS integration: This bug (987358) was mentioned in https://build.opensuse.org/request/show/412561 Factory / ucode-intel works! [ 0.000000] microcode: microcode updated early to revision 0x9e, date = 2016-06-22 openSUSE-RU-2016:2235-1: An update that has two recommended fixes can now be installed. Category: recommended (moderate) Bug References: 958562,987358 CVE References: Sources used: openSUSE Leap 42.1 (src): ucode-intel-20160714-5.1 |