Ubuntu won't boot on Dell Inspiron 7375

Bug #1837688 reported by Agustin Ferrario
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Ubuntu is unable to boot from the installation USB on a Dell Inspiron 7375, with a Ryzen CPU. This affects Ubuntu 19.10 (latest daily), 19.04 and 18.04.2 (videos of each unsuccessful boot will be attached).
I was able to boot using a workaround, by adding to the kernel line:

    amd_iommu=on ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2

You can see it here: https://askubuntu.com/questions/1036357/ubuntu-18-04-wont-boot-on-dell-inspiron-7375

I used this workaround to run the apport-bug tool.

The problem should be in an ubuntu specific vendor patch or configuration since I was able to boot successfully in:
* CentOS 7 (kernel 3.10)
* OpenSUSE Leap 15.1 (kernel 4.12.14)
* OpenSUSE tumbleweed (kernel 5.1.16)
* Fedora 30 (kernel 5.0.9)
* Manjaro (kernel 4.19)
* SystemRescueCd (kernel 4.19.34)

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.0.0-20-generic 5.0.0-20.21
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ubuntu 2186 F.... pulseaudio
 /dev/snd/controlC0: ubuntu 2186 F.... pulseaudio
CasperVersion: 1.411
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 23 21:14:36 2019
LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
MachineType: Dell Inc. Inspiron 7375
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed amd_iommu=on ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 ---
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-20-generic N/A
 linux-backports-modules-5.0.0-20-generic N/A
 linux-firmware 1.180
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.0
dmi.board.name: 0GTNWX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.5.0
dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd07/09/2018:svnDellInc.:pnInspiron7375:pvr1.5.0:rvnDellInc.:rn0GTNWX:rvrA00:cvnDellInc.:ct10:cvr1.5.0:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7375
dmi.product.sku: 0884
dmi.product.version: 1.5.0
dmi.sys.vendor: Dell Inc.

Revision history for this message
Agustin Ferrario (agustin-ferrario) wrote :
Revision history for this message
Agustin Ferrario (agustin-ferrario) wrote :
Revision history for this message
Agustin Ferrario (agustin-ferrario) wrote :

This is the filmed video of the failed boot on 19.10

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Agustin Ferrario (agustin-ferrario) wrote :
Revision history for this message
Agustin Ferrario (agustin-ferrario) wrote :
Revision history for this message
Agustin Ferrario (agustin-ferrario) wrote :

This is a video of Ubuntu 19.10 booting using the workaround mentioned on the bug description

Revision history for this message
Agustin Ferrario (agustin-ferrario) wrote :

I would love to help solving this bug before the next release and/or the next point release of bionic

Revision history for this message
Anthony Wong (anthonywong) wrote :

Can you try one of the mainline kernel builds, such as https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc1/? It is very close to mainline kernel so we can use it to isolate if the bug is caused by any patches in Ubuntu kernel.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Agustin Ferrario (agustin-ferrario) wrote :

Hi! Sorry for the delay. I installed the packages in ubuntu 19.04 (Disco):

$ ls
linux-headers-5.3.0-050300rc1_5.3.0-050300rc1.201907212232_all.deb
linux-image-unsigned-5.3.0-050300rc1-generic_5.3.0-050300rc1.201907212232_amd64.deb
linux-headers-5.3.0-050300rc1-generic_5.3.0-050300rc1.201907212232_amd64.deb
linux-modules-5.3.0-050300rc1-generic_5.3.0-050300rc1.201907212232_amd64.deb
crash@crash-Inspiron-7375:~/Downloads$ sudo dpkg -i linux-*

Then rebooted but with the same error. I will try to manually compile and install the kernel with the sources listed there without the patches and will confirm.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
Agustin Ferrario (agustin-ferrario) wrote :

That kernel booted without problems or needs for workarounds.

I do however get terrible screen tearing with the latest kernel. I do not know if it's a regression or known bug. I send an example attached

Revision history for this message
Agustin Ferrario (agustin-ferrario) wrote :

The tearing gets to the point of being unusable sometimes

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

I think it's a regression in new kernels. I can also observe the same issue but only when using web browsers. I'll see if I can bisect to the regression point.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Bisected and reported to upstream.

Revision history for this message
Agustin Ferrario (agustin-ferrario) wrote :

Great! Hit me if you need some testing when the changes arrive

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-disco
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-eoan
Revision history for this message
Agustin Ferrario (agustin-ferrario) wrote :

Flickr free boot on Eoan! I'll need it to test it in Disco

tags: added: verification-done-eoan
removed: verification-needed-eoan
Revision history for this message
Agustin Ferrario (agustin-ferrario) wrote :

Booted without problems in Disco

tags: added: verification-done-disco
removed: verification-needed-disco
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)

All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

linux-gcp-5.3/unknown (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#linux-gcp-5.3

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (53.1 KiB)

This bug was fixed in the package linux - 5.3.0-22.24

---------------
linux (5.3.0-22.24) eoan; urgency=medium

  * [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout
    setting (LP: #1849682)
    - Revert "md/raid0: avoid RAID0 data corruption due to layout confusion."

  * refcount underflow and type confusion in shiftfs (LP: #1850867) // CVE-2019-15793
    - SAUCE: shiftfs: Correct id translation for lower fs operations
    - SAUCE: shiftfs: prevent type confusion
    - SAUCE: shiftfs: Fix refcount underflow in btrfs ioctl handling

  * CVE-2018-12207
    - kvm: x86, powerpc: do not allow clearing largepages debugfs entry
    - SAUCE: KVM: vmx, svm: always run with EFER.NXE=1 when shadow paging is
      active
    - SAUCE: x86: Add ITLB_MULTIHIT bug infrastructure
    - SAUCE: kvm: mmu: ITLB_MULTIHIT mitigation
    - SAUCE: kvm: Add helper function for creating VM worker threads
    - SAUCE: kvm: x86: mmu: Recovery of shattered NX large pages
    - SAUCE: cpu/speculation: Uninline and export CPU mitigations helpers
    - SAUCE: kvm: x86: mmu: Apply global mitigations knob to ITLB_MULTIHIT

  * CVE-2019-11135
    - x86/msr: Add the IA32_TSX_CTRL MSR
    - x86/cpu: Add a helper function x86_read_arch_cap_msr()
    - x86/cpu: Add a "tsx=" cmdline option with TSX disabled by default
    - x86/speculation/taa: Add mitigation for TSX Async Abort
    - x86/speculation/taa: Add sysfs reporting for TSX Async Abort
    - kvm/x86: Export MDS_NO=0 to guests when TSX is enabled
    - x86/tsx: Add "auto" option to the tsx= cmdline parameter
    - x86/speculation/taa: Add documentation for TSX Async Abort
    - x86/tsx: Add config options to set tsx=on|off|auto
    - [Config] Disable TSX by default when possible

  * CVE-2019-0154
    - SAUCE: drm/i915: Lower RM timeout to avoid DSI hard hangs
    - SAUCE: drm/i915/gen8+: Add RC6 CTX corruption WA

  * CVE-2019-0155
    - SAUCE: drm/i915: Rename gen7 cmdparser tables
    - SAUCE: drm/i915: Disable Secure Batches for gen6+
    - SAUCE: drm/i915: Remove Master tables from cmdparser
    - SAUCE: drm/i915: Add support for mandatory cmdparsing
    - SAUCE: drm/i915: Support ro ppgtt mapped cmdparser shadow buffers
    - SAUCE: drm/i915: Allow parsing of unsized batches
    - SAUCE: drm/i915: Add gen9 BCS cmdparsing
    - SAUCE: drm/i915/cmdparser: Use explicit goto for error paths
    - SAUCE: drm/i915/cmdparser: Add support for backward jumps
    - SAUCE: drm/i915/cmdparser: Ignore Length operands during command matching

linux (5.3.0-21.22) eoan; urgency=medium

  * eoan/linux: 5.3.0-21.22 -proposed tracker (LP: #1850486)

  * Fix signing of staging modules in eoan (LP: #1850234)
    - [Packaging] Leave unsigned modules unsigned after adding .gnu_debuglink

linux (5.3.0-20.21) eoan; urgency=medium

  * eoan/linux: 5.3.0-20.21 -proposed tracker (LP: #1849064)

  * eoan: alsa/sof: Enable SOF_HDA link and codec (LP: #1848490)
    - [Config] Enable SOF_HDA link and codec

  * Eoan update: 5.3.7 upstream stable release (LP: #1848750)
    - panic: ensure preemption is disabled during panic()
    - [Config] updateconfigs for USB_RIO500
    - USB: rio500: Remove Rio 500 kernel driver
   ...

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
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.