Kernel-6.8.5 stops at splash screen

Ask Fedora
, ,
1

I am using fedora 38 workstation on an x86_64 machine (intel core i7-8700, ASUS TUF H370-Pro gaming Wifi). After upgrading to kernel-6.8.5, my machine boots but stops at splash screen (plymouth ?) and can’t get to the login screen. Virtual terminal seems not to be available. Today upgraded to kernel-6.8.6-100.fc38 but this problem persists. I found a suspicious entry in the journal log.
4月 18 13:55:46 mocha.home kernel: BUG: scheduling while atomic: kworker/4:3/614/0x00000002
(sorry for the japanese character but the date reads April the 18th)
followed by (sorry again, I am reading with journalctl -r)
4月 18 13:55:46 mocha.home kernel: e1000_watchdog_task+0xe7/0xab0 [e1000e]
4月 18 13:55:46 mocha.home kernel: e1000e_update_stats+0x513/0x730 [e1000e]
4月 18 13:55:46 mocha.home kernel: e1000e_read_phy_reg_mdic+0x87/0x280 [e1000e]
4月 18 13:55:46 mocha.home kernel: usleep_range_state+0x64/0x90
4月 18 13:55:46 mocha.home kernel: ? __pfx_hrtimer_wakeup+0x10/0x10
4月 18 13:55:46 mocha.home kernel: schedule_hrtimeout_range_clock+0xbe/0x140
4月 18 13:55:46 mocha.home kernel: schedule+0x32/0xd0
4月 18 13:55:46 mocha.home kernel: ? ttwu_do_activate+0x64/0x200
4月 18 13:55:46 mocha.home kernel: __schedule+0x10fa/0x1530
4月 18 13:55:46 mocha.home kernel: __schedule_bug+0x56/0x70
4月 18 13:55:46 mocha.home kernel: dump_stack_lvl+0x64/0x80
4月 18 13:55:46 mocha.home kernel:
4月 18 13:55:46 mocha.home kernel: Call Trace:
4月 18 13:55:46 mocha.home kernel: Workqueue: events e1000_watchdog_task [e1000e]

I have two questions as follows:

  1. I want kernel-6.8.4, the only working kernel on my system, not erased on next dnf uptrade. Is manual “dnf remove kernel-6.8.5” enough or whatelse should I do ?
  2. Can I expect the problem cured in the next few kernel updates ?
1 Like
2

Hello @sigsegv ,
Welcome to :fedora: !
First, you could enter the Grub menu and select your previous kernel from there. Press space key at POST to get the (hidden) grub menu, then select the previous kernel, it should be there after the upgrade.

3

Thank you for the reply.

First, you could enter the Grub menu and select your previous kernel from there.

Yes, of course. I’m running my box with kernel-6.8.4 with this method. Actually, I held shift key instead of space key, though.
My question was as follows: there are 3 kernels (and related packages) installed in my box and on dnf upgrade (kernel), usually the oldest one is removed automatically. (Because /etc/dnf/dnf.conf contains “installonly_limit=3” ?) Actually, I have 6.8.4, 6.8.5 and 6.8.6 instlaled on my box. If kernel-6.8.4 is removed on the next kernel upgrade, I will lose only working kernel and my box will be unusable. I want to prevent automatical removal of kernel-6.8.4 set on next upgrade.
Any suggestion will be welcomed.

4

Grubby should be the tool for the job … maybe the --set-default-index=entry-index option (remember index starts at 0). There are also drop-ins in place in /etc/grub.d I believe, that you can use to adjust the number of entries. Sorry I can’t be of more help, I’ve been booting using systemd-boot for awhile.

5

Basically piggybacking off of @jakfrost here :

sudo grubby --info=ALL | grep kernel

then

sudo grubby --set-default /boot/vmlinuz-<version>

reboot

@jakfrost At this point I have a zettlekasten of commands after recently coalescing some previous notes on all sorts of topics :party:

1 Like
6

Read that as “The oldest kernel not in use is removed automatically” and you should understand.
The system never removes a kernel that is currently used for booting by default.

The suggestions above allow you to set the default kernel for booting, which when combined with the system management in never removing the running kernel should keep you safe.

However, the real issue is to find out why it fails to properly boot.
Please post (using the </> button ) the output of inxi -Fzxx so we can see the hardware installed.

What are you using as a GPU?

1 Like
7

Thank you guys for your replies.

Grubby should be the tool for the job.

sudo grubby --set-default /boot/vmlinuz-

I understand that these command will specify the default kernel on boot (grub selection). Do you suggest that dnf respects grub entry of default kernel ?

By the way, I found these description in man dnf.conf (5).

installonly_limit
integer

         Number of installonly packages allowed to be  installed  concur‐
         rently.  Defaults  to 3. The minimal number of installonly pack‐
         ages is 2. Value 0 means unlimited number of  installonly  pack‐
         ages.  Value  1  is  explicitly not allowed since it complicates
         kernel upgrades due to protection of the running kernel from re‐
         moval.

This description suggests if installonly_limit=1 is allowed, dnf tries to remove the running kernel even if it is the default boot entry.
Also, maybe I would better temporally specify intallonly_limit=0 to completely inhibit automatical removal on dnf upgrade, and manually remove redundant kernels when necessary.

Thank you all for your suggestions. They led me to the manpages of grubby and dnf.conf.

My final hope is to have bug fixed latest kenrel, as dnf check-update says that 6.8.4 has a security bug.

8

Thank you Jeff ! I am happy to know that dnf will not remove the running kernel.

Please post (using the </> button ) the output of inxi -Fzxx so we can see the hardware installed.

Sorry to say that I do not know how to use the “</>” button. I installed inxi package and here are hardware information.

Machine:
  Type: Desktop Mobo: ASUSTeK model: TUF H370-PRO GAMING (WI-FI) v: Rev 1.xx
    serial: <filter> part-nu: ASUS_MB_CNL UEFI: American Megatrends v: 1102
    date: 11/05/2018
CPU:
  Info: 6-core model: Intel Core i7-8700 bits: 64 type: MCP smt: disabled
    arch: Coffee Lake rev: A cache: L1: 384 KiB L2: 1.5 MiB L3: 12 MiB
  Speed (MHz): avg: 800 min/max: 800/4600 cores: 1: 800 2: 800 3: 800 4: 800
    5: 800 6: 800 bogomips: 38399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-9.5 ports: active: HDMI-A-2
    empty: DP-1,DP-2,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:3e92
  Display: server: X.Org v: 22.1.9 with: Xwayland v: 22.1.9
    compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
....
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a348
  API: ALSA v: k6.8.4-100.fc38.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.3 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
  Device-1: Intel Cannon Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:a370
  IF: wlo1 state: up mac: <filter>
  Device-2: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc
  IF: eno1 state: up speed: 10 Mbps duplex: half mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
...
Info:
  Memory: total: 16 GiB available: 15.46 GiB used: 3.42 GiB (22.1%)
    igpu: 64 MiB
  Processes: 312 Power: uptime: 11h 9m wakeups: 0 Init: systemd v: 253
    target: graphical (5) default: graphical

I removed output about Bluetooth and local storage, which will be posted on request.

What are you using as a GPU?

As you can see above, I am using core i7 internal graphics (UHD 630) and no additional graphic cards are installed.

Hope these information helps finding the cause.

9

On the toolbar of the screen where you write your post is that button. (just to the right of the blockquote button "you apparently used)
Highlight the text being posted then click that button. It wraps the text with a
``` on the line preceding the text and the line following the text to retain the on-screen formatting. You can also manually put those triple back quotes before and after the text as I will indicate by editing your post above.

You appear to have trimmed some of the data from the inxi output though it may be that enough is remaining to work with.
The System information at the beginning tells us the Kernel, distro version, and Desktop info that is often needed. The Monitor info may also be important as well as the API under the graphics section.

Pllease post the output of both cat /proc/cmdline and cat /etc/kernel/cmdline

Additionally, I would suggest that you attempt a boot with the latest kernel that is failing (6.8.6) then after rebooting to the working kernel provide the output of journalctl -b -1 so we can see what may have been recorded there.

10

The System information at the beginning tells us the Kernel, distro version, and Desktop info that is often needed. The Monitor info may also be important as well as the API under the graphics section.

Here they are

System:
  Kernel: 6.8.4-100.fc38.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.39-16.fc38
  Console: pty pts/3 wm: gnome-shell DM: GDM Distro: Fedora Linux 38
    (Workstation Edition)

  Monitor-1: HDMI-A-2 mapped: XWAYLAND0 model: Idek Iiyama PL2280H
    res: 1920x1080 dpi: 102 diag: 547mm (21.5")
  API: OpenGL v: 4.6 vendor: intel mesa v: 23.1.9 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
    device-ID: 8086:3e92
  API: EGL Message: EGL data requires eglinfo. Check --recommends.

and

[takemura@mocha ~]$ cat /proc/cmdline 
BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.8.4-100.fc38.x86_64 root=/dev/mapper/fedora_localhost--live-root ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet

I do not have a file “/etc/kernel/cmdline”.

11

Tried to post output of journalctl, but it is too large for the system. The last part seems to be interesting to me. Tell me if you want other part.

4月 18 13:55:46 mocha.home kernel: Lockdown: systemd-logind: hibernation is res
tricted; see man kernel_lockdown.7
 4月 18 13:55:46 mocha.home systemd[1]: Started upower.service - Daemon for powe
r management.
 4月 18 13:55:46 mocha.home audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=upower comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 4月 18 13:55:46 mocha.home kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Up 10 
Mbps Half Duplex, Flow Control: Rx/Tx
 4月 18 13:55:46 mocha.home kernel: BUG: scheduling while atomic: kworker/4:3/61
4/0x00000002
 4月 18 13:55:46 mocha.home kernel: Modules linked in: xt_CHECKSUM xt_MASQUERADE
 xt_conntrack ipt_REJECT nf_nat_tftp nft_masq bridge stp llc nf_conntrack_netbio
s_ns nf_conntrack_broadcast nf_conntrack_tftp nft_fib_inet nft_fib_ipv4 nft_fib_
ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nf_log_sys
log nft_log nft_ct nft_chain_nat nf_tables ebtable_nat ebtable_broute ip6table_n
at ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrac
k nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security sunr
pc ip_set nfnetlink ebtable_filter ebtables ip6table_filter iptable_filter bnep 
binfmt_misc vfat fat snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_in
tel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_
sof_xtensa_dsp snd_sof iwlmvm snd_sof_utils snd_hda_codec_hdmi soundwire_generic
_allocation soundwire_bus snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_
sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_soc_acpi_intel_match snd_soc_a
cpi mac80211
 4月 18 13:55:46 mocha.home kernel:  snd_hda_codec_generic snd_soc_core snd_comp
ress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg intel_rapl_msr sn
d_intel_sdw_acpi intel_rapl_common intel_uncore_frequency libarc4 snd_hda_codec 
intel_uncore_frequency_common iTCO_wdt snd_hda_core intel_pmc_bxt ee1004 mei_hdc
p btusb snd_hwdep spi_nor x86_pkg_temp_thermal iTCO_vendor_support mei_pxp mtd b
trtl snd_seq snd_seq_device intel_powerclamp snd_pcm btintel iwlwifi coretemp sn
d_timer btbcm rapl intel_cstate btmtk snd i2c_i801 cfg80211 intel_uncore bluetoo
th wmi_bmof pcspkr mei_me i2c_smbus soundcore spi_intel_pci intel_pmc_core mei s
pi_intel rfkill intel_vsec joydev pmt_telemetry acpi_pad pmt_class loop zram i91
5 crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic e10
00e ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 i2c_algo_bit drm_bu
ddy ttm drm_display_helper video cec wmi serio_raw scsi_dh_rdac scsi_dh_emc scsi
_dh_alua ip6_tables ip_tables dm_multipath fuse
 4月 18 13:55:46 mocha.home kernel: CPU: 4 PID: 614 Comm: kworker/4:3 Not tainte
d 6.8.6-100.fc38.x86_64 #1
 4月 18 13:55:46 mocha.home kernel: Hardware name: System manufacturer System Pr
oduct Name/TUF H370-PRO GAMING (WI-FI), BIOS 1102 11/05/2018
 4月 18 13:55:46 mocha.home kernel: Workqueue: events e1000_watchdog_task [e1000
e]
 4月 18 13:55:46 mocha.home kernel: Call Trace:
 4月 18 13:55:46 mocha.home kernel:  <TASK>
 4月 18 13:55:46 mocha.home kernel:  dump_stack_lvl+0x64/0x80
 4月 18 13:55:46 mocha.home kernel:  __schedule_bug+0x56/0x70
 4月 18 13:55:46 mocha.home kernel:  __schedule+0x10fa/0x1530
 4月 18 13:55:46 mocha.home kernel:  ? ttwu_do_activate+0x64/0x200
 4月 18 13:55:46 mocha.home kernel:  schedule+0x32/0xd0
 4月 18 13:55:46 mocha.home kernel:  schedule_hrtimeout_range_clock+0xbe/0x140
 4月 18 13:55:46 mocha.home kernel:  ? __pfx_hrtimer_wakeup+0x10/0x10
 4月 18 13:55:46 mocha.home kernel:  usleep_range_state+0x64/0x90
 4月 18 13:55:46 mocha.home kernel:  e1000e_read_phy_reg_mdic+0x87/0x280 [e1000e
]
 4月 18 13:55:46 mocha.home kernel:  e1000e_update_stats+0x513/0x730 [e1000e]
 4月 18 13:55:46 mocha.home kernel:  e1000_watchdog_task+0xe7/0xab0 [e1000e]
 4月 18 13:55:46 mocha.home kernel:  process_one_work+0x171/0x340
 4月 18 13:55:46 mocha.home kernel:  worker_thread+0x27b/0x3a0
 4月 18 13:55:46 mocha.home kernel:  ? __pfx_worker_thread+0x10/0x10
 4月 18 13:55:46 mocha.home kernel:  kthread+0xe5/0x120
 4月 18 13:55:46 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
 4月 18 13:55:46 mocha.home kernel:  ret_from_fork+0x31/0x50
 4月 18 13:55:46 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
 4月 18 13:55:46 mocha.home kernel:  ret_from_fork_asm+0x1b/0x30
 4月 18 13:55:46 mocha.home kernel:  </TASK>
 4月 18 13:55:46 mocha.home systemd[1221]: Started pipewire.service - PipeWire M
ultimedia Service.
 4月 18 13:55:46 mocha.home systemd[1221]: Started wireplumber.service - Multime
dia Service Session Manager.
 4月 18 13:55:46 mocha.home systemd[1]: Starting geoclue.service - Location Look
up Service...
 4月 18 13:55:46 mocha.home systemd[1221]: Started pipewire-pulse.service - Pipe
Wire PulseAudio.
 4月 18 13:55:46 mocha.home polkitd[1037]: Registered Authentication Agent for u
nix-session:c1 (system bus name :1.35 [/usr/bin/gnome-shell], object path /org/f
reedesktop/PolicyKit1/AuthenticationAgent, locale ja_JP.UTF-8)
 4月 18 13:55:46 mocha.home /usr/libexec/gdm-wayland-session[1303]: dbus-daemon[
1303]: [session uid=42 pid=1303] Activating service name='org.gnome.Shell.Notifi
cations' requested by ':1.5' (uid=42 pid=1326 comm="/usr/bin/gnome-shell" label=
"system_u:system_r:xdm_t:s0-s0:c0.c1023")
 4月 18 13:55:46 mocha.home systemd[1]: Starting packagekit.service - PackageKit
 Daemon...
 4月 18 13:55:46 mocha.home rtkit-daemon[950]: Successfully made thread 1716 of 
process 1716 (/usr/bin/pipewire) owned by '42' high priority at nice level -11.
 4月 18 13:55:46 mocha.home PackageKit[1734]: daemon start
 4月 18 13:55:46 mocha.home rtkit-daemon[950]: Successfully made thread 1732 of 
process 1716 (/usr/bin/pipewire) owned by '42' RT at priority 20.
4月 18 13:55:46 mocha.home rtkit-daemon[950]: Successfully made thread 1719 of 
process 1719 (/usr/bin/wireplumber) owned by '42' high priority at nice level -1
1.
 4月 18 13:55:46 mocha.home /usr/libexec/gdm-wayland-session[1303]: dbus-daemon[
1303]: [session uid=42 pid=1303] Successfully activated service 'org.gnome.Shell
.Notifications'
 4月 18 13:55:46 mocha.home rtkit-daemon[950]: Successfully made thread 1727 of 
process 1719 (/usr/bin/wireplumber) owned by '42' RT at priority 20.
 4月 18 13:55:46 mocha.home gnome-shell[1326]: Extension apps-menu@gnome-shell-e
xtensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensi
ons/apps-menu@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/
extensions/apps-menu@gnome-shell-extensions.gcampax.github.com will not be loade
d
 4月 18 13:55:46 mocha.home gnome-shell[1326]: Extension background-logo@fedorah
osted.org already installed in /usr/share/gnome-shell/extensions/background-logo
@fedorahosted.org. /usr/share/gnome-shell/extensions/background-logo@fedorahoste
d.org will not be loaded
 4月 18 13:55:46 mocha.home gnome-shell[1326]: Extension launch-new-instance@gno
me-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-she
ll/extensions/launch-new-instance@gnome-shell-extensions.gcampax.github.com. /us
r/share/gnome-shell/extensions/launch-new-instance@gnome-shell-extensions.gcampa
x.github.com will not be loaded
 4月 18 13:55:46 mocha.home gnome-shell[1326]: Extension places-menu@gnome-shell
extensions.gcampax.github.com already installed in /usr/share/gnome-shell/exten
sions/places-menu@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-sh
ell/extensions/places-menu@gnome-shell-extensions.gcampax.github.com will not be
 loaded
 4月 18 13:55:46 mocha.home gnome-shell[1326]: Extension window-list@gnome-shell
-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/exten
sions/window-list@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-sh
ell/extensions/window-list@gnome-shell-extensions.gcampax.github.com will not be
 loaded
 4月 18 13:55:46 mocha.home gnome-shell[1326]: Extension user-theme@gnome-shell-
extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extens
ions/user-theme@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shel
l/extensions/user-theme@gnome-shell-extensions.gcampax.github.com will not be lo
aded
 4月 18 13:55:46 mocha.home /usr/libexec/gdm-wayland-session[1665]: dbus-daemon[
1665]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (ui
d=42 pid=1326 comm="/usr/bin/gnome-shell" label="system_u:system_r:xdm_t:s0-s0:c
0.c1023")
 4月 18 13:55:46 mocha.home rtkit-daemon[950]: Successfully made thread 1721 of 
process 1721 (/usr/bin/pipewire) owned by '42' high priority at nice level -11.
 4月 18 13:55:46 mocha.home /usr/libexec/gdm-wayland-session[1665]: dbus-daemon[
1665]: Successfully activated service 'org.a11y.atspi.Registry'
 4月 18 13:55:46 mocha.home /usr/libexec/gdm-wayland-session[1764]: SpiRegistry 
 4月 18 13:55:46 mocha.home gnome-shell[1326]: Failed to open sliced image: 操作
がキャンセルされました
 4月 18 13:55:46 mocha.home wireplumber[1719]: SPA handle 'api.libcamera.enum.ma
nager' could not be loaded; is it installed?
 4月 18 13:55:46 mocha.home wireplumber[1719]: PipeWire's libcamera SPA missing 
or broken. libcamera not supported.
 4月 18 13:55:46 mocha.home rtkit-daemon[950]: Successfully made thread 1762 of 
process 1721 (/usr/bin/pipewire) owned by '42' RT at priority 20.
 4月 18 13:55:46 mocha.home org.gnome.Shell.desktop[1326]: Window manager warnin
g: Failed to parse saved session file: ファイル“/var/lib/gdm/.config/mutter/sess
ions/10ae6d084663dc8361171341614517182000000013040000.ms”を開くのに失敗しました:
 そのようなファイルやディレクトリはありません
 4月 18 13:55:47 mocha.home kernel: rfkill: input handler disabled
 4月 18 13:55:47 mocha.home /usr/libexec/gdm-wayland-session[1303]: dbus-daemon[
1303]: [session uid=42 pid=1303] Activating service name='org.freedesktop.system
d1' requested by ':1.13' (uid=42 pid=1778 comm="/usr/libexec/gsd-sharing" label=
"system_u:system_r:xdm_t:s0-s0:c0.c1023")
 4月 18 13:55:47 mocha.home /usr/libexec/gdm-wayland-session[1303]: dbus-daemon[
1303]: [session uid=42 pid=1303] Activated service 'org.freedesktop.systemd1' fa
iled: Process org.freedesktop.systemd1 exited with status 1
 4月 18 13:55:47 mocha.home gsd-sharing[1778]: Failed to StopUnit service: GDBus
.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.sys
:temd1 exited with status 1
 4月 18 13:55:47 mocha.home gsd-sharing[1778]: Failed to StopUnit service: GDBus
.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.sys
temd1 exited with status 1
 4月 18 13:55:47 mocha.home gnome-shell[1326]: Error looking up permission: GDBu
s.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
 4月 18 13:55:47 mocha.home /usr/libexec/gdm-wayland-session[1303]: dbus-daemon[
1303]: [session uid=42 pid=1303] Activating service name='org.freedesktop.portal
.IBus' requested by ':1.27' (uid=42 pid=1813 comm="ibus-daemon --panel disable" 
label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
 4月 18 13:55:47 mocha.home /usr/libexec/gdm-wayland-session[1303]: dbus-daemon[
1303]: [session uid=42 pid=1303] Successfully activated service 'org.freedesktop
.portal.IBus'
 4月 18 13:55:47 mocha.home audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pcscd comm="systemd" e
xe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 4月 18 13:55:47 mocha.home systemd[1]: Started pcscd.service - PC/SC Smart Card
 Daemon.
 4月 18 13:55:47 mocha.home kernel: Bluetooth: RFCOMM TTY layer initialized
 4月 18 13:55:47 mocha.home kernel: Bluetooth: RFCOMM socket layer initialized
 4月 18 13:55:47 mocha.home kernel: Bluetooth: RFCOMM ver 1.11
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/ldac
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSink/aptx_hd
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/aptx_hd
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSink/aptx
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/aptx
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSink/aac
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/aac
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSink/sbc
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/sbc
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSink/sbc_xq
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/sbc_xq
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/aptx_ll_1
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/aptx_ll_0
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/faststream
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/faststream_duplex
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSink/opus_05
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/opus_05
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSink/opus_05_duplex
 4月 18 13:55:47 mocha.home bluetoothd[930]: Endpoint registered: sender=:1.44 p
ath=/MediaEndpoint/A2DPSource/opus_05_duplex
 4月 18 13:55:47 mocha.home cupsd[1089]: REQUEST localhost - - "POST / HTTP/1.1"
 200 359 Create-Printer-Subscriptions successful-ok
 4月 18 13:55:47 mocha.home NetworkManager[1068]: <info>  [1713416147.5574] agen
t-manager: agent[773aff371e5a397c,:1.35/org.gnome.Shell.NetworkAgent/42]: agent 
registered
 4月 18 13:55:48 mocha.home abrt-dump-journal-oops[1034]: abrt-dump-journal-oops
: Found oopses: 1
 4月 18 13:55:48 mocha.home abrt-dump-journal-oops[1034]: abrt-dump-journal-oops
: Creating problem directories
 4月 18 13:55:48 mocha.home systemd[1]: systemd-rfkill.service: Deactivated succ
essfully.
 4月 18 13:55:48 mocha.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 s
es=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-rfkill comm="sy
stemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 4月 18 13:55:48 mocha.home abrt-server[2026]: Can't find a meaningful backtrace
 for hashing in '.'
 4月 18 13:55:48 mocha.home abrt-server[2026]: Deleting non-reportable oops '.' 
because DropNotReportableOopses is set to 'yes'
 4月 18 13:55:48 mocha.home abrt-server[2026]: 'post-create' on '/var/spool/abrt
/oops-2024-04-18-13:55:48-1034-0' exited with 1
 4月 18 13:55:48 mocha.home abrt-server[2026]: Deleting problem directory '/var/
spool/abrt/oops-2024-04-18-13:55:48-1034-0'
 4月 18 13:55:48 mocha.home abrt-server[2026]: Lock file '.lock' was locked by p
rocess 2036, but it crashed?
 4月 18 13:55:49 mocha.home abrt-dump-journal-oops[1034]: Reported 1 kernel oops
es to Abrt
 4月 18 13:55:55 mocha.home systemd[1]: NetworkManager-dispatcher.service: Deact
ivated successfully.
 4月 18 13:55:55 mocha.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 s
es=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatch
er comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? re
s=success'
 4月 18 13:56:13 mocha.home kernel: watchdog: BUG: soft lockup - CPU#4 stuck for
 26s! [kworker/4:1:121]
 4月 18 13:56:13 mocha.home kernel: Modules linked in: rfcomm snd_seq_dummy snd_
hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_nat_tftp nft_masq b
ridge stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_tftp n
ft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_
reject_ipv6 nft_reject nf_log_syslog nft_log nft_ct nft_chain_nat nf_tables ebta
ble_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_securi
ty iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle 
iptable_raw iptable_security sunrpc ip_set nfnetlink ebtable_filter ebtables ip6
table_filter iptable_filter bnep binfmt_misc vfat fat snd_sof_pci_intel_cnl snd_
sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence s
nd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof iwlmvm snd_sof_utils snd
_hda_codec_hdmi soundwire_generic_allocation soundwire_bus snd_soc_skl snd_soc_h
dac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek
 4月 18 13:56:13 mocha.home kernel:  snd_soc_acpi_intel_match snd_soc_acpi mac80
211 snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine s
nd_hda_intel snd_intel_dspcfg intel_rapl_msr snd_intel_sdw_acpi intel_rapl_commo
n intel_uncore_frequency libarc4 snd_hda_codec intel_uncore_frequency_common iTC
O_wdt snd_hda_core intel_pmc_bxt ee1004 mei_hdcp btusb snd_hwdep spi_nor x86_pkg
_temp_thermal iTCO_vendor_support mei_pxp mtd btrtl snd_seq snd_seq_device intel
_powerclamp snd_pcm btintel iwlwifi coretemp snd_timer btbcm rapl intel_cstate b
tmtk snd i2c_i801 cfg80211 intel_uncore bluetooth wmi_bmof pcspkr mei_me i2c_smb
us soundcore spi_intel_pci intel_pmc_core mei spi_intel rfkill intel_vsec joydev
 pmt_telemetry acpi_pad pmt_class loop zram i915 crct10dif_pclmul crc32_pclmul c
rc32c_intel polyval_clmulni polyval_generic e1000e ghash_clmulni_intel sha512_ss
se3 sha256_ssse3 sha1_ssse3 i2c_algo_bit drm_buddy ttm drm_display_helper video 
cec wmi serio_raw scsi_dh_rdac scsi_dh_emc scsi_dh_alua ip6_tables ip_tables dm_
multipath fuse
 4月 18 13:56:13 mocha.home kernel: CPU: 4 PID: 121 Comm: kworker/4:1 Tainted: G
        W          6.8.6-100.fc38.x86_64 #1
 4月 18 13:56:13 mocha.home kernel: Hardware name: System manufacturer System Pr
oduct Name/TUF H370-PRO GAMING (WI-FI), BIOS 1102 11/05/2018
 4月 18 13:56:13 mocha.home kernel: Workqueue: events linkwatch_event
 4月 18 13:56:13 mocha.home kernel: RIP: 0010:native_queued_spin_lock_slowpath+0
x6e/0x2b0
 4月 18 13:56:13 mocha.home kernel: Code: 77 77 f0 0f ba 2b 08 0f 92 c2 8b 03 0f
 b6 d2 c1 e2 08 30 e4 09 d0 3d ff 00 00 00 77 53 85 c0 74 10 0f b6 03 84 c0 74 0
9 f3 90 <0f> b6 03 84 c0 75 f7 b8 01 00 00 00 66 89 03 5b 5d 41 5c 41 5d c3
 4月 18 13:56:13 mocha.home kernel: RSP: 0018:ffffc16dc04d7bc0 EFLAGS: 00000202
 4月 18 13:56:13 mocha.home kernel: RAX: 0000000000000001 RBX: ffff9ffdc293b428 
RCX: 0000000000000000
 4月 18 13:56:13 mocha.home kernel: RDX: 0000000000000000 RSI: 0000000000000001 
RDI: ffff9ffdc293b428
 4月 18 13:56:13 mocha.home kernel: RBP: ffff9ffdf7640134 R08: 0000000000000000 
R09: 0000000000000004
 4月 18 13:56:13 mocha.home kernel: R10: ffff9ffdf76401fc R11: 0000000000000010 
R12: ffff9ffdc293b428
 4月 18 13:56:13 mocha.home kernel: R13: ffff9ffdf7640000 R14: 0000000000000000 
R15: 0000000000000000
 4月 18 13:56:13 mocha.home kernel: FS:  0000000000000000(0000) GS:ffffa0011dd00
000(0000) knlGS:0000000000000000
 4月 18 13:56:13 mocha.home kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 00000000800
50033
 4月 18 13:56:13 mocha.home kernel: CR2: 00005573a2dbab48 CR3: 00000001ac422006 
CR4: 00000000003706f0
 4月 18 13:56:13 mocha.home kernel: DR0: 0000000000000000 DR1: 0000000000000000 
DR2: 0000000000000000
 4月 18 13:56:13 mocha.home kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 
DR7: 0000000000000400
 4月 18 13:56:13 mocha.home kernel: Call Trace:
 4月 18 13:56:13 mocha.home kernel:  <IRQ>
 4月 18 13:56:13 mocha.home kernel:  ? watchdog_timer_fn+0x1e6/0x270
 4月 18 13:56:13 mocha.home kernel:  ? __pfx_watchdog_timer_fn+0x10/0x10
4月 18 13:56:13 mocha.home kernel:  ? __hrtimer_run_queues+0x10f/0x2b0
 4月 18 13:56:13 mocha.home kernel:  ? hrtimer_interrupt+0xf8/0x230
 4月 18 13:56:13 mocha.home kernel:  ? __sysvec_apic_timer_interrupt+0x4d/0x140
 4月 18 13:56:13 mocha.home kernel:  ? sysvec_apic_timer_interrupt+0x6d/0x90
 4月 18 13:56:13 mocha.home kernel:  </IRQ>
 4月 18 13:56:13 mocha.home kernel:  <TASK>
 4月 18 13:56:13 mocha.home kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
 4月 18 13:56:13 mocha.home kernel:  ? native_queued_spin_lock_slowpath+0x6e/0x2
b0
 4月 18 13:56:13 mocha.home kernel:  _raw_spin_lock+0x29/0x30
 4月 18 13:56:13 mocha.home kernel:  e1000e_get_stats64+0x22/0x120 [e1000e]
 4月 18 13:56:13 mocha.home kernel:  dev_get_stats+0x5d/0x110
 4月 18 13:56:13 mocha.home kernel:  rtnl_fill_stats+0x3b/0x130
 4月 18 13:56:13 mocha.home kernel:  rtnl_fill_ifinfo+0x872/0x1580
 4月 18 13:56:13 mocha.home kernel:  ? __alloc_skb+0x8c/0x1a0
 4月 18 13:56:13 mocha.home kernel:  rtmsg_ifinfo_build_skb+0xae/0x120
 4月 18 13:56:13 mocha.home kernel:  rtmsg_ifinfo+0x3c/0x90
 4月 18 13:56:13 mocha.home kernel:  netdev_state_change+0x89/0x90
 4月 18 13:56:13 mocha.home kernel:  linkwatch_do_dev+0x4f/0x60
 4月 18 13:56:13 mocha.home kernel:  __linkwatch_run_queue+0xe1/0x220
 4月 18 13:56:13 mocha.home kernel:  linkwatch_event+0x31/0x40
 4月 18 13:56:13 mocha.home kernel:  process_one_work+0x171/0x340
 4月 18 13:56:13 mocha.home kernel:  worker_thread+0x27b/0x3a0
4月 18 13:56:13 mocha.home kernel:  ? __pfx_worker_thread+0x10/0x10
 4月 18 13:56:13 mocha.home kernel:  kthread+0xe5/0x120
 4月 18 13:56:13 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
 4月 18 13:56:13 mocha.home kernel:  ret_from_fork+0x31/0x50
 4月 18 13:56:13 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
 4月 18 13:56:13 mocha.home kernel:  ret_from_fork_asm+0x1b/0x30
 4月 18 13:56:13 mocha.home kernel:  </TASK>
 4月 18 13:56:15 mocha.home abrt-dump-journal-oops[1034]: abrt-dump-journal-oops
: Found oopses: 1
 4月 18 13:56:15 mocha.home abrt-dump-journal-oops[1034]: abrt-dump-journal-oops
: Creating problem directories
 4月 18 13:56:15 mocha.home abrt-server[2039]: Can't find a meaningful backtrace
 for hashing in '.'
 4月 18 13:56:15 mocha.home abrt-server[2039]: Deleting non-reportable oops '.' 
because DropNotReportableOopses is set to 'yes'
 4月 18 13:56:15 mocha.home abrt-server[2039]: 'post-create' on '/var/spool/abrt
/oops-2024-04-18-13:56:15-1034-0' exited with 1
 4月 18 13:56:15 mocha.home abrt-server[2039]: Deleting problem directory '/var/
spool/abrt/oops-2024-04-18-13:56:15-1034-0'
 4月 18 13:56:15 mocha.home abrt-server[2039]: Lock file '.lock' was locked by p
rocess 2049, but it crashed?
 4月 18 13:56:16 mocha.home abrt-dump-journal-oops[1034]: Reported 1 kernel oops
es to Abrt
4月 18 13:56:31 mocha.home systemd[1]: geoclue.service: start operation timed o
ut. Terminating.
 4月 18 13:56:32 mocha.home systemd[1]: packagekit.service: start operation time
d out. Terminating.
 4月 18 13:56:41 mocha.home kernel: watchdog: BUG: soft lockup - CPU#4 stuck for
 52s! [kworker/4:1:121]
 4月 18 13:56:41 mocha.home kernel: Modules linked in: rfcomm snd_seq_dummy snd_
hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_nat_tftp nft_masq b
ridge stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_tftp n
ft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_
reject_ipv6 nft_reject nf_log_syslog nft_log nft_ct nft_chain_nat nf_tables ebta
ble_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_securi
ty iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle 
iptable_raw iptable_security sunrpc ip_set nfnetlink ebtable_filter ebtables ip6
table_filter iptable_filter bnep binfmt_misc vfat fat snd_sof_pci_intel_cnl snd_
sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence s
nd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof iwlmvm snd_sof_utils snd
_hda_codec_hdmi soundwire_generic_allocation soundwire_bus snd_soc_skl snd_soc_h
dac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek
 4月 18 13:56:41 mocha.home kernel:  snd_soc_acpi_intel_match snd_soc_acpi mac80
211 snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine s
nd_hda_intel snd_intel_dspcfg intel_rapl_msr snd_intel_sdw_acpi intel_rapl_commo
n intel_uncore_frequency libarc4 snd_hda_codec intel_uncore_frequency_common iTC
:O_wdt snd_hda_core intel_pmc_bxt ee1004 mei_hdcp btusb snd_hwdep spi_nor x86_pkg
_temp_thermal iTCO_vendor_support mei_pxp mtd btrtl snd_seq snd_seq_device intel
_powerclamp snd_pcm btintel iwlwifi coretemp snd_timer btbcm rapl intel_cstate b
tmtk snd i2c_i801 cfg80211 intel_uncore bluetooth wmi_bmof pcspkr mei_me i2c_smb
us soundcore spi_intel_pci intel_pmc_core mei spi_intel rfkill intel_vsec joydev
 pmt_telemetry acpi_pad pmt_class loop zram i915 crct10dif_pclmul crc32_pclmul c
rc32c_intel polyval_clmulni polyval_generic e1000e ghash_clmulni_intel sha512_ss
se3 sha256_ssse3 sha1_ssse3 i2c_algo_bit drm_buddy ttm drm_display_helper video 
cec wmi serio_raw scsi_dh_rdac scsi_dh_emc scsi_dh_alua ip6_tables ip_tables dm_
multipath fuse
 4月 18 13:56:41 mocha.home kernel: CPU: 4 PID: 121 Comm: kworker/4:1 Tainted: G
        W    L     6.8.6-100.fc38.x86_64 #1
 4月 18 13:56:41 mocha.home kernel: Hardware name: System manufacturer System Pr
oduct Name/TUF H370-PRO GAMING (WI-FI), BIOS 1102 11/05/2018
 4月 18 13:56:41 mocha.home kernel: Workqueue: events linkwatch_event
 4月 18 13:56:41 mocha.home kernel: RIP: 0010:native_queued_spin_lock_slowpath+0
x6e/0x2b0
 4月 18 13:56:41 mocha.home kernel: Code: 77 77 f0 0f ba 2b 08 0f 92 c2 8b 03 0f
 b6 d2 c1 e2 08 30 e4 09 d0 3d ff 00 00 00 77 53 85 c0 74 10 0f b6 03 84 c0 74 0
9 f3 90 <0f> b6 03 84 c0 75 f7 b8 01 00 00 00 66 89 03 5b 5d 41 5c 41 5d c3
 4月 18 13:56:41 mocha.home kernel: RSP: 0018:ffffc16dc04d7bc0 EFLAGS: 00000202
 4月 18 13:56:41 mocha.home kernel: RAX: 0000000000000001 RBX: ffff9ffdc293b428 
RCX: 0000000000000000
RDI: ffff9ffdc293b428
 4月 18 13:56:41 mocha.home kernel: RBP: ffff9ffdf7640134 R08: 0000000000000000 
R09: 0000000000000004
 4月 18 13:56:41 mocha.home kernel: R10: ffff9ffdf76401fc R11: 0000000000000010 
R12: ffff9ffdc293b428
 4月 18 13:56:41 mocha.home kernel: R13: ffff9ffdf7640000 R14: 0000000000000000 
R15: 0000000000000000
 4月 18 13:56:41 mocha.home kernel: FS:  0000000000000000(0000) GS:ffffa0011dd00
000(0000) knlGS:0000000000000000
 4月 18 13:56:41 mocha.home kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 00000000800
50033
 4月 18 13:56:41 mocha.home kernel: CR2: 00005573a2dbab48 CR3: 00000001ac422006 
CR4: 00000000003706f0
 4月 18 13:56:41 mocha.home kernel: DR0: 0000000000000000 DR1: 0000000000000000 
DR2: 0000000000000000
 4月 18 13:56:41 mocha.home kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 
DR7: 0000000000000400
 4月 18 13:56:41 mocha.home kernel: Call Trace:
 4月 18 13:56:41 mocha.home kernel:  <IRQ>
 4月 18 13:56:41 mocha.home kernel:  ? watchdog_timer_fn+0x1e6/0x270
 4月 18 13:56:41 mocha.home kernel:  ? __pfx_watchdog_timer_fn+0x10/0x10
 4月 18 13:56:41 mocha.home kernel:  ? __hrtimer_run_queues+0x10f/0x2b0
4月 18 13:56:41 mocha.home kernel:  ? hrtimer_interrupt+0xf8/0x230
 4月 18 13:56:41 mocha.home kernel:  ? __sysvec_apic_timer_interrupt+0x4d/0x140
 4月 18 13:56:41 mocha.home kernel:  ? sysvec_apic_timer_interrupt+0x6d/0x90
 4月 18 13:56:41 mocha.home kernel:  </IRQ>
 4月 18 13:56:41 mocha.home kernel:  <TASK>
 4月 18 13:56:41 mocha.home kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
 4月 18 13:56:41 mocha.home kernel:  ? native_queued_spin_lock_slowpath+0x6e/0x2
b0
 4月 18 13:56:41 mocha.home kernel:  _raw_spin_lock+0x29/0x30
 4月 18 13:56:41 mocha.home kernel:  e1000e_get_stats64+0x22/0x120 [e1000e]
 4月 18 13:56:41 mocha.home kernel:  dev_get_stats+0x5d/0x110
 4月 18 13:56:41 mocha.home kernel:  rtnl_fill_stats+0x3b/0x130
 4月 18 13:56:41 mocha.home kernel:  rtnl_fill_ifinfo+0x872/0x1580
 4月 18 13:56:41 mocha.home kernel:  ? __alloc_skb+0x8c/0x1a0
 4月 18 13:56:41 mocha.home kernel:  rtmsg_ifinfo_build_skb+0xae/0x120
 4月 18 13:56:41 mocha.home kernel:  rtmsg_ifinfo+0x3c/0x90
 4月 18 13:56:41 mocha.home kernel:  netdev_state_change+0x89/0x90
 4月 18 13:56:41 mocha.home kernel:  linkwatch_do_dev+0x4f/0x60
 4月 18 13:56:41 mocha.home kernel:  __linkwatch_run_queue+0xe1/0x220
 4月 18 13:56:41 mocha.home kernel:  linkwatch_event+0x31/0x40
 4月 18 13:56:41 mocha.home kernel:  process_one_work+0x171/0x340
 4月 18 13:56:41 mocha.home kernel:  worker_thread+0x27b/0x3a0
 4月 18 13:56:41 mocha.home kernel:  ? __pfx_worker_thread+0x10/0x10
4月 18 13:56:41 mocha.home kernel:  kthread+0xe5/0x120
 4月 18 13:56:41 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
 4月 18 13:56:41 mocha.home kernel:  ret_from_fork+0x31/0x50
 4月 18 13:56:41 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
 4月 18 13:56:41 mocha.home kernel:  ret_from_fork_asm+0x1b/0x30
 4月 18 13:56:41 mocha.home kernel:  </TASK>
 4月 18 13:56:43 mocha.home abrt-dump-journal-oops[1034]: abrt-dump-journal-oops
: Found oopses: 1
 4月 18 13:56:43 mocha.home abrt-dump-journal-oops[1034]: abrt-dump-journal-oops
: Creating problem directories
 4月 18 13:56:43 mocha.home abrt-server[2051]: Can't find a meaningful backtrace
 for hashing in '.'
 4月 18 13:56:43 mocha.home abrt-server[2051]: Deleting non-reportable oops '.' 
because DropNotReportableOopses is set to 'yes'
 4月 18 13:56:43 mocha.home abrt-server[2051]: 'post-create' on '/var/spool/abrt
/oops-2024-04-18-13:56:43-1034-0' exited with 1
 4月 18 13:56:43 mocha.home abrt-server[2051]: Deleting problem directory '/var/
spool/abrt/oops-2024-04-18-13:56:43-1034-0'
 4月 18 13:56:43 mocha.home abrt-server[2051]: Lock file '.lock' was locked by p
rocess 2061, but it crashed?
 4月 18 13:56:44 mocha.home abrt-dump-journal-oops[1034]: Reported 1 kernel oops
es to Abrt
12 
ed with result 'exit-code'.
4月 18 13:56:44 mocha.home systemd[1]: Failed to start NetworkManager-wait-onli
ne.service - Network Manager Wait Online.
4月 18 13:56:44 mocha.home audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-wait-on
line comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? 
res=failed'
4月 18 13:56:44 mocha.home systemd[1]: Reached target network-online.target - N
etwork is Online.
4月 18 13:56:44 mocha.home systemd[1]: iscsi.service: Unit cannot be reloaded b
ecause it is inactive.
4月 18 13:56:44 mocha.home systemd[1]: Starting rpc-statd-notify.service - Noti
fy NFS peers of a restart...
4月 18 13:56:44 mocha.home systemd[1]: Starting rwhod.service - Remote Machine 
Logged In User Lister...
4月 18 13:56:44 mocha.home systemd[1]: Started rwhod.service - Remote Machine L
ogged In User Lister.
4月 18 13:56:44 mocha.home audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rwhod comm="systemd" e
xe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
4月 18 13:56:44 mocha.home sm-notify[2062]: Version 2.6.4 starting
4月 18 13:56:44 mocha.home systemd[1]: Started rpc-statd-notify.service - Notif
y NFS peers of a restart.
4月 18 13:56:44 mocha.home audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rpc-statd-notify comm=
"systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succes
s'
4月 18 13:56:46 mocha.home kernel: rcu: INFO: rcu_preempt self-detected stall o
n CPU
4月 18 13:56:46 mocha.home kernel: rcu:         4-....: (60000 ticks this GP) i
dle=4c8c/1/0x4000000000000000 softirq=8433/8436 fqs=25222
4月 18 13:56:46 mocha.home kernel: rcu:         (t=60000 jiffies g=5657 q=53815
ncpus=6)
4月 18 13:56:46 mocha.home kernel: CPU: 4 PID: 121 Comm: kworker/4:1 Tainted: G
       W    L     6.8.6-100.fc38.x86_64 #1
4月 18 13:56:46 mocha.home kernel: Hardware name: System manufacturer System Pr
oduct Name/TUF H370-PRO GAMING (WI-FI), BIOS 1102 11/05/2018
4月 18 13:56:46 mocha.home kernel: Workqueue: events linkwatch_event
4月 18 13:56:46 mocha.home kernel: RIP: 0010:native_queued_spin_lock_slowpath+0
x6e/0x2b0
4月 18 13:56:46 mocha.home kernel: Code: 77 77 f0 0f ba 2b 08 0f 92 c2 8b 03 0f
b6 d2 c1 e2 08 30 e4 09 d0 3d ff 00 00 00 77 53 85 c0 74 10 0f b6 03 84 c0 74 0
9 f3 90 <0f> b6 03 84 c0 75 f7 b8 01 00 00 00 66 89 03 5b 5d 41 5c 41 5d c3
4月 18 13:56:46 mocha.home kernel: RSP: 0018:ffffc16dc04d7bc0 EFLAGS: 00000202
4月 18 13:56:46 mocha.home kernel: RAX: 0000000000000001 RBX: ffff9ffdc293b428 
RCX: 0000000000000000
4月 18 13:56:46 mocha.home kernel: RDX: 0000000000000000 RSI: 0000000000000001 
RDI: ffff9ffdc293b428
4月 18 13:56:46 mocha.home kernel: RBP: ffff9ffdf7640134 R08: 0000000000000000 
R09: 0000000000000004
4月 18 13:56:46 mocha.home kernel: R10: ffff9ffdf76401fc R11: 0000000000000010 
R12: ffff9ffdc293b428
4月 18 13:56:46 mocha.home kernel: R13: ffff9ffdf7640000 R14: 0000000000000000 
R15: 0000000000000000
4月 18 13:56:46 mocha.home kernel: FS:  0000000000000000(0000) GS:ffffa0011dd00
000(0000) knlGS:0000000000000000
4月 18 13:56:46 mocha.home kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 00000000800
50033
4月 18 13:56:46 mocha.home kernel: CR2: 00005573a2dbab48 CR3: 00000001ac422006 
CR4: 00000000003706f0
4月 18 13:56:46 mocha.home kernel: DR0: 0000000000000000 DR1: 0000000000000000 
DR2: 0000000000000000
4月 18 13:56:46 mocha.home kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 
DR7: 0000000000000400
4月 18 13:56:46 mocha.home kernel: Call Trace:
4月 18 13:56:46 mocha.home kernel:  <IRQ>
4月 18 13:56:46 mocha.home kernel:  ? rcu_dump_cpu_stacks+0xc4/0x100
4月 18 13:56:46 mocha.home kernel:  ? rcu_sched_clock_irq+0x32e/0x1040
4月 18 13:56:46 mocha.home kernel:  ? task_tick_fair+0x40/0x3f0
4月 18 13:56:46 mocha.home kernel:  ? wq_worker_tick+0x12/0xc0
4月 18 13:56:46 mocha.home kernel:  ? trigger_load_balance+0x73/0x360
4月 18 13:56:46 mocha.home kernel:  ? scheduler_tick+0x165/0x2e0
4月 18 13:56:46 mocha.home kernel:  ? update_process_times+0x74/0xb0
4月 18 13:56:46 mocha.home kernel:  ? tick_sched_handle+0x21/0x60
4月 18 13:56:46 mocha.home kernel:  ? tick_nohz_highres_handler+0x6f/0x90
4月 18 13:56:46 mocha.home kernel:  ? __pfx_tick_nohz_highres_handler+0x10/0x10
4月 18 13:56:46 mocha.home kernel:  ? __hrtimer_run_queues+0x10f/0x2b0
4月 18 13:56:46 mocha.home kernel:  ? hrtimer_interrupt+0xf8/0x230
4月 18 13:56:46 mocha.home kernel:  ? __sysvec_apic_timer_interrupt+0x4d/0x140
4月 18 13:56:46 mocha.home kernel:  ? sysvec_apic_timer_interrupt+0x6d/0x90
4月 18 13:56:46 mocha.home kernel:  </IRQ>
4月 18 13:56:46 mocha.home kernel:  <TASK>
4月 18 13:56:46 mocha.home kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
4月 18 13:56:46 mocha.home kernel:  ? native_queued_spin_lock_slowpath+0x6e/0x2
b0
4月 18 13:56:46 mocha.home kernel:  _raw_spin_lock+0x29/0x30
4月 18 13:56:46 mocha.home kernel:  e1000e_get_stats64+0x22/0x120 [e1000e]
4月 18 13:56:46 mocha.home kernel:  dev_get_stats+0x5d/0x110
4月 18 13:56:46 mocha.home kernel:  rtnl_fill_stats+0x3b/0x130
4月 18 13:56:46 mocha.home kernel:  rtnl_fill_ifinfo+0x872/0x1580
4月 18 13:56:46 mocha.home kernel:  ? __alloc_skb+0x8c/0x1a0
4月 18 13:56:46 mocha.home kernel:  rtmsg_ifinfo_build_skb+0xae/0x120
4月 18 13:56:46 mocha.home kernel:  rtmsg_ifinfo+0x3c/0x90
4月 18 13:56:46 mocha.home kernel:  netdev_state_change+0x89/0x90
4月 18 13:56:46 mocha.home kernel:  linkwatch_do_dev+0x4f/0x60
4月 18 13:56:46 mocha.home kernel:  __linkwatch_run_queue+0xe1/0x220
4月 18 13:56:46 mocha.home kernel:  linkwatch_event+0x31/0x40
4月 18 13:56:46 mocha.home kernel:  process_one_work+0x171/0x340
4月 18 13:56:46 mocha.home kernel:  worker_thread+0x27b/0x3a0
4月 18 13:56:46 mocha.home kernel:  ? __pfx_worker_thread+0x10/0x10
4月 18 13:56:46 mocha.home kernel:  kthread+0xe5/0x120
4月 18 13:56:46 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
4月 18 13:56:46 mocha.home kernel:  ret_from_fork+0x31/0x50
4月 18 13:56:46 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
4月 18 13:56:46 mocha.home kernel:  ret_from_fork_asm+0x1b/0x30
4月 18 13:56:46 mocha.home kernel:  </TASK>
4月 18 13:56:48 mocha.home kernel: rcu: INFO: rcu_preempt detected expedited st
alls on CPUs/tasks: { 4-.... } 61551 jiffies s: 1005 root: 0x10/.
4月 18 13:56:48 mocha.home kernel: rcu: blocking rcu_node structures (internal 
RCU debug):
4月 18 13:56:48 mocha.home kernel: Sending NMI from CPU 1 to CPUs 4:
4月 18 13:56:48 mocha.home kernel: NMI backtrace for cpu 4
4月 18 13:56:48 mocha.home kernel: CPU: 4 PID: 121 Comm: kworker/4:1 Tainted: G
       W    L     6.8.6-100.fc38.x86_64 #1
4月 18 13:56:48 mocha.home kernel: Hardware name: System manufacturer System Pr
oduct Name/TUF H370-PRO GAMING (WI-FI), BIOS 1102 11/05/2018
4月 18 13:56:48 mocha.home kernel: Workqueue: events linkwatch_event
4月 18 13:56:48 mocha.home kernel: RIP: 0010:native_queued_spin_lock_slowpath+0
x6e/0x2b0
4月 18 13:56:48 mocha.home kernel: Code: 77 77 f0 0f ba 2b 08 0f 92 c2 8b 03 0f
b6 d2 c1 e2 08 30 e4 09 d0 3d ff 00 00 00 77 53 85 c0 74 10 0f b6 03 84 c0 74 0
9 f3 90 <0f> b6 03 84 c0 75 f7 b8 01 00 00 00 66 89 03 5b 5d 41 5c 41 5d c3
4月 18 13:56:48 mocha.home kernel: RSP: 0018:ffffc16dc04d7bc0 EFLAGS: 00000202
4月 18 13:56:48 mocha.home kernel: RAX: 0000000000000001 RBX: ffff9ffdc293b428 
RCX: 0000000000000000
4月 18 13:56:48 mocha.home kernel: RDX: 0000000000000000 RSI: 0000000000000001 
RDI: ffff9ffdc293b428
4月 18 13:56:48 mocha.home kernel: RBP: ffff9ffdf7640134 R08: 0000000000000000 
R09: 0000000000000004
4月 18 13:56:48 mocha.home kernel: R10: ffff9ffdf76401fc R11: 0000000000000010 
R12: ffff9ffdc293b428
4月 18 13:56:48 mocha.home kernel: R13: ffff9ffdf7640000 R14: 0000000000000000 
R15: 0000000000000000
4月 18 13:56:48 mocha.home kernel: FS:  0000000000000000(0000) GS:ffffa0011dd00
000(0000) knlGS:0000000000000000
4月 18 13:56:48 mocha.home kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 00000000800
50033
4月 18 13:56:48 mocha.home kernel: CR2: 00005573a2dbab48 CR3: 00000001ac422006 
CR4: 00000000003706f0
4月 18 13:56:48 mocha.home kernel: DR0: 0000000000000000 DR1: 0000000000000000 
DR2: 0000000000000000
4月 18 13:56:48 mocha.home kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 
DR7: 0000000000000400
4月 18 13:56:48 mocha.home kernel: Call Trace:
4月 18 13:56:48 mocha.home kernel:  <NMI>
4月 18 13:56:48 mocha.home kernel:  ? nmi_cpu_backtrace+0x99/0x110
4月 18 13:56:48 mocha.home kernel:  ? nmi_cpu_backtrace_handler+0x11/0x20
4月 18 13:56:48 mocha.home kernel:  ? nmi_handle+0x5e/0x150
4月 18 13:56:48 mocha.home kernel:  ? default_do_nmi+0x40/0x100
4月 18 13:56:48 mocha.home kernel:  ? exc_nmi+0x125/0x1a0
4月 18 13:56:48 mocha.home kernel:  ? end_repeat_nmi+0xf/0x60
4月 18 13:56:48 mocha.home kernel:  ? native_queued_spin_lock_slowpath+0x6e/0x2
b0
4月 18 13:56:48 mocha.home kernel:  ? native_queued_spin_lock_slowpath+0x6e/0x2
b0
4月 18 13:56:48 mocha.home kernel:  ? native_queued_spin_lock_slowpath+0x6e/0x2
b0
4月 18 13:56:48 mocha.home kernel:  </NMI>
4月 18 13:56:48 mocha.home kernel:  <TASK>
4月 18 13:56:48 mocha.home kernel:  _raw_spin_lock+0x29/0x30
4月 18 13:56:48 mocha.home kernel:  e1000e_get_stats64+0x22/0x120 [e1000e]
:4月 18 13:56:48 mocha.home kernel:  dev_get_stats+0x5d/0x110
4月 18 13:56:48 mocha.home kernel:  rtnl_fill_stats+0x3b/0x130
4月 18 13:56:48 mocha.home kernel:  rtnl_fill_ifinfo+0x872/0x1580
4月 18 13:56:48 mocha.home kernel:  ? __alloc_skb+0x8c/0x1a0
4月 18 13:56:48 mocha.home kernel:  rtmsg_ifinfo_build_skb+0xae/0x120
4月 18 13:56:48 mocha.home kernel:  rtmsg_ifinfo+0x3c/0x90
4月 18 13:56:48 mocha.home kernel:  netdev_state_change+0x89/0x90
4月 18 13:56:48 mocha.home kernel:  linkwatch_do_dev+0x4f/0x60
4月 18 13:56:48 mocha.home kernel:  __linkwatch_run_queue+0xe1/0x220
4月 18 13:56:48 mocha.home kernel:  linkwatch_event+0x31/0x40
4月 18 13:56:48 mocha.home kernel:  process_one_work+0x171/0x340
4月 18 13:56:48 mocha.home kernel:  worker_thread+0x27b/0x3a0
4月 18 13:56:48 mocha.home kernel:  ? __pfx_worker_thread+0x10/0x10
4月 18 13:56:48 mocha.home kernel:  kthread+0xe5/0x120
4月 18 13:56:48 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
4月 18 13:56:48 mocha.home kernel:  ret_from_fork+0x31/0x50
4月 18 13:56:48 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
4月 18 13:56:48 mocha.home kernel:  ret_from_fork_asm+0x1b/0x30
4月 18 13:56:48 mocha.home kernel:  </TASK>
4月 18 13:57:01 mocha.home systemd[1]: systemd-localed.service: State 'stop-sig
term' timed out. Aborting.
4月 18 13:57:01 mocha.home systemd[1]: systemd-localed.service: Killing process
1679 (systemd-localed) with signal SIGABRT.
4月 18 13:57:02 mocha.home systemd[1]: systemd-hostnamed.service: State 'stop-s
igterm' timed out. Aborting.
4月 18 13:57:02 mocha.home systemd[1]: systemd-hostnamed.service: Killing proce
ss 1038 (systemd-hostnam) with signal SIGABRT.
4月 18 13:57:13 mocha.home kernel: watchdog: BUG: soft lockup - CPU#4 stuck for
82s! [kworker/4:1:121]
4月 18 13:57:13 mocha.home kernel: Modules linked in: rfcomm snd_seq_dummy snd_
hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_nat_tftp nft_masq b
ridge stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_tftp n
ft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_
reject_ipv6 nft_reject nf_log_syslog nft_log nft_ct nft_chain_nat nf_tables ebta
ble_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_securi
ty iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle 
iptable_raw iptable_security sunrpc ip_set nfnetlink ebtable_filter ebtables ip6
table_filter iptable_filter bnep binfmt_misc vfat fat snd_sof_pci_intel_cnl snd_
sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence s
nd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof iwlmvm snd_sof_utils snd
_hda_codec_hdmi soundwire_generic_allocation soundwire_bus snd_soc_skl snd_soc_h
dac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek
4月 18 13:57:13 mocha.home kernel:  snd_soc_acpi_intel_match snd_soc_acpi mac80
211 snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine s
nd_hda_intel snd_intel_dspcfg intel_rapl_msr snd_intel_sdw_acpi intel_rapl_commo
n intel_uncore_frequency libarc4 snd_hda_codec intel_uncore_frequency_common iTC
O_wdt snd_hda_core intel_pmc_bxt ee1004 mei_hdcp btusb snd_hwdep spi_nor x86_pkg
_temp_thermal iTCO_vendor_support mei_pxp mtd btrtl snd_seq snd_seq_device intel
_powerclamp snd_pcm btintel iwlwifi coretemp snd_timer btbcm rapl intel_cstate b
tmtk snd i2c_i801 cfg80211 intel_uncore bluetooth wmi_bmof pcspkr mei_me i2c_smb
us soundcore spi_intel_pci intel_pmc_core mei spi_intel rfkill intel_vsec joydev
pmt_telemetry acpi_pad pmt_class loop zram i915 crct10dif_pclmul crc32_pclmul c
rc32c_intel polyval_clmulni polyval_generic e1000e ghash_clmulni_intel sha512_ss
se3 sha256_ssse3 sha1_ssse3 i2c_algo_bit drm_buddy ttm drm_display_helper video 
cec wmi serio_raw scsi_dh_rdac scsi_dh_emc scsi_dh_alua ip6_tables ip_tables dm_
multipath fuse
4月 18 13:57:13 mocha.home kernel: CPU: 4 PID: 121 Comm: kworker/4:1 Tainted: G
       W    L     6.8.6-100.fc38.x86_64 #1
4月 18 13:57:13 mocha.home kernel: Hardware name: System manufacturer System Pr
oduct Name/TUF H370-PRO GAMING (WI-FI), BIOS 1102 11/05/2018
4月 18 13:57:13 mocha.home kernel: Workqueue: events linkwatch_event
4月 18 13:57:13 mocha.home kernel: RIP: 0010:native_queued_spin_lock_slowpath+0
x6e/0x2b0
4月 18 13:57:13 mocha.home kernel: Code: 77 77 f0 0f ba 2b 08 0f 92 c2 8b 03 0f
b6 d2 c1 e2 08 30 e4 09 d0 3d ff 00 00 00 77 53 85 c0 74 10 0f b6 03 84 c0 74 0
9 f3 90 <0f> b6 03 84 c0 75 f7 b8 01 00 00 00 66 89 03 5b 5d 41 5c 41 5d c3
4月 18 13:57:13 mocha.home kernel: RSP: 0018:ffffc16dc04d7bc0 EFLAGS: 00000202
4月 18 13:57:13 mocha.home kernel: RAX: 0000000000000001 RBX: ffff9ffdc293b428 
RCX: 0000000000000000
4月 18 13:57:13 mocha.home kernel: RDX: 0000000000000000 RSI: 0000000000000001 
RDI: ffff9ffdc293b428
4月 18 13:57:13 mocha.home kernel: RBP: ffff9ffdf7640134 R08: 0000000000000000 
R09: 0000000000000004
4月 18 13:57:13 mocha.home kernel: R10: ffff9ffdf76401fc R11: 0000000000000010 
R12: ffff9ffdc293b428
4月 18 13:57:13 mocha.home kernel: R13: ffff9ffdf7640000 R14: 0000000000000000 
R15: 0000000000000000
4月 18 13:57:13 mocha.home kernel: FS:  0000000000000000(0000) GS:ffffa0011dd00
000(0000) knlGS:0000000000000000
4月 18 13:57:13 mocha.home kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 00000000800
50033
4月 18 13:57:13 mocha.home kernel: CR2: 00005573a2dbab48 CR3: 00000001ac422006 
CR4: 00000000003706f0
4月 18 13:57:13 mocha.home kernel: DR0: 0000000000000000 DR1: 0000000000000000 
DR2: 0000000000000000
4月 18 13:57:13 mocha.home kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 
DR7: 0000000000000400
4月 18 13:57:13 mocha.home kernel: Call Trace:
4月 18 13:57:13 mocha.home kernel:  <IRQ>
4月 18 13:57:13 mocha.home kernel:  ? watchdog_timer_fn+0x1e6/0x270
4月 18 13:57:13 mocha.home kernel:  ? __pfx_watchdog_timer_fn+0x10/0x10
4月 18 13:57:13 mocha.home kernel:  ? __hrtimer_run_queues+0x10f/0x2b0
4月 18 13:57:13 mocha.home kernel:  ? hrtimer_interrupt+0xf8/0x230
4月 18 13:57:13 mocha.home kernel:  ? __sysvec_apic_timer_interrupt+0x4d/0x140
4月 18 13:57:13 mocha.home kernel:  ? sysvec_apic_timer_interrupt+0x6d/0x90
4月 18 13:57:13 mocha.home kernel:  </IRQ>
4月 18 13:57:13 mocha.home kernel:  <TASK>
4月 18 13:57:13 mocha.home kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
4月 18 13:57:13 mocha.home kernel:  ? native_queued_spin_lock_slowpath+0x6e/0x2
b0
4月 18 13:57:13 mocha.home kernel:  _raw_spin_lock+0x29/0x30
4月 18 13:57:13 mocha.home kernel:  e1000e_get_stats64+0x22/0x120 [e1000e]
4月 18 13:57:13 mocha.home kernel:  dev_get_stats+0x5d/0x110
4月 18 13:57:13 mocha.home kernel:  rtnl_fill_stats+0x3b/0x130
4月 18 13:57:13 mocha.home kernel:  rtnl_fill_ifinfo+0x872/0x1580
4月 18 13:57:13 mocha.home kernel:  ? __alloc_skb+0x8c/0x1a0
4月 18 13:57:13 mocha.home kernel:  rtmsg_ifinfo_build_skb+0xae/0x120
4月 18 13:57:13 mocha.home kernel:  rtmsg_ifinfo+0x3c/0x90
4月 18 13:57:13 mocha.home kernel:  netdev_state_change+0x89/0x90
4月 18 13:57:13 mocha.home kernel:  linkwatch_do_dev+0x4f/0x60
4月 18 13:57:13 mocha.home kernel:  __linkwatch_run_queue+0xe1/0x220
4月 18 13:57:13 mocha.home kernel:  linkwatch_event+0x31/0x40
4月 18 13:57:13 mocha.home kernel:  process_one_work+0x171/0x340
4月 18 13:57:13 mocha.home kernel:  worker_thread+0x27b/0x3a0
4月 18 13:57:13 mocha.home kernel:  ? __pfx_worker_thread+0x10/0x10
4月 18 13:57:13 mocha.home kernel:  kthread+0xe5/0x120
4月 18 13:57:13 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
4月 18 13:57:13 mocha.home kernel:  ret_from_fork+0x31/0x50
4月 18 13:57:13 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
4月 18 13:57:13 mocha.home kernel:  ret_from_fork_asm+0x1b/0x30
4月 18 13:57:13 mocha.home kernel:  </TASK>
4月 18 13:57:15 mocha.home abrt-dump-journal-oops[1034]: abrt-dump-journal-oops
: Found oopses: 1
4月 18 13:57:15 mocha.home abrt-dump-journal-oops[1034]: abrt-dump-journal-oops
: Creating problem directories
4月 18 13:57:15 mocha.home abrt-server[2068]: Can't find a meaningful backtrace
for hashing in '.'
4月 18 13:57:15 mocha.home abrt-server[2068]: Deleting non-reportable oops '.' 
because DropNotReportableOopses is set to 'yes'
4月 18 13:57:15 mocha.home abrt-server[2068]: 'post-create' on '/var/spool/abrt
/oops-2024-04-18-13:57:15-1034-0' exited with 1
4月 18 13:57:15 mocha.home abrt-server[2068]: Deleting problem directory '/var/
spool/abrt/oops-2024-04-18-13:57:15-1034-0'
4月 18 13:57:15 mocha.home abrt-server[2068]: Lock file '.lock' was locked by p
rocess 2078, but it crashed?
4月 18 13:57:16 mocha.home abrt-dump-journal-oops[1034]: Reported 1 kernel oops
es to Abrt
4月 18 13:57:17 mocha.home systemd[1]: geoclue.service: State 'stop-sigterm' ti
4月 18 13:57:17 mocha.home systemd[1]: packagekit.service: State 'stop-sigterm'
timed out. Aborting.
4月 18 13:57:17 mocha.home systemd[1]: packagekit.service: Killing process 1734
(packagekitd) with signal SIGABRT.
4月 18 13:57:17 mocha.home gnome-session[1304]: gnome-session-binary[1304]: WAR
NING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to register be
fore timeout
4月 18 13:57:17 mocha.home gnome-session-binary[1304]: WARNING: Application 'or
g.gnome.SettingsDaemon.Power.desktop' failed to register before timeout
4月 18 13:57:17 mocha.home gnome-session-binary[1304]: Unrecoverable failure in
required component org.gnome.SettingsDaemon.Power.desktop
4月 18 13:57:17 mocha.home gnome-session[1304]: gnome-session-binary[1304]: WAR
NING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to registe
r before timeout
4月 18 13:57:17 mocha.home gnome-session-binary[1304]: WARNING: Application 'or
g.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout
4月 18 13:57:17 mocha.home gnome-session-binary[1304]: Unrecoverable failure in
required component org.gnome.SettingsDaemon.MediaKeys.desktop
4月 18 13:57:17 mocha.home gnome-session[1304]: gnome-session-binary[1304]: WAR
NING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register
before timeout
4月 18 13:57:17 mocha.home gnome-session[1304]: gnome-session-binary[1304]: WAR
NING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register be
fore timeout
4月 18 13:57:17 mocha.home gnome-session[1304]: gnome-session-binary[1304]: WAR
NING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' failed to register be
fore timeout
4月 18 13:57:17 mocha.home gnome-session-binary[1304]: WARNING: Application 'or
g.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout
4月 18 13:57:17 mocha.home gnome-session-binary[1304]: Unrecoverable failure in
required component org.gnome.SettingsDaemon.Keyboard.desktop
4月 18 13:57:17 mocha.home gnome-session-binary[1304]: WARNING: Application 'or
g.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
4月 18 13:57:17 mocha.home gnome-session-binary[1304]: Unrecoverable failure in
required component org.gnome.SettingsDaemon.Color.desktop
4月 18 13:57:17 mocha.home gnome-session-binary[1304]: WARNING: Application 'or
g.gnome.SettingsDaemon.Wacom.desktop' failed to register before timeout
4月 18 13:57:17 mocha.home gnome-session-binary[1304]: Unrecoverable failure in
required component org.gnome.SettingsDaemon.Wacom.desktop
4月 18 13:57:17 mocha.home spice-vdagent[2080]: vdagent virtio channel /dev/vir
tio-ports/com.redhat.spice.0 does not exist, exiting
4月 18 13:57:17 mocha.home gnome-session-binary[1304]: Entering running state
4月 18 13:57:41 mocha.home kernel: watchdog: BUG: soft lockup - CPU#4 stuck for
108s! [kworker/4:1:121]
4月 18 13:57:41 mocha.home kernel: Modules linked in: rfcomm snd_seq_dummy snd_
ridge stp llc nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_tftp n
ft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_
reject_ipv6 nft_reject nf_log_syslog nft_log nft_ct nft_chain_nat nf_tables ebta
ble_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_securi
ty iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle 
iptable_raw iptable_security sunrpc ip_set nfnetlink ebtable_filter ebtables ip6
table_filter iptable_filter bnep binfmt_misc vfat fat snd_sof_pci_intel_cnl snd_
sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence s
nd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof iwlmvm snd_sof_utils snd
_hda_codec_hdmi soundwire_generic_allocation soundwire_bus snd_soc_skl snd_soc_h
dac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek
4月 18 13:57:41 mocha.home kernel:  snd_soc_acpi_intel_match snd_soc_acpi mac80
211 snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine s
nd_hda_intel snd_intel_dspcfg intel_rapl_msr snd_intel_sdw_acpi intel_rapl_commo
n intel_uncore_frequency libarc4 snd_hda_codec intel_uncore_frequency_common iTC
O_wdt snd_hda_core intel_pmc_bxt ee1004 mei_hdcp btusb snd_hwdep spi_nor x86_pkg
_temp_thermal iTCO_vendor_support mei_pxp mtd btrtl snd_seq snd_seq_device intel
_powerclamp snd_pcm btintel iwlwifi coretemp snd_timer btbcm rapl intel_cstate b
tmtk snd i2c_i801 cfg80211 intel_uncore bluetooth wmi_bmof pcspkr mei_me i2c_smb
us soundcore spi_intel_pci intel_pmc_core mei spi_intel rfkill intel_vsec joydev
pmt_telemetry acpi_pad pmt_class loop zram i915 crct10dif_pclmul crc32_pclmul c
rc32c_intel polyval_clmulni polyval_generic e1000e ghash_clmulni_intel sha512_ss
cec wmi serio_raw scsi_dh_rdac scsi_dh_emc scsi_dh_alua ip6_tables ip_tables dm_
multipath fuse
4月 18 13:57:41 mocha.home kernel: CPU: 4 PID: 121 Comm: kworker/4:1 Tainted: G
       W    L     6.8.6-100.fc38.x86_64 #1
4月 18 13:57:41 mocha.home kernel: Hardware name: System manufacturer System Pr
oduct Name/TUF H370-PRO GAMING (WI-FI), BIOS 1102 11/05/2018
4月 18 13:57:41 mocha.home kernel: Workqueue: events linkwatch_event
4月 18 13:57:41 mocha.home kernel: RIP: 0010:native_queued_spin_lock_slowpath+0
x6e/0x2b0
4月 18 13:57:41 mocha.home kernel: Code: 77 77 f0 0f ba 2b 08 0f 92 c2 8b 03 0f
b6 d2 c1 e2 08 30 e4 09 d0 3d ff 00 00 00 77 53 85 c0 74 10 0f b6 03 84 c0 74 0
9 f3 90 <0f> b6 03 84 c0 75 f7 b8 01 00 00 00 66 89 03 5b 5d 41 5c 41 5d c3
4月 18 13:57:41 mocha.home kernel: RSP: 0018:ffffc16dc04d7bc0 EFLAGS: 00000202
4月 18 13:57:41 mocha.home kernel: RAX: 0000000000000001 RBX: ffff9ffdc293b428 
RCX: 0000000000000000
4月 18 13:57:41 mocha.home kernel: RDX: 0000000000000000 RSI: 0000000000000001 
RDI: ffff9ffdc293b428
4月 18 13:57:41 mocha.home kernel: RBP: ffff9ffdf7640134 R08: 0000000000000000 
R09: 0000000000000004
4月 18 13:57:41 mocha.home kernel: R10: ffff9ffdf76401fc R11: 0000000000000010 
R12: ffff9ffdc293b428
4月 18 13:57:41 mocha.home kernel: R13: ffff9ffdf7640000 R14: 0000000000000000 
4月 18 13:57:41 mocha.home kernel: FS:  0000000000000000(0000) GS:ffffa0011dd00
000(0000) knlGS:0000000000000000
4月 18 13:57:41 mocha.home kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 00000000800
50033
4月 18 13:57:41 mocha.home kernel: CR2: 00005573a2dbab48 CR3: 00000001ac422006 
CR4: 00000000003706f0
4月 18 13:57:41 mocha.home kernel: DR0: 0000000000000000 DR1: 0000000000000000 
DR2: 0000000000000000
4月 18 13:57:41 mocha.home kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 
DR7: 0000000000000400
4月 18 13:57:41 mocha.home kernel: Call Trace:
4月 18 13:57:41 mocha.home kernel:  <IRQ>
4月 18 13:57:41 mocha.home kernel:  ? watchdog_timer_fn+0x1e6/0x270
4月 18 13:57:41 mocha.home kernel:  ? __pfx_watchdog_timer_fn+0x10/0x10
4月 18 13:57:41 mocha.home kernel:  ? __hrtimer_run_queues+0x10f/0x2b0
4月 18 13:57:41 mocha.home kernel:  ? hrtimer_interrupt+0xf8/0x230
4月 18 13:57:41 mocha.home kernel:  ? __sysvec_apic_timer_interrupt+0x4d/0x140
4月 18 13:57:41 mocha.home kernel:  ? sysvec_apic_timer_interrupt+0x6d/0x90
4月 18 13:57:41 mocha.home kernel:  </IRQ>
4月 18 13:57:41 mocha.home kernel:  <TASK>
4月 18 13:57:41 mocha.home kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
4月 18 13:57:41 mocha.home kernel:  ? native_queued_spin_lock_slowpath+0x6e/0x2
:b0
4月 18 13:57:41 mocha.home kernel:  _raw_spin_lock+0x29/0x30
4月 18 13:57:41 mocha.home kernel:  e1000e_get_stats64+0x22/0x120 [e1000e]
4月 18 13:57:41 mocha.home kernel:  dev_get_stats+0x5d/0x110
4月 18 13:57:41 mocha.home kernel:  rtnl_fill_stats+0x3b/0x130
4月 18 13:57:41 mocha.home kernel:  rtnl_fill_ifinfo+0x872/0x1580
4月 18 13:57:41 mocha.home kernel:  ? __alloc_skb+0x8c/0x1a0
4月 18 13:57:41 mocha.home kernel:  rtmsg_ifinfo_build_skb+0xae/0x120
4月 18 13:57:41 mocha.home kernel:  rtmsg_ifinfo+0x3c/0x90
4月 18 13:57:41 mocha.home kernel:  netdev_state_change+0x89/0x90
4月 18 13:57:41 mocha.home kernel:  linkwatch_do_dev+0x4f/0x60
4月 18 13:57:41 mocha.home kernel:  __linkwatch_run_queue+0xe1/0x220
4月 18 13:57:41 mocha.home kernel:  linkwatch_event+0x31/0x40
4月 18 13:57:41 mocha.home kernel:  process_one_work+0x171/0x340
4月 18 13:57:41 mocha.home kernel:  worker_thread+0x27b/0x3a0
4月 18 13:57:41 mocha.home kernel:  ? __pfx_worker_thread+0x10/0x10
4月 18 13:57:41 mocha.home kernel:  kthread+0xe5/0x120
4月 18 13:57:41 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
4月 18 13:57:41 mocha.home kernel:  ret_from_fork+0x31/0x50
4月 18 13:57:41 mocha.home kernel:  ? __pfx_kthread+0x10/0x10
4月 18 13:57:41 mocha.home kernel:  ret_from_fork_asm+0x1b/0x30
4月 18 13:57:41 mocha.home kernel:  </TASK>
4月 18 13:57:42 mocha.home gnome-session[1304]: gnome-session-binary[1304]: Gno
meDesktop-WARNING: Failed to acquire idle monitor proxy: タイムアウトしました
4月 18 13:57:42 mocha.home gnome-session-binary[1304]: GnomeDesktop-WARNING: Fa
iled to acquire idle monitor proxy: タイムアウトしました
4月 18 13:57:43 mocha.home abrt-dump-journal-oops[1034]: abrt-dump-journal-oops
: Found oopses: 1
4月 18 13:57:43 mocha.home abrt-dump-journal-oops[1034]: abrt-dump-journal-oops
: Creating problem directories
4月 18 13:57:43 mocha.home abrt-server[2089]: Can't find a meaningful backtrace
for hashing in '.'
4月 18 13:57:43 mocha.home abrt-server[2089]: Deleting non-reportable oops '.' 
because DropNotReportableOopses is set to 'yes'
4月 18 13:57:43 mocha.home abrt-server[2089]: 'post-create' on '/var/spool/abrt
/oops-2024-04-18-13:57:43-1034-0' exited with 1
4月 18 13:57:43 mocha.home abrt-server[2089]: Deleting problem directory '/var/
spool/abrt/oops-2024-04-18-13:57:43-1034-0'
4月 18 13:57:43 mocha.home abrt-server[2089]: Lock file '.lock' was locked by p
rocess 2099, but it crashed?
4月 18 13:57:44 mocha.home abrt-dump-journal-oops[1034]: Reported 1 kernel oops
es to Abrt
4月 18 13:57:44 mocha.home systemd[1]: libvirtd.service: Deactivated successful
ly.
4月 18 13:57:44 mocha.home systemd[1]: libvirtd.service: Unit process 1636 (dns
masq) remains running after unit stopped.
4月 18 13:57:44 mocha.home systemd[1]: libvirtd.service: Unit process 1637 (dns
masq) remains running after unit stopped.
4月 18 13:57:44 mocha.home audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 s
es=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=libvirtd comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
4月 18 13:57:46 mocha.home /usr/libexec/gdm-wayland-session[1303]: dbus-daemon[
1303]: [session uid=42 pid=1303] Failed to activate service 'org.gnome.Shell.Scr
eencast': timed out (service_start_timeout=120000ms)
4月 18 13:57:46 mocha.home systemd[1]: systemd-localed.service: State 'stop-wat
chdog' timed out. Killing.
4月 18 13:57:46 mocha.home systemd[1]: systemd-localed.service: Killing process
1679 (systemd-localed) with signal SIGKILL.```
13

There are a lot if details there. I am not an expert so cannot guess at the cause. Maybe someone else here can jump in with advice about the kernel but it looks to me like whatever is causing this may be a factor.

Those logs from the very beginning show things that may be related so hopefully someone with more expertise than I can help.

You could potentially remove both the newer kernels with sudo dnf remove kernel*6.8.5* kernel*6.8.6* to eliminate the failing kernels, then try a simple reinstall of the newest one with sudo dnf upgrade kernel* so it only installs the newest and maybe would solve the issue.

I know there were enough changes between 6.8.4 and the later ones that maybe a bug report would be a good thing.

14

journalctl captures a huge amount of data, so it takes some work to filter out the records needed to understand a specific problem. Try journalctl -b -1 -p err after a boot that fails. Use man journalctl to read about the -b and -p options.

Your BIOS is old:

kernel: Hardware name: System manufacturer System Product Name/TUF H370-PRO GAMING (WI-FI), BIOS 1102 11/05/2018

When you encounter problems it is best to fully update Fedora packages and BIOS firmware so you aren’t wasting time on a solved problem.

There is: TUF H370-PRO GAMING (WI-FI) BIOS 3101 Version 3101 8.46 MB 2021/10/28

  1. Update Intel ME firmware.
  2. Improve system stability".

or use fwupdtool to see if updates are available. In addition to the kernel: BUG: scheduling while atomic there is kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x6e/0x2b0.

These are often associated with outdated BIOS/firmware.

15

Sorry for delayed response. And I’m trying to quote you properly but can’t make your name appear.

Thank you very much, gnwiii. It looked to me this is the problem since nobody else is complaining .
So I tried and successfully updated UEFI-BIOS. inxi -Fzxx now reports,
UEFI: America Megatrends v: 3101 date: 09/10/2021
and rebooted in a hope that 6.8.6 runs smoothly, but failed. My box stopped at splash screen like with old BIOS. But the error looks different now.

[takemura@mocha ~]$ journalctl -b -1 -l --no-pager -p err
 4月 20 15:54:46 mocha.home kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000003e2e0000-0x000000003e2fffff], contact BIOS vendor for fixes
 4月 20 15:54:46 mocha.home kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
 4月 20 15:54:46 mocha.home kernel: x86/cpu: SGX disabled by BIOS.
 4月 20 15:54:51 mocha.home kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
 4月 20 15:54:52 mocha.home libvirtd[1156]: /dev/kvm を開けません: そのようなファイルやディレクトリはありません
 4月 20 15:54:53 mocha.home kernel: BUG: scheduling while atomic: kworker/0:0/8/0x00000002

To my surprise, on kernel-6.8.4, which seems to work normally, the first [Firmware Bug] is repoted.

[takemura@mocha ~]$ journalctl -l --no-pager -b 0 | head -2
 4月 20 15:55:37 mocha.home kernel: Linux version 6.8.4-100.fc38.x86_64 (mockbuild@7f6fc2c4e3a64e84a3b7c413b2fb2c2b) (gcc (GCC) 13.2.1 20240316 (Red Hat 13.2.1-7), GNU ld version 2.39-16.fc38) #1 SMP PREEMPT_DYNAMIC Thu Apr  4 20:40:57 UTC 2024
 4月 20 15:55:37 mocha.home kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.8.4-100.fc38.x86_64 root=/dev/mapper/fedora_localhost--live-root ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet
[takemura@mocha ~]$ journalctl -l --no-pager -b 0 -p err
 4月 20 15:55:37 mocha.home kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000003e2e0000-0x000000003e2fffff], contact BIOS vendor for fixes
 4月 20 15:55:37 mocha.home kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
 4月 20 15:55:37 mocha.home kernel: x86/cpu: SGX disabled by BIOS.
 4月 20 15:55:43 mocha.home libvirtd[1141]: /dev/kvm を開けません: そのようなファイルやディレクトリはありません
 4月 20 15:55:52 mocha.home gdm-password][2289]: gkr-pam: unable to locate daemon control file
 4月 20 15:55:54 mocha.home systemd[2322]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-2970.scope - Application launched by gnome-session-binary.
 4月 20 15:58:15 mocha.home systemd[2322]: Failed to start app-gnome-plan-3662.scope - Application launched by gnome-shell.

but not in the log from 6.8.4 before BIOS update. As you see above, “soft lockup” from watchdog in 6.8.6 disappeared and the log file ended with “scheduling while atomic” right after e1000e, and the last line is

 4月 20 15:54:55 mocha.home abrt-dump-journal-oops[1032]: Reported 1 kernel oops
es to Abrt

The only changes in BIOS setting from default is I turned off hyperthreading, On board LED, and enabled secure boot. These changes are the same before and after the BIOS update.

Although the BIOS update contained Intel ME frmware, the version was 12.0.6.1120, whereas ASUS web contains MEUpdateTool 12.0.81.170v4. So Intel ME firmware on my system is still old. This may be causing problem. Unfortunately, the ASUS ME updater requires Windows environment, which I have not installed on my machine. So the next step will be buying Windows CD or newer mother board ?

Now it seems to me the problem is not in the kernel but in BIIOS/firmware or my setting. I’m still at a loss but the problem seems to be unrelated to fedora.

Thank you all who joined discussion. Your advices are really helpfull. And to all who read this thread, sorry for your time.

16

Fedora is using more recent kernels than most distros, so often reveals problems with older firmware. There has been a push to enable firmware updates without Windows, so the Fedora community may still be able to help.

Less than a year ago: Intel ME Firmware for Linux on ASUS says ASUS is responsible for ME updates. This year: Intel ME Firmware Update Tools says:

ASUS customer support simply say that they don’t support Linux.

It would be helpful to know if a Fedora user with the same model and who dual boots with Windows and has updated the ME has been able to use recent kernels.

Update Intel MS using Linux describes in (great detail) a way to install Lenovo ME updates on a Linux system.

You should not be sorry – your post may still lead to a solution and may help others with the same problem if only to build a “me too” list that can be notified if the Lenovo workaround can be used with ASUS.

Edit: ASUS Offers First Motherboard Firmware Update Via LVFS+Fwupd For Linux Users, but only for some motherboards.

1 Like
17

There has been another kernel update today, as well as a linux firmware update today. Try updating your system again, and also after update try running fwupdtool again to make sure firmware is at the latest for your kernel.

1 Like
18

Finally kernel-6.8.7 came down to F38 so I tried but resulted in the same error.

[takemura@mocha ~]$ journalctl -b -1 -l --no-pager | head -2
 4月 24 13:06:34 mocha.home kernel: Linux version 6.8.7-100.fc38.x86_64 (mockbuild@e5ffecc9229243e59802876e3b83b7d1) (gcc (GCC) 13.2.1 20240316 (Red Hat 13.2.1-7), GNU ld version 2.39-16.fc38) #1 SMP PREEMPT_DYNAMIC Wed Apr 17 19:34:28 UTC 2024
 4月 24 13:06:34 mocha.home kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.8.7-100.fc38.x86_64 root=/dev/mapper/fedora_localhost--live-root ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet
[takemura@mocha ~]$ journalctl -b -1 -p err -l --no-pager
 4月 24 13:06:34 mocha.home kernel: DMAR: [Firmware Bug]: No firmware reserved region can cover this RMRR [0x000000003e2e0000-0x000000003e2fffff], contact BIOS vendor for fixes
 4月 24 13:06:34 mocha.home kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
 4月 24 13:06:34 mocha.home kernel: x86/cpu: SGX disabled by BIOS.
 4月 24 13:06:41 mocha.home libvirtd[1140]: /dev/kvm を開けません: そのようなファイルやディレクトリはありません
 4月 24 13:06:42 mocha.home kernel: BUG: scheduling while atomic: kworker/0:1/10/0x00000002

I could not find linux frimware in this update and its version on my system is still

[takemura@mocha ~]$ rpm -q linux-firmware
linux-firmware-20240312-1.fc38.noarch

also after update try running fwupdtool again

As for fwupdtool, I am not sure what command to be issued, but tried to get information.

[takemura@mocha ~]$ sudo fwupdtool --force get-devices
Loading…                 [******************                     ]04:15:36.291 FuPluginIntelMe      failed to get public key using /fpf/OemCred: generic failure [0xb]
[snip]

Other devices seems to be recognized. Hmm, who signed IntelME ? Probably ASUS ? Where can I get the public key and whre should I put it? Or maybe this is not related to public keys, as in
https://github.com/fwupd/fwupd/issues/5745
I need to study more.

19

Perhaps you could make a cheat sheet for the community.

20

It’s because you’re still on F38 I am thinking. I would try a sudo dnf distro-sync to get up to F40.