Results 1 to 8 of 8

Thread: New journal errors after 2020-09-15 update.

  1. #1

    Default New journal errors after 2020-09-15 update.

    Some of the errors have been around since the system was installed, and were present in Fedora as well. I filtered out the AER errors with grep, because they've been around for years. Here are the errors, the new ones are in bold:

    Code:
    > sudo journalctl -b -p err | grep -v 'AER:'
    -- Logs begin at Mon 2020-08-24 10:14:44 PDT, end at Wed 2020-09-16 14:18:24 PDT. --
    Sep 16 14:04:29 Mobile-PC kernel: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
    Sep 16 14:04:29 Mobile-PC systemd[1]: Failed to start Apply Kernel Variables.
    Sep 16 14:04:29 Mobile-PC systemd-sysctl[217]: Couldn't write '"0 2147483647"' to 'net/ipv4/ping_group_range': Invalid argument
    Sep 16 14:04:29 Mobile-PC kernel: i2c_hid i2c-DELL0812:00: HID over i2c has not been provided an Int IRQ
    Sep 16 14:04:31 Mobile-PC systemd-sysctl[475]: Couldn't write '"0 2147483647"' to 'net/ipv4/ping_group_range': Invalid argument
    Sep 16 14:04:31 Mobile-PC systemd[1]: Failed to start Apply Kernel Variables.
    Sep 16 14:04:32 Mobile-PC systemd-sysctl[540]: Couldn't write '"0 2147483647"' to 'net/ipv4/ping_group_range': Invalid argument
    Sep 16 14:04:32 Mobile-PC systemd[1]: Failed to start Apply Kernel Variables.
    Sep 16 14:04:32 Mobile-PC systemd-sysctl[750]: Couldn't write '"0 2147483647"' to 'net/ipv4/ping_group_range': Invalid argument
    Sep 16 14:04:32 Mobile-PC systemd[1]: Failed to start Apply Kernel Variables.
    Sep 16 14:04:32 Mobile-PC systemd-sysctl[826]: Couldn't write '"0 2147483647"' to 'net/ipv4/ping_group_range': Invalid argument
    Sep 16 14:04:32 Mobile-PC systemd[1]: Failed to start Apply Kernel Variables.
    Sep 16 14:04:41 Mobile-PC lightdm[1537]: gkr-pam: unable to locate daemon control file
    Sep 16 14:04:43 Mobile-PC bluetoothd[1142]: Failed to set mode: Blocked through rfkill (0x12)
    Sep 16 14:06:19 Mobile-PC kernel: iommu ivhd0: AMD-Vi: Event logged [INVALID_DEVICE_REQUEST device=00:00.0 pasid=0x00000 address=0xfffffffdf8000000 flags=0x0a00]
    Here is the list of packages that were updated immediately before the new errors started appearing:

    Code:
    > zypp-hist | grep '2020-09-15 13:1[6-9]'
    2020-09-15 13:16:44 | command | root@Mobile-PC | 'zypper' 'dup'
    2020-09-15 13:16:44 | install | PackageKit-gtk3-module | 1.2.1-1.1
    2020-09-15 13:16:44 | install | boost-license1_74_0 | 1.74.0-2.1
    2020-09-15 13:16:44 | install | chkstat | 1550_20200909-23.1
    2020-09-15 13:16:44 | install | hostname | 3.23-1.1
    2020-09-15 13:16:44 | install | iproute2 | 5.8.0-1.1
    2020-09-15 13:16:45 | install | libQt5Core5 | 5.15.1-1.1
    2020-09-15 13:16:45 | install | libacl1 | 2.2.53-4.1
    2020-09-15 13:16:45 | install | libcares2 | 1.16.1-2.1
    2020-09-15 13:16:45 | install | libefivar1 | 37-4.1
    2020-09-15 13:16:45 | install | liblcms2-2 | 2.11-1.1
    2020-09-15 13:16:45 | install | libmetis5 | 5.1.0-9.1
    2020-09-15 13:16:46 | install | libmysofa1 | 1.1-2.1
    2020-09-15 13:16:46 | install | libneon27 | 0.31.2-1.1
    2020-09-15 13:16:46 | install | libopenblas_pthreads0 | 0.3.10-3.1
    2020-09-15 13:16:46 | install | libp11-3 | 0.4.10-1.4
    2020-09-15 13:16:47 | install | libseccomp2 | 2.5.0-1.1
    2020-09-15 13:16:47 | install | libv4l | 1.20.0-2.1
    2020-09-15 13:16:47 | install | openSUSE-release-appliance-custom | 20200914-692.1
    2020-09-15 13:16:47 | install | opensc | 0.19.0-4.5
    2020-09-15 13:16:48 | install | perl-HTTP-Message | 6.26-1.1
    2020-09-15 13:16:48 | install | permissions-doc | 1550_20200909-23.1
    2020-09-15 13:16:48 | install | xen-libs | 4.14.0_02-2.2
    2020-09-15 13:16:48 | install | libboost_thread1_74_0 | 1.74.0-2.1
    2020-09-15 13:16:48 | install | libboost_iostreams1_74_0 | 1.74.0-2.1
    2020-09-15 13:16:48 | install | libboost_filesystem1_74_0 | 1.74.0-2.1
    2020-09-15 13:16:48 | install | libboost_date_time1_74_0 | 1.74.0-2.1
    2020-09-15 13:16:49 | install | permissions-config | 1550_20200909-23.1
    2020-09-15 13:16:49 | install | libQt5Test5 | 5.15.1-1.1
    2020-09-15 13:16:49 | install | libQt5Sql5 | 5.15.1-1.1
    2020-09-15 13:16:49 | install | libQt5DBus5 | 5.15.1-1.1
    2020-09-15 13:16:49 | install | vim-data-common | 8.2.1412-1.3
    2020-09-15 13:16:49 | install | acl | 2.2.53-4.1
    2020-09-15 13:16:50 | install | libv4lconvert0 | 1.20.0-2.1
    2020-09-15 13:16:50 | install | openSUSE-release | 20200914-692.1
    2020-09-15 13:16:51 | install | rng-tools | 6.10-1.1
    2020-09-15 13:16:51 | install | libboost_locale1_74_0 | 1.74.0-2.1
    2020-09-15 13:16:51 | install | permissions | 20200909.1550-23.1
    2020-09-15 13:16:51 | install | libQt5Sql5-sqlite | 5.15.1-1.1
    2020-09-15 13:16:51 | install | libQt5Positioning5 | 5.15.1-1.1
    2020-09-15 13:16:52 | install | libQt5Network5 | 5.15.1-1.1
    2020-09-15 13:16:52 | install | vim-data | 8.2.1412-1.3
    2020-09-15 13:16:53 | install | libv4l2-0 | 1.20.0-2.1
    2020-09-15 13:16:53 | install | aaa_base | 84.87+git20200909.ee4a72c-1.1
    2020-09-15 13:16:53 | install | sudo | 1.9.2-3.1
    2020-09-15 13:16:56 | install | chromium | 85.0.4183.102-1.1
    2020-09-15 13:16:56 | install | libQt5XmlPatterns5 | 5.15.1-1.1
    2020-09-15 13:16:56 | install | libQt5Gui5 | 5.15.1-1.1
    2020-09-15 13:16:57 | install | vim | 8.2.1412-1.3
    2020-09-15 13:16:57 | install | libv4l1-0 | 1.20.0-2.1
    2020-09-15 13:16:58 | install | aaa_base-extras | 84.87+git20200909.ee4a72c-1.1
    2020-09-15 13:16:58 | install | sudo-plugin-python | 1.9.2-3.1
    2020-09-15 13:16:58 | install | libqt5-qtimageformats | 5.15.1-1.1
    2020-09-15 13:16:58 | install | libqt5-qtbase-platformtheme-gtk3 | 5.15.1-1.1
    2020-09-15 13:16:58 | install | libQt5X11Extras5 | 5.15.1-1.1
    2020-09-15 13:16:59 | install | libQt5Widgets5 | 5.15.1-1.1
    2020-09-15 13:16:59 | install | libqt5-qtstyleplugins-platformtheme-gtk2 | 5.0.0+git20170311-8.4
    2020-09-15 13:16:59 | install | libQtQuick5 | 5.15.1-1.1
    2020-09-15 13:16:59 | install | libQt5Svg5 | 5.15.1-1.1
    2020-09-15 13:16:59 | install | libQt5PrintSupport5 | 5.15.1-1.1
    2020-09-15 13:17:00 | install | libqt5-qtxmlpatterns-imports | 5.15.1-1.1
    2020-09-15 13:17:00 | install | libQt5WebChannel5 | 5.15.1-1.1
    2020-09-15 13:17:01 | install | libqt5-qtwebengine | 5.15.1-1.1
    2020-09-15 13:17:01 | install | libQt5WebChannel5-imports | 5.15.1-1.1
    2020-09-15 13:17:03 | install | discord | 0.0.12-15.1
    Is there an easy way to determine which package update is causing the problem?

    Thanks,
    Gene

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    29,806
    Blog Entries
    15

    Default Re: New journal errors after 2020-09-15 update.

    Hi
    A know issue, edit the /usr/lib/sysctl.d/50-default.conf file and remove the quotes...

    https://forums.opensuse.org/showthre...rnel-Variables

    https://bugzilla.opensuse.org/show_bug.cgi?id=1174504
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3

    Default Re: New journal errors after 2020-09-15 update.

    That fixed most of the errors, but not the first two:

    Code:
    > sudo journalctl -b -p err | grep -v 'AER:'
    -- Logs begin at Mon 2020-08-24 10:14:44 PDT, end at Wed 2020-09-16 16:19:10 PDT. --
    Sep 16 16:13:04 Mobile-PC kernel: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
    Sep 16 16:13:04 Mobile-PC systemd[1]: Failed to start Apply Kernel Variables.
    Sep 16 16:13:04 Mobile-PC systemd-sysctl[222]: Couldn't write '"0 2147483647"' to 'net/ipv4/ping_group_range': Invalid argument
    Sep 16 16:13:16 Mobile-PC lightdm[1534]: gkr-pam: unable to locate daemon control file
    Sep 16 16:13:17 Mobile-PC bluetoothd[1048]: Failed to set mode: Blocked through rfkill (0x12)
    The first two error messages are still showing up at every boot, but the later ones did stop. That quoted string must appear in another file, but I haven't found it yet.

    Gene

  4. #4
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    29,806
    Blog Entries
    15

    Default Re: New journal errors after 2020-09-15 update.

    Quote Originally Posted by Gene_S View Post
    That fixed most of the errors, but not the first two:

    Code:
    > sudo journalctl -b -p err | grep -v 'AER:'
    -- Logs begin at Mon 2020-08-24 10:14:44 PDT, end at Wed 2020-09-16 16:19:10 PDT. --
    Sep 16 16:13:04 Mobile-PC kernel: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
    Sep 16 16:13:04 Mobile-PC systemd[1]: Failed to start Apply Kernel Variables.
    Sep 16 16:13:04 Mobile-PC systemd-sysctl[222]: Couldn't write '"0 2147483647"' to 'net/ipv4/ping_group_range': Invalid argument
    Sep 16 16:13:16 Mobile-PC lightdm[1534]: gkr-pam: unable to locate daemon control file
    Sep 16 16:13:17 Mobile-PC bluetoothd[1048]: Failed to set mode: Blocked through rfkill (0x12)
    The first two error messages are still showing up at every boot, but the later ones did stop. That quoted string must appear in another file, but I haven't found it yet.

    Gene
    Hi
    That is the exact error... the line should be edited to remove the quotes;

    Code:
    before;
    net.ipv4.ping_group_range = "0 2147483647"
    after;
    net.ipv4.ping_group_range = 0 2147483647
    then;
    systemctl restart systemd-sysctl.service
    systemctl status systemd-sysctl.service
    Check down in /etc/sysctl.d directory or /etc/sysctl.conf for something containing the entry then.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  5. #5

    Default Re: New journal errors after 2020-09-15 update.

    I edited that file and checked the other two locations you suggested:

    Code:
    > grep 2147483647 /usr/lib/sysctl.d/* /etc/sysctl.d/* /etc/sysctl.conf
    /usr/lib/sysctl.d/50-default.conf:net.ipv4.ping_group_range = 0 2147483647
    The service is running:

    Code:
    > 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)
        Drop-In: /usr/lib/systemd/system/systemd-sysctl.service.d
                 └─50-kernel-uname_r.conf
         Active: active (exited) since Wed 2020-09-16 17:04:58 PDT; 11min ago
           Docs: man:systemd-sysctl.service(8)
                 man:sysctl.d(5)
        Process: 2859 ExecStartPre=/usr/lib/systemd/systemd-sysctl /boot/sysctl.conf-5.8.7-1-default (code=exited, status=0/SUCCESS)
        Process: 2860 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=0/SUCCESS)
       Main PID: 2860 (code=exited, status=0/SUCCESS)
    
    Sep 16 17:04:58 Mobile-PC systemd[1]: Starting Apply Kernel Variables...
    Sep 16 17:04:58 Mobile-PC systemd[1]: Finished Apply Kernel Variables.
    But the first two errors still show up in the journal:

    Code:
    Sep 16 16:47:13 Mobile-PC systemd[1]: Failed to start Apply Kernel Variables.
    Sep 16 16:47:13 Mobile-PC systemd-sysctl[216]: Couldn't write '"0 2147483647"' to 'net/ipv4/ping_group_range': Invalid argument
    Strange!

    Gene

  6. #6
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    29,806
    Blog Entries
    15

    Default Re: New journal errors after 2020-09-15 update.

    Quote Originally Posted by Gene_S View Post
    I edited that file and checked the other two locations you suggested:

    Code:
    > grep 2147483647 /usr/lib/sysctl.d/* /etc/sysctl.d/* /etc/sysctl.conf
    /usr/lib/sysctl.d/50-default.conf:net.ipv4.ping_group_range = 0 2147483647
    The service is running:

    Code:
    > 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)
        Drop-In: /usr/lib/systemd/system/systemd-sysctl.service.d
                 └─50-kernel-uname_r.conf
         Active: active (exited) since Wed 2020-09-16 17:04:58 PDT; 11min ago
           Docs: man:systemd-sysctl.service(8)
                 man:sysctl.d(5)
        Process: 2859 ExecStartPre=/usr/lib/systemd/systemd-sysctl /boot/sysctl.conf-5.8.7-1-default (code=exited, status=0/SUCCESS)
        Process: 2860 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=0/SUCCESS)
       Main PID: 2860 (code=exited, status=0/SUCCESS)
    
    Sep 16 17:04:58 Mobile-PC systemd[1]: Starting Apply Kernel Variables...
    Sep 16 17:04:58 Mobile-PC systemd[1]: Finished Apply Kernel Variables.
    But the first two errors still show up in the journal:

    Code:
    Sep 16 16:47:13 Mobile-PC systemd[1]: Failed to start Apply Kernel Variables.
    Sep 16 16:47:13 Mobile-PC systemd-sysctl[216]: Couldn't write '"0 2147483647"' to 'net/ipv4/ping_group_range': Invalid argument
    Strange!

    Gene
    Hi
    Likely a leftover, if you can reboot and check the timestamp....
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #7
    Join Date
    Sep 2014
    Location
    Germany
    Posts
    554

    Default Re: New journal errors after 2020-09-15 update.

    Quote Originally Posted by Gene_S View Post
    ... But the first two errors still show up in the journal:

    Code:
    Sep 16 16:47:13 Mobile-PC systemd[1]: Failed to start Apply Kernel Variables.
    Sep 16 16:47:13 Mobile-PC systemd-sysctl[216]: Couldn't write '"0 2147483647"' to 'net/ipv4/ping_group_range': Invalid argument
    Did you rebuild your initrd?

    Try (as root)
    Code:
    # dracut -f
    Regards

    susejunky

  8. #8

    Default Re: New journal errors after 2020-09-15 update.

    Quote Originally Posted by susejunky View Post
    Did you rebuild your initrd?

    Try (as root)
    Code:
    # dracut -f
    Regards

    susejunky
    That was it, thanks! I noticed it was happening in the first stage of boot, I should have thought of that myself.

    Gene

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •