on reboot with linux-image-6.5.0-34 system hangs at loading initial ramdisk

Bug #2063512 reported by James Hill
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-545 (Ubuntu)
Confirmed
Undecided
Unassigned
nvidia-graphics-drivers-550 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

loading initial ramdisk hangs only with linux-image-6.5.0-34

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-550 550.67-0ubuntu1.22.04.2
ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 16:36:07 2024
InstallationDate: Installed on 2021-01-20 (1191 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: nvidia-graphics-drivers-550
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Changed in nvidia-graphics-drivers-550 (Ubuntu):
status: New → Confirmed
Changed in nvidia-graphics-drivers-545 (Ubuntu):
status: New → Confirmed
Revision history for this message
ciriffo (piccoccio) wrote :

I've the same issue on ubuntu 22.04, kernel 6.5.0-34, my VGA: Intel Corporation Device a780;

Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1
    compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
    gpu: i915 resolution: 1920x1080~60Hz

Revision history for this message
COLIN Stéphane (bigbob-fun) wrote :

Doesn't seem to be related to « nvidia » :

bigbob@bigbob-t480s:~$ dpkg -l | grep nvidia
bigbob@bigbob-t480s:~$

Revision history for this message
Hartmut Manz (hartmut-manz) wrote :

With the new kernel update 6.5.0-35 this problem is fixed for me

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.