Tyler's amended kernel got me out of a hole today, thanks for the work.
I've told my users not to update kernel until this is in the Ubuntu

One observation from me is that VirtualBox 5.2.8 causes my HP Z230
(running Ubuntu 16.04.4) to crash and reboot when I try to start a VM.
Not a showstopper for me, and I need to dig around for some clues, but
wondered if anyone else had this problem.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-

Status in intel-microcode package in Ubuntu:
Status in linux package in Ubuntu:
Status in intel-microcode source package in Trusty:
Status in linux source package in Trusty:
  Fix Committed
Status in intel-microcode source package in Xenial:
Status in linux source package in Xenial:
  Fix Committed
Status in intel-microcode source package in Artful:
Status in linux source package in Artful:
  Fix Committed

Bug description:

   * Some systems experience kernel lockups after updating to the latest 
     package or when receiving updated microcode from a BIOS update.

   * In many cases, the lockups occur before users can reach the login screen 
which makes
     it very difficult to debug/workaround.

  [Test Case]

   * The most reliable test case currently known is to install the sssd 
package. Lockups
     may occur during package installation (disable IBPB by writing 0 to
     /proc/sys/kernel/ibpb_enabled to prevent this from happening). A lockup 
will most
     likely occur just after booting the system up as the lock screen is 

  [Regression Potential]

   * The fix is in the task switching code of the kernel so complexity of the 
change is
     relatively high.

  [Original Report]

  I don't know if this is a problem with the kernel or the microcode,
  but we have a significant number of computers in our organization (on
  both 16.04 and 17.10) that fail if they have both updated.  Booting
  with either linux-image-4.13.0-36-generic or intel-microcode
  3.20180108.0+really20170707ubuntu17.10.1 allows all these computers to

  ## Workaround ##
  1. Boot the system with the dis_ucode_ldr kernel boot parameter to temporary 
avoid the problem:
  2. Install the previous version of package from
  3. (Optional) Hold the package so that it won't be upgraded accidentally
     sudo apt-mark hold intel-microcode

To manage notifications about this bug go to:

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

Reply via email to