Public bug reported:
I was running e4defrag -v /dev/sda1. Also had Firefox open with a few
tabs, but hadn't used it within the past 10 mins. System locked solid, I
gave it a couple minutes to see if it would clear itself, it did not.
Tried REISUB, did nothing. Had to hold power to turn off and
log info as it happened. Attaching those captures.
clickwir@mach:~$ uname -a
Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
clickwir@mach:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubu
res.
clickwir@mach:~$ uname -a
Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
clickwir@mach:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Coden
Installed 4.15 rc8 and same issue.
dmesg
[ 1265.953008] sched: RT throttling activated
[ 1265.953018] clocksource: timekeeping watchdog on CPU4: Marking clocksource
'tsc' as unstable because the skew is too large:
[ 1265.953021] clocksource: 'hpet' wd_now:
nds. Then it stopped and nothing responded.
It did this a few times over the course of an hour. Had to power off
the PC to get a reboot. Last time it did this I ssh'd from another PC
to get dmesg and syslog info as it happened. Attaching those captures.
clickwir@mach:~$ uname -a
Linux m
Linux laptop 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Just upgraded from 17.10 to 18.04, sorry, I somehow didn't realize my
laptop was still back on 17.10. Anyway, 17.10 suspend/resume was
perfect. But after about 10 resumes on 18.04, the wired
Just did a fresh install of 20.04 as a Proxmox VM and see this "invalid
argument" in the start up messages and syslog. Trying to start it
manually also fails. Tried recreating it, also failed.
root@changeme:/# fallocate -l 2G /swap.img
root@changeme:/# chmod 600 /swap.img
root@changeme:/# ls
Fixed my problem.
While looking through /var/log/syslog, I noticed this line around the
same time swap mount failed.
BTRFS warning (device sda3): swapfile must not be copy-on-write
Then a few lines later...
systemd[1]: swap.img.swap: Failed with result 'exit-code'.
systemd[1]: Failed to
8 matches
Mail list logo