intel-microcode 3.20180312.0~ubuntu17.10.1 fails to boot on E3-1505M

Bug #1759997 reported by kolya
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
High
Unassigned
Artful
Triaged
High
Unassigned

Bug Description

I have Lenovo P50 with E3-1505M. After intel-microcode 3.20180312.0~ubuntu17.10.1 is installed it hangs during boot some time after graphic display interface - exact time of hang differs from boot to boot. Rolling intel-microcode back to 3.20170707.1 fixes the problem.

This happens on Ubuntu 17.10 with 4.13.0-37-generic and 4.13.0-36-generic kernels.
---
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: kolya 2039 F.... pulseaudio
 /dev/snd/controlC1: kolya 2039 F.... pulseaudio
 /dev/snd/pcmC0D0p: kolya 2039 F...m pulseaudio
 /dev/snd/controlC0: kolya 2039 F.... pulseaudio
CurrentDesktop: MATE
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=UUID=a1a81ad4-e4bc-4115-b60f-07f02f93ecf6
InstallationDate: Installed on 2016-02-20 (768 days ago)
InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: LENOVO 20EN001SUS
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-37-generic N/A
 linux-backports-modules-4.13.0-37-generic N/A
 linux-firmware 1.169.3
Tags: artful
Uname: Linux 4.13.0-37-generic x86_64
UpgradeStatus: Upgraded to artful on 2017-10-29 (152 days ago)
UserGroups: dialout kismet libvirt sudo wireshark
_MarkForUpload: True
dmi.bios.date: 09/28/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET73W (1.46 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EN001SUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN1EET73W(1.46):bd09/28/2017:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P50
dmi.product.name: 20EN001SUS
dmi.product.version: ThinkPad P50
dmi.sys.vendor: LENOVO

kolya (mar-kolya)
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1759997

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: artful
Revision history for this message
kolya (mar-kolya) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
kolya (mar-kolya) wrote : CRDA.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote : CurrentDmesg.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote : IwConfig.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote : JournalErrors.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote : Lspci.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote : Lsusb.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote : ProcEnviron.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote : ProcInterrupts.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote : ProcModules.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote : PulseList.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote : RfKill.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
kolya (mar-kolya) wrote : UdevDb.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote : WifiSyslog.txt

apport information

Revision history for this message
kolya (mar-kolya) wrote :

This is probably a duplicate of #1746418. Confusing part here was that the problem started appearing after microcode update.

Revision history for this message
o.walbert (o-walbert) wrote :

I have the same problem with linux-image-4.13.0-38 on xenial and i7-3520M. It's unbootable right now. The only workaround is noibpb as boot parameter.

Changed in linux (Ubuntu):
importance: Undecided → High
Changed in linux (Ubuntu Artful):
status: New → Triaged
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Changed in linux (Ubuntu Artful):
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.