Failed to start apply kernel variables как исправить

Code: Select all

john@john-520-1020:~$ dmesg -l emerg,alert,crit,err
[    0.651557] Initramfs unpacking failed: Decoding failed
[    1.395372] ACPI BIOS Error (bug): _SB.PCI0.GFX0.LCD0._BQC: Excess arguments - ASL declared 1, ACPI requires 0 (20190816/nsarguments-160)
[    1.396189] ACPI BIOS Error (bug): _SB.PCI0.GFX0.LCD0._BQC: Excess arguments - ASL declared 1, ACPI requires 0 (20190816/nsarguments-160)

john@john-520-1020:~$ inxi -Fxxxz
System:
  Kernel: 5.4.0-42-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.6.6 wm: muffin 4.6.2 dm: LightDM 1.30.0 
  Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: Hewlett-Packard product: 520-1020 v: 1.04 
  serial: <filter> Chassis: type: 3 serial: <filter> 
  Mobo: PEGATRON model: 2AC3 v: 1.04 serial: <filter> UEFI: AMI v: 7.11 
  date: 02/24/2012 
CPU:
  Topology: Dual Core model: Intel Pentium G620 bits: 64 type: MCP 
  arch: Sandy Bridge rev: 7 L2 cache: 3072 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 10376 
  Speed: 1596 MHz min/max: 1600/2600 MHz Core speeds (MHz): 1: 1596 2: 1596 
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
  vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
  chip ID: 8086:0102 
  Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 2000 (SNB GT1) 
  v: 3.3 Mesa 20.0.8 compat-v: 3.0 direct render: Yes 
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
  vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  chip ID: 8086:1c20 
  Sound Server: ALSA v: k5.4.0-42-generic 
Network:
  Device-1: Ralink RT5392 PCIe Wireless Network Adapter driver: rt2800pci 
  v: 2.3.0 port: f040 bus ID: 04:00.0 chip ID: 1814:5392 
  IF: wlp4s0 state: up mac: <filter> 
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Hewlett-Packard driver: r8169 v: kernel port: e000 bus ID: 07:00.0 
  chip ID: 10ec:8168 
  IF: enp7s0 state: down mac: <filter> 
Drives:
  Local Storage: total: 465.76 GiB used: 27.19 GiB (5.8%) 
  ID-1: /dev/sda vendor: Seagate model: ST3500413AS size: 465.76 GiB 
  speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> rev: HP63 scheme: GPT 
Partition:
  ID-1: / size: 54.75 GiB used: 11.16 GiB (20.4%) fs: ext4 dev: /dev/sda5 
  ID-2: /home size: 68.25 GiB used: 15.97 GiB (23.4%) fs: ext4 
  dev: /dev/sda6 
  ID-3: swap-1 size: 4.66 GiB used: 19.0 MiB (0.4%) fs: swap dev: /dev/sda7 
Sensors:
  System Temperatures: cpu: 36.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 198 Uptime: 14h 26m Memory: 3.75 GiB used: 1.40 GiB (37.4%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

john@john-520-1020:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=0264104b-d5bd-4ab8-8724-d7f3eb029bd7 ro

Code: Select all

john@john-520-1020:~$ sudo systemctl status systemd-sysctl.service
[sudo] password for john:  
● systemd-sysctl.service - Apply Kernel Variables
     Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor>
     Active: failed (Result: exit-code) since Thu 2020-07-30 18:23:11 EDT; 14h >
       Docs: man:systemd-sysctl.service(8)
             man:sysctl.d(5)
    Process: 563 ExecStart=/lib/systemd/systemd-sysctl (code=exited, status=1/F>
   Main PID: 563 (code=exited, status=1/FAILURE)

Jul 30 18:23:07 john-520-1020 systemd[1]: Starting Apply Kernel Variables...
Jul 30 18:23:08 john-520-1020 systemd[1]: systemd-sysctl.service: Main process >
Jul 30 18:23:08 john-520-1020 systemd[1]: systemd-sysctl.service: Failed with r>
Jul 30 18:23:08 john-520-1020 systemd[1]: Failed to start Apply Kernel Variable>
Jul 30 18:23:11 john-520-1020 systemd[1]: Starting Apply Kernel Variables...
Jul 30 18:23:11 john-520-1020 systemd[1]: systemd-sysctl.service: Main process >
Jul 30 18:23:11 john-520-1020 systemd[1]: systemd-sysctl.service: Failed with r>
Jul 30 18:23:11 john-520-1020 systemd[1]: Failed to start Apply Kernel Variable>
lines 1-16/16 (END)

Code: Select all

john@john-520-1020:~$ sudo systemctl status systemd-sysctl.service
[sudo] password for john:  
● systemd-sysctl.service - Apply Kernel Variables
     Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static; vendor>
     Active: failed (Result: exit-code) since Thu 2020-07-30 18:23:11 EDT; 1 da>
       Docs: man:systemd-sysctl.service(8)
             man:sysctl.d(5)
   Main PID: 563 (code=exited, status=1/FAILURE)

Jul 30 18:23:07 john-520-1020 systemd[1]: Starting Apply Kernel Variables...
Jul 30 18:23:08 john-520-1020 systemd[1]: systemd-sysctl.service: Main process >
Jul 30 18:23:08 john-520-1020 systemd[1]: systemd-sysctl.service: Failed with r>
Jul 30 18:23:08 john-520-1020 systemd[1]: Failed to start Apply Kernel Variable>
Jul 30 18:23:11 john-520-1020 systemd[1]: Starting Apply Kernel Variables...
Jul 30 18:23:11 john-520-1020 systemd[1]: systemd-sysctl.service: Main process >
Jul 30 18:23:11 john-520-1020 systemd[1]: systemd-sysctl.service: Failed with r>
Jul 30 18:23:11 john-520-1020 systemd[1]: Failed to start Apply Kernel Variable>

Code: Select all

john@john-520-1020:~$ dmesg -l emerg,alert,crit,err
[    0.647289] Initramfs unpacking failed: Decoding failed
[    1.405411] ACPI BIOS Error (bug): _SB.PCI0.GFX0.LCD0._BQC: Excess arguments - ASL declared 1, ACPI requires 0 (20190816/nsarguments-160)
[    1.406346] ACPI BIOS Error (bug): _SB.PCI0.GFX0.LCD0._BQC: Excess arguments - ASL declared 1, ACPI requires 0 (20190816/nsarguments-160)

Code: Select all

for i in /etc/sysctl.d/*; do echo "***FILE***: $i"; cat $i; done
***FILE***: /etc/sysctl.d/10-console-messages.conf

# the following stops low-level messages on console
kernel.printk = 4 4 1 7
***FILE***: /etc/sysctl.d/10-ipv6-privacy.conf
# IPv6 Privacy Extensions (RFC 4941)
# ---
# IPv6 typically uses a device's MAC address when choosing an IPv6 address
# to use in autoconfiguration. Privacy extensions allow using a randomly
# generated IPv6 address, which increases privacy.
#
# Acceptable values:
#    0 - don’t use privacy extensions.
#    1 - generate privacy addresses
#    2 - prefer privacy addresses and use them over the normal addresses.
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2
***FILE***: /etc/sysctl.d/10-kernel-hardening.conf
# These settings are specific to hardening the kernel itself from attack
# from userspace, rather than protecting userspace from other malicious
# userspace things.
#
#
# When an attacker is trying to exploit the local kernel, it is often
# helpful to be able to examine where in memory the kernel, modules,
# and data structures live. As such, kernel addresses should be treated
# as sensitive information.
#
# Many files and interfaces contain these addresses (e.g. /proc/kallsyms,
# /proc/modules, etc), and this setting can censor the addresses. A value
# of "0" allows all users to see the kernel addresses. A value of "1"
# limits visibility to the root user, and "2" blocks even the root user.
kernel.kptr_restrict = 1
***FILE***: /etc/sysctl.d/10-link-restrictions.conf
# These settings eliminate an entire class of security vulnerability:
# time-of-check-time-of-use cross-privilege attacks using guessable
# filenames (generally seen as "/tmp file race" vulnerabilities).
fs.protected_hardlinks = 1
fs.protected_symlinks = 1
***FILE***: /etc/sysctl.d/10-magic-sysrq.conf
# The magic SysRq key enables certain keyboard combinations to be
# interpreted by the kernel to help with debugging. The kernel will respond
# to these keys regardless of the current running applications.
#
# In general, the magic SysRq key is not needed for the average Ubuntu
# system, and having it enabled by default can lead to security issues on
# the console such as being able to dump memory or to kill arbitrary
# processes including the running screen lock.
#
# Here is the list of possible values:
#   0 - disable sysrq completely
#   1 - enable all functions of sysrq
#  >1 - enable certain functions by adding up the following values:
#          2 - enable control of console logging level
#          4 - enable control of keyboard (SAK, unraw)
#          8 - enable debugging dumps of processes etc.
#         16 - enable sync command
#         32 - enable remount read-only
#         64 - enable signalling of processes (term, kill, oom-kill)
#        128 - allow reboot/poweroff
#        256 - allow nicing of all RT tasks
#
#   For example, to enable both control of console logging level and
#   debugging dumps of processes: kernel.sysrq = 10
#
kernel.sysrq = 176
***FILE***: /etc/sysctl.d/10-network-security.conf

# Turn on Source Address Verification in all interfaces to
# prevent some spoofing attacks.
net.ipv4.conf.default.rp_filter=2
net.ipv4.conf.all.rp_filter=2

***FILE***: /etc/sysctl.d/10-ptrace.conf
# The PTRACE system is used for debugging.  With it, a single user process
# can attach to any other dumpable process owned by the same user.  In the
# case of malicious software, it is possible to use PTRACE to access
# credentials that exist in memory (re-using existing SSH connections,
# extracting GPG agent information, etc).
#
# A PTRACE scope of "0" is the more permissive mode.  A scope of "1" limits
# PTRACE only to direct child processes (e.g. "gdb name-of-program" and
# "strace -f name-of-program" work, but gdb's "attach" and "strace -fp $PID"
# do not).  The PTRACE scope is ignored when a user has CAP_SYS_PTRACE, so
# "sudo strace -fp $PID" will work as before.  For more details see:
# https://wiki.ubuntu.com/SecurityTeam/Roadmap/KernelHardening#ptrace
#
# For applications launching crash handlers that need PTRACE, exceptions can
# be registered by the debugee by declaring in the segfault handler
# specifically which process will be using PTRACE on the debugee:
#   prctl(PR_SET_PTRACER, debugger_pid, 0, 0, 0);
#
# In general, PTRACE is not needed for the average running Ubuntu system.
# To that end, the default is to set the PTRACE scope to "1".  This value
# may not be appropriate for developers or servers with only admin accounts.
kernel.yama.ptrace_scope = 1
***FILE***: /etc/sysctl.d/10-zeropage.conf
# Protect the zero page of memory from userspace mmap to prevent kernel
# NULL-dereference attacks against potential future kernel security
# vulnerabilities.  (Added in kernel 2.6.23.)
#
# While this default is built into the Ubuntu kernel, there is no way to
# restore the kernel default if the value is changed during runtime; for
# example via package removal (e.g. wine, dosemu).  Therefore, this value
# is reset to the secure default each time the sysctl values are loaded.
vm.mmap_min_addr = 65536
***FILE***: /etc/sysctl.d/99-sysctl.conf
#
# /etc/sysctl.conf - Configuration file for setting system variables
# See /etc/sysctl.d/ for additional system variables.
# See sysctl.conf (5) for information.
#

#kernel.domainname = example.com

# Uncomment the following to stop low-level messages on console
#kernel.printk = 3 4 1 3

##############################################################3
# Functions previously found in netbase
#

# Uncomment the next two lines to enable Spoof protection (reverse-path filter)
# Turn on Source Address Verification in all interfaces to
# prevent some spoofing attacks
#net.ipv4.conf.default.rp_filter=1
#net.ipv4.conf.all.rp_filter=1

# Uncomment the next line to enable TCP/IP SYN cookies
# See http://lwn.net/Articles/277146/
# Note: This may impact IPv6 TCP sessions too
#net.ipv4.tcp_syncookies=1

# Uncomment the next line to enable packet forwarding for IPv4
#net.ipv4.ip_forward=1

# Uncomment the next line to enable packet forwarding for IPv6
#  Enabling this option disables Stateless Address Autoconfiguration
#  based on Router Advertisements for this host
#net.ipv6.conf.all.forwarding=1


###################################################################
# Additional settings - these settings can improve the network
# security of the host and prevent against some network attacks
# including spoofing attacks and man in the middle attacks through
# redirection. Some network environments, however, require that these
# settings are disabled so review and enable them as needed.
#
# Do not accept ICMP redirects (prevent MITM attacks)
#net.ipv4.conf.all.accept_redirects = 0
#net.ipv6.conf.all.accept_redirects = 0
# _or_
# Accept ICMP redirects only for gateways listed in our default
# gateway list (enabled by default)
# net.ipv4.conf.all.secure_redirects = 1
#
# Do not send ICMP redirects (we are not a router)
#net.ipv4.conf.all.send_redirects = 0
#
# Do not accept IP source route packets (we are not a router)
#net.ipv4.conf.all.accept_source_route = 0
#net.ipv6.conf.all.accept_source_route = 0
#
# Log Martian Packets
#net.ipv4.conf.all.log_martians = 1
#

###################################################################
# Magic system request Key
# 0=disable, 1=enable all, >1 bitmask of sysrq functions
# See https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html
# for what other values do
#kernel.sysrq=438

####################################################################
vm.swappiness=10

####################################################################
Cache parameter
# Improve cache management
vm.vfs_cache_pressure=50

***FILE***: /etc/sysctl.d/README.sysctl
Kernel system variables configuration files

Files found under the /etc/sysctl.d directory that end with .conf are
parsed within sysctl(8) at boot time.  If you want to set kernel variables
you can either edit /etc/sysctl.conf or make a new file.

The filename isn't important, but don't make it a package name as it may clash
with something the package builder needs later. It must end with .conf though.

My personal preference would be for local system settings to go into
/etc/sysctl.d/local.conf but as long as you follow the rules for the names
of the file, anything will work. See sysctl.conf(8) man page for details
of the format.

After making any changes, please run "service procps reload" (or, from
a Debian package maintainer script "deb-systemd-invoke restart procps.service").

Code: Select all

####################################################################
vm.swappiness=10

####################################################################
Cache parameter
# Improve cache management
vm.vfs_cache_pressure=50

Code: Select all

####################################################################
vm.swappiness=10

####################################################################
# Cache parameter
# Improve cache management
vm.vfs_cache_pressure=50

Community of ArchLinux.org,

I have been recently experiencing an issue in regards to systemd as follows:

[term@localhost ~]$ sudo systemctl status systemd-sysctl.service  
* systemd-sysctl.service - Apply Kernel Variables
   Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2016-05-20 19:23:02 UTC; 16min ago
     Docs: man:systemd-sysctl.service(8)
           man:sysctl.d(5)
  Process: 959 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=1/FAILURE)
 Main PID: 959 (code=exited, status=1/FAILURE)

May 20 19:23:02 localhost systemd[1]: Starting Apply Kernel Variables...
May 20 19:23:02 localhost systemd-sysctl[959]: Couldn't write '1' to 'kernel/kptr_restrict', ignoring: Invalid argument
May 20 19:23:02 localhost systemd-sysctl[959]: Couldn't write '1' to 'net/ipv6/conf/all/rp_filter', ignoring: No such file or directory
May 20 19:23:02 localhost systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
May 20 19:23:02 localhost systemd[1]: Failed to start Apply Kernel Variables.
May 20 19:23:02 localhost systemd[1]: systemd-sysctl.service: Unit entered failed state.
May 20 19:23:02 localhost systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.

I could use some assistance in troubleshooting this issue, as I have read over many threads and bug submissions in seeking a resolution to this issue.

Regards,

Community,

Apparently, there were some configuration files I had created which were empty; whereas, I meant to add a few lines to harden the kernel.
A simple deletion of the files and a reboot fixed the issue; however, I will attempt to add the configurations once again.
I will keep you fellow Arch users informed with an update.

—UPDATE—

Issue has returned with the creation of:

File: /etc/sysctl.d/50-kptr-restrict.conf 
kernel.kptr_restrict = 1

I am running the latest grsec kernel. Is it possible that this configuration is conflicting with the kernel?

Regards,

Last edited by user023 (2016-05-21 00:17:04)

Community,

Is it true that the latest Grsec kernel includes kptr and dmesg restriction by default?

I followed the wiki here: https://wiki.archlinux.org/index.php/sy … _hardening

Under TCP/IP Stack Hardening, I created a file: /etc/sysctl.d/90-override.conf and placed those configurations in here.

I am now wondering why the error occurs in my first post:

May 20 19:23:02 localhost systemd-sysctl[959]: Couldn't write '1' to 'net/ipv6/conf/all/rp_filter', ignoring: No such file or directory

Pleasre review my questions in the previous posts for objective correspondence.

Thank you,

Last edited by user023 (2016-05-21 00:46:24)

Hi, if is the precompile kernel you can not use it, also is useless. you can use without problem  the kernel.dmesg_restrict flag. Are you using your system as router ?, if not undo the job you did about TCP/IP stack hardening and read the warning improving performance. This should solve the problem.

I guess you are using the precompile cause you are asking.

Last edited by Irok (2016-05-21 02:46:20)

Files don’t magically materialise at that location for no reason, so instead of bandaiding over it ignoring the contents, you should know why and for what reason the files was there in the first place.

In any case, it’s unlikely that your case has any relation to the one being discussed here which is about a kernel no longer available in the repos, please don’t necrobump.

Closing.

Last edited by V1del (2019-06-25 16:09:59)

Code: Select all

[edson@edson-pc6540br ~]$ sudo journalctl -p 3 -xb
[sudo] senha para edson: 
-- Logs begin at Tue 2019-06-18 09:19:35 -03, end at Tue 2019-06-18 09:21:12 -03. --
jun 18 09:19:35 edson-pc6540br systemd-sysctl[315]: Couldn't write '0' to 'vm/dirty_backg>
jun 18 09:19:35 edson-pc6540br systemd-sysctl[315]: Couldn't write '0' to 'vm/dirty_bytes>
jun 18 09:19:37 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 09:19:37 edson-pc6540br systemd-sysctl[408]: Couldn't write '0' to 'vm/dirty_backg>
jun 18 09:19:37 edson-pc6540br systemd-sysctl[408]: Couldn't write '0' to 'vm/dirty_bytes>
jun 18 09:19:38 edson-pc6540br systemd[1]: Failed to start Apply Kernel Variables.
-- Subject: A unidade systemd-sysctl.service falhou
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A unidade systemd-sysctl.service falhou.
-- 
-- O resultado é failed.
jun 18 09:19:48 edson-pc6540br esets_mac[548]: error[02240000]: Cannot unblock removable >
jun 18 09:19:54 edson-pc6540br lightdm[562]: gkr-pam: unable to locate daemon control file
jun 18 09:20:07 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 09:20:07 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 09:20:55 edson-pc6540br daemon/bluetooth[662]: bluetooth.go:236: Failed to activat>
                                                        ->  bluetooth.go:211
                                                        ->  asm_amd64.s:1337
lines 1-21/21 (END)...skipping...
-- Logs begin at Tue 2019-06-18 09:19:35 -03, end at Tue 2019-06-18 09:21:12 -03. --
jun 18 09:19:35 edson-pc6540br systemd-sysctl[315]: Couldn't write '0' to 'vm/dirty_background_bytes': Invalid argument
jun 18 09:19:35 edson-pc6540br systemd-sysctl[315]: Couldn't write '0' to 'vm/dirty_bytes': Invalid argument
jun 18 09:19:37 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 09:19:37 edson-pc6540br systemd-sysctl[408]: Couldn't write '0' to 'vm/dirty_background_bytes': Invalid argument
jun 18 09:19:37 edson-pc6540br systemd-sysctl[408]: Couldn't write '0' to 'vm/dirty_bytes': Invalid argument
jun 18 09:19:38 edson-pc6540br systemd[1]: Failed to start Apply Kernel Variables.
-- Subject: A unidade systemd-sysctl.service falhou
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A unidade systemd-sysctl.service falhou.
-- 
-- O resultado é failed.
jun 18 09:19:48 edson-pc6540br esets_mac[548]: error[02240000]: Cannot unblock removable media (org.freedesktop.udisks2.filesystem-mount)
jun 18 09:19:54 edson-pc6540br lightdm[562]: gkr-pam: unable to locate daemon control file
jun 18 09:20:07 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 09:20:07 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 09:20:55 edson-pc6540br daemon/bluetooth[662]: bluetooth.go:236: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
                                                        ->  bluetooth.go:211
                                                        ->  asm_amd64.s:1337

Code: Select all

[2019-06-18 09:15] [ALPM] upgraded linux-headers (5.1.9.arch1-1 -> 5.1.11.arch1-1)
[2019-06-18 09:15] [ALPM] upgraded lib32-glibc (2.29-1 -> 2.29-2)
[2019-06-18 09:15] [ALPM] upgraded gpgme (1.13.0-1 -> 1.13.1-1)
[2019-06-18 09:15] [ALPM] upgraded gcc (8.3.0-1 -> 9.1.0-1)
[2019-06-18 09:15] [ALPM] upgraded evince (3.32.0-1 -> 3.32.0+22+g0fecf871-1)
[2019-06-18 09:15] [ALPM] upgraded deepin-anything-arch (0.1.0-7 -> 0.1.0-9)
[2019-06-18 09:15] [ALPM] upgraded broadcom-wl (6.30.223.271-110 -> 6.30.223.271-112)
[2019-06-18 09:15] [ALPM] upgraded linux (5.1.9.arch1-1 -> 5.1.11.arch1-1)
[2019-06-18 09:15] [ALPM] upgraded libarchive (3.3.3-1 -> 3.4.0-2)
[2019-06-18 09:15] [ALPM] upgraded binutils (2.32-1 -> 2.32-2)
[2019-06-18 09:15] [ALPM] upgraded atom (1.38.1-1 -> 1.38.2-1)
[2019-06-18 09:13] [ALPM] upgraded libtool (2.4.6+42+gb88cebd5-3 -> 2.4.6+42+gb88cebd5-4)
[2019-06-18 09:13] [ALPM] upgraded polkit (0.116-1 -> 0.116-2)
[2019-06-18 09:13] [ALPM] upgraded dbus (1.12.14-1 -> 1.12.16-1)
[2019-06-18 09:13] [ALPM] upgraded mesa (19.0.6-1 -> 19.1.0-1)
[2019-06-18 09:13] [ALPM] upgraded gcc-libs (8.3.0-1 -> 9.1.0-1)
[2019-06-18 09:13] [ALPM] upgraded glibc (2.29-1 -> 2.29-2)
[2019-06-18 09:13] [ALPM] upgraded linux-api-headers (5.0.7-1 -> 5.1-1)

Code: Select all

[edson@edson-pc6540br ~]$ systemctl restart systemd-sysctl
Job for systemd-sysctl.service failed because the control process exited with error code.
See "systemctl status systemd-sysctl.service" and "journalctl -xe" for details.
[edson@edson-pc6540br ~]$ sudo systemctl restart systemd-sysctl
[sudo] senha para edson: 
Job for systemd-sysctl.service failed because the control process exited with error code.
See "systemctl status systemd-sysctl.service" and "journalctl -xe" for details.
[edson@edson-pc6540br ~]$ systemctl status systemd-sysctl.service
● systemd-sysctl.service - Apply Kernel Variables
   Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2019-06-18 09:52:19 -03; 31s ago
     Docs: man:systemd-sysctl.service(8)
           man:sysctl.d(5)
  Process: 3904 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=1/FAILURE)
 Main PID: 3904 (code=exited, status=1/FAILURE)

jun 18 09:52:19 edson-pc6540br systemd[1]: Starting Apply Kernel Variables...
jun 18 09:52:19 edson-pc6540br systemd-sysctl[3904]: Couldn't write '0' to 'vm/dirty_background_bytes': Invalid argument
jun 18 09:52:19 edson-pc6540br systemd-sysctl[3904]: Couldn't write '0' to 'vm/dirty_bytes': Invalid argument
jun 18 09:52:19 edson-pc6540br systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
jun 18 09:52:19 edson-pc6540br systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
jun 18 09:52:19 edson-pc6540br systemd[1]: Failed to start Apply Kernel Variables.
[edson@edson-pc6540br ~]$ journalctl -xe
-- 
-- The unit systemd-sysctl.service has entered the 'failed' state with result 'exit-code'.
jun 18 09:52:00 edson-pc6540br systemd[1]: Failed to start Apply Kernel Variables.
-- Subject: A unidade systemd-sysctl.service falhou
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A unidade systemd-sysctl.service falhou.

Code: Select all

[edson@edson-pc6540br ~]$ uname -a
Linux edson-pc6540br 5.1.9-arch1-1-ARCH #1 SMP PREEMPT Tue Jun 11 16:18:09 UTC 2019 x86_64 GNU/Linux
[edson@edson-pc6540br ~]$ update
[sudo] senha para edson: 
:: Sincronizando a base de dados de pacotes...
 core                                         134,9 KiB   255K/s 00:01 [---------------------------------------] 100%
 extra                                       1631,2 KiB   292K/s 00:06 [---------------------------------------] 100%
 community                                      4,8 MiB   220K/s 00:22 [---------------------------------------] 100%
 multilib                                     171,2 KiB   201K/s 00:01 [---------------------------------------] 100%
 arcolinux_repo                                30,2 KiB   135K/s 00:00 [---------------------------------------] 100%
 arcolinux_repo.sig                           310,0   B  0,00B/s 00:00 [---------------------------------------] 100%
 arcolinux_repo_3party                         10,1 KiB  0,00B/s 00:00 [---------------------------------------] 100%
 arcolinux_repo_3party.sig                    310,0   B  0,00B/s 00:00 [---------------------------------------] 100%
 arcolinux_repo_submicron                       9,9 KiB  0,00B/s 00:00 [---------------------------------------] 100%
 arcolinux_repo_submicron.sig                 309,0   B  0,00B/s 00:00 [---------------------------------------] 100%
:: Iniciando atualização completa do sistema...
atenção: linux: ignorando atualização do pacote (5.1.9.arch1-1 => 5.1.11.arch1-1)
 não há nada a fazer
[edson@edson-pc6540br ~]$ skel
[edson@edson-pc6540br ~]$ cb
                    /-                      edson@edson-pc6540br 
                   ooo:                     -------------------- 
                  yoooo/                    OS: ArcoLinuxB-deepin v19.06.1 
                 yooooooo                   Kernel: 5.1.9-arch1-1-ARCH 
                yooooooooo                  Uptime: 4 mins 
               yooooooooooo                 Packages: 1202 (pacman) 
             .yooooooooooooo                Shell: bash 5.0.7 
            .oooooooooooooooo               Resolution: 1920x1080 
           .oooooooarcoooooooo              DE: Deepin 
          .ooooooooo-oooooooooo             WM: Mutter(DeepinGala) 
         .ooooooooo-  oooooooooo            Theme: Arc-Dark [GTK2/3] 
        :ooooooooo.    :ooooooooo           Icons: Sardi-Arc [GTK2], Sardi-Mono-Colora [GTK3] 
       :ooooooooo.      :ooooooooo          Terminal: deepin-terminal 
      :oooarcooo         .oooarcooo         Terminal Font: Droid Sans Mono 11 
     :ooooooooy           .ooooooooo        CPU: Intel i3 540 (4) @ 3.067GHz 
    :ooooooooo   /ooooooooooooooooooo       GPU: Intel Core Processor 
   :ooooooooo      .-ooooooooooooooooo.     Memory: 2706MiB / 7712MiB 
  ooooooooo-             -ooooooooooooo.
 ooooooooo-                 .-oooooooooo.                           
ooooooooo.                     -ooooooooo                           


[edson@edson-pc6540br ~]$ jctl
-- Logs begin at Tue 2019-06-18 17:42:59 -03, end at Tue 2019-06-18 17:46:55 -03. --
jun 18 17:42:59 edson-pc6540br kernel: vfs_monitor: version magic '5.1.11-arch1-1-ARCH SMP preempt mod_unload ' shou>
jun 18 17:42:59 edson-pc6540br systemd-modules-load[302]: Failed to insert module 'vfs_monitor': Exec format error
jun 18 17:43:01 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 17:43:01 edson-pc6540br systemd-modules-load[404]: Failed to insert module 'vfs_monitor': Exec format error
jun 18 17:43:01 edson-pc6540br kernel: vfs_monitor: version magic '5.1.11-arch1-1-ARCH SMP preempt mod_unload ' shou>
jun 18 17:43:01 edson-pc6540br systemd[1]: Failed to start Load Kernel Modules.
-- Subject: A unidade systemd-modules-load.service falhou
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A unidade systemd-modules-load.service falhou.
-- 
-- O resultado é failed.
jun 18 17:43:11 edson-pc6540br esets_mac[529]: error[02110000]: Cannot unblock removable media (org.freedesktop.udis>
jun 18 17:43:19 edson-pc6540br lightdm[561]: gkr-pam: unable to locate daemon control file
jun 18 17:43:32 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 17:43:33 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 17:44:19 edson-pc6540br daemon/bluetooth[659]: bluetooth.go:236: Failed to activate service 'org.bluez': time>
                                                        ->  bluetooth.go:211
                                                        ->  asm_amd64.s:1337
...skipping...
-- Logs begin at Tue 2019-06-18 17:42:59 -03, end at Tue 2019-06-18 17:46:55 -03. --
jun 18 17:42:59 edson-pc6540br kernel: vfs_monitor: version magic '5.1.11-arch1-1-ARCH SMP preempt mod_unload ' shou>
jun 18 17:42:59 edson-pc6540br systemd-modules-load[302]: Failed to insert module 'vfs_monitor': Exec format error
jun 18 17:43:01 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 17:43:01 edson-pc6540br systemd-modules-load[404]: Failed to insert module 'vfs_monitor': Exec format error
jun 18 17:43:01 edson-pc6540br kernel: vfs_monitor: version magic '5.1.11-arch1-1-ARCH SMP preempt mod_unload ' shou>
jun 18 17:43:01 edson-pc6540br systemd[1]: Failed to start Load Kernel Modules.
-- Subject: A unidade systemd-modules-load.service falhou
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A unidade systemd-modules-load.service falhou.
-- 
-- O resultado é failed.
jun 18 17:43:11 edson-pc6540br esets_mac[529]: error[02110000]: Cannot unblock removable media (org.freedesktop.udis>
jun 18 17:43:19 edson-pc6540br lightdm[561]: gkr-pam: unable to locate daemon control file
jun 18 17:43:32 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 17:43:33 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 17:44:19 edson-pc6540br daemon/bluetooth[659]: bluetooth.go:236: Failed to activate service 'org.bluez': time>
                                                        ->  bluetooth.go:211
                                                        ->  asm_amd64.s:1337

Code: Select all

edson@edson-pc6540br ~]$ sudo pacman -S linux
:: linux está no IgnorePkg/IgnoreGroup. Instalar assim mesmo? [S/n] s
resolvendo dependências...
procurando por pacotes conflitantes...

Pacote (1)  Versão antiga  Versão nova      Diferença

core/linux  5.1.9.arch1-1  5.1.11.arch1-1    -0,09 MiB

Tamanho total instalado:  76,40 MiB
Alteração no tamanho:   -0,09 MiB

:: Continuar a instalação? [S/n] s
(1/1) verificando chaves no chaveiro                                   [---------------------------------------] 100%
(1/1) verificando integridade do pacote                                [---------------------------------------] 100%
(1/1) carregando arquivos do pacote                                    [---------------------------------------] 100%
(1/1) verificando conflitos de arquivo                                 [---------------------------------------] 100%
:: Processando alterações do pacote...
(1/1) atualizando linux                                                [---------------------------------------] 100%
:: Executando hooks pós-transação...
(1/3) Updating linux module dependencies...
(2/3) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.1.11-arch1-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.1.11-arch1-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
(3/3) Arming ConditionNeedsUpdate...
[edson@edson-pc6540br ~]$ 

Code: Select all

edson@edson-pc6540br ~]$ update
[sudo] senha para edson: 
:: Sincronizando a base de dados de pacotes...
 core                                         134,9 KiB  26,7K/s 00:05 [---------------------------------------] 100%
 extra                                       1631,3 KiB   197K/s 00:08 [---------------------------------------] 100%
 community                                      4,8 MiB   339K/s 00:15 [---------------------------------------] 100%
 multilib                                     171,2 KiB   115K/s 00:01 [---------------------------------------] 100%
 arcolinux_repo                                30,2 KiB  53,6K/s 00:01 [---------------------------------------] 100%
 arcolinux_repo.sig                           310,0   B  0,00B/s 00:00 [---------------------------------------] 100%
 arcolinux_repo_3party                         10,1 KiB  0,00B/s 00:00 [---------------------------------------] 100%
 arcolinux_repo_3party.sig                    310,0   B  0,00B/s 00:00 [---------------------------------------] 100%
 arcolinux_repo_submicron                       9,9 KiB  0,00B/s 00:00 [---------------------------------------] 100%
 arcolinux_repo_submicron.sig                 309,0   B  0,00B/s 00:00 [---------------------------------------] 100%
:: Iniciando atualização completa do sistema...
 não há nada a fazer
[edson@edson-pc6540br ~]$ skel
[edson@edson-pc6540br ~]$ cb
                    /-                      edson@edson-pc6540br 
                   ooo:                     -------------------- 
                  yoooo/                    OS: ArcoLinuxB-deepin v19.06.1 
                 yooooooo                   Kernel: 5.1.11-arch1-1-ARCH 
                yooooooooo                  Uptime: 2 mins 
               yooooooooooo                 Packages: 1202 (pacman) 
             .yooooooooooooo                Shell: bash 5.0.7 
            .oooooooooooooooo               Resolution: 1920x1080 
           .oooooooarcoooooooo              DE: Deepin 
          .ooooooooo-oooooooooo             WM: Mutter(DeepinGala) 
         .ooooooooo-  oooooooooo            Theme: Arc-Dark [GTK2/3] 
        :ooooooooo.    :ooooooooo           Icons: Sardi-Arc [GTK2], Sardi-Mono-Colora [GTK3] 
       :ooooooooo.      :ooooooooo          Terminal: deepin-terminal 
      :oooarcooo         .oooarcooo         Terminal Font: Droid Sans Mono 11 
     :ooooooooy           .ooooooooo        CPU: Intel i3 540 (4) @ 3.067GHz 
    :ooooooooo   /ooooooooooooooooooo       GPU: Intel Core Processor 
   :ooooooooo      .-ooooooooooooooooo.     Memory: 835MiB / 7712MiB 
  ooooooooo-             -ooooooooooooo.
 ooooooooo-                 .-oooooooooo.                           
ooooooooo.                     -ooooooooo                           


[edson@edson-pc6540br ~]$ jctl
-- Logs begin at Tue 2019-06-18 18:30:57 -03, end at Tue 2019-06-18 18:32:52 -03. --
jun 18 18:30:57 edson-pc6540br systemd-sysctl[319]: Couldn't write '0' to 'vm/dirty_background_bytes': Invalid argum>
jun 18 18:30:57 edson-pc6540br systemd-sysctl[319]: Couldn't write '0' to 'vm/dirty_bytes': Invalid argument
jun 18 18:30:57 edson-pc6540br systemd[1]: Failed to start Apply Kernel Variables.
-- Subject: A unidade systemd-sysctl.service falhou
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A unidade systemd-sysctl.service falhou.
-- 
-- O resultado é failed.
jun 18 18:30:59 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 18:30:59 edson-pc6540br systemd-sysctl[410]: Couldn't write '0' to 'vm/dirty_background_bytes': Invalid argum>
jun 18 18:30:59 edson-pc6540br systemd-sysctl[410]: Couldn't write '0' to 'vm/dirty_bytes': Invalid argument
jun 18 18:30:59 edson-pc6540br systemd[1]: Failed to start Apply Kernel Variables.
-- Subject: A unidade systemd-sysctl.service falhou
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A unidade systemd-sysctl.service falhou.
-- 
-- O resultado é failed.
jun 18 18:31:06 edson-pc6540br ntpd[447]: bind(24) AF_INET6 fe80::6986:216e:44f9:826d%2#123 flags 0x11 failed: Canno>
jun 18 18:31:06 edson-pc6540br ntpd[447]: unable to create socket on enp1s0 (5) for fe80::6986:216e:44f9:826d%2#123
jun 18 18:31:10 edson-pc6540br esets_mac[551]: error[02270000]: Cannot unblock removable media (org.freedesktop.udis>
jun 18 18:31:17 edson-pc6540br lightdm[565]: gkr-pam: unable to locate daemon control file
jun 18 18:31:30 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 18:31:31 edson-pc6540br kernel: usb 1-1.6: 3:1: cannot get freq at ep 0x84
jun 18 18:32:18 edson-pc6540br daemon/bluetooth[662]: bluetooth.go:236: Failed to activate service 'org.bluez': time>
                                                        ->  bluetooth.go:211
                                                        ->  asm_amd64.s:1337