启动讨论 grub/grub2/syslinux/grub4dos/Lilo
-
tedchina
- 帖子： 71
- 注册时间： 2008-11-18 15:08
#1
帖子
由 tedchina » 2019-01-22 21:28
Ubuntu 18.04 LTS，此前配置了XX-NET脚本自启动如下，一直工作正常。
代码： 全选
xxxx:~$ ls -l /etc/systemd/system/rc-local.service
lrwxrwxrwx 1 root root 36 Sep 13 22:31 /etc/systemd/system/rc-local.service -> /lib/systemd/system/rc-local.service
xxxx:~$ cat /etc/systemd/system/rc-local.service
# SPDX-License-Identifier: LGPL-2.1+
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# This unit gets pulled automatically into multi-user.target by
# systemd-rc-local-generator if /etc/rc.local is executable.
[Unit]
Description=/etc/rc.local Compatibility
Documentation=man:systemd-rc-local-generator(8)
ConditionFileIsExecutable=/etc/rc.local
After=network.target
[Service]
Type=forking
ExecStart=/etc/rc.local start
TimeoutSec=0
RemainAfterExit=yes
GuessMainPID=no
[Install]
WantedBy=multi-user.target
Alias=rc-local.service
xxxx:~$ ls -l /etc/rc.local
-rwxr-xr-x 1 root root 59 Sep 13 22:31 /etc/rc.local
xxxx:~$ cat /etc/rc.local
#!/bin/bash
sudo /opt/xxnet/xx_net.sh start
sudo miredo
不知是否因为最近装了一堆各种各样的Docker及container，
现在变成每次开机后的xx_net.sh跟没有运行过一样，127.0.0.1:8085的访问时提示“This site can’t be reached”，只得重新手动再执行一遍这行命令方可。miredo倒是不需要重新执行。
开机后未运行任何命令时的网络配置如下：
代码： 全选
xxxx:~$ ifconfig
br-361f98a41e90: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.19.0.1 netmask 255.255.0.0 broadcast 172.19.255.255
ether 02:42:54:ce:79:4d txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-fa374fa8f91a: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
ether 02:42:f9:89:88:46 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:1e:42:0b:e5 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp8s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.91 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::a624:e346:4450:b3b7 prefixlen 64 scopeid 0x20<link>
ether e8:9a:8f:c9:2a:54 txqueuelen 1000 (Ethernet)
RX packets 4993 bytes 4356003 (4.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5399 bytes 641551 (641.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 1 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 689 bytes 56423 (56.4 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 689 bytes 56423 (56.4 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
teredo: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1280
inet6 fe80::a52a:8887:57cc:18fe prefixlen 64 scopeid 0x20<link>
inet6 fe80::ffff:ffff:ffff prefixlen 64 scopeid 0x20<link>
inet6 2001:0:53aa:64c:14c1:a37e:4b54:c542 prefixlen 32 scopeid 0x0<global>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 19 bytes 1272 (1.2 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
代码： 全选
xxxx:~$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
xxxx:~$
-
astolia
- 论坛版主
- 帖子： 6436
- 注册时间： 2008-09-18 13:11
#2
帖子
由 astolia » 2019-01-23 10:52
出问题去查日志啊
代码： 全选
journalctl -u rc-local
另外rc-local本来就是以root权限运行的，没必要再用sudo
-
tedchina
- 帖子： 71
- 注册时间： 2008-11-18 15:08
#3
帖子
由 tedchina » 2019-01-25 0:22
astolia 写了： ↑2019-01-23 10:52
出问题去查日志啊
代码： 全选
journalctl -u rc-local
另外rc-local本来就是以root权限运行的，没必要再用sudo
谢谢版主，一语点醒梦中人。回头去看看（现在用的是其它机器）。
-
tedchina
- 帖子： 71
- 注册时间： 2008-11-18 15:08
#4
帖子
由 tedchina » 2019-01-27 18:49
谢谢版主指点，查看日志后发现，其实还是偶有成功，只是失败概率极高。
失败原因是启动teredo时失败，因而导致启动整个rc.local失败，然后貌似就回滚了（即xxnet相当于没有执行）。注释掉teredo启动行后xxnet启动就成功了（因为没有自动启动teredo，还是需要手动启动一下teredo）。
代码： 全选
Jan 27 18:01:35 HASEE rc.local[1452]: Cannot create PID file /var/run/miredo.pid:
Jan 27 18:01:35 HASEE rc.local[1452]: Resource temporarily unavailable
Jan 27 18:01:35 HASEE rc.local[1452]: Please make sure another instance of the program is not already running.
现在是的疑问是：
- 什么进程在抢占资源，是新装的那一堆Docker吗？
- 如何在rc.local中实现保护以保证miredo(teredo)命令行一定成功？
一个完整的失败日志如下：
代码： 全选
Jan 27 18:01:35 HASEE systemd[1]: Starting /etc/rc.local Compatibility...
Jan 27 18:01:35 HASEE sudo[1495]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/opt/xxnet/xx_net.sh start
Jan 27 18:01:35 HASEE sudo[1495]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 27 18:01:35 HASEE rc.local[1452]: Starting xx_net proxy server: xx_net.
Jan 27 18:01:35 HASEE sudo[1495]: pam_unix(sudo:session): session closed for user root
Jan 27 18:01:35 HASEE sudo[1610]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/miredo
Jan 27 18:01:35 HASEE sudo[1610]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 27 18:01:35 HASEE rc.local[1452]: Cannot create PID file /var/run/miredo.pid:
Jan 27 18:01:35 HASEE rc.local[1452]: Resource temporarily unavailable
Jan 27 18:01:35 HASEE rc.local[1452]: Please make sure another instance of the program is not already running.
Jan 27 18:01:35 HASEE sudo[1610]: pam_unix(sudo:session): session closed for user root
Jan 27 18:01:35 HASEE systemd[1]: rc-local.service: Control process exited, code=exited status=1
Jan 27 18:01:35 HASEE systemd[1]: rc-local.service: Failed with result 'exit-code'.
Jan 27 18:01:35 HASEE systemd[1]: Failed to start /etc/rc.local Compatibility.
rc.local中只有两行：第一行启动xxnet，第二行启动miredo(teredo)：
代码： 全选
xxxx:~$ cat /etc/rc.local
#!/bin/bash
sudo /opt/xxnet/xx_net.sh start
# sudo miredo
-
astolia
- 论坛版主
- 帖子： 6436
- 注册时间： 2008-09-18 13:11
#5
帖子
由 astolia » 2019-01-29 11:31
tedchina 写了： ↑2019-01-27 18:49
失败原因是启动teredo时失败，因而导致启动整个rc.local失败，然后貌似就回滚了（即xxnet相当于没有执行）
这不叫回滚。只是systemd认为启动失败，把rc.local已启动的子进程全部中止了。所以传统上rc.local最后一定会用exit 0保证退出码是0，即使中间有些命令失败也不影响其他。
tedchina 写了： ↑2019-01-27 18:49
现在是的疑问是：
- 什么进程在抢占资源，是新装的那一堆Docker吗？
- 如何在rc.local中实现保护以保证miredo(teredo)命令行一定成功？
如果你是安装的源里的miredo包，它自带有/lib/systemd/system/miredo.service，启动顺序一般应该是在rc.local之前。也就是说当前已经有个miredo进程在运行了
-
tedchina
- 帖子： 71
- 注册时间： 2008-11-18 15:08
#6
帖子
由 tedchina » 2019-01-30 0:28
astolia 写了： ↑2019-01-29 11:31
如果你是安装的源里的miredo包，它自带有/lib/systemd/system/miredo.service，启动顺序一般应该是在rc.local之前。也就是说当前已经有个miredo进程在运行了
应该不是自带的miredo吧？如果rc.local失败，后续也没有“自动”的miredo被启动，我需要手动启动它。
-
astolia
- 论坛版主
- 帖子： 6436
- 注册时间： 2008-09-18 13:11
#7
帖子
由 astolia » 2019-01-30 11:41
你开头可不是这么说的
miredo倒是不需要重新执行。
在rc.local里运行miredo之前，加上
代码： 全选
ps -A > /tmp/a.txt
lsof | grep /var/run/miredo.pid >> /tmp/a.txt
看一下呗
-
tedchina
- 帖子： 71
- 注册时间： 2008-11-18 15:08
#8
帖子
由 tedchina » 2019-01-31 23:40
原先/etc/rc.local有miredo命令时，当xxnet失败后，的确不需要重新执行miredo命令（查ifconfig能看到teredo），只需重新执行xxnet脚本即可。
当注释掉/etc/rc.local中的那行miredo命令后，的确需要重新执行miredo命令（等好一会儿后查ifconfig看不到teredo）。
拿掉注释重新使能/etc/rc.local中的那行miredo命令，并在其前加入版主的log命令再试。
1、本次尝试的miredo命令执行成功
2、看版主要求的log，发现前面已有过一次miredo了。这是哪来的？
代码： 全选
xxxx:~$ cat /etc/rc.local
#!/bin/bash
/opt/xxnet/xx_net.sh start
ps -A > /tmp/a.txt
lsof | grep /var/run/miredo.pid >> /tmp/a.txt
miredo
代码： 全选
xxxx:~$ journalctl -u rc-local
xxxx
-- Reboot --
Jan 31 20:24:53 HASEE systemd[1]: Starting /etc/rc.local Compatibility...
Jan 31 20:24:53 HASEE rc.local[1264]: Starting xx_net proxy server: xx_net.
Jan 31 20:24:53 HASEE systemd[1]: Started /etc/rc.local Compatibility.
Jan 31 23:25:28 HASEE systemd[1]: Stopping /etc/rc.local Compatibility...
Jan 31 23:25:29 HASEE systemd[1]: Stopped /etc/rc.local Compatibility.
-- Reboot --
Jan 31 23:25:57 HASEE systemd[1]: Starting /etc/rc.local Compatibility...
Jan 31 23:25:58 HASEE rc.local[1443]: Starting xx_net proxy server: xx_net.
Jan 31 23:25:58 HASEE miredo[1636]: Starting...
Jan 31 23:25:58 HASEE systemd[1]: Started /etc/rc.local Compatibility.
Jan 31 23:26:10 HASEE miredo[1639]: New Teredo address/MTU
Jan 31 23:26:10 HASEE miredo[1639]: Teredo pseudo-tunnel started
Jan 31 23:26:10 HASEE miredo[1639]: (address: 2001:0:53aa:64c:20b2:f0fe:4b54:c542, MTU: 1280)
代码： 全选
xxxx:~$ cat /tmp/a.txt
PID TTY TIME CMD
1 ? 00:00:01 systemd
2 ? 00:00:00 kthreadd
3 ? 00:00:00 kworker/0:0
4 ? 00:00:00 kworker/0:0H
5 ? 00:00:00 kworker/u16:0
6 ? 00:00:00 mm_percpu_wq
7 ? 00:00:00 ksoftirqd/0
8 ? 00:00:00 rcu_sched
9 ? 00:00:00 rcu_bh
10 ? 00:00:00 migration/0
11 ? 00:00:00 watchdog/0
12 ? 00:00:00 cpuhp/0
13 ? 00:00:00 cpuhp/1
14 ? 00:00:00 watchdog/1
15 ? 00:00:00 migration/1
16 ? 00:00:00 ksoftirqd/1
17 ? 00:00:00 kworker/1:0
18 ? 00:00:00 kworker/1:0H
19 ? 00:00:00 cpuhp/2
20 ? 00:00:00 watchdog/2
21 ? 00:00:00 migration/2
22 ? 00:00:00 ksoftirqd/2
23 ? 00:00:00 kworker/2:0
24 ? 00:00:00 kworker/2:0H
25 ? 00:00:00 cpuhp/3
26 ? 00:00:00 watchdog/3
27 ? 00:00:00 migration/3
28 ? 00:00:00 ksoftirqd/3
29 ? 00:00:00 kworker/3:0
30 ? 00:00:00 kworker/3:0H
31 ? 00:00:00 kdevtmpfs
32 ? 00:00:00 netns
33 ? 00:00:00 rcu_tasks_kthre
34 ? 00:00:00 kauditd
35 ? 00:00:00 kworker/0:1
36 ? 00:00:00 kworker/2:1
37 ? 00:00:00 khungtaskd
38 ? 00:00:00 oom_reaper
39 ? 00:00:00 writeback
40 ? 00:00:00 kcompactd0
41 ? 00:00:00 ksmd
42 ? 00:00:00 khugepaged
43 ? 00:00:00 crypto
44 ? 00:00:00 kintegrityd
45 ? 00:00:00 kblockd
46 ? 00:00:00 ata_sff
47 ? 00:00:00 md
48 ? 00:00:00 edac-poller
49 ? 00:00:00 devfreq_wq
50 ? 00:00:00 watchdogd
51 ? 00:00:00 kworker/u16:1
52 ? 00:00:00 kworker/1:1
53 ? 00:00:00 kworker/3:1
55 ? 00:00:00 kswapd0
56 ? 00:00:00 ecryptfs-kthrea
98 ? 00:00:00 kthrotld
99 ? 00:00:00 acpi_thermal_pm
100 ? 00:00:00 kworker/u16:2
104 ? 00:00:00 ipv6_addrconf
113 ? 00:00:00 kworker/0:2
114 ? 00:00:00 kstrp
131 ? 00:00:00 charger_manager
165 ? 00:00:00 kworker/u16:3
183 ? 00:00:00 kworker/3:2
184 ? 00:00:00 scsi_eh_0
185 ? 00:00:00 scsi_tmf_0
186 ? 00:00:00 scsi_eh_1
187 ? 00:00:00 scsi_tmf_1
188 ? 00:00:00 scsi_eh_2
189 ? 00:00:00 scsi_tmf_2
190 ? 00:00:00 scsi_eh_3
191 ? 00:00:00 scsi_tmf_3
192 ? 00:00:00 scsi_eh_4
193 ? 00:00:00 kworker/3:3
194 ? 00:00:00 scsi_tmf_4
195 ? 00:00:00 scsi_eh_5
196 ? 00:00:00 scsi_tmf_5
197 ? 00:00:00 kworker/3:4
198 ? 00:00:00 kworker/u16:4
199 ? 00:00:00 kworker/u16:5
200 ? 00:00:00 kworker/u16:6
201 ? 00:00:00 kworker/u17:0
202 ? 00:00:00 i915/signal:0
203 ? 00:00:00 i915/signal:1
204 ? 00:00:00 i915/signal:2
205 ? 00:00:00 kworker/u16:7
206 ? 00:00:00 nvkm-disp
207 ? 00:00:00 kworker/1:2
217 ? 00:00:00 kworker/0:1H
223 ? 00:00:00 ttm_swap
224 ? 00:00:00 kworker/0:3
230 ? 00:00:00 kworker/1:3
231 ? 00:00:00 kworker/2:1H
254 ? 00:00:00 jbd2/sda2-8
255 ? 00:00:00 ext4-rsv-conver
284 ? 00:00:00 ureadahead
287 ? 00:00:00 systemd-journal
308 ? 00:00:00 kworker/1:1H
313 ? 00:00:01 systemd-udevd
315 ? 00:00:00 kworker/3:1H
356 ? 00:00:00 irq/28-mei_me
474 ? 00:00:00 cfg80211
554 ? 00:00:00 systemd-rfkill
598 ? 00:00:00 kworker/2:2
606 ? 00:00:00 kworker/2:3
608 ? 00:00:00 kworker/2:4
698 ? 00:00:00 loop0
718 ? 00:00:00 loop1
725 ? 00:00:00 loop2
727 ? 00:00:00 loop3
742 ? 00:00:00 loop4
746 ? 00:00:00 loop5
749 ? 00:00:00 plymouthd
762 ? 00:00:00 loop6
765 ? 00:00:00 systemd-resolve
766 ? 00:00:00 systemd-timesyn
767 ? 00:00:00 loop7
768 ? 00:00:00 loop8
769 ? 00:00:00 loop9
770 ? 00:00:00 loop10
771 ? 00:00:00 loop11
772 ? 00:00:00 loop12
773 ? 00:00:00 loop13
774 ? 00:00:00 loop14
775 ? 00:00:00 loop15
777 ? 00:00:00 loop16
778 ? 00:00:00 loop17
779 ? 00:00:00 loop18
780 ? 00:00:00 loop19
782 ? 00:00:00 loop20
786 ? 00:00:00 loop21
884 ? 00:00:00 avahi-daemon
894 ? 00:00:00 (-cpufreq)
899 ? 00:00:00 acpid
902 ? 00:00:00 accounts-daemon
907 ? 00:00:00 avahi-daemon
926 ? 00:00:00 networkd-dispat
927 ? 00:00:00 rsyslogd
929 ? 00:00:00 systemd-logind
930 ? 00:00:00 thermald
944 ? 00:00:00 cron
945 ? 00:00:00 ModemManager
946 ? 00:00:00 udisksd
947 ? 00:00:00 irqbalance
948 ? 00:00:00 snapd
949 ? 00:00:00 dbus-daemon
990 ? 00:00:00 NetworkManager
992 ? 00:00:00 wpa_supplicant
997 ? 00:00:00 cupsd
1044 ? 00:00:00 cups-browsed
1100 ? 00:00:00 polkitd
1226 ? 00:00:00 systemd-hostnam
1253 ? 00:00:00 nm-dispatcher
1302 ? 00:00:00 unattended-upgr
1309 ? 00:00:00 containerd
1381 ? 00:00:00 dhclient
1415 ? 00:00:00 01-ifupdown
1416 ? 00:00:00 run-parts
1441 ? 00:00:00 dockerd
1443 ? 00:00:00 rc.local
1447 ? 00:00:00 virtualbox
1448 ? 00:00:00 nmbd
1449 ? 00:00:00 whoopsie
1455 ? 00:00:00 kerneloops
1464 ? 00:00:00 kerneloops
1501 ? 00:00:00 python
1502 ? 00:00:00 ps
1505 ? 00:00:00 iprt-VBoxWQueue
1509 ? 00:00:00 iprt-VBoxTscThr
1532 ? 00:00:00 smbd
1549 ? 00:00:00 miredo
1551 ? 00:00:00 invoke-rc.d
1554 ? 00:00:00 modprobe
-
tedchina
- 帖子： 71
- 注册时间： 2008-11-18 15:08
#9
帖子
由 tedchina » 2019-02-03 18:18
什么都没改，换了一天，新开机的机器，结果又有两个miredo。
代码： 全选
-- Reboot --
Feb 03 15:32:39 HASEE systemd[1]: Starting /etc/rc.local Compatibility...
Feb 03 15:32:40 HASEE rc.local[1540]: Starting xx_net proxy server: xx_net.
Feb 03 15:32:40 HASEE rc.local[1540]: Cannot create PID file /var/run/miredo.pid:
Feb 03 15:32:40 HASEE rc.local[1540]: Resource temporarily unavailable
Feb 03 15:32:40 HASEE rc.local[1540]: Please make sure another instance of the program is not already running.
Feb 03 15:32:40 HASEE systemd[1]: rc-local.service: Control process exited, code=exited status=1
Feb 03 15:32:40 HASEE systemd[1]: rc-local.service: Failed with result 'exit-code'.
Feb 03 15:32:40 HASEE systemd[1]: Failed to start /etc/rc.local Compatibility.
lines 3491-3519/3519 (END)
代码： 全选
xxxx:~$ cat /tmp/a.txt
PID TTY TIME CMD
1 ? 00:00:01 systemd
2 ? 00:00:00 kthreadd
3 ? 00:00:00 kworker/0:0
4 ? 00:00:00 kworker/0:0H
5 ? 00:00:00 kworker/u16:0
6 ? 00:00:00 mm_percpu_wq
7 ? 00:00:00 ksoftirqd/0
8 ? 00:00:00 rcu_sched
9 ? 00:00:00 rcu_bh
10 ? 00:00:00 migration/0
11 ? 00:00:00 watchdog/0
12 ? 00:00:00 cpuhp/0
13 ? 00:00:00 cpuhp/1
14 ? 00:00:00 watchdog/1
15 ? 00:00:00 migration/1
16 ? 00:00:00 ksoftirqd/1
17 ? 00:00:00 kworker/1:0
18 ? 00:00:00 kworker/1:0H
19 ? 00:00:00 cpuhp/2
20 ? 00:00:00 watchdog/2
21 ? 00:00:00 migration/2
22 ? 00:00:00 ksoftirqd/2
23 ? 00:00:00 kworker/2:0
24 ? 00:00:00 kworker/2:0H
25 ? 00:00:00 cpuhp/3
26 ? 00:00:00 watchdog/3
27 ? 00:00:00 migration/3
28 ? 00:00:00 ksoftirqd/3
29 ? 00:00:00 kworker/3:0
30 ? 00:00:00 kworker/3:0H
31 ? 00:00:00 kdevtmpfs
32 ? 00:00:00 netns
33 ? 00:00:00 rcu_tasks_kthre
34 ? 00:00:00 kauditd
35 ? 00:00:00 kworker/0:1
36 ? 00:00:00 kworker/2:1
37 ? 00:00:00 khungtaskd
38 ? 00:00:00 oom_reaper
39 ? 00:00:00 writeback
40 ? 00:00:00 kcompactd0
41 ? 00:00:00 ksmd
42 ? 00:00:00 khugepaged
43 ? 00:00:00 crypto
44 ? 00:00:00 kintegrityd
45 ? 00:00:00 kblockd
46 ? 00:00:00 ata_sff
47 ? 00:00:00 md
48 ? 00:00:00 edac-poller
49 ? 00:00:00 devfreq_wq
50 ? 00:00:00 watchdogd
51 ? 00:00:00 kworker/u16:1
52 ? 00:00:00 kworker/1:1
53 ? 00:00:00 kworker/3:1
55 ? 00:00:00 kswapd0
56 ? 00:00:00 ecryptfs-kthrea
98 ? 00:00:00 kthrotld
99 ? 00:00:00 acpi_thermal_pm
100 ? 00:00:00 kworker/u16:2
104 ? 00:00:00 kworker/0:2
105 ? 00:00:00 ipv6_addrconf
114 ? 00:00:00 kstrp
131 ? 00:00:00 charger_manager
169 ? 00:00:00 kworker/u16:3
187 ? 00:00:00 scsi_eh_0
188 ? 00:00:00 scsi_tmf_0
189 ? 00:00:00 scsi_eh_1
190 ? 00:00:00 scsi_tmf_1
191 ? 00:00:00 scsi_eh_2
192 ? 00:00:00 scsi_tmf_2
193 ? 00:00:00 scsi_eh_3
194 ? 00:00:00 scsi_tmf_3
195 ? 00:00:00 scsi_eh_4
196 ? 00:00:00 scsi_tmf_4
197 ? 00:00:00 scsi_eh_5
198 ? 00:00:00 scsi_tmf_5
199 ? 00:00:00 kworker/u16:4
200 ? 00:00:00 kworker/u16:5
201 ? 00:00:00 kworker/u16:6
202 ? 00:00:00 kworker/u16:7
203 ? 00:00:00 kworker/2:2
204 ? 00:00:00 kworker/u16:8
205 ? 00:00:00 kworker/2:3
206 ? 00:00:00 kworker/2:4
207 ? 00:00:00 kworker/u17:0
208 ? 00:00:00 i915/signal:0
209 ? 00:00:00 i915/signal:1
210 ? 00:00:00 i915/signal:2
213 ? 00:00:00 kworker/0:1H
214 ? 00:00:00 kworker/0:3
215 ? 00:00:00 nvkm-disp
228 ? 00:00:00 ttm_swap
229 ? 00:00:00 kworker/3:2
233 ? 00:00:00 kworker/3:3
261 ? 00:00:00 jbd2/sda2-8
262 ? 00:00:00 ext4-rsv-conver
291 ? 00:00:00 ureadahead
297 ? 00:00:00 kworker/2:1H
302 ? 00:00:00 systemd-journal
310 ? 00:00:00 kworker/1:1H
323 ? 00:00:00 systemd-udevd
325 ? 00:00:00 kworker/3:1H
386 ? 00:00:00 irq/28-mei_me
398 ? 00:00:00 cfg80211
511 ? 00:00:00 kworker/1:2
557 ? 00:00:00 kworker/1:3
558 ? 00:00:00 kworker/1:4
571 ? 00:00:00 systemd-rfkill
734 ? 00:00:00 plymouthd
735 ? 00:00:00 loop0
744 ? 00:00:00 loop1
745 ? 00:00:00 loop2
749 ? 00:00:00 loop3
750 ? 00:00:00 loop4
752 ? 00:00:00 loop5
760 ? 00:00:00 loop6
761 ? 00:00:00 loop7
763 ? 00:00:00 loop8
765 ? 00:00:00 systemd-resolve
766 ? 00:00:00 systemd-timesyn
767 ? 00:00:00 loop9
768 ? 00:00:00 loop10
770 ? 00:00:00 loop11
771 ? 00:00:00 loop12
773 ? 00:00:00 loop13
778 ? 00:00:00 loop14
779 ? 00:00:00 loop15
780 ? 00:00:00 loop16
781 ? 00:00:00 loop17
782 ? 00:00:00 loop18
783 ? 00:00:00 loop19
784 ? 00:00:00 loop20
785 ? 00:00:00 loop21
907 ? 00:00:00 udisksd
929 ? 00:00:00 networkd-dispat
934 ? 00:00:00 ModemManager
936 ? 00:00:00 accounts-daemon
937 ? 00:00:00 irqbalance
946 ? 00:00:00 dbus-daemon
1024 ? 00:00:00 wpa_supplicant
1025 ? 00:00:00 avahi-daemon
1033 ? 00:00:00 thermald
1034 ? 00:00:00 rsyslogd
1061 ? 00:00:00 avahi-daemon
1084 ? 00:00:00 acpid
1090 ? 00:00:00 systemd-logind
1098 ? 00:00:00 anacron
1101 ? 00:00:00 (-cpufreq)
1106 ? 00:00:00 NetworkManager
1109 ? 00:00:00 snapd
1110 ? 00:00:00 cron
1111 ? 00:00:00 cupsd
1178 ? 00:00:00 cups-browsed
1180 ? 00:00:00 polkitd
1383 ? 00:00:00 systemd-hostnam
1406 ? 00:00:00 nm-dispatcher
1447 ? 00:00:00 dhclient
1469 ? 00:00:00 01-ifupdown
1470 ? 00:00:00 run-parts
1509 ? 00:00:00 unattended-upgr
1523 ? 00:00:00 nmbd
1525 ? 00:00:00 virtualbox
1526 ? 00:00:00 whoopsie
1537 ? 00:00:00 dockerd
1540 ? 00:00:00 rc.local
1541 ? 00:00:00 containerd
1542 ? 00:00:00 miredo
1543 ? 00:00:00 snap
1550 ? 00:00:00 kerneloops
1552 ? 00:00:00 kerneloops
1558 ? 00:00:00 miredo
1563 ? 00:00:00 miredo-privproc
1587 ? 00:00:00 iprt-VBoxWQueue
1591 ? 00:00:00 iprt-VBoxTscThr
1616 ? 00:00:00 apt.systemd.dai
1636 ? 00:00:00 modprobe
1638 ? 00:00:00 miredo
1639 ? 00:00:00 invoke-rc.d
1642 ? 00:00:00 python
1643 ? 00:00:00 ps
1648 ? 00:00:00 apt.systemd.dai
1649 ? 00:00:00 apt.systemd.dai
1650 ? 00:00:00 systemctl
1652 ? 00:00:00 modprobe
