I just installed Ubuntu for the first time, and I dint have the option to connect to wifi at all. Looked on here and tried everything and nothing worked. Here's my terminal with the Broadcom stuff

"01:00.0 Network controller [0280]: Broadcam Inc. And subsidiaries Device [14e4:4434] (rev 04)

And then right below it

"01:00.0 Network controller [0280]: Broadcam Inc. And subsidiaries Device [14e4:5f72](rev 04)

I run Xubuntu version 25.10 with Nvidia driver enabled in system settings. After installing the latest updates the screen shows some flickering. When I try to change to Xorg X open source driver on next reboot I have a black screen. By entering into recovery console I can sort of 'purge' the nvidia settings but still I cannot enable the open source driver without black screen. What is going wrong here?

Thanks for any advice on resolving this issue.

Best regards jd

(venv) PS D:\workspace\project_db> ssh -i "karachi-server-key.pem" ubuntu@3.1XX.XXX.61

Load key "karachi-server-key.pem": Permission denied

ubuntu@3.109.184.61: Permission denied (publickey).

logs are above as follows

I am a long-time Ubuntu user, and have been using this laptop with Ubuntu as the only OS since I bought it six years ago. I am currently running Ubuntu 25.10. The laptop has always booted up in around a minute or so. Recently I added a second screen for my coding work so I can ssh to Arduinos, ESP32s and my new toy, a Jetson Orin Nano. At first booting was as before, but I noticed that sometimes the Ubuntu symbol appeared on the second screen but without the login box, so I had no way of logging in.

I held down the power switch (I should have ran Alt-Print-reisub, but I forgot about that until now), and then powered it back on. This time both screens remained blank. I powered down again by holding down the power switch (bad I know) removed the second screen and powered back up. Nothing was happening on the screen, but the HDD LED was flashing now and then and sometimes the fan started up, but the screen remained blank for several minutes.

After a while I left the laptop to go and do something else. When I returned the login screen was there and everything worked as normal. I intend to shutdown properly now without the second screen connected to see if I can logon in a reasonable time frame next time, but I thought I'd ask if anyone here has had experienced this first.

Recently, I have been noticing that for Ubuntu 24.04.4, whenever the computer resumes from an automatic suspend mode, it actually did not suspend and resume. Rather, the computer logout and I was required to login again. I say this because a resume screen does not appear but the GDM login screen appears. Also, after login, I have to restart all my apps again.

Below are some info I can gather about the system, GPU and suspend log related to the suspend and resume event.

$ uname -a
Linux MACHINE 6.17.0-19-generic #19~24.04.2-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar  6 23:08:46 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.4 LTS
Release:    24.04
Codename:   noble

$ nvidia-smi --query-gpu=gpu_name,driver_version --format=csv,noheader   
NVIDIA GeForce RTX 5060 Ti, 590.48.01

$ journalctl -b | grep -i suspend
Apr 01 10:25:52 MACHINE systemd-logind[1659]: The system will suspend now!
Apr 01 10:25:52 MACHINE ModemManager[1793]: <msg> [sleep-monitor-systemd] system is about to suspend
Apr 01 10:25:56 MACHINE systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions...
Apr 01 10:25:56 MACHINE suspend[260828]: nvidia-suspend.service
Apr 01 10:25:56 MACHINE logger[260828]: <13>Apr  1 10:25:56 suspend: nvidia-suspend.service
Apr 01 10:25:58 MACHINE systemd[1]: nvidia-suspend.service: Deactivated successfully.
Apr 01 10:25:58 MACHINE systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
Apr 01 10:25:58 MACHINE systemd[1]: nvidia-suspend.service: Consumed 1.280s CPU time.
Apr 01 10:25:58 MACHINE systemd[1]: Starting systemd-suspend.service - System Suspend...
Apr 01 10:25:58 MACHINE systemd-sleep[260850]: Performing sleep operation 'suspend'...
Apr 01 10:25:58 MACHINE kernel: PM: suspend entry (deep)

Apr 01 11:25:15 MACHINE kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Apr 01 11:25:15 MACHINE kernel: PM: suspend exit
Apr 01 11:25:15 MACHINE systemd-sleep[260850]: System returned from sleep operation 'suspend'.
Apr 01 11:25:16 MACHINE systemd[1]: systemd-suspend.service: Deactivated successfully.
Apr 01 11:25:16 MACHINE systemd[1]: Finished systemd-suspend.service - System Suspend.
Apr 01 11:25:16 MACHINE systemd[1]: systemd-suspend.service: Consumed 1.087s CPU time.
Apr 01 11:25:16 MACHINE systemd[1]: Reached target suspend.target - Suspend.
Apr 01 11:25:16 MACHINE systemd[1]: Stopped target suspend.target - Suspend.
Apr 01 11:25:16 MACHINE suspend[261267]: nvidia-resume.service
Apr 01 11:25:16 MACHINE logger[261267]: <13>Apr  1 11:25:16 suspend: nvidia-resume.service
Apr 01 11:25:16 MACHINE systemd-logind[1659]: Operation 'suspend' finished

The system used to be able to suspend and resume.

How to fix this issue?

Update: I noticed this gdm log for the Automatic Suspend event. These are its final few lines.

$ journalctl -b | grep -i gdm
....
Apr 01 10:25:35 MACHINE /usr/libexec/gdm-x-session[261646]: (II) NVIDIA(GPU-0): Deleting GPU-0
Apr 01 10:25:35 MACHINE /usr/libexec/gdm-x-session[261646]: (II) Server terminated successfully (0). Closing log file.
Apr 01 10:25:35 MACHINE gdm-launch-environment][261486]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Apr 01 10:25:35 MACHINE gdm3[2357]: Gdm: Child process -261639 was already dead.
Apr 01 10:25:35 MACHINE gdm3[2357]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed

I use fzf to searched for error and session at the timestamp of the automatic suspend event, and found a fatal server error.

$ journalctl -b |  grep 10:25 | fzf -m > error_session.log

$ cat error_session.log
Apr 01 10:25:34 MACHINE gnome-session[262658]: gnome-session-binary[262658]: GnomeDesktop-WARNING: Could not create transient scope for PID 262985: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Apr 01 10:25:34 MACHINE gnome-session[262658]: gnome-session-binary[262658]: GnomeDesktop-WARNING: Could not create transient scope for PID 262939: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Apr 01 10:25:32 MACHINE gnome-session[262658]: gnome-session-binary[262658]: GnomeDesktop-WARNING: Could not create transient scope for PID 262690: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Apr 01 10:25:32 MACHINE gnome-session[262658]: gnome-session-binary[262658]: GnomeDesktop-WARNING: Could not create transient scope for PID 262687: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Apr 01 10:25:32 MACHINE gnome-session[262658]: gnome-session-binary[262658]: GnomeDesktop-WARNING: Could not create transient scope for PID 262672: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Apr 01 10:25:17 MACHINE gnome-session[244008]: gnome-session-binary[244008]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Apr 01 10:25:34 MACHINE gnome-session-binary[262658]: GnomeDesktop-WARNING: Could not create transient scope for PID 262985: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Apr 01 10:25:34 MACHINE gnome-session-binary[262658]: GnomeDesktop-WARNING: Could not create transient scope for PID 262939: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Apr 01 10:25:32 MACHINE gnome-session-binary[262658]: GnomeDesktop-WARNING: Could not create transient scope for PID 262690: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Apr 01 10:25:32 MACHINE gnome-session-binary[262658]: GnomeDesktop-WARNING: Could not create transient scope for PID 262687: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Apr 01 10:25:32 MACHINE gnome-session-binary[262658]: GnomeDesktop-WARNING: Could not create transient scope for PID 262672: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Apr 01 10:25:17 MACHINE gnome-session-binary[244008]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Apr 01 10:25:21 MACHINE gnome-session[261742]: gnome-session-binary[261742]: WARNING: Could not check if unit gnome-session-x11@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Apr 01 10:25:21 MACHINE gnome-session-binary[261742]: WARNING: Could not check if unit gnome-session-x11@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Apr 01 10:25:30 MACHINE /usr/libexec/gdm-x-session[262381]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Apr 01 10:25:19 MACHINE /usr/libexec/gdm-x-session[261646]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Apr 01 10:25:17 MACHINE /usr/libexec/gdm-x-session[243731]: (EE) Server terminated with error (1). Closing log file.
Apr 01 10:25:34 MACHINE /usr/libexec/gdm-x-session[262753]: Errors from xkbcomp are not fatal to the X server
Apr 01 10:25:32 MACHINE /usr/libexec/gdm-x-session[262415]: Errors from xkbcomp are not fatal to the X server
Apr 01 10:25:23 MACHINE /usr/libexec/gdm-x-session[261978]: Errors from xkbcomp are not fatal to the X server
Apr 01 10:25:22 MACHINE /usr/libexec/gdm-x-session[261826]: Errors from xkbcomp are not fatal to the X server
Apr 01 10:25:21 MACHINE /usr/libexec/gdm-x-session[261732]: Errors from xkbcomp are not fatal to the X server
Apr 01 10:25:16 MACHINE /usr/libexec/gdm-x-session[243731]: Fatal server error:
Apr 01 10:25:32 MACHINE user-session-migration[262632]: Exited with an error

The lines after the Fatal server error at timestamp 10:25:16 are:

Apr 01 10:25:16 MACHINE /usr/libexec/gdm-x-session[243731]: Fatal server error:
Apr 01 10:25:16 MACHINE /usr/libexec/gdm-x-session[243731]: (EE) EnterVT failed for screen 0
Apr 01 10:25:16 MACHINE /usr/libexec/gdm-x-session[243731]: (EE)
Apr 01 10:25:16 MACHINE /usr/libexec/gdm-x-session[243731]: (EE)
Apr 01 10:25:16 MACHINE /usr/libexec/gdm-x-session[243731]: Please consult the The X.Org Foundation support
Apr 01 10:25:16 MACHINE /usr/libexec/gdm-x-session[243731]:          at http://wiki.x.org
Apr 01 10:25:16 MACHINE /usr/libexec/gdm-x-session[243731]:  for help.
Apr 01 10:25:16 MACHINE /usr/libexec/gdm-x-session[243731]: (EE) 

In response to @DanielT comment. I ran the command. These last 3 lines appears in yellow color. However, they don't seem related to my issue.

$ journalctl --user -b0
---
Apr 01 12:25:19 MACHINE gnome-shell[262700]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
Apr 01 12:25:19 MACHINE gnome-shell[262700]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
Apr 01 12:26:38 MACHINE gnome-text-edit[269410]: Broken accounting of active state for widget 0x576f6476e830(GtkPopoverMenu)

I upgraded from Ubuntu server 24.04 lts to 25.10 and after that I can't connect to Tor (though my Snowflake proxy which I run is up and no issues), login manager having issues in boot, half of sites are not loading (Not a problem with internet I checked) and rdr2 installer isn't working. Weird thing is in logs, there doesn't seem to be any issue and this is like a pause/hang even when my specs are good enough (i5-13450 hx, rtx 4050, 24+512). Before upgrade, there wasn't any issue, and system was stable and working. But suddenly after upgrade, half of my system isn't working. This is my first upgrade, so maybe I think I missed something. Any advice on what I should do? Thanks

It all started today. Whenever I try to update anything using the sudo command the terminal throws an error. See the error as attached.

Loading new broadcom-sta-6.30.223.271 DKMS files...
Building for 6.17.0-19-generic
Building initial module for 6.17.0-19-generic
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/broadcom-sta-dkms.0.crash'
Error! Bad return status for module build on kernel: 6.17.0-19-generic (x86_64)
Consult /var/lib/dkms/broadcom-sta/6.30.223.271/build/make.log for more information.
dpkg: error processing package broadcom-sta-dkms (--configure):
installed broadcom-sta-dkms package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of bcmwl-kernel-source:
bcmwl-kernel-source depends on broadcom-sta-dkms (= 6.30.223.271-23ubuntu1.1); however:
Package broadcom-sta-dkms is not configured yet.

dpkg: error processing package bcmwl-kernel-source (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.  
Processing triggers for libc-bin (2.39-0ubuntu8.7) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for dbus (1.14.10-4ubuntu4.1) ...
Processing triggers for initramfs-tools (0.142ubuntu25.8) ...
update-initramfs: Generating /boot/initrd.img-6.17.0-19-generic
Errors were encountered while processing:
  broadcom-sta-dkms
  bcmwl-kernel-source
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@prabhakar-gautam-HP-Laptop:~# █

I already tried removing and purging these two specific packages, but I can't reinstall them at all or else it gives the same error. I am new to Ubuntu, so help me in ways that don't wreck my system. I found information on some other forum about deleting the kernel altogether, but I don't know how to boot from an old kernel.

Xubuntu 25.10 > do-release-upgrade -d > 26.04 beta

The firmware is now split by vendor. One would expect only the x86 firmware to be included. But I also see e.g. a /lib/firmware/arm directory. None of the "what package provides" methods I found via google finds the providing package. Are these files left-overs from the previous monolithic firmware package? Can I safely purge those arm firmware files?

Also it is not unthinkable that a vendor provides x86 and arm firmware. How would that situation be handled?

I rent two virtual servers at Strato. A few days ago I upgrade both machines via do-release-upgrade to Ubuntu 24.04 coming from 22.04. On one machine everything works fine, on the other one I have DNS name resolution problems. I found this question: DNS at systemd's 127.0.0.53 is ignoring some lookups and tried following the answer to that. I also had a look at https://wiki.ubuntuusers.de/systemd/systemd-resolved/

As far as I could say, the systemd-resolved looked like it should. /etc/resolv.conf was a symlink to /run/systemd/resolve/stub-resolv.conf in /etc/systemd/resolved.conf I had the same content as on the other server where it works fine:

[Resolve]
DNS=85.214.154.81
DNS=2620:fe::fe
FallbackDNS=85.215.236.86

But after the upgrade to 24.04 name resolution was just impossible. I changed DNS server addresses, I removed the symlink und recreated it. I checked if there is any other software triing to make dns, but there wasn't. If I try to ping a domain like google.com I only get Temporary failure in name resolution

The only possibility I found to be able to have name resolution is to remove the symlink and instead make a plain file /etc/resolv.conf with nameserver 8.8.8.8 as the only content, other strato nameservers don't work there.

Then I can do apt update and upgrade and ping domains. But after a while without touching (I am not yet sure how long it takes, but it is less then 12 hours) name resolution again doesn't work. Even though systemd-resolved status says it runs, without failures. A restart of the service makes name resolution functioning again.

If I google for my problem, beneath the resolved things I mentioned above, most likely it is suggested I should check my netplan configuration. But there is no netplan configuration, beacuse netplan is not installed (on the other server, that doesn't have any problems, it is not installed either).

I checked local firewall, if there is anything outgoing blocked, but there isn't. I reinstalled systemd-resolved.

On this server I am only hosting a nextcloud, nothing else happens on this server.

I am pretty sure I forgot some information you would need to help me and also forget to write soemthin I already tried as I invested multiple hours in this till now. I appreciate any hint and help with this.

The weirdest part for me is, that 8.8.8.8 as nameserver in /etc/resolv.conf works, other servers, that are reachable by there IP don't. And if I set the symlink and write 8.8.8.8 as nameserver in /etc/systemd/resolved.conf it doesn't work either. I sure miss somethin here, but I don't get what...

Thanks in advance.

Okay, again I did now:

resolvectl log-level debug
resolvectl query example.com
journalctl -u systemd-resolved -b0

And here is the section from the log I think is relevant.

    Apr 01 14:31:23 h2976228.stratoserver.net systemd-resolved[323]: Setting log level to debug.
Apr 01 14:31:23 h2976228.stratoserver.net systemd-resolved[323]: Sent message type=method_return sender=n/a destination=:1.15 path=n/a interface=n/a member=n/a cookie=14 reply_cookie=2 signature=n/a error-name=n/a error-message=n/a
Mär 27 15:53:04 h2976228.stratoserver.net systemd[1]: Stopping systemd-resolved.service - Network Name Resolution...
Mär 27 15:53:04 h2976228.stratoserver.net systemd[1]: systemd-resolved.service: Deactivated successfully.
Mär 27 15:53:06 h2976228.stratoserver.net systemd[1]: Stopped systemd-resolved.service - Network Name Resolution.
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Got message type=method_call sender=:1.16 destination=org.freedesktop.resolve1 path=/org/freedesktop/resolve1 interface=org.freedesktop.resolve1.Manager member=ResolveHostname  cookie=2 reply_cookie=0 signature=isit error-name=n/a error-message=n/a
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: idn2_lookup_u8: example.com → example.com
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetConnectionUnixProcessID cookie=15 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.0 path=n/a interface=n/a member=n/a  cookie=9 reply_cookie=15 signature=u error-name=n/a error-message=n/a
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: D-Bus hostname resolution request from client PID 12057 (resolvectl) with UID 0
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Looking up RR for example.com IN A.
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Looking up RR for example.com IN AAAA.
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=16 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetNameOwner cookie=17 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.0 path=n/a interface=n/a member=n/a  cookie=11 reply_cookie=17 signature=s error-name=n/a error-message=n/a
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: sd-event: Failed to create timer event "query-timeout": Invalid argument
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Freeing transaction 65111.
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Freeing transaction 63768.
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=RemoveMatch cookie=18 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Sent message type=error sender=n/a destination=:1.16 path=n/a interface=n/a member=n/a cookie=19 reply_cookie=2 signature=s error-name=org.freedesktop.DBus.Error.InvalidArgs error-message=Invalid argument
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Failed to process message type=method_call sender=:1.16 destination=org.freedesktop.resolve1 path=/org/freedesktop/resolve1 interface=org.freedesktop.resolve1.Manager member=ResolveHostname cookie=2 reply_cookie=0 signature=isit error-name=n/a error-message=n/a: Invalid argument
Apr 01 14:31:33 h2976228.stratoserver.net systemd-resolved[323]: Got message type=method_return sender=org.freedesktop.DBus destination=:1.0 path=n/a interface=n/a member=n/a  cookie=10 reply_cookie=16 signature=n/a error-name=n/a error-message=n/a

The output of uname -a is (behind the hostname):

5.4.0 #1 SMP Mon Sep 30 15:36:27 MSK 2024 x86_64 x86_64 x86_64 GNU/Linux

Hello Everyone I am using Ubuntu 24.04.4 LTS.

Couple of days ago I think that my GNOME started to having an issue with showing wifi. - Basically my Wifi is connected, I can ping both domains and IP's, go to the internet, i checked with nmcli device status I am connected, IP commands are showing that I have an IP address, I can do traceroute and etc..

Device Info: MediaTek MT7921 Wi‑Fi adapter

Tried Restarting NetworkManager, Firewall is not making any problems, I tried to reset gnome-shell but nothing worked.

The issue is even though I am connected Wifi Icon is showing question mark.

On Ubuntu 24.04, poweroff alternatives (hibernate, suspend) are missing on menus, and broken on cli (crash computer, hard reboot necessary).

how to fix this?

I'm a new Ubuntu user. I'm using ubuntu 24.04.3 LTS for about one month now. The problem is Ubuntu window started freezing recently. Mouse point not moving, keyboard not responding, if i'm listening to audio the last second repeating non-stop. How to fix it??? After installing Ubuntu the laptop starts without any problem. The problem arise while using the laptop.

I am new to all this so I probably screwed up a lot, but Xubuntu 24.04.4 was working last night. This morning it got stuck on initramfs before the login screen. I don’t even know what I did to ‘fix’ that (I know I probably broke it here, but I don’t know what I did. I’m sorry.) I think I used fsck with sda1 and sda4 and that did something. Now I’m stuck at the login screen, and nothing will type where my password would go. It’s as simple as that, it's not even typing.

I have a tower running Ubuntu server and I had it configured to always display the motd on ssh login. It has been doing so without error for months and it suddenly stopped displaying today. Went through the pam.d to see if the lines were there for it and they are. The sshd_config is set to use PAM and the print motd is uncommented and set to yes. The run-parts command prints the expected results of the motd as well, no errors. I don't know what could have caused this. tried rebooting to see if it was something odd with startup and it still wasn't working. All the files have execute privileges as well

Any ideas?

This was an active issue and incident as of March 21, 2026, with resolution on or about March 24, 2026.

This issue recurred on April 1, 2026.

I am seeing a question mark on my networking in Desktop and Network Manager but my network is functioning with internet. Sometimes I am told to 'sign in' to my network even though I am already connected. (Or in some cases, people are being asked to sign into Wi-Fi when they don't have Wi-Fi.)

Why is this?

Playing audio like Spotify playlist doesn't keep Ubuntu from suspending, when "suspend after [] minutes" is turned on. I tried to find a solution for a good long while in the process of switching to Ubuntu before giving up and turning off 'suspend automatically' entirely.

Playing videos, on the other hand, works just fine and will keep my PC's screen from turning off or my PC from suspending. It also doesn't suspend while downloading files.

To be clear: I don't want to prevent my screen from sleeping while there's only audio (no video) playing.

I tried this script but I'm not sure if I installed it correctly, or if there's some other issue. It didn't work when I tested it with Spotify and it in fact seemed to stop me from manually turning off my PC by clicking 'power off' (it froze on a half dimmed screen until I clicked the physical power button).

Of course, I'd like to suspend automatically after a set time when my PC is not playing audio, to save power. Is there any way to do this? Is it maybe Spotify itself that's the problem, and if I play my music in another app it won't automatically suspend?

I want to stop my PC from suspending while Spotify is playing, even when it's playing in the background (which is why the programs that keep your PC awake when there's a full-screen application aren't suitable).

I have a Lenovo P1 Gen6 and recently installed 24.04.1 on it. Through my dock (Lenovo 40AN thunderbolt 3 dock) Ubuntu recognized 3 monitors (1 laptop display and 2 external monitors), but it only has picture on one external monitor. There's also another monitor that isn't recognized. These all worked with Ubuntu 22.04 as well with an early release of 24.04.

I switched to the nvidia-driver-550 and installed the synaptic DisplayLink driver.

This is what I get on rebooting now:

[    2.330459] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)  
[    2.417906] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)  
[    3.402894] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)  
[    3.498167] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)

This has been on my screen for about 10 minutes now, so I'm pretty sure I'm stuck at a black screen here.

I can't get a shell to run any commands.

I had 3 different kernels installed. I rebooted twice more selecting a different one each time. 6.8.0-40-generic worked, even without recovery, however there are a few issues:

1. Only the built-in display is recognized.
2. The built-in 4k display is only at 1920x1200 resolution.
3. Before switching to Wayland display, the console shows ^@ and when returning to console (e.g. reboot) I see there are a bunch more ^@
4. Everything else seems to work.

I guess recovery mode is out of the question ...

Now what should I do?

I have an AWS EC2 FIPS compliant 20.04 instance, I have applied the DISA STIGS to this instance, except for one. Every time I set the password for Single User mode I am no longer able to boot the server. Is this not possible on AWS? I have discovered some new information, this is only an issue with systems that are in FIPS mode. It seems like the prompt for the username and password comes up before TTYS0 is available for input. If I grab a screenshot of the machine it shows the prompt for a username, but the EC2 serial console is not available. For reference the instructions are below:

Discussion: To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DoD-approved PKIs, all DoD systems (e.g., web servers and web portals) must be properly configured to incorporate access control methods that do not rely solely on the possession of a certificate for access.

Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement.

Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system.

Check Text: Run the following command to verify the encrypted password is set:

$ sudo grep -i password /boot/grub/grub.cfg 

password_pbkdf2 root grub.pbkdf2.sha512.10000.MFU48934NJA87HF8NSD34493GDHF84NG 

If the root password entry does not begin with password_pbkdf2, this is a finding.

Fix Text: Configure the system to require a password for authentication upon booting into single-user and maintenance modes. 
 
Generate an encrypted (grub) password for root with the following command: 
 
$ grub-mkpasswd-pbkdf2 
Enter Password: 
Reenter Password: 
PBKDF2 hash of your password is grub.pbkdf2.sha512.10000.MFU48934NJD84NF8NSD39993JDHF84NG 

Using the hash from the output, modify the /etc/grub.d/40_custom file with the following command to add a boot password:

$ sudo sed -i '$i set superusers=\"root\"\npassword_pbkdf2 root <hash>' /etc/grub.d/40_custom 

where <hash> is the hash generated by grub-mkpasswd-pbkdf2 command.

Generate an updated "grub.conf" file with the new password by using the following command:

$ sudo update-grub

I'm trying to get the Remote Desktop feature working on Ubuntu (Desktop) 22.04, but I can't seem to connect to my Ubuntu desktop from a Windows (10) PC. I'm using these instructions:

• https://help.ubuntu.com/stable/ubuntu-help/sharing-desktop.html.en
• https://linuxconfig.org/ubuntu-22-04-remote-desktop-access-from-windows-10

I've enabled Remote Desktop in the (Ubuntu) Sharing Settings, however when I run the Remote Desktop client (i.e. the standard mstsc.exe client) on Windows and connect to the IP address of the Ubuntu server, I get this login dialog:

The Session dropdown has 4 options:

• Xorg
• Xvnc
• vnc-any
• neutrinordp-any

Selecting Xorg and some login credentials causes the window to close. If I leave the credentials blank I get an Ok dialog with this message:

Connecting to sesman ip 127.0.0.1 port 3350
sesman connect ok
sending login info to session manager, please wait...
login failed for display 0

If I click Ok the it takes me back to the login dialog.

If I select Xvnc and some credentials then I get a blank green screen.

I get similar behaviour if I disable Remote Desktop in the Sharing settings.

I tried the same thing with a second Ubuntu 22.04 host and get the same thing.

I am deaf in one ear and want Ubuntu to mix both left and right audio channels to mono audio. There is an Accessibility Setting for this in Windows, but I cannot find one in Ubuntu. The only Hearing Accessibility Setting I can find is for Visual Alerts. I am currently using 21.10, but also couldn't didn't see anything on my other computer running 20.04 LTS.

I saw a couple of older search results for mono audio in individual programs, but would prefer a solution that handles audio for the entire OS.

Thanks for any help.

A few days ago Ubuntu froze and I hard reboot the laptop and when I wanted to boot Ubuntu again this message showed up.

[    0.057166] BUG: Bad page state in process swapper  pfn:23c706
[    0.057220] BUG: Bad page state in process swapper  pfn:23c708
[    0.057251] BUG: Bad page state in process swapper  pfn:23c70a
[    0.057281] BUG: Bad page state in process swapper  pfn:23c70c
[    0.057310] BUG: Bad page state in process swapper  pfn:23c710
[    0.057339] BUG: Bad page state in process swapper  pfn:23c712
[    0.057368] BUG: Bad page state in process swapper  pfn:23c728
[    0.057397] BUG: Bad page state in process swapper  pfn:23c742
[    0.057425] BUG: Bad page state in process swapper  pfn:23c770
[    0.057454] BUG: Bad page state in process swapper  pfn:23c781
[    0.057483] BUG: Bad page state in process swapper  pfn:23c7c1
[    0.057512] BUG: Bad page state in process swapper  pfn:23c7d3
[    0.057540] BUG: Bad page state in process swapper  pfn:23c7d9
[    0.057569] BUG: Bad page state in process swapper  pfn:23c7eb
/dev/sda2: recovering journal
/dev/sda2: clean, 567812/2444624 files, 7825769/9765625 blocks
_

After searching a lot on the internet, I tried to boot with older kernels and also I booted Ubuntu with different grub parameters (like nomodeset), and every time I faced different kernel panic errors as you can see (and sometimes "Fixing recursive fault but a reboot is needed"):

[    0.592978] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    0.593719] CR2: 0000000000000008 CR3: 000000020c410001 CR4: 00000000003706e0
[    0.594467] Call Trace:
[    0.595196]  free_unref_page+0x56/0x70
[    0.595929]  __free_pages+0x69/0x80
[    0.596656]  free_reserved_area+0xf8/0x160
[    0.597360]  free_init_pages+0x6d/0x80
[    0.598063]  free_kernel_image_pages+0x17/0x40
[    0.598753]  ? rest_init+0xba/0xba
[    0.599457]  free_initmem+0x2d/0x30
[    0.600147]  kernel_init+0x27/0x116
[    0.600850]  ret_from_fork+0x22/0x30
[    0.601539] Modules linked in:
[    0.602232] CR2: 0000000000000008
[    0.602896] ---[ end trace 3734b6e0a5224b58 ]---
[    0.603558] RIP: 0010:free_unref_page_commit+0x74/0xd0
[    0.604228] Code: 83 f9 04 74 61 48 69 c0 c0 05 00 00 48 8b 54 02 60 65 48 03 15 15 18 d6 5e 48 c1 e1 04 4a 8d 04 02 48
[    0.604935] RSP: 0000:ffffa22f0006fe38 EFLAGS: 00010002
[    0.605629] RAX: ffff8f0326d80020 RBX: 0000000000000202 RCX: 0000000000000000
[    0.606324] RDX: ffff8f0326d80000 RSI: ffffe8efc831e9c8 RDI: ffffe8efc831e9c0
[    0.607026] RBP: ffffa22f0006fe38 R08: 0000000000000020 R09: 0000000000000001
[    0.607716] R10: ffff8f032efd8280 R11: ffffa22f0006fde0 R12: ffffe8efc831e9c0
[    0.608413] R13: 000000000020c7a7 R14: ffffffff a29a8000 R15: cccccccccccccccc
[    0.609103] FS:  0000000000000000(0000) GS:ffff8f0326d80000(0000) knlGS:0000000000000000
[    0.609798] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    0.610474] CR2: 0000000000000008 CR3: 000000020c410001 CR4: 00000000003706e0
[    0.611157] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
[    0.611860] Kernel Offset: 0x20000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[    0.612553] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 ]---
_

I booted Ubuntu via recovery mode and I saw weird behavior on the screen. By the way, I was able to enter the root shell prompt and I saw my files too. I also copied my necessary files to a USB, but the root shell prompt was unstable and after 1 or 2 minutes the same errors appeared on the screen. I was no longer able to work with it and the only solution was rebooting.

After all of these, I booted from a Ubuntu bootable live USB for any chance of backing up my data and when the disk's process was completed, it was just a blank screen.

I use Ubuntu 20.04 LTS. In the grub menu there are 2 possible kernels:

5.11.0.40-generic
5.11.0.38-generic

My laptop is Acer Aspire F5-573G-793D
CPU: Intel Core i7-7500U 2.7Ghz
RAM: 8 GB DDR4
GPU: Nvidia GeForce 940 MX with 4GB dedicated VRAM

1. Is my RAM damaged or is there any hardware issue generally?
2. How can I back up my data?

In my current network topology I have multiple VLANs - each of which has it's own routing:

VLAN 10:
  DHCP:    10.0.10.10-10.0.10.255
  Subnet:  255.255.255.0
  Gateway: 10.0.10.1

VLAN 11
  DHCP:    10.0.11.10-10.0.11.255
  Subnet:  255.255.255.0
  Gateway: 10.0.11.1

The machine(s) I'm automatically provisioning have a single NIC. This is why I would like to avoid using static configurations and rather relay on the DHCP to provide the "correct" settings.

My yaml looks like this:

network:
  version: 2
  renderer: networkd
  ethernets:
    enp5s0:
      # Designate the connection as "critical to the system", meaning that special care will be taken by systemd-networkd 
      # to not release the IP from DHCP when it the daemon is restarted.
      critical: yes
      dhcp4: no

  vlans:
    cloud:
      id: 10
      link: enp5s0
      dhcp4: yes
      dhcp4-overrides:
        route-metric: 200

    office:
      id: 11
      link: enp5s0
      dhcp4: yes
      dhcp4-overrides:
        route-metric: 100

The problem is it only gets the DHCP settings for the cloud vlan and does nothing with the office one. Am I missing something here?

NOTE:
This is not a duplicate of netplan with multiple vlans on single interface - help needed.

I am using Ubuntu 20.04. Clamtk finding PUA or trojans daily, despite me deleting them and deleting cache and using bleachbit regularly. I have seen the previous post about false positives but how do you tell?

I am a newbie still and not sure what else I can be doing to protect from these or how much they are compromising the security of my system.

I am unable to boot from a Ubuntu Live USB stick (current version 20.04 LTS) whatever I try. The boot stops right after the "disk check" completed successfully. When booting without the splash screen (nosplash), I get the following message:

run-init: can't execute 's/sbin/init': No such file or directory
Target filesystem doesn't have requested /sbin/init.
run-init: can't execute 's/sbin/init': No such file or directory
run-init: can't execute 'etc/init': Permission denied
Kernel Panic - not syncing: Attempted to kill init! exitcode=0x00000100

Kernel panic:

Checking ./install/mt86plus...../install/mt86plus: OK
Check finished: no errors found.

Begin: Moving mount points... ... done.
Begin: Running /scripts/nfs-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
run-init: can't execute '/sbin/init': No such file or directory
Target filesystem doesn't have requested /sbin/init.
run-init: can't execute '/sbin/init': No such file or directory
run-init: can't execute '/etc/init': Permission denied
[   17.659043] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[   17.659714] CPU: 0 PID: 1 Comm: run-init Not tainted 5.4.0-26-generic #30-Ubuntu
[   17.660395] Hardware name: MSI MS-7977/Z170A GAMING M5 (MS-7977), BIOS 1.I0 06/26/2018
[   17.661087] Call Trace:
[   17.661778]  dump_stack+0x6d/0x9a
[   17.662511]  panic+0x101/0x2e3
[   17.663193]  do_exit.cold+0x21/0xb5
[   17.663873]  do_group_exit+0x47/0xb0
[   17.664554]  __x64_sys_exit_group+0x18/0x20
[   17.665226]  do_syscall_64+0x57/0x190
[   17.665912]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   17.666650] RIP: 0033:0x7f3f420e9136
[   17.667344] Code: fa 41 b8 e7 00 00 00 be 3c 00 00 00 eb 15 66 0f 1f 44 00 00 89 d7 89 f0 0f 05 48 3d 00 f0 ff ff 77 22 f4 8
[   17.668086] RSP: 002b:00007ffeba9e41b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
[   17.668829] RAX: ffffffffffffffda RBX: 00007f3f421f0610 RCX: 00007f3f420e9136
[   17.669579] RDX: 0000000000000001 RSI: 000000000000003c RDI: 0000000000000001
[   17.670324] RBP: 0000000000000001 R08: 00000000000000e7 R09: ffffffffffffff80
[   17.671118] R10: 0000000000000002 R11: 0000000000000246 R12: 00007f3f421f0610
[   17.671870] R13: 0000000000000001 R14: 00007f3f421f3fc8 R15: 0000000000000000
[   17.672660] Kernel Offset: 0x22200000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[   17.673497] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 ]---
_

Since the boot does not get me even to a command line, I cannot provide a log as text file. However there is a video of the entire boot process. If you think that helps, I can put that somewhere.

I have been researching for days and believe to have tried every last thing that was suggested in any post I could find. Here is a list of all the things I've tried, not necessarily in chronological order:

1. Verified downloaded ISO successfully (SHA256 as provided here)
2. Tried three different USB sticks, two USB 3, one USB 2, each of which was set up multiple times with the latest version of Rufus (3.10).
3. Tried different USB sockets on the computer, from both of the two USB controllers which the mainboard has.
4. Played around with the few options my Bios offers regarding booting (e.g. UEFI vs. Legacy+UEFI, Support for Win 7/8 installations on/off, secure boot)
5. Updated BIOS
6. Tried booting with UEFI and non-UEFI
7. Tried all these advanced boot options: nosplash, nomodeset, acpi=off, nolapic
8. Disconnected everything from the computer other than Live USB stick, keyboard+mouse dongle and screen
9. Checked that my hardware is supported, which seems to be the case for the (presumably most important) Intel Z170 chipset

My computer:

• MSI Z170A Gaming M5 (MS-7977, specification) (I'm not a gamer, but this model ticked all my boxes at the time...)
• Intel Core i7-6700 CPU (3.40GHz)
• Corsair Vengeance LPX 2x8GB DDR4
• Should not be relevant, but there's a Samsung SSD 950 M.2-drive inside, which houses Windows 10 (which always has been and still is running without issues)

I just don't understand how the kernel (?) cannot access files from an image that it has (presumably) either extracted into memory just a second earlier or at least successfully checked for integrity the moment before. What am I doing wrong??

I really need assistance in setting up SNMP to work with Zabbix on my dashboard. I have set up an Ubuntu 18.04 Zabbix server and have added over 18 agents. All virtual machines with Zabbix agents and they are working great!

Now I have gotten to the point where I need to have the AP's set up for Zabbix. I have followed the instructions and did the following so far:

sudo apt-get update
sudo apt-get install snmp snmp-mibs-downloader
sudo apt-get update
sudo apt-get install snmpd

I opened sudo nano /etc/snmp/snmp.conf and commented the following line:

#mibs :

Then I went into the configuration file:

sudo nano /etc/snmp/snmpd.conf

And from there I made changes to the following lines:

Listen for connections from the local system only
agentAddress  udp:127.0.0.1:161  <--- commented this part.
Listen for connections on all interfaces (both IPv4 and IPv6)
agentAddress udp:161,udp6:[::1]:161  <--remove the comment from this line to make it work.

Then I set up the Zabbix dashboard side. I will attach pictures of the set-up.

1st zabbix dashboard menu:

2nd dashboard set-up menu:

I get the following error:

I will also attach picture that shows my meraki access point set-up.

Meraki AP SNMP set-up:

Lastly, I will add a picture that shows the Linux Zabbix server terminal set up on that config file.

Linux Zabbix Server:

I am stumped and cannot figure out why Zabbix still throwing out that error.

I have gone thru the Zabbix documentation but cannot find a solution to my problem.

I have a Dell XPS 15, with both an integrate Intel GPU and a discrete Nvidia one. I use the Nvidia X Server Settings program to set my system to use the Intel one, for power saving reasons. Regardless, the nouveau driver is loaded, and when this is the case, most times when I try to suspend, suspending fails and I just end up at the lock screen (and am able to unlock normally). Once in a blue moon it works though.

Now I would be happy with a solution that makes the nouveau drivers work with suspend, but I would also be fine with not loading them at all, since I use the Intel GPU anyway.

I'm running 18.04 and kernel 4.15.0-20.

Output of sudo lshw -C display:

  *-display                 
       description: 3D controller
       product: GP107M [GeForce GTX 1050 Mobile]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list rom
       configuration: driver=nouveau latency=0
       resources: irq:141 memory:ec000000-ecffffff memory:c0000000-cfffffff memory:d0000000-d1ffffff ioport:e000(size=128) memory:ed000000-ed07ffff
  *-display
       description: VGA compatible controller
       product: Intel Corporation
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 04
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:130 memory:eb000000-ebffffff memory:80000000-8fffffff ioport:f000(size=64) memory:c0000-dffff

If use Nvidia X Server Settings to switch to the proprietary nvidia drivers, the above changes to reflect that, and suspending works fine. (Actually that's not true, but it breaks in a different and less drastic way, and I don't care.)

I have some files in /etc/modprobe.d/ (that I didn't create) that I would think would blacklist nouveau. Output of cat /etc/modprobe.d/nvidia-graphics-drivers.conf /etc/modprobe.d/blacklist-nvidia.conf:

blacklist nouveau
blacklist lbm-nouveau
alias nouveau off
alias lbm-nouveau off

# Do not modify
# This file was generated by nvidia-prime
blacklist nvidia
blacklist nvidia-drm
blacklist nvidia-modeset
alias nvidia off
alias nvidia-drm off
alias nvidia-modeset off

In /var/log/syslog, after a failed attempt to suspend, I find the following:

systemd[1]: Starting TLP suspend/resume...
kernel: [  113.015159] msr: Direct access to MSR 1b0
systemd[1]: Started TLP suspend/resume.
systemd[1]: Reached target Sleep.
systemd[1]: Starting Suspend...
systemd-sleep[2460]: Suspending system...
kernel: [  113.045574] PM: suspend entry (deep)
kernel: [  113.045575] PM: Syncing filesystems ... done.
kernel: [  113.056901] Freezing user space processes ... (elapsed 0.001 seconds) done.
kernel: [  113.058642] OOM killer disabled.
kernel: [  113.058643] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
kernel: [  113.059619] Suspending console(s) (use no_console_suspend to debug)
kernel: [  113.263840] psmouse serio1: Failed to disable mouse on isa0060/serio1
kernel: [  116.155267] ------------[ cut here ]------------
kernel: [  116.155268] nouveau 0000:01:00.0: timeout
kernel: [  116.155299] WARNING: CPU: 7 PID: 611 at /build/linux-5s7Xkn/linux-4.15.0/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:207 gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
kernel: [  116.155299] Modules linked in: rfcomm ccm thunderbolt msr cmac bnep arc4 uvcvideo btusb videobuf2_vmalloc videobuf2_memops btrtl btbcm videobuf2_v4l2 btintel videobuf2_core bluetooth videodev media ecdh_generic nouveau ttm nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch snd_hda_codec_realtek snd_hda_codec_generic dell_smbios_wmi dell_wmi wmi_bmof dell_wmi_descriptor dell_laptop mxm_wmi intel_wmi_thunderbolt dell_smbios_smm dell_smbios dcdbas dell_smm_hwmon snd_hda_intel snd_hda_codec intel_rapl ath10k_pci snd_hda_core x86_pkg_temp_thermal intel_powerclamp snd_hwdep ath10k_core snd_pcm coretemp kvm_intel snd_seq_midi ath snd_seq_midi_event kvm mac80211 snd_rawmidi snd_seq irqbypass intel_cstate snd_seq_device intel_rapl_perf snd_timer rtsx_pci_ms cfg80211 memstick idma64 virt_dma snd joydev input_leds
kernel: [  116.155320]  mei_me serio_raw soundcore intel_lpss_pci processor_thermal_device mei shpchp intel_pch_thermal intel_lpss intel_soc_dts_iosf int3403_thermal int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad intel_hid wmi mac_hid tpm_crb sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt usbhid rtsx_pci_sdmmc i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd i2c_algo_bit glue_helper cryptd drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops nvme drm nvme_core ahci rtsx_pci libahci i2c_hid hid video
kernel: [  116.155339] CPU: 7 PID: 611 Comm: kworker/u16:6 Tainted: G        W        4.15.0-20-generic #21-Ubuntu
kernel: [  116.155340] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.7.1 01/25/2018
kernel: [  116.155342] Workqueue: events_unbound async_run_entry_fn
kernel: [  116.155358] RIP: 0010:gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
kernel: [  116.155359] RSP: 0018:ffffb7cfc23d3710 EFLAGS: 00010286
kernel: [  116.155359] RAX: 0000000000000000 RBX: ffff9ba8eb20ea00 RCX: ffffffffb94628a8
kernel: [  116.155360] RDX: ffffffffb94628a8 RSI: 0000000000000086 RDI: 0000000000000202
kernel: [  116.155361] RBP: ffffb7cfc23d3748 R08: 0000000000000000 R09: 000000000000001d
kernel: [  116.155361] R10: ffffffffc0cc01e0 R11: 0000000000000620 R12: ffff9ba8e8809800
kernel: [  116.155361] R13: ffff9ba8eb7cb3c0 R14: 0000001a942e54c0 R15: ffff9ba8ae5c5a00
kernel: [  116.155362] FS:  0000000000000000(0000) GS:ffff9ba8fe5c0000(0000) knlGS:0000000000000000
kernel: [  116.155363] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: [  116.155363] CR2: 000055d23a343286 CR3: 00000001e4a0a001 CR4: 00000000003606e0
kernel: [  116.155364] Call Trace:
kernel: [  116.155380]  gp100_vmm_flush+0x17/0x20 [nouveau]
kernel: [  116.155394]  nvkm_vmm_iter.constprop.13+0x2e5/0x880 [nouveau]
kernel: [  116.155408]  ? gp100_vmm_pgt_sparse+0xd0/0xd0 [nouveau]
kernel: [  116.155417]  ? nvkm_object_init+0xc2/0x190 [nouveau]
kernel: [  116.155430]  nvkm_vmm_unmap_locked+0x8a/0xc0 [nouveau]
kernel: [  116.155442]  ? gp100_vmm_pgt_sparse+0xd0/0xd0 [nouveau]
kernel: [  116.155454]  nvkm_uvmm_mthd+0x662/0x8d0 [nouveau]
kernel: [  116.155463]  nvkm_object_mthd+0x1a/0x30 [nouveau]
kernel: [  116.155471]  nvkm_ioctl_mthd+0x5d/0xb0 [nouveau]
kernel: [  116.155479]  nvkm_ioctl+0x11d/0x280 [nouveau]
kernel: [  116.155522]  nvkm_client_ioctl+0x12/0x20 [nouveau]
kernel: [  116.155530]  nvif_object_ioctl+0x47/0x50 [nouveau]
kernel: [  116.155538]  nvif_object_mthd+0x129/0x150 [nouveau]
kernel: [  116.155581]  ? nouveau_mem_host+0x122/0x1b0 [nouveau]
kernel: [  116.155590]  nvif_vmm_unmap+0x3b/0x60 [nouveau]
kernel: [  116.155605]  nouveau_vma_unmap+0x24/0x40 [nouveau]
kernel: [  116.155620]  nouveau_bo_move_ntfy+0x9e/0xe0 [nouveau]
kernel: [  116.155623]  ttm_bo_handle_move_mem+0x251/0x5c0 [ttm]
kernel: [  116.155625]  ? ttm_bo_mem_space+0x39d/0x470 [ttm]
kernel: [  116.155627]  ttm_bo_evict+0x13d/0x340 [ttm]
kernel: [  116.155629]  ttm_mem_evict_first+0x159/0x1b0 [ttm]
kernel: [  116.155631]  ttm_bo_force_list_clean+0x6c/0x120 [ttm]
kernel: [  116.155633]  ttm_bo_evict_mm+0x26/0x50 [ttm]
kernel: [  116.155647]  nouveau_do_suspend+0x81/0x2c0 [nouveau]
kernel: [  116.155661]  nouveau_pmops_suspend+0x39/0x80 [nouveau]
kernel: [  116.155663]  pci_pm_suspend+0x8c/0x150
kernel: [  116.155665]  dpm_run_callback+0x5a/0x150
kernel: [  116.155666]  ? pci_pm_resume+0xb0/0xb0
kernel: [  116.155667]  __device_suspend+0x126/0x450
kernel: [  116.155668]  async_suspend+0x1f/0xa0
kernel: [  116.155669]  async_run_entry_fn+0x3c/0x150
kernel: [  116.155670]  process_one_work+0x1de/0x410
kernel: [  116.155671]  worker_thread+0x32/0x410
kernel: [  116.155673]  kthread+0x121/0x140
kernel: [  116.155674]  ? process_one_work+0x410/0x410
kernel: [  116.155675]  ? kthread_create_worker_on_cpu+0x70/0x70
kernel: [  116.155677]  ret_from_fork+0x35/0x40
kernel: [  116.155677] Code: 41 5e 41 5f 5d c3 49 8b 7c 24 10 48 8b 5f 50 48 85 db 74 47 e8 86 39 a2 f7 48 89 da 48 89 c6 48 c7 c7 28 47 d1 c0 e8 a4 bb 46 f7 <0f> 0b eb bf 49 8b 7c 24 10 48 8b 5f 50 48 85 db 74 24 e8 5d 39 
kernel: [  116.155693] ---[ end trace 3ca36c17fb64f8b9 ]---
kernel: [  118.156703] ------------[ cut here ]------------
kernel: [  118.156703] nouveau 0000:01:00.0: timeout
kernel: [  118.156735] WARNING: CPU: 3 PID: 611 at /build/linux-5s7Xkn/linux-4.15.0/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:207 gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
kernel: [  118.156736] Modules linked in: rfcomm ccm thunderbolt msr cmac bnep arc4 uvcvideo btusb videobuf2_vmalloc videobuf2_memops btrtl btbcm videobuf2_v4l2 btintel videobuf2_core bluetooth videodev media ecdh_generic nouveau ttm nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch snd_hda_codec_realtek snd_hda_codec_generic dell_smbios_wmi dell_wmi wmi_bmof dell_wmi_descriptor dell_laptop mxm_wmi intel_wmi_thunderbolt dell_smbios_smm dell_smbios dcdbas dell_smm_hwmon snd_hda_intel snd_hda_codec intel_rapl ath10k_pci snd_hda_core x86_pkg_temp_thermal intel_powerclamp snd_hwdep ath10k_core snd_pcm coretemp kvm_intel snd_seq_midi ath snd_seq_midi_event kvm mac80211 snd_rawmidi snd_seq irqbypass intel_cstate snd_seq_device intel_rapl_perf snd_timer rtsx_pci_ms cfg80211 memstick idma64 virt_dma snd joydev input_leds
kernel: [  118.156751]  mei_me serio_raw soundcore intel_lpss_pci processor_thermal_device mei shpchp intel_pch_thermal intel_lpss intel_soc_dts_iosf int3403_thermal int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad intel_hid wmi mac_hid tpm_crb sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt usbhid rtsx_pci_sdmmc i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd i2c_algo_bit glue_helper cryptd drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops nvme drm nvme_core ahci rtsx_pci libahci i2c_hid hid video
kernel: [  118.156765] CPU: 3 PID: 611 Comm: kworker/u16:6 Tainted: G        W        4.15.0-20-generic #21-Ubuntu
kernel: [  118.156766] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.7.1 01/25/2018
kernel: [  118.156767] Workqueue: events_unbound async_run_entry_fn
kernel: [  118.156782] RIP: 0010:gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
kernel: [  118.156782] RSP: 0018:ffffb7cfc23d3540 EFLAGS: 00010286
kernel: [  118.156783] RAX: 0000000000000000 RBX: ffff9ba8eb20ea00 RCX: ffffffffb94628a8
kernel: [  118.156784] RDX: ffffffffb94628a8 RSI: 0000000000000086 RDI: 0000000000000202
kernel: [  118.156784] RBP: ffffb7cfc23d3578 R08: 0000000000000000 R09: 000000000000001d
kernel: [  118.156785] R10: ffffffffc0c136d0 R11: 000000000000065a R12: ffff9ba8e8809800
kernel: [  118.156785] R13: ffff9ba8eb7cb3c0 R14: 0000001b0b7aeb40 R15: ffff9ba8e524e400
kernel: [  118.156786] FS:  0000000000000000(0000) GS:ffff9ba8fe4c0000(0000) knlGS:0000000000000000
kernel: [  118.156786] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: [  118.156787] CR2: 0000556f80622ec6 CR3: 00000001e4a0a001 CR4: 00000000003606e0
kernel: [  118.156787] Call Trace:
kernel: [  118.156802]  gp100_vmm_flush+0x17/0x20 [nouveau]
kernel: [  118.156816]  nvkm_vmm_iter.constprop.13+0x2e5/0x880 [nouveau]
kernel: [  118.156818]  ? down_trylock+0x2e/0x40
kernel: [  118.156831]  ? gp100_vmm_pgt_sgl+0x180/0x180 [nouveau]
kernel: [  118.156844]  ? nvkm_vmm_map_choose+0xb0/0xb0 [nouveau]
kernel: [  118.156845]  ? vprintk_emit+0x326/0x3a0
kernel: [  118.156846]  ? vprintk_default+0x29/0x50
kernel: [  118.156859]  nvkm_vmm_map+0x21e/0x400 [nouveau]
kernel: [  118.156871]  ? gp100_vmm_pgt_sgl+0x180/0x180 [nouveau]
kernel: [  118.156872]  ? __switch_to_asm+0x34/0x70
kernel: [  118.156884]  nvkm_vram_map+0x57/0x80 [nouveau]
kernel: [  118.156897]  nvkm_uvmm_mthd+0x792/0x8d0 [nouveau]
kernel: [  118.156906]  nvkm_object_mthd+0x1a/0x30 [nouveau]
kernel: [  118.156914]  nvkm_ioctl_mthd+0x5d/0xb0 [nouveau]
kernel: [  118.156922]  nvkm_ioctl+0x11d/0x280 [nouveau]
kernel: [  118.156938]  nvkm_client_ioctl+0x12/0x20 [nouveau]
kernel: [  118.156946]  nvif_object_ioctl+0x47/0x50 [nouveau]
kernel: [  118.156953]  nvif_object_mthd+0x129/0x150 [nouveau]
kernel: [  118.156969]  ? nv50_grctx_generate+0xbd0/0x16e0 [nouveau]
kernel: [  118.156971]  ? _cond_resched+0x19/0x40
kernel: [  118.156972]  ? __kmalloc+0x18e/0x220
kernel: [  118.156980]  nvif_vmm_map+0x88/0xb0 [nouveau]
kernel: [  118.156996]  nouveau_mem_map+0x88/0xf0 [nouveau]
kernel: [  118.157011]  nouveau_bo_move_m2mf.constprop.24+0x1a3/0x1d0 [nouveau]
kernel: [  118.157025]  nouveau_bo_move+0xab/0x440 [nouveau]
kernel: [  118.157033]  ? nvif_vmm_unmap+0x3b/0x60 [nouveau]
kernel: [  118.157047]  ? nouveau_vma_unmap+0x24/0x40 [nouveau]
kernel: [  118.157050]  ttm_bo_handle_move_mem+0x29f/0x5c0 [ttm]
kernel: [  118.157052]  ? ttm_bo_mem_space+0x39d/0x470 [ttm]
kernel: [  118.157054]  ttm_bo_evict+0x13d/0x340 [ttm]
kernel: [  118.157056]  ttm_mem_evict_first+0x159/0x1b0 [ttm]
kernel: [  118.157058]  ttm_bo_force_list_clean+0x6c/0x120 [ttm]
kernel: [  118.157059]  ttm_bo_evict_mm+0x26/0x50 [ttm]
kernel: [  118.157073]  nouveau_do_suspend+0x81/0x2c0 [nouveau]
kernel: [  118.157087]  nouveau_pmops_suspend+0x39/0x80 [nouveau]
kernel: [  118.157088]  pci_pm_suspend+0x8c/0x150
kernel: [  118.157089]  dpm_run_callback+0x5a/0x150
kernel: [  118.157090]  ? pci_pm_resume+0xb0/0xb0
kernel: [  118.157091]  __device_suspend+0x126/0x450
kernel: [  118.157092]  async_suspend+0x1f/0xa0
kernel: [  118.157093]  async_run_entry_fn+0x3c/0x150
kernel: [  118.157094]  process_one_work+0x1de/0x410
kernel: [  118.157095]  worker_thread+0x32/0x410
kernel: [  118.157096]  kthread+0x121/0x140
kernel: [  118.157097]  ? process_one_work+0x410/0x410
kernel: [  118.157098]  ? kthread_create_worker_on_cpu+0x70/0x70
kernel: [  118.157099]  ret_from_fork+0x35/0x40
kernel: [  118.157100] Code: 41 5e 41 5f 5d c3 49 8b 7c 24 10 48 8b 5f 50 48 85 db 74 47 e8 86 39 a2 f7 48 89 da 48 89 c6 48 c7 c7 28 47 d1 c0 e8 a4 bb 46 f7 <0f> 0b eb bf 49 8b 7c 24 10 48 8b 5f 50 48 85 db 74 24 e8 5d 39 
kernel: [  118.157116] ---[ end trace 3ca36c17fb64f8ba ]---
kernel: [  120.157961] ------------[ cut here ]------------
kernel: [  120.157962] nouveau 0000:01:00.0: timeout
.
. the same kind of crap repeated multiple times
.
kernel: [  140.182517] nouveau 0000:01:00.0: fifo: channel 0 [DRM] kick timeout
kernel: [  140.182520] nouveau 0000:01:00.0: fifo: channel 0: killed
kernel: [  140.182521] nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
kernel: [  140.182525] nouveau 0000:01:00.0: fifo: engine 7: scheduled for recovery
kernel: [  140.182527] nouveau: DRM:00000000:0000c06f: detach ce0 failed, -110
kernel: [  140.182528] nouveau: DRM:0004c1b5:0000c1b5: suspend failed with -110
kernel: [  140.182531] nouveau 0000:01:00.0: DRM: channel 0 killed!
kernel: [  140.182618] pci_pm_suspend(): nouveau_pmops_suspend+0x0/0x80 [nouveau] returns -110
kernel: [  140.182620] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110
kernel: [  140.182622] PM: Device 0000:01:00.0 failed to suspend async: error -110
kernel: [  140.182737] PM: Some devices failed to suspend, or early wake event detected
kernel: [  140.184000] ACPI: button: The lid device is not compliant to SW_LID.
kernel: [  140.558982] ata2: SATA link down (SStatus 4 SControl 300)
kernel: [  140.683376] acpi LNXPOWER:16: Turning OFF
kernel: [  140.683519] acpi LNXPOWER:15: Turning OFF
kernel: [  140.683655] acpi LNXPOWER:14: Turning OFF
kernel: [  140.683790] acpi LNXPOWER:13: Turning OFF
kernel: [  140.683924] acpi LNXPOWER:12: Turning OFF
kernel: [  140.684058] acpi LNXPOWER:11: Turning OFF
kernel: [  140.684190] acpi LNXPOWER:10: Turning OFF
kernel: [  140.684324] acpi LNXPOWER:0f: Turning OFF
kernel: [  140.684459] acpi LNXPOWER:0e: Turning OFF
kernel: [  140.684592] acpi LNXPOWER:0d: Turning OFF
kernel: [  140.684726] acpi LNXPOWER:0c: Turning OFF
kernel: [  140.684860] acpi LNXPOWER:0b: Turning OFF
kernel: [  140.684995] acpi LNXPOWER:0a: Turning OFF
kernel: [  140.685128] acpi LNXPOWER:09: Turning OFF
kernel: [  140.685264] acpi LNXPOWER:08: Turning OFF
kernel: [  140.685398] acpi LNXPOWER:07: Turning OFF
kernel: [  140.685532] acpi LNXPOWER:06: Turning OFF
kernel: [  140.685666] acpi LNXPOWER:05: Turning OFF
kernel: [  140.685800] acpi LNXPOWER:04: Turning OFF
kernel: [  140.685933] acpi LNXPOWER:03: Turning OFF
kernel: [  140.686032] OOM killer enabled.
kernel: [  140.686033] Restarting tasks ... 
kernel: [  140.687401] [drm] RC6 on
kernel: [  140.688963] done.
rtkit-daemon[1207]: The canary thread is apparently starving. Taking action.
rtkit-daemon[1207]: Demoting known real-time threads.
rtkit-daemon[1207]: Successfully demoted thread 1814 of process 1806 (n/a).
rtkit-daemon[1207]: Successfully demoted thread 1813 of process 1806 (n/a).
rtkit-daemon[1207]: Successfully demoted thread 1806 of process 1806 (n/a).
rtkit-daemon[1207]: Demoted 3 threads.
kernel: [  140.720271] PM: suspend exit
kernel: [  140.720299] PM: suspend entry (s2idle)
kernel: [  140.720300] PM: Syncing filesystems ... done.
kernel: [  140.734445] Freezing user space processes ... (elapsed 0.001 seconds) done.
kernel: [  140.736143] OOM killer disabled.
kernel: [  140.736144] Freezing remaining freezable tasks ... (elapsed 0.128 seconds) done.
kernel: [  140.865009] Suspending console(s) (use no_console_suspend to debug)
kernel: [  149.147400] psmouse serio1: Failed to disable mouse on isa0060/serio1
kernel: [  151.838519] ------------[ cut here ]------------
kernel: [  151.838520] nouveau 0000:01:00.0: timeout
kernel: [  151.838550] WARNING: CPU: 5 PID: 2498 at /build/linux-5s7Xkn/linux-4.15.0/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmmgf100.c:207 gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
kernel: [  151.838551] Modules linked in: rfcomm ccm thunderbolt msr cmac bnep arc4 uvcvideo btusb videobuf2_vmalloc videobuf2_memops btrtl btbcm videobuf2_v4l2 btintel videobuf2_core bluetooth videodev media ecdh_generic nouveau ttm nls_iso8859_1 snd_hda_codec_hdmi hid_multitouch snd_hda_codec_realtek snd_hda_codec_generic dell_smbios_wmi dell_wmi wmi_bmof dell_wmi_descriptor dell_laptop mxm_wmi intel_wmi_thunderbolt dell_smbios_smm dell_smbios dcdbas dell_smm_hwmon snd_hda_intel snd_hda_codec intel_rapl ath10k_pci snd_hda_core x86_pkg_temp_thermal intel_powerclamp snd_hwdep ath10k_core snd_pcm coretemp kvm_intel snd_seq_midi ath snd_seq_midi_event kvm mac80211 snd_rawmidi snd_seq irqbypass intel_cstate snd_seq_device intel_rapl_perf snd_timer rtsx_pci_ms cfg80211 memstick idma64 virt_dma snd joydev input_leds
kernel: [  151.838572]  mei_me serio_raw soundcore intel_lpss_pci processor_thermal_device mei shpchp intel_pch_thermal intel_lpss intel_soc_dts_iosf int3403_thermal int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad intel_hid wmi mac_hid tpm_crb sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt usbhid rtsx_pci_sdmmc i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd i2c_algo_bit glue_helper cryptd drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops nvme drm nvme_core ahci rtsx_pci libahci i2c_hid hid video
kernel: [  151.838591] CPU: 5 PID: 2498 Comm: kworker/u16:40 Tainted: G        W        4.15.0-20-generic #21-Ubuntu
kernel: [  151.838591] Hardware name: Dell Inc. XPS 15 9560/05FFDN, BIOS 1.7.1 01/25/2018
kernel: [  151.838594] Workqueue: events_unbound async_run_entry_fn
kernel: [  151.838609] RIP: 0010:gf100_vmm_flush_+0x15c/0x1a0 [nouveau]
kernel: [  151.838610] RSP: 0000:ffffb7cfc39b7830 EFLAGS: 00010282
kernel: [  151.838611] RAX: 0000000000000000 RBX: ffff9ba8eb20ea00 RCX: ffffffffb94628a8
kernel: [  151.838612] RDX: ffffffffb94628a8 RSI: 0000000000000082 RDI: 0000000000000202
kernel: [  151.838612] RBP: ffffb7cfc39b7868 R08: 0000000000000000 R09: 000000000000001d
kernel: [  151.838613] R10: ffffffffc0c136d0 R11: 00000000000009a5 R12: ffff9ba8e8809800
kernel: [  151.838613] R13: ffff9ba8eb7cb3c0 R14: 00000022e315a340 R15: ffff9ba8e524e000
kernel: [  151.838614] FS:  0000000000000000(0000) GS:ffff9ba8fe540000(0000) knlGS:0000000000000000
kernel: [  151.838614] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: [  151.838615] CR2: 00007f374fbba508 CR3: 00000001e4a0a005 CR4: 00000000003606e0
kernel: [  151.838615] Call Trace:
kernel: [  151.838632]  gp100_vmm_flush+0x17/0x20 [nouveau]
kernel: [  151.838645]  nvkm_vmm_iter.constprop.13+0x2e5/0x880 [nouveau]
kernel: [  151.838659]  ? gp100_vmm_pgt_sgl+0x180/0x180 [nouveau]
kernel: [  151.838671]  ? nvkm_vmm_map_choose+0xb0/0xb0 [nouveau]
kernel: [  151.838684]  nvkm_vmm_map+0x21e/0x400 [nouveau]
kernel: [  151.838696]  ? gp100_vmm_pgt_sgl+0x180/0x180 [nouveau]
kernel: [  151.838708]  nvkm_vram_map+0x57/0x80 [nouveau]
kernel: [  151.838721]  nv50_instobj_map+0x19/0x20 [nouveau]
kernel: [  151.838729]  nvkm_gpuobj_heap_map+0x19/0x20 [nouveau]
kernel: [  151.838744]  gm200_secboot_run_blob+0xa4/0x1c0 [nouveau]
kernel: [  151.838758]  gp102_secboot_run_blob+0x1d9/0x2e0 [nouveau]
kernel: [  151.838759]  ? flush_work+0x5b/0x1e0
kernel: [  151.838761]  ? _cond_resched+0x19/0x40
kernel: [  151.838775]  acr_r352_shutdown+0x47/0x150 [nouveau]
kernel: [  151.838787]  acr_r352_fini+0xe/0x10 [nouveau]
kernel: [  151.838799]  gm200_secboot_fini+0x29/0x30 [nouveau]
kernel: [  151.838811]  nvkm_secboot_fini+0x23/0x30 [nouveau]
kernel: [  151.838820]  nvkm_subdev_fini+0x5f/0x150 [nouveau]
kernel: [  151.838834]  nvkm_device_fini+0x87/0x1c0 [nouveau]
kernel: [  151.838848]  nvkm_udevice_fini+0x53/0x70 [nouveau]
kernel: [  151.838857]  nvkm_object_fini+0xbd/0x220 [nouveau]
kernel: [  151.838865]  nvkm_object_fini+0x78/0x220 [nouveau]
kernel: [  151.838882]  nvkm_client_suspend+0x13/0x20 [nouveau]
kernel: [  151.838890]  nvif_client_suspend+0x1d/0x20 [nouveau]
kernel: [  151.838906]  nouveau_do_suspend+0x1a0/0x2c0 [nouveau]
kernel: [  151.838920]  nouveau_pmops_suspend+0x39/0x80 [nouveau]
kernel: [  151.838922]  pci_pm_suspend+0x8c/0x150
kernel: [  151.838924]  dpm_run_callback+0x5a/0x150
kernel: [  151.838925]  ? pci_pm_resume+0xb0/0xb0
kernel: [  151.838926]  __device_suspend+0x126/0x450
kernel: [  151.838927]  async_suspend+0x1f/0xa0
kernel: [  151.838928]  async_run_entry_fn+0x3c/0x150
kernel: [  151.838929]  process_one_work+0x1de/0x410
kernel: [  151.838930]  worker_thread+0x32/0x410
kernel: [  151.838931]  kthread+0x121/0x140
kernel: [  151.838932]  ? process_one_work+0x410/0x410
kernel: [  151.838933]  ? kthread_create_worker_on_cpu+0x70/0x70
kernel: [  151.838935]  ret_from_fork+0x35/0x40
kernel: [  151.838935] Code: 41 5e 41 5f 5d c3 49 8b 7c 24 10 48 8b 5f 50 48 85 db 74 47 e8 86 39 a2 f7 48 89 da 48 89 c6 48 c7 c7 28 47 d1 c0 e8 a4 bb 46 f7 <0f> 0b eb bf 49 8b 7c 24 10 48 8b 5f 50 48 85 db 74 24 e8 5d 39 
kernel: [  151.838951] ---[ end trace 3ca36c17fb64f8c6 ]---
.
. a few more times the same timeout what-not blahblah
.
kernel: [  153.861931] nouveau 0000:01:00.0: secboot: suspend failed, -110
kernel: [  153.861957] nouveau: DRM-master:00000000:00000080: suspend failed with -110
kernel: [  153.862060] pci_pm_suspend(): nouveau_pmops_suspend+0x0/0x80 [nouveau] returns -110
kernel: [  153.862062] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110
kernel: [  153.862064] PM: Device 0000:01:00.0 failed to suspend async: error -110
kernel: [  154.159403] PM: Some devices failed to suspend, or early wake event detected
kernel: [  154.332079] OOM killer enabled.
kernel: [  154.332080] Restarting tasks ... done.
/usr/lib/gdm3/gdm-x-session[1640]: (EE) client bug: timer event7 keyboard: offset negative (-12669ms)
/usr/lib/gdm3/gdm-x-session[1640]: (EE) client bug: timer event12 keyboard: offset negative (-12669ms)
rtkit-daemon[1207]: The canary thread is apparently starving. Taking action.
systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
rtkit-daemon[1207]: Demoting known real-time threads.
systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
rtkit-daemon[1207]: Successfully demoted thread 1814 of process 1806 (n/a).
systemd[1]: Failed to start Suspend.
kernel: [  154.384596] PM: suspend exit
rtkit-daemon[1207]: Successfully demoted thread 1813 of process 1806 (n/a).
systemd[1]: Dependency failed for Suspend.
rtkit-daemon[1207]: Successfully demoted thread 1806 of process 1806 (n/a).
systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
rtkit-daemon[1207]: Demoted 3 threads.
systemd[1]: sleep.target: Unit not needed anymore. Stopping.
systemd[1]: Stopped target Sleep.
systemd[1]: tlp-sleep.service: Unit not needed anymore. Stopping.
systemd[1]: Stopping TLP suspend/resume...

The same /var/log/syslog includes similar complaints with nouveau 0000:01:00.0: timeout and all that at every boot. On the rare occasion that suspending succeeds, the log is missing all this crap about nouveau.

Any pointers for how to fix the issue (great) or disable nouveau (good)? Why don't the /etc/modprobe.d/ blacklist files prevent the loading of the whole driver? How would I manually go about unloading it? (I tried modprobe -r to no great success.)

I am really struggling to figure out how to fix the boot for my Ubuntu server after running some updates recently.

This is the error on boot:

[  0.453037] Key type dns_resolver registered
[  0.455503] RAS: Correctable Errors collector initialized.
[  0.457334] sched_clock: Marking stable (457271600, 0)->(603354001, -146082401)
[  0.460908] registered taskstats version 1
[  0.462694] Loading compiled-in X.509 certificates
[  0.466969] Loaded X.509 cert 'Build time autogenerated kernel key: 4f0e518fe6e203292fbf35df5fac675bae7fc15a'
[  0.468915] Couldn't get size: 0x800000000000000e
[  0.470727] MODSIGN: Couldn't get UEFI db list
[  0.472590] Couldn't get size: 0x800000000000000e
[  0.474500] MODSIGN: Couldn't get UEFI MokListRT
[  0.476391] Couldn't get size: 0x800000000000000e
[  0.478207] MODSIGN: Couldn't get UEFI dbx list
[  0.480143] zswap: loaded using pool lzo/zbud
[  0.485629] Key type big_key registered
[  0.487484] Key type trusted registered
[  0.490212] Key type encrypted registered
[  0.491951] AppArmor: AppArmor sha1 policy hashing enabled
[  0.493835] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
[  0.495729] evm: HMAC attrs: 0x1
[  0.497930] Magic number: 14:354:220
[  0.499761] dmi id: hash matches
[  0.501911] rtc_cmos 00:05: setting system clock to 2018-04-18 08:13:36 UTC (1524039216)
[  0.504184] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[  0.506050] EDD information not available.
[  0.508035] md: Waiting for all devices to be available before autodetect
[  0.509873] md: If you don't use raid, use raid=noautodetect
[  0.512049] md: Autodetecting RAID arrays.
[  0.513902] md: autorun ...
[  0.515740] md: ... autorun DONE.
[  0.517655] VFS: Cannot open root device "mapper/AtlassianServers--vg-root" or unknown-block(0,0): error -6
[  0.519452] Please append a correct "root=" boot option; here are the available partitions:
[  0.521424] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[  0.523268] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.13.0-38-generic #43-Ubuntu
[  0.525136] Hardware name:    BHYVE, BIOS 1.00 03/14/2014
[  0.527005] Call Trace:
[  0.528833]  dump_stack+0x63/0x8b
[  0.530626]  panic+0xe4/0x247
[  0.532392]  mount_block_root+0x1f4/0x2ab
[  0.534177]  ? set_debug_rodata+0x17/0x17
[  0.535900]  mount_root+0x38/0x3a
[  0.537645]  prepare_namespace+0x139/0x18e
[  0.539455]  kernel_init_freeable+0x229/0x256
[  0.541197]  ? rest_init+0xc0/0xc0
[  0.542846]  kernel_init+0xe/0xfc
[  0.545066]  ret_from_fork+0x35/0x40
[  0.547000] Kernel Offset: 0x29800000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[  0.548728] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I can't seem to see any grub loader screen for repair, so I reattached the installation ISO to the VM, and select repair. I've tried a few options, but the result is always the same.

I can get execute a shell on the root of what I think is my installation.

Running fdisk -l /dev/sda gives this output:

root@ubuntu:/# sudo fdisk -l /dev/sda
sudo: unable to resolve host ubuntu: Resource temporarily unavailable
GPT PMBR size mismatch (83886079 != 125829119) will be corrected by w(rite).
Disk /dev/sda: 60 GiB, 64424509440 bytes, 125829120 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes
Disklabel type: gpt
Disk identifier: E584DF2E-7A8D-4D1B-A4C5-3AD0818A2CF6

Device         Start       End  Sectors  Size Type
/dev/sda1       2048   1050623  1048576  512M EFI System
/dev/sda2    1050624  83884031 82833408 39.5G Linux LVM
root@ubuntu:/# █

uname -r shows that I am on 4.13.0-21-generic, but I have newer installations in the boot directory. I don't know if that is because an upgrade has failed, or because the version running is currently from the CD ISO.

I have tried auto removing to clean, but there were a lot of errors. I thought it might be because there was no space left on the boot partition, but I believe there is plenty.

I have also tried update-initramfs on several of the kernel versions, but I get errors such as:

root@ubuntu:/# sudo update-initramfs -c -k 4.13.0-38-generic
sudo: unable to resolve host ubuntu: Resource temporarily unavailable
update-initramfs: Generating /boot/initrd.img-4.13.0-38-generic
WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is deprecated and will stop working in the future. Use /etc/cryptsetup-initramfs/conf-hook instead.
cp: cannot stat '/usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif.ttf': No such file or directory
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.13.0-38-generic with 1.
root@ubuntu:/# █

I have tried the advice for similar looking issue here including the mount options Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) but still get the same error.

The disks/partitions are not encrypted. This is all being run from a Bhyve VM from FreeNAS.

The results of lsblk are:

root@ubuntu:/# lsblk
NAME                            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                               8:0    0    60G  0 disk
├─sda1                            8:1    0   512M  0 part /boot/efi
└─sda2                            8:2    0  39.5G  0 part
├─AtlassianServers--vg-root   253:0    0  35.5G  0 lvm  /
└─AtlassianServers--vg-swap_1 253:1    0     4G  0 lvm

sr0                              11:0    1   754M  0 rom
root@ubuntu:/# █

When I am asked when booting from the original CD, what I want to connect root to, I am selecting the AtlassianServers--vg-root option. It then displays a message saying there is also a boot/efi partition which will also be mounted.

I'm a bit stuck what to try next. Is there a way to repair it that's fairly straightforward, or do I just install again over the top, and keep the underlying files mostly intact?

Followup to an earlier question on having my encrypted disk auto-decrypt on startup. It seems I completely shut myself out of my system, I'm getting a kernel panic on startup.

Here's what I did:

First I added a trivial password abc123 to unlock my partition using

cryptsetup luksAddKey /dev/sda3

Then I followed exactly these steps ("How I did it on Ubuntu 16.04.3"). Note that I inserted sudo where appropriate.

That is:

1. appended ,keyscript=/root/lukspw at the end of the line in etc/crypttab that contains sda3_crypt (.....) none luks (sda3 is the disk for which I was prompted during startup to enter the decryption password)

2. Created the file /root/lukspw with the content:

    #!/bin/sh
    printf "abc123"
   

and made it executable: sudo chmod +x /root/lukspw

3. And finally:

    sudo update-initramfs -u -k`uname -r`
   

I did not get any errors during any step of the process.

Now upon reboot, either in normal or 'recovery' mode (through the Advanced options at startup) I get this (Kernel panic - not syncing at the end):

[    0.698341] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    0.698366] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.698392] usb usb2: Product: xHCI Host Controller
[    0.698411] usb usb2: Manufacturer: Linux 4.4.0-87-generic xhci-hcd
[    0.698434] usb usb2: SerialNumber: 0000:00:14.0
[    0.698585] hub 2-0:1.0: USB hub found
[    0.698610] hub 2-0:1.0: 6 ports detected
[    0.702853] usb: port power management may be unreliable
[    0.704102] i8042: PNP: No PS/2 controller found. Probing ports directly.
[    1.788390] i8042: No controller found
[    1.789442] tsc: Refined TSC clocksource calibration: 2207.999 MHz
[    1.790491] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x1fd3b75da7f, max_idle_ns: 440795296082 ns
[    1.791791] mousedev: PS/2 mouse device common for all mice
[    1.793208] rtc_cmos 00:03: RTC can wake from S4
[    1.794688] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[    1.795900] rtc_cmos 00:03: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[    1.796991] i2c /dev entries driver
[    1.798122] device-mapper: uevent: version 1.0.3
[    1.799350] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: dm-devel@redhat.com
[    1.800468] Intel P-state driver initializing.
[    1.802320] intel_pstate: HWP enabled
[    1.803077] ledtrig-cpu: registered to indicate activity on CPUs
[    1.803778] EFI Variables Facility v0.08 2004-May-17
[    1.826642] NET: Registered protocol family 10
[    1.827584] NET: Registered protocol family 17
[    1.828285] Key type dns_resolver registered
[    1.829163] microcode: CPU0 sig=0x806e9, pf=0x40, revision=0x5e
[    1.829834] microcode: CPU1 sig=0x806e9, pf=0x40, revision=0x5e
[    1.830552] microcode: CPU2 sig=0x806e9, pf=0x40, revision=0x5e
[    1.831261] microcode: CPU3 sig=0x806e9, pf=0x40, revision=0x5e
[    1.832180] microcode: Microcode Update Driver: v2.01 tigran@aivazian.fsnet.co.uk, Peter Oruba
[    1.833201] registered taskstats version 1
[    1.833876] Loading compiled-in X.509 certificates
[    1.835037] Loaded X.509 cert 'Build time autogenerated kernel key: '
[    1.835700] zswap: loaded using pool lzo/zbud
[    1.836911] Key type trusted registered
[    1.838613] Key type encrypted registered
[    1.839329] AppArmor: AppArmor sha1 policy hashing enabled
[    1.839974] ima: No TPM chip found, activating TPM-bypass!
[    1.840613] evm: HMAC attrs: 0x1
[    1.842023] Magic number: 9:976:896
[    1.843038] rtc_cmos 00:03: setting system clock to 2017-11-24 17:52:28 UTC (1511545948)
[    1.843816] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[    1.844479] EDD information not available.
[    1.845998] Freeing unused kernel memory: 1488K (ffffffff81f45000 - ffffffff820b9000)
[    1.846647] Write protecting the kernel read-only data: 14336k
[    1.847417] usb 1-1: new full-speed USB device number 2 using xhci_hcd
[    1.848580] Freeing unused kernel memory: 1756K (ffff880002849000 - ffff880002a00000)
[    1.849532] Freeing unused kernel memory: 112K (ffff880002de4000 - ffff880002e00000)
[    1.850280] Failed to execute /init (error -2)
[    1.851020] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentat
[    1.851700] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.0-87-generic #110-Ubuntu
[    1.852404] Hardware name: Intel Corporation NUC7i5BNH/NUC7i5BNB, BIOS BNKBL357.86A.0047.2017.0518.1824 05/18/2017
[    1.853118] 0000000000000086 ea9e96badcd2f370 ffff88046c74beb0 ffffffff813f9903
[    1.853819] ffffffff81ca58f0 ffff88046c74bf48 ffff88046c74bf38 ffffffff8118d807
[    1.854538] ea9e96badcd2f370 ffff88046c74bf48 ffff88046c74bee0 ea9e96badcd2f370
[    1.855269] Call Trace:
[    1.855964] [<ffffffff813f9903>] dump_stack+0x63/0x90
[    1.856674] [<ffffffff8118d807>] panic+0xd3/0x215
[    1.857362] [<ffffffff8121ef04>] ? putname+0x54/0x60
[    1.858062] [<ffffffff81835710>] ? rest_init+0x80/0x80
[    1.858753] [<ffffffff818357e9>] kernel_init+0xd9/0xe0
[    1.859446] [<ffffffff8184224f>] ret_from_fork+0x3f/0x70
[    1.860101] [<ffffffff81835710>] ? rest_init+0x80/0x80
[    1.860848] Kernel Offset: disabled
[    1.861540] ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Doc
_

I can't do anything, no interaction, no response on keyboard activity.

I'm looking for a graphics program that will permit me to make a watermark on photographs. Can anyone advise me on this? Thank you.

I have one speaker next to my computer which I use mostly as a headphone amplifier. On occasion I need to use it as a loudspeaker. Is it possible to quickly change the audio output from stereo to mono, either system-wide or as a plugin for a media player?