I'm on an ARM board running Linux. The hardware is a vehicle domain control board which has 6 core ARM Cortex-A78AE and some machine learning cores. I don't want to reboot it because It might be a hardware or driver bug? which might be the reason that causes my performance loss issue.

root@hobot:~# uname -a
Linux hobot 6.1.94-rt33 #1 SMP PREEMPT_RT Fri Nov  8 15:11:35 CST 2024 aarch64 GNU/Linux

I don't know what happend with my OS today, I just suddenly found out that shell commands takes too long to finish. but everything was fine a little while ago. like: As you can see, ls takes about over 5 seconds and it takes 100% CPU in core 4th. I tried strace with ls. It get stuck in nothing. What should I monitor to find out what happened?

Using RHEL-8.10 x86-64, I have the network cable unplugged (purposely) and in /etc/fstab I still have 192.168.1.2:/data /data nfs defaults 0 0 during boot, with the console being verbose per GRUB_CMDLINE_LINUX not having rhgb quiet and having verbose instead I get 1. The verbose line item (from systemd?) showing the attempting mount of /data with a 1m30s time window 2. At some time in the middle of that, the end time changes to 1m38s but then the delay completes and the boot process continues successfully. My NFS /data mount does not happen, which recognize and expect - I did not want to comment out that entry in fstab. - Why the change on the duration? What causes that, for any other delays during boot which I have noticed? It's not just for NFS. - Can I modify this timeout duration? To either not happen, or to be something less infuriating when watching it and after 10s I am out of patience? - Is there a way to keep the default time duration, but a console keyboard entry that will kill that wait and proceed with the boot process? **Specifically** this, as this delay example of NFS mount is not the only thing I run into; when I get delayed like this during boot (when you recognize it's not a problem) is there a way to kill this ~1m30s delay? - The worst is for those items, which I have run into, where the 1m30s duration keeps changing so the delay becomes infinite, and you have to power button reboot and then boot into single user mode to correct the problem.

Stuck for quite a while with the problem that launching GNOME apps causes a delay of exactly 25 seconds. I hope someone can read this syslog excerpt better than I can; what a "background monitor", "secret proxy", and "skeleton to export" are is a total mystery to me. Syslog transcript (rtkit-daemon entries excised):

2023-12-01T16:55:43.335760-08:00 dowland dbus-daemon: [session uid=1000 pid=209259] Activating service name='org.freedesktop.portal.Desktop' requested by ':1.1041' (uid=1000 pid=1410414 comm="evince ibook.pdf")
2023-12-01T16:55:43.344016-08:00 dowland dbus-daemon: [session uid=1000 pid=209259] Activating service name='org.freedesktop.portal.Documents' requested by ':1.1042' (uid=1000 pid=1410419 comm="/usr/libexec/xdg-desktop-portal")
2023-12-01T16:55:43.344099-08:00 dowland dbus-daemon: [session uid=1000 pid=209259] Successfully activated service 'org.freedesktop.portal.Documents'
2023-12-01T16:55:43.345334-08:00 dowland org.freedesktop.portal.Documents: fusermount3: failed to access mountpoint /run/user/1000/doc: Permission denied
2023-12-01T16:55:43.345466-08:00 dowland org.freedesktop.portal.Documents: error: fuse init failed: Can't mount path /run/user/1000/doc
2023-12-01T16:55:43.360001-08:00 dowland xdg-desktop-por: value "((GDBusConnectionFlags) G_DBUS_CONNECTION_FLAGS_AUTHENTICATION_CLIENT | G_DBUS_CONNECTION_FLAGS_MESSAGE_BUS_CONNECTION | 64)" of type 'GDBusConnectionFlags' is invalid or out of range for property 'flags' of type 'GDBusConnectionFlags'
2023-12-01T16:55:43.360077-08:00 dowland xdg-desktop-por: Failed to create background monitor: The connection is closed
2023-12-01T16:55:43.360138-08:00 dowland xdg-desktop-por: No skeleton to export
2023-12-01T16:55:43.361944-08:00 dowland dbus-daemon: [session uid=1000 pid=209259] Activating service name='org.freedesktop.secrets' requested by ':1.1042' (uid=1000 pid=1410419 comm="/usr/libexec/xdg-desktop-portal")
2023-12-01T16:55:43.364847-08:00 dowland gnome-keyring-d: The Secret Service was already initialized
2023-12-01T16:55:43.366081-08:00 dowland org.freedesktop.secrets: discover_other_daemon: 1
2023-12-01T16:56:08.387485-08:00 dowland xdg-desktop-por: Failed to create secret proxy: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached
2023-12-01T16:56:08.387739-08:00 dowland xdg-desktop-por: No skeleton to export
2023-12-01T16:56:08.389574-08:00 dowland dbus-daemon: [session uid=1000 pid=209259] Successfully activated service 'org.freedesktop.portal.Desktop'
2023-12-01T16:56:08.427842-08:00 dowland dbus-daemon: [session uid=1000 pid=209259] Activating service name='org.gnome.evince.Daemon' requested by ':1.1041' (uid=1000 pid=1410414 comm="evince ibook.pdf")
2023-12-01T16:56:08.430806-08:00 dowland dbus-daemon: [session uid=1000 pid=209259] Successfully activated service 'org.gnome.evince.Daemon'

Software versions (Debian unstable, just updated):

dbus-daemon                               1.14.10-1~deb12u1
gnome-keyring                             42.1-1+b2
xdg-desktop-portal                        1.16.0-2
xdg-desktop-portal-gnome                  43.1-2
xdg-desktop-portal-gtk                    1.14.1-1
xdg-utils                                 1.1.3-4.1

I have no idea what /run/user/1000/doc is supposed to be, but it's already mounted:

portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

I'm using meld to compare some files, on a machine running SLES 15 SP 1, and with the X server running on a Windows desktop; it's MobaXTerm 's embedded X server, which I believe is Cygwin'ish. For some reason, meld takes ~30 seconds create its window on the X server - even if no files are being compared and it's just the empty window. The same is true for gedit, for example. However, for apps like xclock, xterm or even say kile - the delay is very small - less than half a second. After coming up, the apps are pretty responsive, and this is all on a LAN, so it's not as though it's a communications problem (I'm pretty sure anyway). What could cause such delays, and what can I do to avoid or at least mitigate them? Naturally, I'll provide any additional information which might be useful to figure this out.

What could be the cause if every second ping is delayed for a second when pinging through the host-to-network VPN while at the same time pinging the security gateway outside the VPN takes 13 ms on average and no more than 20 ms maximum, even when using largest possible ping -s 1464 ? (Larger pings result in icmp_seq=1 Frag needed and DF set (mtu = 1492).)

bytes from 192.168.178.1: icmp_seq=2300 ttl=64 time=1031 ms
64 bytes from 192.168.178.1: icmp_seq=2301 ttl=64 time=17.6 ms
64 bytes from 192.168.178.1: icmp_seq=2302 ttl=64 time=1034 ms
64 bytes from 192.168.178.1: icmp_seq=2303 ttl=64 time=19.8 ms
64 bytes from 192.168.178.1: icmp_seq=2304 ttl=64 time=1032 ms
64 bytes from 192.168.178.1: icmp_seq=2305 ttl=64 time=18.6 ms
64 bytes from 192.168.178.1: icmp_seq=2306 ttl=64 time=803 ms
64 bytes from 192.168.178.1: icmp_seq=2307 ttl=64 time=19.6 ms
64 bytes from 192.168.178.1: icmp_seq=2308 ttl=64 time=455 ms
64 bytes from 192.168.178.1: icmp_seq=2309 ttl=64 time=19.9 ms
64 bytes from 192.168.178.1: icmp_seq=2310 ttl=64 time=18.4 ms
64 bytes from 192.168.178.1: icmp_seq=2311 ttl=64 time=1052 ms
64 bytes from 192.168.178.1: icmp_seq=2312 ttl=64 time=1019 ms
64 bytes from 192.168.178.1: icmp_seq=2313 ttl=64 time=18.2 ms
64 bytes from 192.168.178.1: icmp_seq=2314 ttl=64 time=1023 ms

That is getting worse with even slightly larger packets:

ping -s 234 192.168.178.1
242 bytes from 192.168.178.1: icmp_seq=8 ttl=64 time=23.7 ms
242 bytes from 192.168.178.1: icmp_seq=9 ttl=64 time=18.6 ms
242 bytes from 192.168.178.1: icmp_seq=10 ttl=64 time=2060 ms
242 bytes from 192.168.178.1: icmp_seq=11 ttl=64 time=1043 ms
242 bytes from 192.168.178.1: icmp_seq=12 ttl=64 time=1024 ms
242 bytes from 192.168.178.1: icmp_seq=13 ttl=64 time=41.2 ms
242 bytes from 192.168.178.1: icmp_seq=14 ttl=64 time=2047 ms
242 bytes from 192.168.178.1: icmp_seq=15 ttl=64 time=1042 ms
242 bytes from 192.168.178.1: icmp_seq=16 ttl=64 time=2034 ms
242 bytes from 192.168.178.1: icmp_seq=17 ttl=64 time=1032 ms
242 bytes from 192.168.178.1: icmp_seq=18 ttl=64 time=18.7 ms

Is it possible that there are packet losses on the network in the protocols under IPsec while ICMP ping goes through undisturbed ? If yes, how to debug these ? Edit: Could this have been introduced by the recent fix by AVM for a yet undisclosed vulnerability in all kinds of Fritz-Box ? Client is vpnc 0.5.3r550-3.1 on LUbuntu 20.04, Security Gateway is Fritz-Box 7530 with up to date software. Rebooting these did not help. The same client software and hardware did work with the same gateway hardware on ADSL without these delays. Switching to the current fibre-optic network seems to have caused the problems, but there might also have been a software update on the Fritz-Box causing the problems.

With this scripts i check if a host is response on a given port with the **bash's built-in /dev/tcp**. I can use ip address or domains(hostnames). **Script 1**

#!/bin/bash

HOST_NAME="127.1"
HOST_PORT="80"

if ( (exec 3/dev/tcp/${HOST_NAME}/${HOST_PORT}) 2> /dev/null); then
	echo -e "PORT: ${HOST_PORT} | ON"
	else
	echo -e "PORT: ${HOST_PORT} | OFF"
fi

exit;

**Script 2**

#!/bin/bash

HOST_NAME="127.1"

for HOST_PORT in {1..1000}
do

if ( (exec 3/dev/tcp/${HOST_NAME}/${HOST_PORT}) 2> /dev/null); then
	echo -e "PORT: ${HOST_PORT} | ON"
	else
	echo -e "PORT: ${HOST_PORT} | OFF"
fi
done

exit;

Script 3

#!/bin/bash

HOST_NAME="127.1"
declare -A PORT_ON

for HOST_PORT in {1..65535}
do
	if ( (exec 3/dev/tcp/${HOST_NAME}/${HOST_PORT}) 2> /dev/null); then
		PORT_ON[${HOST_PORT}]="ON"
	fi
done

for i in ${!PORT_ON[*]}
do
    echo -e "$i : ${PORT_ON[$i]}"
done

exit;

On some of our local and online domains **Script 3** hangs on some ports and takes longer to jump to the next port scan, for example on ssh(because of firewalls or other services). How can i manage this that it continues straight away and is it possible to speed the script up, it takes a long time, when i scan all 65535 ports an. **My GNU/Linux Distro:**

Distributor ID: Debian

Description:    Debian GNU/Linux 10 (buster)

Release:        10

Codename:       buster

4.19.0-16-amd64

**My /etc/apt/sources.list**

deb http://security.debian.org/debian-security  buster/updates main contrib

deb-src http://security.debian.org/debian-security  buster/updates main contrib

deb http://deb.debian.org/debian/  buster-updates main contrib

deb-src http://deb.debian.org/debian/  buster-updates main contrib

I can only install from this repos. *bash script, check port response with bash's built-in /dev/tcp, time delay | hangs | speed up* **how can i speed up and terminate the time delay?**

The home directory of user bob is mounted by a superuser from elsewhere. bob himself is a sudoer, he is logged in and is happily using his mounted home directory. He finishes his work and wants to run a script which will log him out *and* unmount his home directory. He tries:

cd / # switch to a directory other than /home/bob to avoid keeping it busy
bash -c 'sleep 5 && sudo umount /home/bob /dev/null & disown
gnome-session-quit --no-prompt

He gets logged out but then, when alice logs in (also a sudoer), she sees bob's home directory still mounted after a while. Apparently, the umount command fails for some reason. How can bob reliably unmount it upon logging out?

When using a TTY login shell by entering e.g. Ctrl+Alt+F1 on Debian Jessie. There is an inhuman fast delay, specifically, these values are set (250ms): root@VB-NB-Debian:~# kbdrate Typematic Rate set to 10.9 cps (delay = 250 ms) vlastimil@VB-NB-Debian:~$ sudo kbdrate Typematic Rate set to 10.9 cps (delay = 250 ms) I don't understand, since I have a "normal" 810ms set in my KDE system. Still, in Xterm the kbdrate says I have a delay of 250ms set. Anyway, this is not the point. I need to permanently change the delay for all TTYs. Can you help me with that? I found this: https://unix.stackexchange.com/questions/58651/adjusting-keyboard-sensitivity-in-a-command-line-terminal but it doesn't guide me. What exactly shall I do? So, the question is, how to set the delay (not interested in the rate) once and for all?

If I'm executing a long process, is there any way I can execute some time-based commands? For example, I'm running a really long process which runs for roughly 10 minutes. After 5 minutes, I would like to run a separate command. For illustration, the separate command could be: echo 5 minutes complete (Note: I don't want progress toward completion of the command, but simply commands executed after specified intervals.) Is it possible?

I have a debian 7 server hosted by Google Cloud running a game server and a rails server. The rails server run on port 80 and the game server on port 8000. I want to apply a network rule that allow the game server packets to have a higher priority in order to minimize latency. For now, I found that iptables could help me with this : iptables -A PREROUTING -t mangle -p tcp --dport 8000:8010 -j TOS --set-tos Minimize-Delay But when I check if my rule has been added : iptables -L -vt nat Chain PREROUTING (policy ACCEPT 877 packets, 100K bytes) pkts bytes target prot opt in out source destination Chain INPUT (policy ACCEPT 877 packets, 100K bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 329 packets, 20395 bytes) pkts bytes target prot opt in out source destination Chain POSTROUTING (policy ACCEPT 329 packets, 20395 bytes) pkts bytes target prot opt in out source destination I'm not seeing my rule. What I'm doing wrong ? And also, is this the right way to do what I want ?

I'm getting huge a delay in ps output -- when it outputs the first line (systemd-networkd), there is a huge delay about **20** to **25** seconds, then the rest are displayed instantly.

$ ps -eaf
. . .
systemd+ 31865     1  0 Jul22 ?        00:00:10 /lib/systemd/systemd-networkd
62583    31891     1  0 Jul22 ?        00:00:12 /lib/systemd/systemd-timesyncd
root     31922     1  0 Jul22 ?        00:02:09 /lib/systemd/systemd-journald
. . .

Any idea why (and the fix)?

$ time ps -o uname -p 31891
USER
62583

real    0m25.025s
user    0m0.006s
sys     0m0.006s

$ time getent passwd 62583 | wc
      0       0       0

real    0m25.030s
user    0m0.005s
sys     0m0.001s

$ grep 62583 /etc/passwd | wc 
      0       0       0

$ grep passwd /etc/nsswitch.conf
passwd:         compat systemd

$ grep compat /etc/nsswitch.conf
passwd:         compat systemd
group:          compat systemd
shadow:         compat

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:        18.04
Codename:       bionic

$ uname -rm
5.4.0-1047-azure x86_64

I understand that there is a multitude of options to shutdown or reboot a linux system. Normally I would just use shutdown with the appropriate option. However, I find myself having no control of the environment and needing to reboot the system using only systemctl but having to do so with a delay. Now systemctl supports poweroff und reboot which however in turn do not support delays afaik and as far as man is concerned. Is there a way to delay a systemctl reboot for x seconds without resorting to other commands like sleep 3 && systemctl reboot but just using systemctl? I could not find anything regarding a systemctl shutdown command, but understand that e.g. reboot invokes the shutdown (systemcall|command). man for systemctl, reboot, systemd-halt.service didn't list any delay parameter/configuration options. [original question was posed on reddit](https://www.reddit.com/r/linuxquestions/comments/okmihi/systemctl_poweroff_with_delay/) , but I it fit here better.

I wanted to simulate execution time of certain scripts for which I found sleep NUMBER does exactly what I want.
In my scenario I needed something like sleep 5 | command | sleep 5 ... But it behaved strangely so I've tested sleeps alone, and I was surprised that
This takes 10 seconds sleep 10 | sleep 5
and **this also takes 10 seconds** sleep 5 | sleep 10 I even tried sleep 1 | sleep in case sleep was listening to standard input stdin Only thing I got working is when I was looking on how to force stdout as argument (with xargs) sleep 3; echo 3 | xargs sleep; echo "finished" But since I need to time the whole execution I had to do time -p (sleep 3; echo 3) | (xargs sleep; echo "finished") Hoe to pipe sleeps? If there is a better way, I'd still ike to know why sleep 1 | sleep 1 isn't working in the first place?

friends! Happy New 2021 Year here! I use Devuan with SysVinit, because I want to speedup my system and get unnecessary non-free stuff away as possible, but also I need Debian-like distribution cause of software and ease. I want to discover why Atheros stops and also is it possible to initialize it after slim runs? [ 5.665127] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4 [ 5.665241] ath9k_htc 1-1:1.0: FW RMW support: On [ 5.665845] ath: EEPROM regdomain: 0x809c [ 5.665846] ath: EEPROM indicates we should expect a country code [ 5.665846] ath: doing EEPROM country->regdmn map search [ 5.665846] ath: country maps to regdmn code: 0x52 [ 5.665847] ath: Country alpha2 being used: CN [ 5.665847] ath: Regpair used: 0x52 [ 5.670273] ieee80211 phy1: Atheros AR9271 Rev:1 ....here boot process stops for 3-4 seconds... [ 10.390281] usb 1-14: New USB device found, idVendor=0cf3, idProduct=e005, bcdDevice= 0.02 [ 10.390707] usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 10.400582] ath9k_htc 1-1:1.0 wlx6cfdb9834ef2: renamed from wlan1 [ 10.577632] Adding 1000444k swap on /dev/sdb3. Priority:-2 extents:1 across:1000444k SSFS [ 10.604895] EXT4-fs (sdb2): re-mounted. Opts: (null) [ 10.810039] device-mapper: uevent: version 1.0.3 [ 10.810588] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com [ 10.866508] lp: driver loaded but no devices found [ 10.882348] ppdev: user-space parallel port driver [ 11.157659] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null) I have these services on my runlevel 2: # ls /etc/rc2.d/ K01speech-dispatcher S02acpi-fakekey S02stop-bootlogd S04acpid S04dbus S04mdadm S04rmnologin S05slim S07rc.local README S02lvm2-lvmpolld S02sudo S04anacron S04exim4 S04ntp S04rsync S05wicd S01console-setup.sh S02rsyslog S02uuidd S04cron S04hddtemp S04pcscd S05elogind S06bootlogs PS: Why I moved from Debian with systemd to Devuan with sysvinit. I had ugly delay on shutdown when used Debian with systemd - waiting some process kill. I know that it is possible to setup max delay for killing process. But another problem was ModemManager and wicd not connected after boot to wifi after some days of using and was some delay when opened wicd wifi connections window. So, I want better control and also i prefer opensource projects and computing freedom.

I've noticed after I come back to my newly installed Fedora 20 system, there's a delay in typing. For example, if I have a terminal window open, and I leave it alone for a few minutes and return, when I type, it takes multiple seconds for my typing to manifest. It's fine after that, provided I don't wait too long between typing. This happens for any typing, not just the terminal. It could be the password on the lock screen, terminal sessions, web forms in FireFox, etc. My system has 32G of RAM, and it occurs with nothing active, except for a terminal or webpage, nothing significantly taxing. The keyboard is the build in laptop physical keyboard. The laptop is a Dell Inspiron 17R (17RM-16452sLV). Is there a known reason this occurs? How can I diagnose and fix the cause of the issue?

My scenario is as follows: After updating files on my Git repository, I have a Git hook that calls an API from my web server. This API performs a Git pull and then I have a Git hook post-merge that restart the web server (Gunicorn). The restart of the web server should occurs a few seconds after the pull is completed otherwise the web server is shutting down before the API call is completed and that returns an error to the Git hook. Currently I worked out the following solution but I am not happy with it. The file .git/hooks/post-merge #!/bin/sh /var/www/tempcollect/.git/hooks/restart > /var/www/tempcollect/.git/hooks/restart.log & The file .git/hooks/restart sleep 10s /usr/bin/sudo systemctl restart tempcollect I would prefer to have the command to restart the web server in the post-merge file. The execution of the file post-merge is started by Git at the end of the pull, thus I have no control on the way it is started.

*Note:* I had posted this on Ask Ubuntu, but was told that forum is for questions related to real Ubuntu, only. I was advised to post here, so I'm moving the question over here. I have installed Zorin-OS Education Lite 32bit on my aged Thinkpad T43p. This distro is based on Ubuntu, with xfce and lightdm for the graphical interface. Initially the separate partitions for /, swap, /var, /var/log, and /home were on the HDD. Then I decided to add a small (32G) SSD besides the HDD (the T43p supports two storage devices) to hopefully speed up the system. I move the root partition to the SSD and left all other on the HDD. Only things changed on the HDD: old root partiton deleted, and swap partition deleted/created (was too small). Basically, a great success. It is fun how much faster the system is working now. At one point, however, a naughty problem arose (I can't tell exactly when this started): - When I shut down the system, and later power it on again, the boot process is excessively slow. After about 4-5 minutes, the system is up and works as expected. No grub menu is shown in this process, which is expected bevahiour. - When I force a power off (holding down the power button) while the excessively long startup, an then restart the system, it quickly comes up and presents the grub menu. Selecting the normal "Zorin OS" from the boot menu brings the system up and running in less than a minute. (The grub mennu is show, I suspect, because the system was not cleanly shutdown, right?) I have compared the boot log (dmesg) from both boots, and have found a few differences. Interpreting those is beyond my knowledge of the boot process; hopefully one or the other difference will ring a bell with some knowledgable soul out there. To find the differences, I have stipped the timestamp at the start of the message, sorted them lexically, and fed them into a comarison tool. The result is as follows (lines marked with "delayed ->" are from delayed boot, those marked with "normal ->" are from speedy boot after forced power off)

----------------------------------------------------------------------------------
delayed ->        .data : 0xdd9b5c60 - 0xdde8eb40   (4963 kB)
                  .init : 0xddea6000 - 0xddfc8000   (1160 kB)
                  .text : 0xdd000000 - 0xdd9b5c60   (9943 kB)
normal  ->        .data : 0xd49b5c60 - 0xd4e8eb40   (4963 kB)
                  .init : 0xd4ea6000 - 0xd4fc8000   (1160 kB)
                  .text : 0xd4000000 - 0xd49b5c60   (9943 kB)
---------------------------------------------------------------------
delayed ->  Console: colour dummy device 80x25
normal  ->  Console: colour VGA+ 80x25
            Console: switching to colour dummy device 80x25
            Console: switching to colour frame buffer device 175x65
---------------------------------------------------------------------
delayed ->  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=d50a32c6-34b0-11eb-a9eb-7111d485222b ro initrd=/casper/initrd.lz4 quiet splash vt.handoff=1
normal  ->  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=d50a32c6-34b0-11eb-a9eb-7111d485222b ro initrd=/casper/initrd.lz4 quiet splash
---------------------------------------------------------------------
delayed ->  Memory: 1995804K/2095608K available (9943K kernel code, 938K rwdata, 3992K rodata, 1160K init, 836K bss, 99804K reserved, 0K cma-reserved, 1188744K highmem)
normal  ->  Memory: 1996092K/2095608K available (9943K kernel code, 938K rwdata, 3992K rodata, 1160K init, 836K bss, 99516K reserved, 0K cma-reserved, 1188744K highmem)
---------------------------------------------------------------------
delayed ->  [TTM] Zone  kernel: Available graphics memory: 434278 KiB
            [TTM] Zone highmem: Available graphics memory: 1028650 KiB
normal  ->  [TTM] Zone  kernel: Available graphics memory: 434422 KiB
            [TTM] Zone highmem: Available graphics memory: 1028794 KiB
---------------------------------------------------------------------
delayed ->  checking generic (c0000000 5a0000) vs hw (c0000000 8000000)
---------------------------------------------------------------------
delayed ->  clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x1eae0a205f2, max_idle_ns: 440795277977 ns
normal  ->  clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x1ead52fe7de, max_idle_ns: 440795275707 ns
---------------------------------------------------------------------
delayed ->  fb0: VESA VGA frame buffer device
            fb0: switching to radeondrmfb from VESA VGA
            fbcon: Deferring console take-over
            fbcon: Deferring console take-over
---------------------------------------------------------------------
delayed ->  initial memory mapped: [mem 0x00000000-0x1e5fffff]
normal  ->  initial memory mapped: [mem 0x00000000-0x155fffff]
---------------------------------------------------------------------
delayed ->  rtc_cmos 00:02: setting system clock to 2020-12-04T13:04:12 UTC (1607087052)
normal  ->  rtc_cmos 00:02: setting system clock to 2020-12-04T13:22:52 UTC (1607088172)
---------------------------------------------------------------------
delayed ->  smpboot: Total of 1 processors activated (4256.82 BogoMIPS)
normal  ->  smpboot: Total of 1 processors activated (4256.44 BogoMIPS)
---------------------------------------------------------------------
delayed ->  systemd-journald: Received request to flush runtime journal from PID 1
normal  ->  systemd-journald: File /var/log/journal/bd8e491d3fd246aba6861a6970e39e0d/system.journal corrupted or uncleanly shut down, renaming and replacing.
            systemd-journald: Received request to flush runtime journal from PID 1
---------------------------------------------------------------------
normal  ->  systemd: Created slice system-postfix.slice.
---------------------------------------------------------------------
delayed ->  systemd: Listening on Journal Socket.
            systemd: Mounting Huge Pages File System...
            systemd: Reached target User and Group Name Lookups.
normal  ->  systemd: Listening on Journal Audit Socket.
            systemd: Listening on Syslog Socket.
---------------------------------------------------------------------
delayed ->  tsc: Detected 2128.414 MHz processor
            tsc: Fast TSC calibration using PIT
normal  ->  tsc: Detected 2128.220 MHz processor
            tsc: Fast TSC calibration failed
---------------------------------------------------------------------
normal  ->  tsc: PIT calibration matches PMTIMER. 1 loops
---------------------------------------------------------------------
delayed ->  vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
            vesafb: framebuffer at 0xc0000000, mapped to 0x(ptrval), using 5760k, total 5760k
            vesafb: mode is 1400x1050x32, linelength=5600, pages=0
            vesafb: scrolling: redraw
---------------------------------------------------------------------
delayed ->  vt handoff: transparent VT on vt#1
------------------------------------------------------------------------

The final part of the boot log for the delayed boot looks as follows:

[   15.216730] audit: type=1400 audit(1607087065.208:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer" pid=676 comm="apparmor_parser"
[   15.216737] audit: type=1400 audit(1607087065.208:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer//sanitized_helper" pid=676 comm="apparmor_parser"
[  174.735613] thinkpad_ec: loading out-of-tree module taints kernel.
[  174.735783] thinkpad_ec: module verification failed: signature and/or required key missing - tainting kernel
[  174.740215] thinkpad_ec: thinkpad_ec 0.42 loaded.
[  174.741379] tp_smapi 0.42 loading...
[  174.743033] tp_smapi successfully loaded (smapi_port=0xb2).
[  174.767561] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_NOT_FOUND
[  174.767572] ACPI: \_SB_.PCI0.LPC_.EC__.HKEY: BCTG: evaluate failed
[  174.812330] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_NOT_FOUND
[  174.812341] ACPI: \_SB_.PCI0.LPC_.EC__.HKEY: BCTG: evaluate failed
[  195.615652] lib80211_crypt: registered algorithm 'CCMP'
[  195.673147] lib80211_crypt: registered algorithm 'TKIP'
[  195.689827] IPv6: ADDRCONF(NETDEV_CHANGE): wlp11s2: link becomes ready
[  211.880332] ipw2200: Firmware error detected.  Restarting.

and those for the normal speed boot are:

[   14.430661] audit: type=1400 audit(1607088184.628:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer" pid=693 comm="apparmor_parser"
[   14.430665] audit: type=1400 audit(1607088184.628:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer//sanitized_helper" pid=693 comm="apparmor_parser"
[   25.976615] thinkpad_ec: loading out-of-tree module taints kernel.
[   25.976668] thinkpad_ec: module verification failed: signature and/or required key missing - tainting kernel
[   25.981152] thinkpad_ec: thinkpad_ec 0.42 loaded.
[   25.981993] tp_smapi 0.42 loading...
[   25.983999] tp_smapi successfully loaded (smapi_port=0xb2).
[   26.011674] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_NOT_FOUND
[   26.011683] ACPI: \_SB_.PCI0.LPC_.EC__.HKEY: BCTG: evaluate failed
[   26.054491] thinkpad_acpi: acpi_evalf(BCTG, dd, ...) failed: AE_NOT_FOUND
[   26.054503] ACPI: \_SB_.PCI0.LPC_.EC__.HKEY: BCTG: evaluate failed
[  121.255499] ipw2200: Firmware error detected.  Restarting.
[  137.612515] lib80211_crypt: registered algorithm 'CCMP'
[  137.738593] lib80211_crypt: registered algorithm 'TKIP'
[  137.784727] IPv6: ADDRCONF(NETDEV_CHANGE): wlp11s2: link becomes ready

Some of the delay before the *ipw2200* message is due to *me* having to press *enter* when the grub menu is shown. I noticed that the kernel is started with an additional parm:

.handoff=1

when the boot process is delayed. Also there are some differences related to the video, syslogd, and some others. Any hint what to look at next? TIA **Update 10.12.2020** I have deciced to start all over again, and will not follow this problem in this thread any longer. I had installed the system twice before starting this question, and each time, I think, did the problem appear some time after the installation. Currently, I fear that some software update -- as usual after installing from DVD, there are plenty -- is causing the problem. So, I decided to do a fresh install, but will not do a general update right away. Hoping to find the cause by step by step updating. Nevermind, and thanks for your time.

After a recent hardware migration I started experiencing weird I/O stalls affecting my desktop Debian Stretch system. Typical symptoms, all happening during each stall: - I stop being able to interact with Chromium, my web browser. Nothing works: webpage scrolling (usually this is the way I notice the stall), switching tabs, etc. No mouse-over actions either, whether on a web page or Chromium UI. - In a virtual terminal, I can't run new processes anymore. For example, I open a new tab in mate-terminal and my shell doesn't show up, just the cursor blinking. In a terminal with shell opened before a stall, I can type a command, but usually it doesn't start; sudo something doesn't even ask for a password. - Other programs, like RStudio, can't save anything to disk and often hang when they attempt to. - I see in the logs of journald -f that if the stall is long enough, journald itself restarts, example: sty 30 14:03:54 liori-pc systemd: systemd-journald.service: Main process exited, code=killed, status=6/ABRT sty 30 14:03:54 liori-pc systemd: systemd-journald.service: Unit entered failed state. sty 30 14:03:54 liori-pc systemd: systemd-journald.service: Failed with result 'watchdog'. sty 30 14:03:54 liori-pc systemd: systemd-journald.service: Service has no hold-off time, scheduling restart. sty 30 14:03:54 liori-pc systemd: Stopped Flush Journal to Persistent Storage. sty 30 14:03:54 liori-pc systemd: Stopping Flush Journal to Persistent Storage... sty 30 14:03:54 liori-pc systemd: Stopped Journal Service. sty 30 14:03:54 liori-pc systemd: Starting Journal Service... sty 30 14:03:54 liori-pc systemd-journald: Journal started sty 30 14:03:54 liori-pc systemd-journald: System journal (/var/log/journal/2318080f60e357aaf765e98d0000035c) is 2.1G, max 4.0G, 1.8G free. - When using dm_crypt, a dmcrypt_write process starts taking 100% of a single CPU core (I later got rid of dm_crypt from this system, but stalls still happen). - I observe /proc/meminfo and see that the Dirty number is never more than few megabytes. Notably, during a stall, this number doesn't change. - In rare cases, I even get a kernel message in the form of "INFO: task «some process» blocked for more than 120 seconds.", with «some_process» being usually mdX_raid5, chromium or one of its threads, etc. [Example log](https://gist.github.com/liori/1201305ceb5787308c46b051aa16fbe3) . Initially my setup was just a single 600GB ext4 file system on a partition on a single 1TB drive (current /dev/sdd). Then I migrated to 3×6TB drives (/dev/sd{b,c,e}), with LVM-based raid5, bcache with its cache on an SSD drive, then dm_crypt — and that's when the stalls started. In the process of debugging, I simplified it to just LVM-raid5, with no bcache or dm_crypt; stalls still happen, though I feel they are less often now. This kind of stall happens several times a day and usually lasts few minutes. I noticed that I can break it by explicitly requesting some disk operation: I was able to sometimes break it by logging in to this system by ssh from a remote machine, or (almost always) by just cat /dev/sdb >/dev/null or cat /dev/sdc >/dev/null (sometimes one, sometimes the other works; notably cat /dev/sde >/dev/null never helped). Then, everything that stalled suddenly start working again. So I suspect the problem is caused by one of or interaction of: - The drives: all three are Seagate Skyhawk ST6000VX0023. Two of them unused before this setup, the third one used for half a year (/dev/sdc). - Disk controllers: the motherboard: [Gigabyte Z68X-UD3H-B3](https://www.gigabyte.com/Motherboard/GA-Z68X-UD3H-B3-rev-10#sp) has two controllers: Marvell 88SE9172 where one of the drives is connected to, and the chipset-builtin controller (Intel® Z68) with two others (can I check which one is where in software?). - Some bug in the controller kernel drivers. - Some bug in LVM or raid5. This is a Debian Stretch system with some backported packages installed, most notably kernel 4.19.0-0.bpo.1-amd64. Intel Core i7-2600k, 16GB of RAM. At this point I ran out of ideas. How do I debug this problem further? Edit: I started a script that's reading a single random sector from one of these drives every 4 seconds, and had no stalls for 2 days now. So indeed it does look like some system component (LVM? raid?) doesn't properly wake up devices from some kind of a low-power mode when it's necessary. Edit: I no longer have access to this system, so I can no longer test any hypothesis. I can only say that after running that script I was no longer getting the stalls. I wish I knew how to debug it, though.

I have a few video files which have "humm" sound in the audio. So, I created the following script for batch processing. **I am using ffmpeg, to extract audio to .mp3, and sox to denoise,** which will output noise free mp3 file.

mkdir -p ./tmp;
for f in *.mp4;
do
    title=${f%.mp4};
    echo "Working on $f";
    mv ./"$f" ./tmp/ && ffmpeg -i ./tmp/"$f" -f mp3 -ab 128000 -vn ./tmp/"$title"_noise.mp3;

    echo "Sox process started...";
    sox -v 0.80 ./tmp/"$title"_noise.mp3 ./tmp/"$title"_128.mp3 noisered ./noise_profile 0.20 && sox ./tmp/"$title"_128.$mp3 -C 96 ./$title.mp3;

    echo "Removing Audio from video file...";
    ffmpeg -loglevel warning -stats -y -i ./tmp/"$f" -c copy -an ./"$f";
done

But the problem is, I observed that there is 00:00:00.050s (HH:MM:SS.ms - Checked with Audacity) of delay added to the final mp3 file. I believe **Sox** is adding this delay. 1. **How can I solve this? Or, how can I remove/trim 00.050 seconds from the beginning and add 00.050 seconds of silence at the end of the audio track?** OR 2. **Is there any other better way to finish my task?** NOTE: I am trying to work with .wav instead of .mp3 after reading below reply, if it works I will update here.)

Since a couple of days, my machine experiences a delay when loading webpages. Rather than starting loading, the browser sits there for several seconds (around 5 or 10 seconds), seemingly doing nothing. Chromium says "Resolving host..." in its status bar while waiting. Firefox says "Looking up [domain]" and after a few seconds "Performing a TLS handshake to [domain]..." before the page finally loads. The loading process itself is not slow; this only happens on opening, not during loading of data. An online internet speed test also reveals that the speed is the same as normal (47 Mbps down, 56 Mbps up). And another computer in the same network (running a different OS) does not have the same problem. Does anybody know what I can do to check what is wrong? I'm not running out of disk space. I cleared out my browsers' caches, but that hasn't helped. And now I don't know, e.g. which log file(s) to look in. I found several things to check when I searched, such as [Ubuntu 18.04 slow after 2019 update](https://askubuntu.com/q/1138691/61377) , but none that address this particular problem. This is with Debian 9.12, KDE.