[19.10] Boot hangs at "loading initial ramdisk"

[Fredrik Normann]

[19.10] Boot hangs at "loading initial ramdisk"

So after completing the upgrade from 19.04 to 19.10, my computer got stuck on the solid purple Grub screen upon reboot. After getting into the grub menu on next boot and booting from advanced options, I see that it gets to "loading initial ramdisk" and then just hangs forever. I am able to boot without issues on the old kernel (5.0.0-32-generic), but not the one that got installed with the upgrade (5.3.0-18-generic).

Things I've tried based on what worked for other people who got this problem (though I haven't found anyone who has it specifically with 19.10):

    acpi=off

    dis_ucode_ldr

    disabling secure boot

    recovery mode

    making sure all packages are up to date

I'm kind of at a loss of what to do, other than just keep using the old kernel. (which presumably might cause problems at some point?)

I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10 resulted in unable to boot system.

Hardware Dell XPS 9550

# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.
91 structures occupying 5683 bytes.
Table at 0x000E0000.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
 Vendor: Dell Inc.
 Version: 1.11.2
 Release Date: 07/30/2019
 Address: 0xF0000
 Runtime Size: 64 kB
 ROM Size: 16 MB
 Characteristics:
  PCI is supported
  PNP is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  EDD is supported
  5.25"/1.2 MB floppy services are supported (int 13h)
  3.5"/720 kB floppy services are supported (int 13h)
  3.5"/2.88 MB floppy services are supported (int 13h)
  Print screen service is supported (int 5h)
  8042 keyboard services are supported (int 9h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  ACPI is supported
  USB legacy is supported
  Smart battery is supported
  BIOS boot specification is supported
  Function key-initiated network boot is supported
  Targeted content distribution is supported
  UEFI is supported
 BIOS Revision: 1.11

Handle 0x0001, DMI type 1, 27 bytes
System Information
 Manufacturer: Dell Inc.
 Product Name: XPS 15 9550
 Version: Not Specified
 Serial Number: 5QRHRF2
 UUID: 4c4c4544-0051-5210-8048-b5c04f524632
 Wake-up Type: Power Switch
 SKU Number: 06E4
 Family: XPS

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
 Manufacturer: Dell Inc.
 Product Name: 0N7TVV
 Version: A01
 Serial Number: /5QRHRF2/CN129636CS0026/
 Asset Tag: Not Specified
 Features:
  Board is a hosting board
  Board is replaceable
 Location In Chassis: Not Specified
 Chassis Handle: 0x0003
 Type: Motherboard
 Contained Object Handles: 0

Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
 Manufacturer: Dell Inc.
 Type: Laptop
 Lock: Not Present
 Version: Not Specified
 Serial Number: 5QRHRF2
 Asset Tag: Not Specified
 Boot-up State: Safe
 Power Supply State: Safe
 Thermal State: Safe
 Security Status: None
 OEM Information: 0x00000000
 Height: Unspecified
 Number Of Power Cords: 1
 Contained Elements: 0
 SKU Number: Laptop

Handle 0x0004, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JUSB1
 Internal Connector Type: None
 External Reference Designator: USB1
 External Connector Type: Access Bus (USB)
 Port Type: USB

Handle 0x0005, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JUSB2
 Internal Connector Type: None
 External Reference Designator: USB2
 External Connector Type: Access Bus (USB)
 Port Type: USB

Handle 0x0006, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JUSBC1
 Internal Connector Type: None
 External Reference Designator: USB TYPEC
 External Connector Type: Access Bus (USB)
 Port Type: USB

Handle 0x0007, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JHDMI1
 Internal Connector Type: None
 External Reference Designator: HDMI
 External Connector Type: Other
 Port Type: Video Port

Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JCR
 Internal Connector Type: None
 External Reference Designator: CARD READER
 External Connector Type: Other
 Port Type: Other

Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JHP1
 Internal Connector Type: None
 External Reference Designator: Audio JACK
 External Connector Type: Mini Jack (headphones)
 Port Type: Audio Port

Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JFAN1 - CPU FAN1
 Internal Connector Type: Other
 External Reference Designator: Not Specified
 External Connector Type: None
 Port Type: Other

Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JFAN2 - CPU FAN2
 Internal Connector Type: Other
 External Reference Designator: Not Specified
 External Connector Type: None
 Port Type: Other

Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JTP - TOUCH PAD CONN
 Internal Connector Type: Other
 External Reference Designator: Not Specified
 External Connector Type: None
 Port Type: Other

Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JEDP - EDP CONN
 Internal Connector Type: Other
 External Reference Designator: Not Specified
 External Connector Type: None
 Port Type: Other

Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JNGFF1 - WLAN CONN
 Internal Connector Type: Other
 External Reference Designator: Not Specified
 External Connector Type: None
 Port Type: Other

Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JNGFF2 - SSD CONN
 Internal Connector Type: Other
 External Reference Designator: Not Specified
 External Connector Type: None
 Port Type: Other

Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: BAT100 - BATTERY CONN
 Internal Connector Type: Other
 External Reference Designator: Not Specified
 External Connector Type: None
 Port Type: Other

Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JKB - KEYBOARD CONN
 Internal Connector Type: Other
 External Reference Designator: Not Specified
 External Connector Type: None
 Port Type: Other

Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JSPK1 - SPEAKER CONN
 Internal Connector Type: Other
 External Reference Designator: Not Specified
 External Connector Type: None
 Port Type: Other

Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JRTC - RTC CONN
 Internal Connector Type: Other
 External Reference Designator: Not Specified
 External Connector Type: None
 Port Type: Other

Handle 0x0014, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JTS - TOUCH SCREEN CONN
 Internal Connector Type: Other
 External Reference Designator: Not Specified
 External Connector Type: None
 Port Type: Other

Handle 0x0015, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: JHDD - HDD CONN
 Internal Connector Type: Other
 External Reference Designator: Not Specified
 External Connector Type: None
 Port Type: Other

Handle 0x0016, DMI type 8, 9 bytes
Port Connector Information
 Internal Reference Designator: ADP100 - AC JACK
 Internal Connector Type: Other
 External Reference Designator: Not Specified
 External Connector Type: None
 Port Type: Other

Handle 0x0017, DMI type 10, 6 bytes
On Board Device Information
 Type: Video
 Status: Enabled
 Description: "Intel HD Graphics"

Handle 0x0018, DMI type 11, 5 bytes
OEM Strings
 String 1: Dell System
 String 2: 1[06E4]
 String 3: 3[1.0]
 String 4: 12[www.dell.com]
 String 5: 14[1]
 String 6: 15[0]
 String 7: 27[12502210574]

Handle 0x0019, DMI type 12, 5 bytes
System Configuration Options
 Option 1: To Be Filled By O.E.M.

Handle 0x001A, DMI type 15, 35 bytes
System Event Log
 Area Length: 4 bytes
 Header Start Offset: 0x0000
 Header Length: 2 bytes
 Data Start Offset: 0x0002
 Access Method: Indexed I/O, one 16-bit index port, one 8-bit data port
 Access Address: Index 0x046A, Data 0x046C
 Status: Invalid, Not Full
 Change Token: 0x00000000
 Header Format: No Header
 Supported Log Type Descriptors: 6
 Descriptor 1: End of log
 Data Format 1: OEM-specific
 Descriptor 2: End of log
 Data Format 2: OEM-specific
 Descriptor 3: End of log
 Data Format 3: OEM-specific
 Descriptor 4: End of log
 Data Format 4: OEM-specific
 Descriptor 5: End of log
 Data Format 5: OEM-specific
 Descriptor 6: End of log
 Data Format 6: OEM-specific

Handle 0x001B, DMI type 21, 7 bytes
Built-in Pointing Device
 Type: Touch Pad
 Interface: Bus Mouse
 Buttons: 2

Handle 0x0020, DMI type 25, 9 bytes
 System Power Controls
 Next Scheduled Power-on: *-* 00:00:00

Handle 0x0021, DMI type 32, 20 bytes
System Boot Information
 Status: No errors detected

Handle 0x0022, DMI type 34, 11 bytes
Management Device
 Description: LM78-1
 Type: LM78
 Address: 0x00000000
 Address Type: I/O Port

Handle 0x0024, DMI type 36, 16 bytes
Management Device Threshold Data
 Lower Non-critical Threshold: 1
 Upper Non-critical Threshold: 2
 Lower Critical Threshold: 3
 Upper Critical Threshold: 4
 Lower Non-recoverable Threshold: 5
 Upper Non-recoverable Threshold: 6

Handle 0x0026, DMI type 36, 16 bytes
Management Device Threshold Data
 Lower Non-critical Threshold: 1
 Upper Non-critical Threshold: 2
 Lower Critical Threshold: 3
 Upper Critical Threshold: 4
 Lower Non-recoverable Threshold: 5
 Upper Non-recoverable Threshold: 6

Handle 0x0028, DMI type 36, 16 bytes
Management Device Threshold Data

Handle 0x002E, DMI type 41, 11 bytes
Onboard Device
 Reference Designation: Onboard IGD
 Type: Video
 Status: Enabled
 Type Instance: 1
 Bus Address: 0000:00:02.0

Handle 0x002F, DMI type 41, 11 bytes
Onboard Device
 Reference Designation: Onboard LAN
 Type: Ethernet
 Status: Enabled
 Type Instance: 1
 Bus Address: 0000:00:19.0

Handle 0x0030, DMI type 41, 11 bytes
Onboard Device
 Reference Designation: Onboard 1394
 Type: Other
 Status: Enabled
 Type Instance: 1
 Bus Address: 0000:03:1c.2

Handle 0x0031, DMI type 248, 9 bytes
OEM-specific Type
 Header and Data:
  F8 09 31 00 00 00 00 00 01
 Strings:
  BDF_RV_0519

Handle 0x0032, DMI type 255, 8 bytes
OEM-specific Type
 Header and Data:
  FF 08 32 00 01 02 00 00
 Strings:
  _SIDOhoHKb1R8FKF
  06E4
  _SIDAvf90w7wKZiZ
  DELL

Handle 0x0033, DMI type 7, 19 bytes
Cache Information
 Socket Designation: L1 Cache
 Configuration: Enabled, Not Socketed, Level 1
 Operational Mode: Write Back
 Location: Internal
 Installed Size: 128 kB
 Maximum Size: 128 kB
 Supported SRAM Types:
  Synchronous
 Installed SRAM Type: Synchronous
 Speed: Unknown
 Error Correction Type: Parity
 System Type: Data
 Associativity: 8-way Set-associative

Handle 0x0034, DMI type 7, 19 bytes
Cache Information
 Socket Designation: L1 Cache
 Configuration: Enabled, Not Socketed, Level 1
 Operational Mode: Write Back
 Location: Internal
 Installed Size: 128 kB
 Maximum Size: 128 kB
 Supported SRAM Types:
  Synchronous
 Installed SRAM Type: Synchronous
 Speed: Unknown
 Error Correction Type: Parity
 System Type: Instruction
 Associativity: 8-way Set-associative

Handle 0x0035, DMI type 7, 19 bytes
Cache Information
 Socket Designation: L2 Cache
 Configuration: Enabled, Not Socketed, Level 2
 Operational Mode: Write Back
 Location: Internal
 Installed Size: 1024 kB
 Maximum Size: 1024 kB
 Supported SRAM Types:
  Synchronous
 Installed SRAM Type: Synchronous
 Speed: Unknown
 Error Correction Type: Single-bit ECC
 System Type: Unified
 Associativity: 4-way Set-associative

Handle 0x0036, DMI type 7, 19 bytes
Cache Information
 Socket Designation: L3 Cache
 Configuration: Enabled, Not Socketed, Level 3
 Operational Mode: Write Back
 Location: Internal
 Installed Size: 6144 kB
 Maximum Size: 6144 kB
 Supported SRAM Types:
  Synchronous
 Installed SRAM Type: Synchronous
 Speed: Unknown
 Error Correction Type: Multi-bit ECC
 System Type: Unified
 Associativity: 12-way Set-associative

Handle 0x0037, DMI type 4, 48 bytes
Processor Information
 Socket Designation: U3E1
 Type: Central Processor
 Family: Core i7
 Manufacturer: Intel(R) Corporation
 ID: E3 06 05 00 FF FB EB BF
 Signature: Type 0, Family 6, Model 94, Stepping 3
 Flags:
  FPU (Floating-point unit on-chip)
  VME (Virtual mode extension)
  DE (Debugging extension)
  PSE (Page size extension)
  TSC (Time stamp counter)
  MSR (Model specific registers)
  PAE (Physical address extension)
  MCE (Machine check exception)
  CX8 (CMPXCHG8 instruction supported)
  APIC (On-chip APIC hardware supported)
  SEP (Fast system call)
  MTRR (Memory type range registers)
  PGE (Page global enable)
  MCA (Machine check architecture)
  CMOV (Conditional move instruction supported)
  PAT (Page attribute table)
  PSE-36 (36-bit page size extension)
  CLFSH (CLFLUSH instruction supported)
  DS (Debug store)
  ACPI (ACPI supported)
  MMX (MMX technology supported)
  FXSR (FXSAVE and FXSTOR instructions supported)
  SSE (Streaming SIMD extensions)
  SSE2 (Streaming SIMD extensions 2)
  SS (Self-snoop)
  HTT (Multi-threading)
  TM (Thermal monitor supported)
  PBE (Pending break enabled)
 Version: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
 Voltage: 0.9 V
 External Clock: 100 MHz
 Max Speed: 2600 MHz
 Current Speed: 2600 MHz
 Status: Populated, Enabled
 Upgrade: Other
 L1 Cache Handle: 0x0034
 L2 Cache Handle: 0x0035
 L3 Cache Handle: 0x0036
 Serial Number: To Be Filled By O.E.M.
 Asset Tag: To Be Filled By O.E.M.
 Part Number: To Be Filled By O.E.M.
 Core Count: 4
 Thread Count: 8
 Characteristics:
  64-bit capable
  Multi-Core
  Hardware Thread
  Execute Protection
  Enhanced Virtualization
  Power/Performance Control

Handle 0x0038, DMI type 16, 23 bytes
Physical Memory Array
 Location: System Board Or Motherboard
 Use: System Memory
 Error Correction Type: None
 Maximum Capacity: 32 GB
 Error Information Handle: Not Provided
 Number Of Devices: 2

Handle 0x0039, DMI type 17, 40 bytes
Memory Device
 Array Handle: 0x0038
 Error Information Handle: Not Provided
 Total Width: 64 bits
 Data Width: 64 bits
 Size: 8192 MB
 Form Factor: SODIMM
 Set: None
 Locator: DIMM A
 Bank Locator: DIMM A
 Type: DDR4
 Type Detail: Synchronous
 Speed: 2133 MT/s
 Manufacturer: SK Hynix
 Serial Number: 12161215
 Asset Tag: 0B350000
 Part Number: HMA41GS6AFR8N-TF
 Rank: 2
 Configured Memory Speed: 2133 MT/s
 Minimum Voltage: Unknown
 Maximum Voltage: Unknown
 Configured Voltage: 1.2 V

Handle 0x003A, DMI type 17, 40 bytes
Memory Device
 Array Handle: 0x0038
 Error Information Handle: Not Provided
 Total Width: 64 bits
 Data Width: 64 bits
 Size: 8192 MB
 Form Factor: SODIMM
 Set: None
 Locator: DIMM B
 Bank Locator: DIMM B
 Type: DDR4
 Type Detail: Synchronous
 Speed: 2133 MT/s
 Manufacturer: SK Hynix
 Serial Number: 12121212
 Asset Tag: 0B350000
 Part Number: HMA41GS6AFR8N-TF
 Rank: 2
 Configured Memory Speed: 2133 MT/s
 Minimum Voltage: Unknown
 Maximum Voltage: Unknown
 Configured Voltage: 1.2 V

Handle 0x003B, DMI type 19, 31 bytes
Memory Array Mapped Address
 Starting Address: 0x00000000000
 Ending Address: 0x003FFFFFFFF
 Range Size: 16 GB
 Physical Array Handle: 0x0038
 Partition Width: 2

Handle 0x003C, DMI type 221, 12 bytes
OEM-specific Type
 Header and Data:
  DD 0C 3C 00 01 01 00 01 08 00 00 00
 Strings:
  Reference Code - ACPI

Handle 0x003D, DMI type 20, 35 bytes
Memory Device Mapped Address
 Starting Address: 0x00000000000
 Ending Address: 0x001FFFFFFFF
 Range Size: 8 GB
 Physical Device Handle: 0x0039
 Memory Array Mapped Address Handle: 0x003B
 Partition Row Position: 1
 Interleave Position: 1
 Interleaved Data Depth: 1

Handle 0x003E, DMI type 20, 35 bytes
Memory Device Mapped Address
 Starting Address: 0x00200000000
 Ending Address: 0x003FFFFFFFF
 Range Size: 8 GB
 Physical Device Handle: 0x003A
 Memory Array Mapped Address Handle: 0x003B
 Partition Row Position: 1
 Interleave Position: 2
 Interleaved Data Depth: 1

Handle 0x0300, DMI type 126, 22 bytes
Inactive

Handle 0x1600, DMI type 22, 26 bytes
Portable Battery
 Location: Sys. Battery Bay
 Manufacturer: SMP
 Manufacture Date: 12/04/2016
 Serial Number: 00C1
 Name: DELL 1P6KD5A
 Design Capacity: 83990 mWh
 Design Voltage: 11400 mV
 SBDS Version: 1.0
 Maximum Error: 5%
 SBDS Chemistry: LiP
 OEM-specific Information: 0x00000801

Handle 0x1B00, DMI type 27, 15 bytes
Cooling Device
 Temperature Probe Handle: 0x1C00
 Type: Chip Fan
 Status: OK
 OEM-specific Information: 0x0000DD00
 Nominal Speed: 6000 rpm
 Description: CPU Fan

Handle 0x1C00, DMI type 28, 22 bytes
Temperature Probe
 Description: CPU Probe
 Location: Motherboard
 Status: OK
 Maximum Value: 127.0 deg C
 Minimum Value: -127.0 deg C
 Resolution: 1.000 deg C
 Tolerance: Unknown
 Accuracy: Unknown
 OEM-specific Information: 0x0000DC00
 Nominal Value: 10.0 deg C

Handle 0x1C01, DMI type 28, 22 bytes
Temperature Probe
 Description: True Ambient
 Location: Motherboard
 Status: OK
 Maximum Value: 127.0 deg C
 Minimum Value: -127.0 deg C
 Resolution: 1.000 deg C
 Tolerance: Unknown
 Accuracy: Unknown
 OEM-specific Information: 0x0000DC01
 Nominal Value: 10.0 deg C

Handle 0x1C02, DMI type 28, 22 bytes
Temperature Probe
 Description: Memory Module
 Location: Motherboard
 Status: OK
 Maximum Value: 127.0 deg C
 Minimum Value: -127.0 deg C
 Resolution: 1.000 deg C
 Tolerance: Unknown
 Accuracy: Unknown
 OEM-specific Information: 0x0000DC02
 Nominal Value: 10.0 deg C

Handle 0x1C03, DMI type 28, 22 bytes
Temperature Probe
 Description: Other Probe
 Location: Processor
 Status: OK
 Maximum Value: 127.0 deg C
 Minimum Value: -127.0 deg C
 Resolution: 1.000 deg C
 Tolerance: Unknown
 Accuracy: Unknown
 OEM-specific Information: 0x0000DC03
 Nominal Value: 10.0 deg C

Handle 0xB100, DMI type 177, 12 bytes
OEM-specific Type
 Header and Data:
  B1 0C 00 B1 1A 00 00 00 00 00 00 00

Handle 0xB200, DMI type 178, 88 bytes
OEM-specific Type
 Header and Data:
  B2 58 00 B2 3D 00 0C 00 3C 00 0A 00 3B 00 0B 00
  0A 01 12 00 52 00 20 00 30 00 24 00 42 00 18 00
  58 00 14 00 57 00 13 00 10 00 FF 00 11 00 FF 00
  12 00 FF 00 13 00 FF 00 14 00 FF 00 1E 00 FF 00
  1F 00 FF 00 20 00 FF 00 21 00 FF 00 22 00 FF 00
  50 01 26 00 44 00 16 00
 Strings:

Handle 0xD000, DMI type 208, 16 bytes
OEM-specific Type
 Header and Data:
  D0 10 00 D0 03 0A FE 00 E4 06 01 02 00 00 00 00
 Strings:
  20161227
  20170709

Handle 0xD800, DMI type 216, 9 bytes
OEM-specific Type
 Header and Data:
  D8 09 00 D8 01 02 01 88 00
 Strings:
  "Intel Corp."
  "2089"

Handle 0xD900, DMI type 217, 8 bytes
OEM-specific Type
 Header and Data:
  D9 08 00 D9 01 02 01 03
 Strings:
  US-101
  Proprietary

Handle 0xDA00, DMI type 218, 251 bytes
OEM-specific Type
 Header and Data:
  DA FB 00 DA B2 00 04 FF 1F B6 40 1E 00 1E 00 00
  00 22 00 22 00 01 00 23 00 23 00 00 00 28 00 28
  00 00 00 29 00 29 00 01 00 2A 00 2A 00 02 00 2B
  00 2B 00 FF FF 2C 00 2C 00 FF FF 40 00 40 00 01
  00 41 00 41 00 00 00 42 00 42 00 01 00 43 00 43
  00 00 00 50 00 50 00 01 00 55 00 55 00 00 00 5C
  00 5C 00 01 00 5D 00 5D 00 00 00 7D 00 7D 00 FF
  FF 93 00 93 00 01 00 94 00 94 00 00 00 9B 00 9B
  00 01 00 9C 00 9C 00 00 00 9F 00 9F 00 00 00 A0
  00 A0 00 01 00 A1 00 A1 00 00 00 A3 00 A3 00 01
  00 D1 00 D1 00 01 00 D2 00 D2 00 00 00 EA 00 EA
  00 00 00 EB 00 EB 00 01 00 EC 00 EC 00 02 00 ED
  00 ED 00 00 00 F0 00 F0 00 01 00 09 01 09 01 00
  00 0E 01 0E 01 01 00 0F 01 0F 01 00 00 17 01 17
  01 00 00 18 01 18 01 01 00 19 01 19 01 00 00 1A
  01 1A 01 01 00 FF FF FF FF 00 00

Handle 0xDA01, DMI type 218, 251 bytes
OEM-specific Type
 Header and Data:
  DA FB 01 DA B2 00 04 FF 1F B6 40 2B 01 2B 01 01
  00 2C 01 2C 01 00 00 2D 01 2D 01 01 00 2E 01 2E
  01 00 00 35 01 35 01 FF 00 38 01 38 01 01 00 39
  01 39 01 02 00 40 01 40 01 00 00 41 01 41 01 01
  00 44 01 44 01 00 00 45 01 45 01 01 00 46 01 46
  01 00 00 47 01 47 01 01 00 4A 01 4A 01 00 00 4B
  01 4B 01 01 00 4C 01 4C 01 01 00 4D 01 4D 01 00
  00 52 01 52 01 01 00 53 01 53 01 00 00 75 01 75
  01 02 00 76 01 76 01 01 00 7F 01 7F 01 00 00 80
  01 80 01 01 00 81 01 81 01 00 00 82 01 82 01 01
  00 89 01 89 01 00 00 8A 01 8A 01 01 00 9B 01 9B
  01 00 00 9C 01 9C 01 01 00 DE 01 DE 01 00 00 DF
  01 DF 01 01 00 E1 01 E1 01 00 00 E8 01 E8 01 00
  00 E9 01 E9 01 01 00 EA 01 EA 01 00 00 EB 01 EB
  01 01 00 02 02 02 02 00 00 03 02 03 02 01 00 04
  02 04 02 00 00 FF FF FF FF 00 00

Handle 0xDA02, DMI type 218, 251 bytes
OEM-specific Type
 Header and Data:
  DA FB 02 DA B2 00 04 FF 1F B6 40 05 02 05 02 01
  00 16 02 16 02 06 00 2D 02 2D 02 01 00 2E 02 2E
  02 00 00 32 02 32 02 02 00 33 02 33 02 01 00 35
  02 35 02 01 00 36 02 36 02 00 00 4A 02 4A 02 01
  00 4B 02 4B 02 01 00 4C 02 4C 02 00 00 64 02 64
  02 01 00 65 02 65 02 00 00 66 02 66 02 01 00 67
  02 67 02 00 00 68 02 68 02 01 00 69 02 69 02 00
  00 6C 02 6C 02 01 00 6D 02 6D 02 00 00 6E 02 6E
  02 00 00 85 02 85 02 01 00 86 02 86 02 00 00 94
  02 94 02 01 00 95 02 95 02 00 00 A5 02 A5 02 01
  00 A6 02 A6 02 00 00 A7 02 A7 02 01 00 A8 02 A8
  02 00 00 B9 02 B9 02 01 00 BA 02 BA 02 00 00 BD
  02 BD 02 01 00 BE 02 BE 02 00 00 CD 02 CD 02 01
  00 D8 02 D8 02 FF FF D9 02 D9 02 FF FF DA 02 DA
  02 FF FF DB 02 DB 02 FF FF DC 02 DC 02 FF FF DD
  02 DD 02 FF FF FF FF FF FF 00 00

Handle 0xDA03, DMI type 218, 251 bytes
OEM-specific Type
 Header and Data:
  DA FB 03 DA B2 00 04 FF 1F B6 40 DE 02 DE 02 FF
  FF DF 02 DF 02 FF FF E3 02 E3 02 01 00 E4 02 E4
  02 00 00 E5 02 E5 02 01 00 EB 02 EB 02 06 00 F6
  02 F6 02 08 00 12 03 12 03 03 00 13 03 13 03 01
  00 14 03 14 03 00 00 15 03 15 03 01 00 16 03 16
  03 00 00 17 03 17 03 01 00 18 03 18 03 00 00 19
  03 19 03 01 00 1A 03 1A 03 00 00 1B 03 1B 03 01
  00 1C 03 1C 03 00 00 1D 03 1D 03 01 00 1E 03 1E
  03 00 00 1F 03 1F 03 01 00 20 03 20 03 00 00 25
  03 25 03 01 00 26 03 26 03 01 00 2B 03 2B 03 01
  00 2C 03 2C 03 00 00 38 03 38 03 01 00 39 03 39
  03 01 00 41 03 41 03 03 00 42 03 42 03 04 00 43
  03 43 03 05 00 46 03 46 03 01 00 47 03 47 03 02
  00 48 03 48 03 05 00 49 03 49 03 FF FF 4A 03 4A
  03 FF FF 4D 03 4D 03 01 00 4E 03 4E 03 00 00 4F
  03 4F 03 01 00 FF FF FF FF 00 00

Handle 0xDA04, DMI type 218, 251 bytes
OEM-specific Type
 Header and Data:
  DA FB 04 DA B2 00 04 FF 1F B6 40 50 03 50 03 00
  00 57 03 57 03 00 00 58 03 58 03 01 00 5B 03 5B
  03 01 00 5C 03 5C 03 00 00 5D 03 5D 03 01 00 5E
  03 5E 03 00 00 5F 03 5F 03 01 00 60 03 60 03 00
  00 61 03 61 03 01 00 62 03 62 03 00 00 64 03 64
  03 01 00 65 03 65 03 00 00 66 03 66 03 00 00 67
  03 67 03 01 00 6C 03 6C 03 00 00 6D 03 6D 03 01
  00 6E 03 6E 03 FF FF 74 03 74 03 00 00 75 03 75
  03 01 00 78 03 78 03 01 00 79 03 79 03 00 00 95
  03 95 03 01 00 96 03 96 03 00 00 A2 03 A2 03 01
  00 A3 03 A3 03 00 00 A6 03 A6 03 01 00 A7 03 A7
  03 00 00 BE 03 BE 03 FF FF C1 03 C1 03 02 00 C2
  03 C2 03 03 00 C3 03 C3 03 04 00 C5 03 C5 03 01
  00 C6 03 C6 03 00 00 C7 03 C7 03 01 00 C8 03 C8
  03 02 00 C9 03 C9 03 01 00 CA 03 CA 03 00 00 CB
  03 CB 03 FF FF FF FF FF FF 00 00

Handle 0xDA05, DMI type 218, 251 bytes
OEM-specific Type
 Header and Data:
  DA FB 05 DA B2 00 04 FF 1F B6 40 D3 03 D3 03 FF
  FF D4 03 D4 03 01 00 D5 03 D5 03 00 00 D6 03 D6
  03 01 00 D7 03 D7 03 00 00 F6 03 F6 03 01 00 F7
  03 F7 03 00 00 FE 03 FE 03 01 00 FF 03 FF 03 00
  00 01 04 01 04 01 00 02 04 02 04 00 00 03 04 03
  04 01 00 04 04 04 04 00 00 1E 04 1E 04 01 00 1F
  04 1F 04 00 00 20 04 20 04 FF FF 2B 04 2B 04 FF
  FF 31 04 31 04 FF FF 32 04 32 04 01 00 33 04 33
  04 00 00 38 04 38 04 01 00 39 04 39 04 00 00 40
  04 40 04 01 00 41 04 41 04 00 00 42 04 42 04 01
  00 43 04 43 04 00 00 44 04 44 04 01 00 45 04 45
  04 00 00 46 04 46 04 01 00 47 04 47 04 00 00 51
  04 51 04 FF FF 52 04 52 04 FF FF 61 04 61 04 01
  00 62 04 62 04 00 00 85 04 85 04 01 00 86 04 86
  04 00 00 87 04 87 04 01 00 88 04 88 04 00 00 9E
  04 9E 04 01 00 FF FF FF FF 00 00

Handle 0xDA06, DMI type 218, 113 bytes
OEM-specific Type
 Header and Data:
  DA 71 06 DA B2 00 04 FF 1F B6 40 9F 04 9F 04 00
  00 A0 04 A0 04 01 00 A1 04 A1 04 00 00 A2 04 A2
  04 01 00 A3 04 A3 04 00 00 E6 04 E6 04 01 00 E7
  04 E7 04 00 00 EC 04 EC 04 01 00 ED 04 ED 04 00
  00 4A 40 4A 40 01 00 4B 40 4B 40 00 00 0C 80 0C
  80 00 00 0D 80 0D 80 00 00 0E 80 0E 80 01 00 0F
  80 0F 80 FF FF 04 A0 04 A0 01 00 FF FF FF FF 00
  00

Handle 0xDA07, DMI type 218, 77 bytes
OEM-specific Type
 Header and Data:
  DA 4D 07 DA B2 00 04 FF 1F B6 40 00 F1 00 F1 01
  00 02 F1 02 F1 01 00 10 F1 10 F1 01 00 12 F1 12
  F1 01 00 20 F1 20 F1 01 00 22 F1 22 F1 01 00 30
  F1 30 F1 01 00 32 F1 32 F1 01 00 00 F6 00 F6 01
  00 01 F6 01 F6 01 00 FF FF FF FF 00 00

Handle 0xDA08, DMI type 218, 29 bytes
OEM-specific Type
 Header and Data:
  DA 1D 08 DA B2 00 04 FF 1F B6 40 D7 03 3A 05 00
  00 D6 03 3A 05 01 00 FF FF FF FF 00 00

Handle 0xDC00, DMI type 220, 22 bytes
OEM-specific Type
 Header and Data:
  DC 16 00 DC 00 F1 00 00 02 F1 00 00 00 00 00 00
  00 00 00 00 00 00

Handle 0xDC01, DMI type 220, 22 bytes
OEM-specific Type
 Header and Data:
  DC 16 01 DC 10 F1 00 00 12 F1 00 00 00 00 00 00
  00 00 00 00 00 00

Handle 0xDC02, DMI type 220, 22 bytes
OEM-specific Type
 Header and Data:
  DC 16 02 DC 20 F1 00 00 22 F1 00 00 00 00 00 00
  00 00 00 00 00 00

Handle 0xDC03, DMI type 220, 22 bytes
OEM-specific Type
 Header and Data:
  DC 16 03 DC 30 F1 00 00 32 F1 00 00 00 00 00 00
  00 00 00 00 00 00

Handle 0xDD00, DMI type 221, 19 bytes
OEM-specific Type
 Header and Data:
  DD 13 00 DD 02 01 00 00 F6 01 F6 00 00 00 00 00
  00 00 00

Handle 0xDE00, DMI type 222, 16 bytes
OEM-specific Type
 Header and Data:
  DE 10 00 DE 01 04 00 00 19 10 11 08 26 01 00 00

Handle 0xF026, DMI type 130, 20 bytes
OEM-specific Type
 Header and Data:
  82 14 26 F0 24 41 4D 54 00 00 00 00 00 A5 AF 02
  C0 00 00 00

Handle 0xF027, DMI type 131, 64 bytes
OEM-specific Type
 Header and Data:
  83 40 27 F0 31 00 00 00 0B 00 00 00 00 00 0A 00
  F8 00 4E A1 00 00 00 00 01 00 00 00 08 00 0B 00
  E9 0D 3C 00 00 00 00 00 FE 00 FF FF 00 00 00 00
  00 00 00 00 22 00 00 00 76 50 72 6F 00 00 00 00

Handle 0xF028, DMI type 221, 26 bytes
OEM-specific Type
 Header and Data:
  DD 1A 28 F0 03 01 00 01 08 00 00 00 02 00 00 00
  00 C6 00 03 00 00 05 00 00 00
 Strings:
  Reference Code - CPU
  uCode Version
  TXT ACM version

Handle 0xF029, DMI type 221, 26 bytes
OEM-specific Type
 Header and Data:
  DD 1A 29 F0 03 01 00 01 08 00 00 00 02 00 0B 00
  00 0A 00 03 04 0B 08 3C E9 0D
 Strings:
  Reference Code - ME 11.0
  MEBx version
  ME Firmware Version
  Corporate SKU

Handle 0xF02A, DMI type 221, 68 bytes
OEM-specific Type
 Header and Data:
  DD 44 2A F0 09 01 00 01 08 00 00 00 02 03 FF FF
  FF FF FF 04 00 FF FF FF 31 00 05 00 FF FF FF 31
  00 06 00 FF FF FF FF FF 07 00 3E 00 00 00 00 08
  00 34 00 00 00 00 09 00 3E 00 00 00 00 0A 00 34
  00 00 00 00
 Strings:
  Reference Code - SKL PCH
  PCH-CRID Status
  Disabled
  PCH-CRID Original Value
  PCH-CRID New Value
  OPROM - RST - RAID
  SKL PCH H Bx Hsio Version
  SKL PCH H Dx Hsio Version
  SKL PCH LP Bx Hsio Version
  SKL PCH LP Cx Hsio Version

Handle 0xF02B, DMI type 221, 54 bytes
OEM-specific Type
 Header and Data:
  DD 36 2B F0 07 01 00 01 08 00 00 00 02 00 01 08
  00 01 00 03 00 01 08 00 00 00 04 05 FF FF FF FF
  FF 06 00 FF FF FF 07 00 07 00 FF FF FF 07 00 08
  00 FF FF FF FF FF
 Strings:
  Reference Code - SA - System Agent
  Reference Code - MRC
  SA - PCIe Version
  SA-CRID Status
  Disabled
  SA-CRID Original Value
  SA-CRID New Value
  OPROM - VBIOS

Handle 0xF02C, DMI type 221, 96 bytes
OEM-specific Type
 Header and Data:
  DD 60 2C F0 0D 01 00 00 00 00 00 00 02 00 FF FF
  FF FF FF 03 04 FF FF FF FF FF 05 06 FF FF FF FF
  FF 07 08 FF FF FF FF FF 09 00 00 00 00 00 00 0A
  00 FF FF FF FF FF 0B 00 FF FF 00 00 00 0C 00 00
  09 00 61 10 0D 00 02 00 00 00 00 0E 00 FF FF FF
  FF FF 0F 00 FF FF FF FF FF 10 11 01 02 02 03 00
 Strings:
  Lan Phy Version
  Sensor Firmware Version
  Debug Mode Status
  Enabled
  Performance Mode Status
  Disabled
  Debug Use USB(Disabled:Serial)
  Disabled
  ICC Overclocking Version
  UNDI Version
  EC FW Version
  GOP Version
  BIOS Guard Version
  Base EC FW Version
  EC-EC Protocol Version
  Royal Park Version
  BP1.2.2.0_RP03

Handle 0xF03A, DMI type 136, 6 bytes
OEM-specific Type
 Header and Data:
  88 06 3A F0 00 00

Handle 0xF03B, DMI type 14, 26 bytes
Group Associations
 Name: Firmware Version Info
 Items: 7
  0x003C (OEM-specific)
  0xDD00 (OEM-specific)
  0xF028 (OEM-specific)
  0xF029 (OEM-specific)
  0xF02A (OEM-specific)
  0xF02B (OEM-specific)
  0xF02C (OEM-specific)

Handle 0xF03C, DMI type 14, 8 bytes
Group Associations
 Name: $MEI
 Items: 1
  0x0000 (OEM-specific)

Handle 0xF03D, DMI type 219, 81 bytes
OEM-specific Type
 Header and Data:
  DB 51 3D F0 01 03 01 45 02 00 90 06 83 10 89 30
  00 00 00 04 40 68 00 01 1F 00 00 C9 0B C0 47 02
  FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
  FF FF FF FF FF FF FF FF 03 00 00 00 80 00 00 00
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  00
 Strings:
  MEI1
  MEI2
  MEI3

Handle 0xF03E, DMI type 13, 22 bytes
BIOS Language Information
 Language Description Format: Long
 Installable Languages: 2
  en|US|iso8859-1
  <BAD INDEX>
 Currently Installed Language: en|US|iso8859-1

Handle 0xF043, DMI type 127, 4 bytes
End Of Table

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1853369/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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 1853369

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.

[Kai-Heng Feng (kaihengfeng)]

Please update it to 5.3.0-24-generic and see if it helps.

[Fredrik Normann (smartypants)]

I encountered this bug when doing a do-release-upgrade. Unable to boot. If I update now, will kernel 5.3.0-24-generic be used?

[Kai-Heng Feng (kaihengfeng)]

Yes, it should be the one picked by GRUB.

[David Wilson (dw-i)]

The problem still manifests with 5.3.0-24-generic, in addition to the previously known-good kernel used by 19.04.

Like others I tried disabling the TPM but it did not help.

Given the problem still manifests with the previous kernel, this looks like it may be a GRUB issue. Will try downgrading GRUB and updating this ticket if I learn more.

[David Wilson (dw-i)]

This is to confirm manually downgrading the grub packages to those found in 19.04 fixes the problem. This is with TPM still disabled in the BIOS and dis_ucode_ldr kernel command line flag, but I don't think either of those are contributing to the successful boot.

If you're stuck on this issue,

$ sudo dpkg --get-selections | grep ^grub

- For each package listed in the output, visit https://packages.ubuntu.com/ and search the 'disco-updates' distribution for the associated package name.

- Get the URL: Ensure you selected 'disco-updates' distribution in the search config, do the search, click the single result (link is also "disco-updates"), click "amd64", right-click copy one of the .deb download links

- wget each package in turn, for example:

$ wget http://mirrors.kernel.org/ubuntu/pool/main/g/grub2/grub2-common_2.02+dfsg1-12ubuntu2.1_amd64.deb

- dpkg -i each package in turn, for example:

$ sudo dpkg -i grub2-common_2.02+dfsg1-12ubuntu2.1_amd64.deb

Some packages depend on each other, so you might have to download e.g. the common package and install it with "dpkg -i" at the same time as the dependent package -- just supply both .debs on the dpkg command line.

- Run update-grub and grub-install

- Your machine should boot again.

- Don't install upgrades from apt until a real fix appears -- they'll upgrade GRUB again. Investigate apt package pinning to keep this configuration permanently (TBD -- I haven't done this yet)

[David Wilson (dw-i)]

Forgot to mention: I'm also on XPS 9550, and used an 18.04 live CD to get into a rescue system (mounted the SSD, bind mounted /proc /sys /run /dev then chrooted)

[David Wilson (dw-i)]

For anyone trying to figure out what's broken,

$ git diff debian/2.02+dfsg1-12ubuntu2.1 debian/2.04-1ubuntu12|diffstat

Using the repo from https://git.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/

Unfortunately produces a 392k diff. The tags don't appear to share a common ancestry so 'git log' is similarly useless

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Álvaro Souza (alvarofernandoms)]

This bug supposedly was fixed in the linux 5.3.0-26.28. But for me, in my Dell 7567 isn't working. 😢

I'm using 5.0.0-36 for now and it's working.

Font: https://launchpad.net/ubuntu/+source/linux/5.3.0-26.28

[Joseph Maillardet (jokx)]

I am also affected

My laptop hangs on "loading initial ramdisk" at startup. However, it start up without any problems when the power supply is connected 0_o …

[Joseph Maillardet (jokx)]

You can find my data here : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858810

Ask me anything that'll help.

[PhilJ (zfil)]

Joseph I've the same issue on dell precision 7530 but with 5.0.0-37 kernel. I've noticed as well I can't wake up from sleep if the power supply is not connected.

[georg (butunu)]

same probleme here since month,
problem started with kernel 5 and every version seems affected,
"loading initial ramdisk" hangs at startup,
last working kernel for me: linux-image-4.18.0-17-generic

my system:
MEDION® AKOYA® S6426, Intel® Core™ i5-8250U, 39,6 cm (15,6'') FHD Display, 6 GB RAM, Notebook
Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
    Device: Mesa DRI Intel(R) UHD Graphics 620 (Kabylake GT2) (0x5917)

with the 4.18 kernel i have some issues with waking up too,

[Kai-Heng Feng (kaihengfeng)]

Have you tried HWE kernel, which is v5.3 based?

[Joseph Maillardet (jokx)]

I'm running 19.10 with linux package 5.3.0-29.31 ... problem still here.

[georg (butunu)]

@Kai;
i tried kernel linux-image-generic-hwe-18.04, which is
5.3.0.28.96,

... still the same problem

[Andy (smiffy75)]

Same issue here on dell xps 13. Last working kernel 5.0.0-36. Have tried up to 5.3.0-29 but not working.

[You-Sheng Yang (vicamo)]

Please add following kernel boot parameters and try again:

  initcall_debug ignore_loglevel=1 earlycon=efifb

Since you have neither access to console at early boot hang nor journald that writes down kernel dmesg for further inspection, you may need to take a picture of what's left on the screen at the end.

[Joseph Maillardet (jokx)]

@vicamo

I tried your boot parameters, I'm attaching photos of the boot sequence in a zip file.

I don't understand why booting work when "power" is connected (2 thunderbolt dock or notebook charger) and not when on battery.

[You-Sheng Yang (vicamo)]

@Joseph, the last line you see is:

  printk: bootconsole [efifb0] disabled

And system just hangs unless manually powered off. Is this correct?

Then, two things you might want to try:

1. could you also try booting with "nosmp"?

2. does your system still boot normally in other ways, so that you can get into the system and dump CPU microcode info? What's the output of following command on your system?

   $ dmesg |grep microcode

I'm suspecting your case is a duplicate of bug 1862751 or similar.

[Joseph Maillardet (jokx)]

@vicamo, "system just hangs unless manually powered off. Is this correct?": Yes !

1. It's work !
2. Yes, I attach the result

[You-Sheng Yang (vicamo)]

@joseph, unlinked your bug 1858810 from this one. Please move the discussion there.

[You-Sheng Yang (vicamo)]

For XPS 15 9550:

$ dmesg |grep microcode
[ 0.000000] microcode: microcode updated early to revision 0xd6, date = 2019-10-03
[ 1.948537] microcode: sig=0x506e3, pf=0x20, revision=0xd6
[ 1.950991] microcode: Microcode Update Driver: v2.2.

$ dpkg -l|grep micro
ii amd64-microcode 3.20191021.1+really3.20181128.1ubuntu1.1 amd64 Processor microcode firmware for AMD CPUs
ii intel-microcode 3.20191115.1ubuntu0.19.04.2 amd64 Processor microcode firmware for Intel CPUs

[You-Sheng Yang (vicamo)]

To be fixed in bug 1862751 together.

[Álvaro Souza (alvarofernandoms)]

For Dell 7567, still not working.

Last Kernel working: 5.0.0-36

I've tried: from 5.3.0-26 to 5.3.0-40

More info:

$ dmesg |grep microcode
[ 0.000000] microcode: microcode updated early to revision 0xca, date = 2019-10-03
[ 0.197485] mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1581946905 SOCKET 0 APIC 0 microcode ca
[ 0.197492] mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1581946905 SOCKET 0 APIC 0 microcode ca
[ 0.197498] mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1581946905 SOCKET 0 APIC 0 microcode ca
[ 0.197503] mce: [Hardware Error]: PROCESSOR 0:906e9 TIME 1581946905 SOCKET 0 APIC 0 microcode ca
[ 0.652963] microcode: sig=0x906e9, pf=0x20, revision=0xca
[ 0.653165] microcode: Microcode Update Driver: v2.2.
$ dpkg -l | grep micro
ii amd64-microcode 3.20191021.1+really3.20181128.1ubuntu2 amd64 Processor microcode firmware for AMD CPUs
ii intel-microcode 3.20191115.1ubuntu0.19.10.2 amd64 Processor microcode firmware for Intel CPUs
ii iucode-tool 2.3.1-1 amd64 Intel processor microcode tool
ii libxmuu1:amd64

[You-Sheng Yang (vicamo)]

@alvarofernandoms, please follow https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852586/comments/37 and file a new bug.

[Viacheslav Semykrasov (7krasov)]

Using 19.10 for a long time. This week had 2 times issue:
1st time:

last kernel 5.3.0-45
hanged on boot and on recovery:
loading initial ramdisk (in recovery mode, 5.3.0-45)
Somehow I managed to boot and after this worked properly

2nd time, today:
the same behavior, 5.3.0-42 recovery too.
Chrooted from rescue USB and upgraded 3 packages, one of them was something about microcode...
here are my versions, but didn't help...
slava@slava-Latitude-5500:~$ dpkg -l | grep microcode
ii amd64-microcode 3.20191021.1+really3.20181128.1ubuntu2 amd64 Processor microcode firmware for AMD CPUs
ii intel-microcode 3.20191115.1ubuntu0.19.10.2 amd64 Processor microcode firmware for Intel CPUs
ii iucode-tool 2.3.1-1 amd64 Intel processor microcode tool

After I found your comments before, I tried to plug in power cable to my Dell Lattitude 5500 and I managed to boot with a normal mode. This way I remembered I plugged in a cable the 1st time too before successful booting
The laptop is based on intel

[Viacheslav Semykrasov (7krasov)]

Have just removed the cable, rebooted and boot feezes again. Had to plug in the cable to boot

[Viacheslav Semykrasov (7krasov)]

Intel(R) Core(TM) i5-8365U CPU

slava@slava-Latitude-5500:~$ journalctl -b | grep microcode
кві 01 21:38:43 slava-Latitude-5500 kernel: microcode: microcode updated early to revision 0xca, date = 2019-10-03
кві 01 21:38:43 slava-Latitude-5500 kernel: microcode: sig=0x806ec, pf=0x80, revision=0xca
кві 01 21:38:43 slava-Latitude-5500 kernel: microcode: Microcode Update Driver: v2.2.

[Marco de Bock (bockbock)]

Yesterday evening I installed updates on Ubuntu 19.10 running on a Dell Latitude 5591 (Core i7-8850H @ 2.60 Ghz x 12, GeForce MX130). Laptop connected to power supply. Nothing special, just the updates that were proposed as they always do. Reboot afterwards was fine.

This morning I started the laptop on the battery. Booting failed with purple screen. Recovery option mentioned Loading initial ramdisk. After I plugged in the power supply Ubuntu started successfully.

[Neal Shireman (nshire)]

2016 XPS 13 9350 with i5-6200u on Ubuntu 18.04LTS. I tried everything in these threads, even a full OS reinstall and nothing worked.

I enabled SecureBoot in my UEFI settings and it booted right up.

[Andreas (blueeyedcreature)]

aloha
i have that too. (fun fact: also on fedora.. but their nvidia implementation is less.. user friendly)

dell latitude 5591 / intel cpu + geforce mx130 (nvidia prime) - tested with nouveau and proprietary driver
both freeze the system when it suspends at 'loading initial ram disk'

booting then seems to fail without a plugged in power cable (wth?)

secure boot disabled in bios (to make nvidia prime work)
just updated ubuntu to kernel 5.3.0-46 but same same

any log/help that I can provide?

Andreas

[FreudianSlip (freudianslyp)]

I had exactly the same issue as nshire (above). Was running 19.10 without problems, went to do a routine update, completed successfully - reboot - freeze at loading initial Ramdisk. I downloaded the 19.10 iso tried to boot using that, but no joy. Tried all the suggestions here about nosmp, nomodeset etc - same problems.

I then enabled secure boot as per nshire's suggestion and boom - I'm in.

[Viacheslav Semykrasov (7krasov)]

Guys, today after reading FreudianSlipl's advice
>I then enabled secure boot as per nshire's suggestion and boom - I'm in.
remembered that I've enabled secure boot mode few days ago in BIOS. Have just tried to reboot without connected cable and boom too :-) I'm in

[tyknkd (tyknkd)]

Enabling secure boot had no effect for me, but plugging in power cable worked.

[Joseph Maillardet (jokx)]

Have updated my laptop to Ubuntu 20.04. Problem still here... 😭😭😭

[Viacheslav Semykrasov (7krasov)]

Yesterday my son shut down my laptop with a power button in a forced way. After this, I couldn't boot without cable again.
Today, I had to reboot and had no success to boot as well and after this, I plugged in my cable but forget to switch on the power filter (so cable had no power), but I managed to boot this time.
I suppose that:
- Secure Boot doesn't help each time at least
- probably hard power off makes some influence booting success
Seems to be a floating bug

[Luis Forquesato (luisforque)]

I can confirm that I tried updating to 20.04 and had this issue. Also Dell device.
I tried enabling the secure boot, also tried with and without power cable, and the issue persists.

[FreudianSlip (freudianslyp)]

My issue has returned following a reboot of the laptop. Changing between secure and non-secure boot doesn't affect the result any more. I've (just) installed 20.04 and have the same issues.

[Daniel Grebe (danielgrebe)]

I had the same problem while upgrading to 19.10 on a dell 7567.
Secure Boot/plugging in didn't work, but I was able to boot when I turned off PTT

[Miguel (miguelrodcar)]

Also on a Dell 5567, I was able to boot only after switching PTT Security off in BIOS.

[David Wilson (dw-i)]

I'm not sure why this is filed against intel-microcode now, it is related to an update of grub (see my previous comment)

[Luis Forquesato (luisforque)]

I updated the bios and retried the update onto 20.04 and it seems to be ok now... Not 100% sure its related, but it seems to be working fine now, with and without the cable

[Jan-Jonas Sämann (janjonas)]

I recently came across this issue multiple times in ansible-managed virtual environments. (Really bad)
This happens to me all the time because of invalid GRUB configurations.
Namingly if GRUB is set to also output to serial when there is no serial port attached to the vm.

Could imagine that maybe at the time of the last kernel update, there was (accidently) some usb drive connected to the mashine of the TE wich grub now manifested and requires to map the device tree... o.O

If so, both cases must not prevent a mashine from being bootable.

[Andreas (blueeyedcreature)]

Aloha.
upgrade from my previous post.

I just upgraded to 20.04 and this happens when the laptop has slept for longer times (like.. overnight) after short periods resume works fine.

> disabled NVIDIA proprietary
> masked hibernate.target and suspend-then-hibernate.target
> once it happens it won't reboot, either. keeps freezing
> FIX: boot with power cable plugged in (???!??)

Dell 5591 here. Any files/dumps I can provide to help?

thanks

Andreas

[Álvaro Souza (alvarofernandoms)]

Hello, @danielgrebe! Thank you so much for the suggestion in turn off the PTT Security option. In my Dell 7567 I was able to boot as well. Thanks everybody.

[Andreas (blueeyedcreature)]

Aloha.
just captured a failed boot. Power cable in and saw:
"initramfs unpacking failed: Decoding failed"
could this be related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660
or
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1870260
?

I am testing with COMPRESS=gzip instead of lz4 for science....

Andreas

[Andreas (blueeyedcreature)]

update: disabling PTT did not change anything.
still need to have power cable plugged in.

changing compress to gzip didn't change anything. ssdd

[Marco de Bock (bockbock)]

I don't have this issue anymore. Today my laptop (Dell Latitude E5591) starts when using the battery. I have installed some Ubuntu updates a few days ago (just regular ones that come with automatic updates), and a BIOS firmware update too (provided by Dell). One of those updates, or the combination of the two, solved it.

[John Nelson (john-nelson2)]

Ran into this today applying a mass set of updates to an 18.04 system that was last updated sometime last year. Running on a 2007 iMac.

Apple hasn't made firmware updates for this model in years -- and firmware updates require MacOS installed anyway AFIAK -- so that approach is closed to me.

That said, David Wilson's workaround at #7 above worked perfectly.

[Fredrik Normann (smartypants)]

I did an upgrade to day from 19.04 -> 19.10 -> 20.04 and now the system
still hangs. Tried all bios settings suggested in this thread. I'll try the
grub fix, from David Wilson, but disco packages is not available anymore. I
would say that this bug should have status updated.

On Tue, May 19, 2020 at 5:20 AM John Nelson <email address hidden>
wrote:

> Ran into this today applying a mass set of updates to an 18.04 system
> that was last updated sometime last year. Running on a 2007 iMac.
>
> Apple hasn't made firmware updates for this model in years -- and
> firmware updates require MacOS installed anyway AFIAK -- so that
> approach is closed to me.
>
> That said, David Wilson's workaround at #7 above worked perfectly.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1853369
>
> Title:
> [19.10] Boot hangs at "loading initial ramdisk"
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1853369/+subscriptions
>

--
Mvh
-fredrik-normann-

Sent from my Gmail Account

[Xandor Schiefer (zeorin)]

I did the same upgrade over the weekend and ran into this same bug. I applied a variation of David Wilson's workaround.

I first booted on a 19.04 liveCD (downloaded from http://old-releases.ubuntu.com/releases/disco/), 20.04 liveCD also wouldn't boot (never tried the 19.10 liveCD), and then chrooted into my broken system using instructions from https://help.ubuntu.com/community/LiveCdRecovery#Update_Failure

I added

deb http://old-releases.ubuntu.com/ubuntu disco main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu disco-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu disco-security main restricted universe multiverse

To /etc/apt/sources.list, and created /etc/apt/preferences.d/grub with contents:

Package: *
Pin: release n=disco
Pin-Priority: -10

Package: grub-common
Pin: release n=disco
Pin-Priority: 1000

Package: grub-efi-amd64
Pin: release n=disco
Pin-Priority: 1000

Package: grub-efi-amd64-bin
Pin: release n=disco
Pin-Priority: 1000

Package: grub-efi-amd64-signed
Pin: release n=disco
Pin-Priority: 1000

Package: grub2-common
Pin: release n=disco
Pin-Priority: 1000

and then ran

apt update
apt upgrade

which warned me about _downgrading_ grub, which is exactly what I want for the workaround.

Until I remove the preferences file which pins the grub version I'm not in danger of overwriting the old grub packages on a regular upgrade.

[Fredrik Normann (smartypants)]

@zeorin Thanks for that info. I had to do the following extra. Since I use LUKS encrypted disk and uefi.

1) Open the encrypted disk in File explorer
2) Mount the lvm partition on /mnt
   mount /dev/ubuntu-vg/root /mnt

Mount boot
mount /dev/nvme0n1p2 /mnt/boot

Mount efi
mount /dev/nvme0n1p1 /mnt/boot/efi

Standard chroot mounts
mount --bind /proc /mnt/proc
mount --bind /dev /mnt/dev
mount --bind /sys /mnt/sys
mount --bind /run /mnt/run <-- This was not listed.

Then chroot into /mnt

After adding the new apt sources and pinning the grub version and 'apt update && apt upgrade' I had to manually install 'grub2-common'. It did not install by default with 'apt upgrade'.

After this was done. I ran update-grub and grub-install. With efi mounted this worked and I could reboot with old working grub.

This is bug needs to be fixed.

[Ashu (ashusharma)]

I am having the similar issue on my Dell XPS 8930 Desktop when tried upgrading from 18.04 LTS to 20.04 LTS. Mine is dual boot linux with Windows 10.
I had successfully running Windows 10 and Ubuntu Linux 18.04 LTS system for almost 2.5 years. Then heard about 20.04 LTS - seems to be smooth installed-i wanted to try it. I followed this link Did everything from command line. Everything went fine. I have Linux installed on PCI NVME SSD and Windows 10 on normal SSD. I used Windows boot loader as the default entry and Ubuntu Linux to be selected if i want to go to Linux. As per that link, i installed not using kernels to clean up some space. I was getting purple grub screen.

But after this upgrade - i get this black grub screen.
on which Linuxes - there are two entries - i don't know which one is default. But if i try to select either of the linux - it doesn't boot Linux and it's all dark screen.

Though on Grub - i can select the entry for Windows and it boots it without any issues.

What went wrong? How to come back to normal life with this upgraded ubuntu Linux 20.04 LTS? I can select the advanced option and then tried booting 5.4.0-31-generic(kernel which comes with Ubuntu Linux 20.04 LTS) After that it displays: Loading Linux 5.4.0-31-generic ... Loading initial ramdisk
and then it freezes
What could be the issue? But after selecting Advanced options for Ubuntu when i select Ubuntu with Linux 4.15.0-101-generic it shows me same messages Loading Linux 4.15.0-101-generic… Loading initial ramdisk… but not getting stuck or freeze and finally loads new Ubuntu Linux 20.04 LTS

What's going on here? I checked that 20.04 LTS is installed and working with this choice root@ashu-XPS-8930:/home/ashu# cat /etc/lsb-release

I was upgrading using this command on the command line:
sudo do-release-upgrade -d

[Ashu (ashusharma)]

dmesg | grep microcode
[ 1.906785] microcode: sig=0x906ea, pf=0x2, revision=0xca
[ 1.907050] microcode: Microcode Update Driver: v2.2.

I can only login to old kernel(4.15.0-101-generic) and from there i am providing this information. Recovery mode boot via 5.4.0-31-generic got me till the login screen and then system froze.

[Ashu (ashusharma)]

I tried what "Xandor Schiefer (zeorin)" stated. But 5.4.0-31-generic couldn't be booted. Then tried recovery mode for 5.4.0-31-generic - it worked with lower resolution. Then tried log in using 5.4.0-31-generic but no success.

Well it has nothing to do with power cable as i am on desktop. I have the most updated BIOS for my Dell XPS 8930. Don't know what could be the issue but it's just not working for me. I have posted my original question here:
https://askubuntu.com/questions/1243328/dual-boot-windows-10-ubuntu-linux-18-04-lts-upgrade-to-20-04lts-kernel-5-4-is

[Viacheslav Semykrasov (7krasov)]

Upgraded to Ubuntu 20.04, boot hanging issue still presents

5.4.0-31-generic
intel-microcode 3.20191115.1ubuntu3

[ekasperc (ekasperc1)]

Although i presume this issue is quite tricky, a fix which seems to work well has been to deactivate SGX on my intel laptop (ice lake 1065G7).

[Joseph Maillardet (jokx)]

I've been trying to disable SGX myself. But it didn't help. It's been almost a year since my laptop stopped booting up without a power supply. It's extremely frustrating and annoying!

[Daniel Tan (riefu)]

Did any of you tried to reinstall Ubuntu after this happened?

I started having this issue today after upgraded to 5.4.0-37-generic. I then fallback to 5.4.0-33-generic (which works previously) and it no longer boot without a power supply.

5.4.0-31-generic is the one that works for me now.

[Rhonal Velasco (rhonal-velasco)]

I was dealing with some of these issues after install new kernel version this morning. However I was able to boot with older kernel versions. After a lot of test, now I am able to boot in the new kernel without any problem.
Here there are some checks and tasks that I could accomplish:

-) Check in /etc/fstab and make sure that there are not duplicated mount points for EFI.

-) Try apt install --reinstall linux-image-5.4.0-37-generic

-) Try sudo update-grub

Also, I removed drivers for nvidia and VirtualBox because some errors that I saw in journalctl.

Hope this helps somebody.

[Rhonal Velasco (rhonal-velasco)]

FYI: I installed VirtualBox again and the issue reappeared.

[thiago castanho (thiagoppte)]

same problem with my dell, only work in 16.04
04

[Joseph Maillardet (jokx)]

I have received the updated package intel-microcode 3.20200609.0ubuntu0.20.04.2.
I still have the same problem. Without power supply the boot hang at ramdisk

[Marco de Bock (bockbock)]

I had this issue before, then it got fixed (don't know how), but since a week the issue is back. Can't boot on battery power. After Grub I get a blank screen, black, nothing more.

Dell Latitude 5591 (Core i7-8850H @ 2.60 Ghz x 12, GeForce MX130)

I searched and found this more my model, may be I'll try tomorrow:
https://www.dell.com/community/Latitude/Linux-does-not-boot-on-Latitude-5591-when-on-battery/td-p/7494242

[Viacheslav Semykrasov (7krasov)]

It seems with the last 2 kernel versions/microcode versions I'm not able to reload my Dell Latitude 5500 without power cable at all. Earlier I was oftener able to do it without cable

[Jack (jkpe)]

I too have this issue with a Dell Latitude 7400.
Booting with power attached works fine, booting on battery power results in getting stuck at “loading initial ramdisk”

In an attempt to rule out Ubuntu I installed Windows 10, patched to the latest versions, and experience a similar hang booting Windows on battery power (the laptop entirely hangs just before the Windows login screen is displayed). Windows Recovery tools still seem operational.

Seems like hardware/BIOS related to me. Sorry I can’t offer anything more than anecdotal information.

[Ashu (ashusharma)]

I am posting my updates on askubuntu.com also:
https://askubuntu.com/questions/1243328/dual-boot-windows-10-ubuntu-linux-18-04-lts-upgrade-to-20-04lts-kernel-5-4-is

I tried installing various other kernels thinking that it might fix this problem but no luck. Mine is Dell XPS 8930 Desktop so I don't power cable should be an issue for laptops. Recently my other Dell XPS laptop got a BIOS update. It is running Windows 10 dual boot with Ubuntu 18.04 LTS - I am not going to upgrade ubuntu due to this issue.

[John Nelson (john-nelson2)]

Quick update on my encounter with this issue in 18.04 against an (ancient!) 2007 iMac... after updating "intel-microcode" to version 3.20200609 (which wasn't yet available when this was reported), I am no longer able to repro the issue. All packages are up-to-date (for 18.04 anyway), and the system is now booting fine again.

[Ashu (ashusharma)]

Could somebody help me out in terms of how to update "intel-microcode" to version 3.20200609? and after that what needs to be done to get this fixed?

[ET (eterradas)]

Have been facing this issue* since updating to 20.04
*stuck at boot. And when booting from recovery seeing "Loading initial ramdisk"

on XPS 13 (DELL) the solution has been disabling SGX (Intel's Software Guard Extensions (SGX)) on the bios.

After that managed to boot normally.

[Ashu (ashusharma)]

I have fixed this issue.
I uninstalled ubuntu and installed it all over again. It was pain. I
screwed up ubuntu as well as Windows. Luckily - I had no important data in
ubuntu linux and in Windows - I keep all the data in D and E drives.
My stuff mentioned here:
https://askubuntu.com/questions/1268013/deleted-ubuntu-and-grub-but-windows-10-is-not-booting

It's working fine after that.
I have Windows 10 and ubuntu 20.4.1 LTS installed - dual boot.

On Mon, Aug 31, 2020 at 10:50 AM ET <email address hidden> wrote:

> Have been facing this issue* since updating to 20.04
> *stuck at boot. And when booting from recovery seeing "Loading initial
> ramdisk"
>
> on XPS 13 (DELL) the solution has been disabling SGX (Intel's Software
> Guard Extensions (SGX)) on the bios.
>
> After that managed to boot normally.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1853369
>
> Title:
> [19.10] Boot hangs at "loading initial ramdisk"
>
> Status in intel-microcode package in Ubuntu:
> In Progress
>
> Bug description:
> [19.10] Boot hangs at "loading initial ramdisk"
>
> So after completing the upgrade from 19.04 to 19.10, my computer got
> stuck on the solid purple Grub screen upon reboot. After getting into
> the grub menu on next boot and booting from advanced options, I see
> that it gets to "loading initial ramdisk" and then just hangs forever.
> I am able to boot without issues on the old kernel (5.0.0-32-generic),
> but not the one that got installed with the upgrade
> (5.3.0-18-generic).
>
> Things I've tried based on what worked for other people who got this
> problem (though I haven't found anyone who has it specifically with
> 19.10):
>
> acpi=off
>
> dis_ucode_ldr
>
> disabling secure boot
>
> recovery mode
>
> making sure all packages are up to date
>
> I'm kind of at a loss of what to do, other than just keep using the
> old kernel. (which presumably might cause problems at some point?)
>
> I'm posting this from Ubuntu 19.04, since upgrade from 19.04 to 19.10
> resulted in unable to boot system.
>
> Hardware Dell XPS 9550
>
> # dmidecode 3.2
> Getting SMBIOS data from sysfs.
> SMBIOS 2.8 present.
> 91 structures occupying 5683 bytes.
> Table at 0x000E0000.
>
> Handle 0x0000, DMI type 0, 24 bytes
> BIOS Information
> Vendor: Dell Inc.
> Version: 1.11.2
> Release Date: 07/30/2019
> Address: 0xF0000
> Runtime Size: 64 kB
> ROM Size: 16 MB
> Characteristics:
> PCI is supported
> PNP is supported
> BIOS is upgradeable
> BIOS shadowing is allowed
> Boot from CD is supported
> Selectable boot is supported
> EDD is supported
> 5.25"/1.2 MB floppy services are supported (int 13h)
> 3.5"/720 kB floppy services are supported (int 13h)
> 3.5"/2.88 MB floppy services are supported (int 13h)
> Print screen service is supported (int 5h)
> 8042 keyboard servi...

[Ben Kraft (benjaminjkraft)]

This also affected me. Downgrading grub using the instructions from comment #54/#55 fixed the issue, so this definitely seems to be a grub issue, and is still a problem as of version 2.04-1ubuntu26.4.

Running those instructions broke my encrypted drive setup; the instructions at https://gist.github.com/dragon788/e777ba64d373210e4f6306ad40ee0e80 fixed that (and describe why setting up the chroot that way caused the problem). Unrelated, but I mention it here in case anyone else runs into that problem.

[dan hawk (culori-media)]

Adding dis_ucode_ldr to boot options fixed it for me (https://www.dell.com/community/Precision-Mobile-Workstations/Precision-7540-will-only-boot-Linux-if-charger-is-connected/m-p/7466713/highlight/true#M2874). Million kiddos for flea plus, the original poster.

[Joseph Maillardet (jokx)]

I haven't noticed the intel-microcode update of 2020/12/11
Know, with intel-microcode 3.20201110.0ubuntu0.20.04.2 focal package, my computer start normally and without any tweak ! Greaaat !
Thanks a lot to anybody make it happen.

[Aidan Sojourner (tuxxi)]

This bug started affecting me a few weeks ago. It seems to happen whenever a new kernel version is pushed out.

This time, what Ben did in #75 -- downgrading grub to 2.02+dfsg1-12ubuntu2.1 -- was the only thing that fixed it for me. I cannot remember exactly what fixed it for me the first time, but I did not have to downgrade grub - I believe installing an older kernel was what finally fixed it.

I have a Dell XPS 15 9550, Ubuntu 20.04 installed with EFI, and a LUKS encrypted primary drive.

[Fredrik Normann (smartypants)]

Is this solved now in 22.04? Want to do a release upgrade, but it's such a hassle to work-around the bug by pinning grub.