Ubuntu 22.10 only works with nomodeset - will freeze otherwise

Bug #2000829 reported by Attila
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Ubuntu 22.10 only works with nomodeset - will freeze otherwise.

A fresh install of Ubuntu 22.10 on Dell Latitude 7390. This was achieved with adding the nomodeset in the GRUB, while I was booting from the live USB (without nomodeset) - the system freezes at one point.

After install, when booting the system from the SSD, I have to keep using nomodeset, otherwise, the system will freeze quite quickly.

Further, if I issue the command in the retminal:

systemctl suspend
or
systemctl hibernate

The system will go into suspend/hibernate mode, from which I am unable to get back to work. No keyboard keypress, no mouse move, no power button will wake the system up. I will have to do a hard reset by pressing the power button for 5 seconds and start the system again.

I have been using 18.04.6 and 16.04 for a little while on this machine to test them out. 16.04 will not require nomodeset, I am able to install from USB and run the system off SSD, all goes fine, until the system goes into suspend/hibernate, when, similar to 22.10, the system will no longer wake up.

I have also tried the 18.04.6 which behaves similar to 16.04, no need for nomodeset at install time, nor after, for normal running, until the system will go into suspend/hibernate... then, it no longer wakes up?

NOTE: I had Windows 10 Pro on it prior which worked well - I mention this in order to exclude the hardware failure.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-26-generic 5.19.0-26.27
ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
Uname: Linux 5.19.0-26-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: maximus 1481 F.... wireplumber
 /dev/snd/seq: maximus 1478 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 1 11:14:34 2023
InstallationDate: Installed on 2023-01-01 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. Integrated Webcam_HD
 Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 7390
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic root=UUID=21a5ce3b-5646-49ba-a1fc-ae8a100106d5 ro quiet nomodeset splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-26-generic N/A
 linux-backports-modules-5.19.0-26-generic N/A
 linux-firmware 20220923.gitf09bebf3-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2022
dmi.bios.release: 1.30
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.30.0
dmi.board.name: 09386V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.30.0:bd11/20/2022:br1.30:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn09386V:rvrA00:cvnDellInc.:ct10:cvr:sku081B:
dmi.product.family: Latitude
dmi.product.name: Latitude 7390
dmi.product.sku: 081B
dmi.sys.vendor: Dell Inc.

Revision history for this message
Attila (usingubuntu) wrote :
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
Attila (usingubuntu)
information type: Public → Private Security
Revision history for this message
Alex Murray (alexmurray) wrote :

By marking this bug Private Security it is not able to be seen by the required developers - I am marking it public again as there doesn't appear to be anything security relevant here.

information type: Private Security → Public
Revision history for this message
Attila (usingubuntu) wrote :

By searching on google I could see others have similar issues:

https://www.google.com/search?q=ubuntu+does+not+wake+up+after+sleep

Revision history for this message
Attila (usingubuntu) wrote :

I have freshly reinstalled 22.10 from USB live with nomodeset added at boot in GRUB. Then, after install I issued:

sudo systemctl suspend

The system went into suspend mode. After, I woke up the system by pressing the power button. The screen remained blank, however, I have noticed the keyboard backlight to switch on and then fade away and switch back on if I moved around on the touchpad.

Therefore, I have tried to log in as usual (without seeing anything), after which I pressed CTRL+ALT+T to launch a terminal and then I used:

sudo reboot

Followed by my password.

And the system rebooted.

Then, even further, I have managed to SSH to this Dell Latitude 7390 and can now confirm, the system is fine after wake up, with the screen remaining blank/black.

I have attached the output for:

journalctl -eb -1

Which contains the wake-up process.

Revision history for this message
Attila (usingubuntu) wrote :

With the help of tomreyn (Tom Reynolds) from #ubuntu on libera.chat I managed to gather the attached netconsole kernel debug info. The no 2 and no 4 contain at the very end a CPU not responding and shutting down CPUs.

This is on a fresh install of 22.10 with no updates (only some other installs like netconsole, mc, etc).

If there is any more I can provide, feel free to comment.

netconsole.log.1-frozen-2-seconds-after-desktop-shows-without-nomodeset

Revision history for this message
Attila (usingubuntu) wrote :

netconsole.log-2-frozen-after-aprox-25-seconds-after-desktop-without-nomodeset

(has some CPU not responding at the end)

Revision history for this message
Attila (usingubuntu) wrote :

netconsole.log-3-frozen-after-desktop-shown-less-than-20-seconds-without-nomodeset

Revision history for this message
Attila (usingubuntu) wrote :

netconsole.log-4-frozen-after-about-50-seconds-after-desktop-shown-without-nomodeset

(has some CPU not responding at the end)

NOTE: netconsole is very nice! :) on the host machine (the one that is being debugged), for me wifi was not suitable and had to switch to eth (cable) in order for this to work. For anyone willing to do similar debugging the below link might be helpful:

https://wiki.ubuntu.com/DebuggingKernelBoot

Revision history for this message
Attila (usingubuntu) wrote :

NOTE: by using nomodeset for kernel boot option, the system boots fine and runs fine. Only issue is when it is sent to sleep and has to wake up!

Attached a netconsole log for the below scenario:

booted with nomodeset
started firefox
loaded google.com
closed firefox
CTRL+ALT+T to start a terminal window
started a 2nd terminal window
waited and did nothing for about 1 minute
issued sudo systemctl suspend
in about 1 minutes time I pressed the power button to wake up the system
then SSH into the system
ran top, all went fine

Revision history for this message
Attila (usingubuntu) wrote (last edit ):

Log 8: Booting up the system into the desktop (user logged in automatically) - with nomodeset.

Revision history for this message
Attila (usingubuntu) wrote :

Log 8: Shutting down - opening terminal and issuing:

sudo shutdown now

Revision history for this message
Attila (usingubuntu) wrote :

Log 9.1: bootup into desktop with nomodeset

Revision history for this message
Attila (usingubuntu) wrote :

Log 9.2: open terminal and issue sudo systemctl suspend

Revision history for this message
Attila (usingubuntu) wrote :

Log 9.3: ssh into debugged system

Revision history for this message
Attila (usingubuntu) wrote :

Log 9.4: shutdown debbuged system via ssh

Revision history for this message
Benjamin Renard (brenard) wrote :

With some help (https://gitlab.freedesktop.org/drm/intel/-/issues/4813), I finally found a better workaround than the "nomodeset" kernel parameter : replace it by "i915.enable_psr=0". See https://gitlab.freedesktop.org/drm/intel/-/issues/4813 for details. For me, all seem works well now (including suspend on RAM/disk and with/without my DisplayLink USB-C dock).

Revision history for this message
Attila (usingubuntu) wrote :

Thank you for this, Benjamin Renard! I have tried this and indeed, the problem is gone. I only have the laptop, no additional displays attached, however, it works fine! Until the problem is 100% solved by someone, I will just use the "i915.enable_psr=0" kernel parameter at boot time. For anyone who is looking to do the same, just follow the steps after >>> Solution – Part II (Permanent "nomodeset" option) <<< from https://www.dell.com/support/kbdoc/en-uk/000123893/manual-nomodeset-kernel-boot-line-option-for-linux-booting and replace "nomodeset" with i915.enable_psr=0

Any other updates to this issue are appreciated here! :) Have a great week!

PS: a more transparent and better written bug report can be found here -> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006994

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.