After Upgrade to 22.04. System does not boot into graphical mode without being connected to the network

Bug #1977684 reported by Jürgen Hemelt
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After long wait time many systemd services fail with a timeout. Connecting to a network via Ethernet does not make the boot continuing. When the network cable is connected before booting the boot process works fine.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.10
ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
Uname: Linux 5.15.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 5 15:32:01 2022
InstallationDate: Installed on 2022-01-25 (131 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to jammy on 2022-05-20 (15 days ago)
VarLogDistupgradeTermlog:

Revision history for this message
Jürgen Hemelt (jhemelt) wrote :
description: updated
affects: ubuntu → ubuntu-release-upgrader (Ubuntu)
Revision history for this message
Nick Rosbrook (enr0n) wrote :

Can you specify which systemd services are failing and timing out on boot? And can you provide some log output from those services?

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Incomplete
Revision history for this message
Jürgen Hemelt (jhemelt) wrote :

Each time I boot it looks like the failing services are different. Currently I get timeout errors with

* systemd-timesyncd.service
* systemd-oomd.service

I attach the relevant output of journalctl --system below.

Revision history for this message
Nick Rosbrook (enr0n) wrote :
Download full text (7.6 KiB)

Thanks. I noticed the following kernel stack trace in that log:

---
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: BUG: kernel NULL pointer dereference, address: 0000000000000058
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: #PF: supervisor read access in kernel mode
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: #PF: error_code(0x0000) - not-present page
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: PGD 0 P4D 0
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: Oops: 0000 [#1] SMP NOPTI
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: CPU: 5 PID: 141 Comm: kworker/5:1 Tainted: G W 5.15.0-33-generic #34-Ubuntu
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: Hardware name: HP HP ENVY x360 Convertible 13-ar0xxx/85DE, BIOS F.19 12/26/2019
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: Workqueue: events_long ucsi_init_work [typec_ucsi]
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: RIP: 0010:typec_register_altmode+0x30/0x3b0 [typec]
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: Code: 48 89 e5 41 57 41 56 41 55 49 89 f5 41 54 49 89 fc 48 8d bf 00 03 00 00 53 48 83 ec 30 65 48 8b 04 25 28 00 00 00 48 89 45 d0 <48> 8b 87 58 fd ff ff 48 3d 80 37 3c c0 74 1a 49 8d 94 24 f0 02 00
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: RSP: 0018:ffffa7b78077fca0 EFLAGS: 00010286
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: RAX: b2e6484fbd696500 RBX: ffff944f4324a000 RCX: 0000000000000001
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: RDX: 0000000000000000 RSI: ffffa7b78077fd78 RDI: 0000000000000300
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: RBP: ffffa7b78077fcf8 R08: 0000000000000000 R09: 0000000000000000
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: R13: ffffa7b78077fd78 R14: ffffa7b78077fd78 R15: 0000000000000000
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: FS: 0000000000000000(0000) GS:ffff9451d0b40000(0000) knlGS:0000000000000000
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: CR2: 0000000000000058 CR3: 0000000109c20000 CR4: 00000000003506e0
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: Call Trace:
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel:
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: ? wait_for_completion_timeout+0x1d/0x20
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: typec_partner_register_altmode+0xe/0x10 [typec]
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: ucsi_register_altmode.constprop.0+0x1e4/0x270 [typec_ucsi]
 Jun 06 15:55:28 juergen-HP-ENVY-x360-Convertible-13-ar0xxx kernel: ucsi_register_altmodes+0x156/0x210 [typec_ucsi]
 Jun 06 15:5...

Read more...

affects: ubuntu-release-upgrader (Ubuntu) → linux (Ubuntu)
Revision history for this message
Jürgen Hemelt (jhemelt) wrote :

Thanks for your help. Obviously this seems to be the reason for the bug. I blacklisted the ucsi_acpi module and the system boots correctly. Hopefully there will be a backport for the 5.15. kernel so that I can remove the blacklist. Otherwise I have to wait for an Ubuntu distro with 5.16. kernel.
Again thanks for your effort.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.