*** This bug is a duplicate of bug 1829620 ***
    https://bugs.launchpad.net/bugs/1829620

Thanks for testing, Jackneill.

To explain, the "dis_ucode_ldr" option disables loading of microcode
updates by Linux. Microcode updates are are binary blobs (no source code
is available) which modify operation of a CPU until the next reboot.
They are supplied by CPU manufacturers / vendors to mainboard
manufacturers / vendors and are now more commonly shared with operating
systems, too. Linux supports loading them into the CPU during early
boot.

Unfortunately, with the latest microcode update (which was released by
the same time as the kernel updates you reported about on 19.04 and
18.04 LTS), your CPU seems to not behave reliably, causing a high
percentage of your boots into Ubuntu to fail. This root cause is
confirmed by using the dis_ucode_ldr kernel boot parameter, which, as
you report, ensures your system boots up fine every time.

I will now mark this bug report as a duplicate of bug #1829620 (I am
convinced both Kai-Heng and TJ meant to point to the same bug report)
and suggest you keep using "dis_ucode_ldr" temporarily until Intel
releases a new microcode update and it becomes available in Ubuntu via
https://packages.ubuntu.com/search?keywords=intel-microcode - the status
of bug #1829620 should change to "fix released" at that time. Feel free
to address me on IRC (#ubuntu) in case of any questions of a support
nature, or add to the bug report if you would like to report more
details on this issue.

** This bug has been marked a duplicate of bug 1829620
   intel-microcode on ASUS makes kernel stuck during loading initramfs on 
bionic-updates, bionic-security

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829402

Title:
  Purple screen hangup during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Specs:
  Ubuntu 19.04 fresh install, everything updated
  Firmware is latest (Bios version 300)
  Asus vivobook s14 
  LVM disk encryption

  Steps to reproduce:
  - Install ubuntu 19.04/18.10
  - Reboot
  - Purple screen indefinitely

  Setting kernel cmdline args only to ro nomodeset seems solves it.

  After some debugging session with #ubuntu with different cmdline args,
  it seems now the default one works too. I have not edited anything,
  but now i am unable to reproduce it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  markbartos   1778 F.... pulseaudio
  Date: Thu May 16 17:15:07 2019
  InstallationDate: Installed on 2019-05-16 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3526 IMC Networks 
   Bus 001 Device 002: ID 13d3:56c1 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X430FA_S430FA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware                            1.178.1
  SourcePackage: linux
  StagingDrivers: r8822be
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X430FA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X430FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX430FA.300:bd11/22/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX430FA_S430FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX430FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X430FA_S430FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829402/+subscriptions

-- 
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