[Testing Update] 2021-11-13 - Kernel, Gnome 41.1, Xorg-Server 21.1, LxQt 1.0, Nvidia 470.86, Plasma 5.23.3

Hello community,

Another testing branch update with some usual updates for you.


The third point release of Plasma 5.23 is out now!

  • We updated our Kernels. Note that 5.13 series is marked EOL and 5.12 got removed!
  • Pipewire got updated to 0.3.40, which brings better Jack compatibility
  • Gnome 41 is maybe the biggest addition to this update
  • After a long time there is a new Xorg-Server release. 21.1 brings new features and might break support on Nvidia drivers. So let us know if you see any issues, before we drop them.
  • Finally there is the first stable release of LxQt!
  • Plasma got another point release: 5.23.3
  • With 470.86 the Nvidia driver for Keppler cards got additional fixes.
  • A lot of Python and Haskell updates got added
  • Other regular upstream updates

Get our latest daily developer images now from Github: Plasma, Gnome, XFCE. You get the latest stable releases of Manjaro from CDN77.


Our current supported kernels

  • linux44 4.4.291
  • linux49 4.9.289
  • linux414 4.14.254
  • linux419 4.19.216
  • linux54 5.4.158
  • linux510 5.10.78
  • linux513 5.13.19 [EOL]
  • linux514 5.14.17
  • linux515 5.15.1
  • linux510-rt 5.10.73_rt54
  • linux515-rt 5.15_rt17

Package Updates (Thu Nov 11 10:35:53 CET 2021)

A detailed list of all package changes can be found here.

  • No issue, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself.(Please post your solution)
  • Yes i am currently experiencing an issue due to the update. (Please post about it)

0 voters

Check if your mirror has already synced:

13 Likes

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed


New issues:

  • nvidia-390xx is not compatible to Xorg-Server 21.1.1 yet. For all those with that Xorg ABI error and having no /etc/X11/xorg.conf: Search for a file called /etc/X11/xorg.conf.d/20-server_flags.conf. If it does not exist yet, create it. Amend the file and paste the well-known contents there:
Section "ServerFlags"
  Option "IgnoreABI" "1"
EndSection
  • freetype2 update might result in font characters becoming squares. Don’t worry, a relogin to your UI should fix it. We recommend to do the update in a TTY. Affected UIs so far: Gnome, Phosh, Cinnamon.

  • Compiz packages like compiz-easy-patch got dropped from our repositories. Due to protobuf update you may need to rebuild that package locally on your end. Compiz-easy-patch removed from repos

  • :information_source: Announcement for PipeWire users:

    Re-enable any per-user enabled `pipewire-media-session.service` manually

    You should re-enable any per-user pipewire-media-session.service manually to establish a new service alias for pipewire-session-manager.service added with 0.3.38.

     systemctl --user enable pipewire-media-session
    

    See the PipeWire Release Notes for more info


Older Issues

Please click the ► at the beginning of this line to view content of this section
  • OS prober does not run and add other operating systems

    Please click the ► at the beginning of this line to view this solution

    To restore, please execute: echo GRUB_DISABLE_OS_PROBER=false|sudo tee -a /etc/default/grub && sudo update-grub

    For more information, see opening post in [Stable Update] 2021-03-08.

Nvidia card owners

  • We simplified nVidia driver installation. This means we dropped legacy drivers.
    • We recommend to switch over to Nouveau drivers if your card is mentioned here and the feature you need is not in red TO DO here for your particular card.

    • If you however still need proprietary drivers, you may want to execute the following to ensure all parts of the nVidia drivers get installed properly:

      sudo mhwd -a pci nonfree 0300
      
      If proprietary drivers don't fix everything, please click the ► at the beginning of this line to view more info
      1. try installing kernel 5.4 LTS (Long Term Support)
      2. If that doesn’t fix it, take a full system backup, go to a console using Ctrl+Alt+F2 and:
      • Backup /etc/X11/mhwd.d/nvidia.conf if you ever edited that manually

      • remove all nVidia related drivers and applications:

        pacman --remove nvidia*
        
      • Note which applications are being removed and keep them handy in a list

      • Install the driver first:

        mhwd --install video-hybrid-XXX-nvidia-prime
        

        (Where XXX is amd or intel if you have hybrid graphics or the whole thing is video-nvidia if you’re on an nVidia-only system)

      • reboot and see if you at least get a screen.

      • Install all the other applications from your handy list that you still need one by one.

      • Restore /etc/X11/mhwd.d/nvidia.conf if you ever edited that manually

      • If that wouldn’t solve the issue open a new issue here referring to this update and posting at a minimum the full output of:

        inxi --admin --verbosity=7 --filter --no-host --width
        

      If you however still have issues with your Nvidia card, you may open a new thread in our forum: Graphics & Display - Manjaro Linux Forum or look at our tutorial on compiling old Nvidia drivers.

For AMD GPU users having a black screen with kernel 5.10

Please click the ► at the beginning of this line to view more info

Due to a bug in the AMD drivers, please try the following first:

For GRUB:

  1. Open a terminal or a TTY
  2. Open /etc/default/grub in your favourite CLI editor (nano vi, emacs`)
  3. Find the line: GRUB_CMDLINE_LINUX_DEFAULT="
  4. Add amdgpu.dc=0
  5. Save
  6. Execute sudo update-grub and reboot

For systemd-boot:

  1. Open a terminal or a TTY
  2. Open /boot/loader/entries/manjarolinux5.10.conf in your favourite CLI editor (nano vi, emacs`)
  3. Add amdgpu.dc=0 to the end of the line options
  4. Save & reboot

For rEFInd:

  1. Open a terminal or a TTY
  2. Open /boot/refind_linux.conf in your favourite CLI editor (nano vi, emacs`)
  3. Find the line: "Boot using default options" "root=
  4. Add amdgpu.dc=0
  5. Save & reboot

Possible 2 Min delay on shutdown with Gnome

Please click the ► at the beginning of this line to view more info
  • If you got the problem with shutdown delay (about 2min) on Gnome, here is a workaround:
    • Edit /usr/lib/systemd/user/gnome-session-restart-dbus.service in your favourite editor as root and add Slice=-.slice as a line all by itself like this:

      [Service]
      Type=notify
      Slice=-.slice
      ExecStart=/usr/lib/gnome-session-ctl --restart-dbus
      
    • Click this link For more information

Touchpad on a ThinkPad stops working

  • Restart again, please.

You get [PKGNAME] warning: directory permissions differ on [Directory name]

followed by:

Filesystem: NNN package MMM

Please click the ► at the beginning of this line to view this solution
  • The solution:

    sudo chmod MMM DirectoryName
    

Where obviously MMM is the second number you see (the correct one)

  • The explanation:
    Your package expects the security permissions to be MMM but your system is set to NNN. This is just a warning (today) but to ensure you remain up-to-date with the latest and greatest security rules it’s advised to execute the above command.

Systemd error message: .slice: Failed to migrate controller cgroups

If you have a similar error message like this:

systemd[1004]: -.slice: Failed to migrate controller cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: Permission denied

… you may need to add this Grub parameter to your /etc/default/grub file in line GRUB_CMDLINE_LINUX_DEFAULT: systemd.unified_cgroup_hierarchy=true. To update your grub menu, call: sudo update-grub. For more information on that issue, see also Arch Forum.


Python 3.9 Requires Rebuilds

Instructions for quickly and easily rebuilding affected AUR packages:

# Install yay
sudo pacman -S --needed --noconfirm yay

# Rebuild AUR python packages
yay -S --noconfirm $(pacman -Qqo "/usr/lib/python3.8/site-packages")

libtraceevent>=5.9-1 update requires manual intervention

2020-10-23 - Sébastien Luttringer

The libtraceevent package prior to version 5.9-1 was missing a soname link. This has been fixed in 5.9-1, so the upgrade will need to overwrite the untracked files created by ldconfig. If you get any of these errors

libtraceevent: /usr/lib/libtraceevent.so.1 exists in filesystem

when updating, use

pacman -Syu --overwrite /usr/lib/libtraceevent.so.1

to perform the upgrade.

Arch Linux - News: libtraceevent>=5.9-1 update requires manual intervention

OpenVPN connection times out.

Workaround: downgrade openvpn (2.5.0-1 => 2.4.9-2).
For a proper solution follow this bug report on Arch Linux: FS#68480 : [openvpn] running unprivileged with iproute no longer working

PAM and PAMBASE got updated, which might prevent you from login

Due to updates from pambase and pam you might take care about any .pacnew files in /etc/pam.d as for example pam_tally, pam_tally2 and pam_cracklib got deprecated. Read in the ArchWiki about managing those files.

Typical issue:

For recovery, it is enough to boot with kernel option “systemd.unit=rescue.target”, then proceed into /etc/pam.d and merge “system-auth” and “system-auth.pacnew”

System takes a long time to boot

If you’ve got errors like Failed to start Network Manager Wait Online. you can try removing systemd from passwd and group in /etc/nsswitch.conf as described here
Update: If you can see the line
dbus-daemon[1453]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 45146ms)
in in your dbus log ( journalctl -b -u dbus ), the new/better workaround is to switch cups from service to socket as described here:
systemctl disable cups.service
systemctl enable cups.socket

I think I’ve some font problems

With the update of fontconfig some major rules how fonts get applied changed. Make sure that your system has ttf-dejavu installed. A more in depth explanation can be found here.

Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

1 Like

there is something wrong with kernel 5.15.2 , i lost keyboard and text video is stopped ( gui is not started )
i get this ( try with initrams also return same result )
it works on version 5.14 and 5.15.1

nov. 13 14:41:47 mjro systemd-fsck[503]: home : récupération du journal
nov. 13 14:41:47 mjro systemd-fsck[503]: home : propre, 178223/28917760 fichiers, 57567604/115645184 blocs
nov. 13 14:41:47 mjro systemd[1]: Mounted /boot/efi.
nov. 13 14:41:47 mjro systemd[1]: Finished File System Check on /dev/disk/by-uuid/05923b1e-dbe7-4d73-9440-2c067e027f1a.
nov. 13 14:41:47 mjro audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-by\x2duuid-05923b1e\x2ddbe7\x2d4d73\x2d9440\x2d2c067e027f1a comm="sy>
nov. 13 14:41:47 mjro systemd[1]: Mounting /home...
nov. 13 14:41:47 mjro systemd-udevd[416]: Using default interface naming scheme 'v249'.
nov. 13 14:41:47 mjro kernel: BUG: unable to handle page fault for address: ffffaaa643b52000
nov. 13 14:41:47 mjro kernel: #PF: supervisor read access in kernel mode
nov. 13 14:41:47 mjro kernel: #PF: error_code(0x0000) - not-present page
nov. 13 14:41:47 mjro kernel: PGD 100000067 P4D 100000067 PUD 1001c0067 PMD 10f981067 PTE 0
nov. 13 14:41:47 mjro kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
nov. 13 14:41:47 mjro kernel: CPU: 8 PID: 233 Comm: kworker/8:2 Tainted: G           OE     5.15.2-1-MANJARO #1 d68d158d4f98b4d55496e4b8ec4ea7ac9e330397
nov. 13 14:41:47 mjro kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS PRO/X570 AORUS PRO, BIOS F30 09/15/2020
nov. 13 14:41:47 mjro kernel: Workqueue: events drm_fb_helper_damage_work
nov. 13 14:41:47 mjro kernel: RIP: 0010:memcpy_toio+0x23/0x50
nov. 13 14:41:47 mjro kernel: Code: c6 66 0f 1f 44 00 00 0f 1f 44 00 00 48 85 d2 74 28 40 f6 c7 01 75 33 48 83 fa 01 76 06 40 f6 c7 02 75 1f 48 89 d1 48 c1 e9 02 <f3> a5 f6 c2 02 74 02 66 a>
nov. 13 14:41:47 mjro kernel: RSP: 0018:ffffaaa6409f7c70 EFLAGS: 00010212
nov. 13 14:41:47 mjro kernel: RAX: 0000000000002000 RBX: ffffaaa641868000 RCX: 0000000000000180
nov. 13 14:41:47 mjro kernel: RDX: 0000000000001e00 RSI: ffffaaa643b52000 RDI: ffffaaa641869800
nov. 13 14:41:47 mjro kernel: RBP: ffffaaa643b50800 R08: 0000000000060000 R09: 0000000034325258
nov. 13 14:41:47 mjro kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000001e00
nov. 13 14:41:47 mjro kernel: R13: ffff905cc0e42200 R14: 0000000000000405 R15: 0000000000000408
nov. 13 14:41:47 mjro kernel: FS:  0000000000000000(0000) GS:ffff905feec00000(0000) knlGS:0000000000000000
nov. 13 14:41:47 mjro kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
nov. 13 14:41:47 mjro kernel: CR2: ffffaaa643b52000 CR3: 0000000104708000 CR4: 0000000000350ee0
nov. 13 14:41:47 mjro kernel: Call Trace:
nov. 13 14:41:47 mjro kernel:  drm_fb_memcpy_dstclip+0x6f/0xa0
nov. 13 14:41:47 mjro kernel:  drm_fb_blit_rect_dstclip+0xd0/0xf0
nov. 13 14:41:47 mjro kernel:  simpledrm_simple_display_pipe_update+0xc5/0xe0
nov. 13 14:41:47 mjro kernel:  drm_atomic_helper_commit_planes+0xc2/0x260
nov. 13 14:41:47 mjro kernel:  drm_atomic_helper_commit_tail+0x42/0x80
nov. 13 14:41:47 mjro kernel:  commit_tail+0xd8/0x130
nov. 13 14:41:47 mjro kernel:  drm_atomic_helper_commit+0x11f/0x150
nov. 13 14:41:47 mjro kernel:  drm_atomic_helper_dirtyfb+0x193/0x280
nov. 13 14:41:47 mjro kernel:  drm_fb_helper_damage_work+0x1cf/0x310
nov. 13 14:41:47 mjro kernel:  process_one_work+0x1e8/0x3c0
nov. 13 14:41:47 mjro kernel:  worker_thread+0x50/0x3c0
nov. 13 14:41:47 mjro kernel:  ? process_one_work+0x3c0/0x3c0
nov. 13 14:41:47 mjro kernel:  kthread+0x132/0x160
nov. 13 14:41:47 mjro kernel:  ? set_kthread_struct+0x50/0x50
nov. 13 14:41:47 mjro kernel:  ret_from_fork+0x22/0x30
nov. 13 14:41:47 mjro kernel: Modules linked in: snd_intel_dspcfg(+) kvm(+) snd_intel_sdw_acpi vfat fat pcc_cpufreq(-) snd_hda_codec fjes(-) irqbypass snd_hda_core crct10dif_pclmul ghash_cl>
nov. 13 14:41:47 mjro kernel: CR2: ffffaaa643b52000
nov. 13 14:41:47 mjro kernel: ---[ end trace 98f4b05f481c5976 ]---
nov. 13 14:41:47 mjro kernel: RIP: 0010:memcpy_toio+0x23/0x50
nov. 13 14:41:47 mjro kernel: Code: c6 66 0f 1f 44 00 00 0f 1f 44 00 00 48 85 d2 74 28 40 f6 c7 01 75 33 48 83 fa 01 76 06 40 f6 c7 02 75 1f 48 89 d1 48 c1 e9 02 <f3> a5 f6 c2 02 74 02 66 a>
nov. 13 14:41:47 mjro kernel: RSP: 0018:ffffaaa6409f7c70 EFLAGS: 00010212
nov. 13 14:41:47 mjro kernel: RAX: 0000000000002000 RBX: ffffaaa641868000 RCX: 0000000000000180
nov. 13 14:41:47 mjro kernel: RDX: 0000000000001e00 RSI: ffffaaa643b52000 RDI: ffffaaa641869800
nov. 13 14:41:47 mjro kernel: RBP: ffffaaa643b50800 R08: 0000000000060000 R09: 0000000034325258
nov. 13 14:41:47 mjro kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000001e00
nov. 13 14:41:47 mjro kernel: R13: ffff905cc0e42200 R14: 0000000000000405 R15: 0000000000000408
nov. 13 14:41:47 mjro kernel: FS:  0000000000000000(0000) GS:ffff905feec00000(0000) knlGS:0000000000000000
nov. 13 14:41:47 mjro kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
nov. 13 14:41:47 mjro kernel: CR2: ffffaaa643b52000 CR3: 0000000104708000 CR4: 0000000000350ee0
nov. 13 14:41:47 mjro kernel: EXT4-fs (sdf3): mounted filesystem with ordered data mode. Opts: discard. Quota mode: none.
nov. 13 14:41:47 mjro systemd[1]: Mounted /home.

i do others checks under 5.14 version

@philm
updated : youtube (1080p) is ok , steam with proton 6.7 (vulkan is ok) for kernel 5.14 and Nvidias

boot is also ok with kernel 5.15.1 and drivers nvidia 490 series ( from previous Testing )
by downgrade linux515 , linux515-nvidia ( and i should add linux515-virtualbox-host-modules)

==> something changed in drm-fb(-helper) between 5.15.1 and 5.15.2

5.15.2 also got more config changes. We will see if that created additional regressions.

1 Like

I’m unable to mount my NTFS partitions with ntfs3 type in /etc/fstab It fails on boot. Shouldn’t we be able to mount using ntfs3 now with kernel 5.15.2?

//EDIT: NEVERMIND, my bad, I left some options that were not supported by ntfs3 precisely big_writes,windows_names. After I removed these options I can boot and disk mount with the new ntfs3 driver.

:+1:

1 Like

With this update HARDWARE Acceleration in KDE Plasma was broken! It uses software rendering now. I have RX560 and Mesa

you mean you can’t go to kcmshell5 qtquicksettings and change it back?

Yes, when I trying to change QtQuick options and KWin compositing - i can change options, but its does nothing

1 Like

So … obviously something went wrong with NVidia driver with this release as it was told in the release post :frowning:
I’m using 340xx driver because it’s an old computer and Nouveau is not working properlly on it
Does anyone know howto solve this problem?

Nvidia proprietary + Wayland + KDE is more broken than the last releases.
On login the screen alternates between solid black and a few coloured pixels three times and then returns to the login prompt. I pulled some logs from dmesg, let me know if more info is required.

I am getting the below error while updating through pamac

Error: Failed to prepare transaction: target not found: xdg-desktop-portal-gnome

And I am not able to get any update through pacman, the output from pacman is “there is nothing to do”

@0mega refresh your mirror list.

1 Like

you goback to stable

OK. But how to?

sudo pacman-mirrors --api --set-branch stable

pacman -Syyuu

1 Like

So… before I succeded to downgrade xorg to the previous version. Now NVidia driver is loaded but… when I downgrade some packages were deleted. and now the system boot normally until I have to type my password and I can’t cause the keyboard/mouse aren’t working. I guess xf86-input-evdev and xf86-input-libinput are lacking.
My question now is: how can I boot in console mode? Just to make everything in commandline?

Dont login via display manager like you do normally. When booted to lock screen, press ctrl+alt+f1 or ctrl+alt+f2 or ctrl+alt+f3 or ctrl+alt+f4 and it will take you to cmd line. login there and fix

Edit: for some reason this forum would not show that i replied to some comment. Weird

Thank U
I knew that already :smiley:
The problem is that whan X is loaded, the keybord and mouse aren’t working.
So I have to boot in a kind of rescue mode prevented X to start

yep, loading into 5.15 got me massive graphical corruption. 5.10 is okay, though.

$ journalctl -b -1 -p 4

Summary

– Journal begins at Wed 2021-11-10 00:52:16 EST, ends at Sat 2021-11-13 12:01:01 EST. –
Nov 13 11:44:01 belphanior kernel: tsc: Unable to calibrate against PIT
Nov 13 11:44:01 belphanior kernel: pci 0000:03:00.0: [Firmware Bug]: disabling VPD access (can’t determine size of non-standard VPD format)
Nov 13 11:44:01 belphanior kernel: ata1.00: supports DRM functions and may not be fully accessible
Nov 13 11:44:01 belphanior kernel: ata1.00: supports DRM functions and may not be fully accessible
Nov 13 11:44:01 belphanior kernel: simple-framebuffer simple-framebuffer.0: [drm] drm_plane_enable_fb_damage_clips() not called
Nov 13 11:44:01 belphanior kernel: nvidia: loading out-of-tree module taints kernel.
Nov 13 11:44:01 belphanior kernel: nvidia: module license ‘NVIDIA’ taints kernel.
Nov 13 11:44:01 belphanior kernel: Disabling lock debugging due to kernel taint
Nov 13 11:44:01 belphanior kernel:
Nov 13 11:44:01 belphanior kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 495.44 Fri Oct 22 06:13:12 UTC 2021
Nov 13 11:44:01 belphanior kernel: nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint.
Nov 13 11:44:01 belphanior kernel: resource sanity check: requesting [mem 0x000e0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000e0000-0x000e3fff window]
Nov 13 11:44:01 belphanior kernel: caller _nv032275rm+0x2a/0x60 [nvidia] mapping multiple BARs
Nov 13 11:44:01 belphanior kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000d3fff window]
Nov 13 11:44:01 belphanior kernel: caller _nv000717rm+0x1ad/0x200 [nvidia] mapping multiple BARs
Nov 13 11:44:02 belphanior kernel: ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20210730/utaddress-204)
Nov 13 11:44:02 belphanior kernel: ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210730/utaddress-204)
Nov 13 11:44:02 belphanior kernel: ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210730/utaddress-204)
Nov 13 11:44:02 belphanior kernel: ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210730/utaddress-204)
Nov 13 11:44:02 belphanior kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210730/utaddress-204)
Nov 13 11:44:02 belphanior kernel: ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210730/utaddress-204)
Nov 13 11:44:02 belphanior kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov 13 11:44:02 belphanior kernel: at24 3-0050: supply vcc not found, using dummy regulator
Nov 13 11:44:02 belphanior kernel: at24 3-0051: supply vcc not found, using dummy regulator
Nov 13 11:44:02 belphanior kernel: at24 3-0052: supply vcc not found, using dummy regulator
Nov 13 11:44:02 belphanior kernel: at24 3-0053: supply vcc not found, using dummy regulator
Nov 13 11:44:03 belphanior kernel: urandom_read: 4 callbacks suppressed
Nov 13 11:44:08 belphanior kernel: kauditd_printk_skb: 22 callbacks suppressed
Nov 13 11:44:08 belphanior kernel: BUG: unable to handle page fault for address: ffffbcf080e84000
Nov 13 11:44:08 belphanior kernel: #PF: supervisor read access in kernel mode
Nov 13 11:44:08 belphanior kernel: #PF: error_code(0x0000) - not-present page
Nov 13 11:44:08 belphanior kernel: Oops: 0000 [#1] PREEMPT SMP PTI
Nov 13 11:44:08 belphanior kernel: CPU: 2 PID: 33 Comm: kworker/2:0 Tainted: P OE 5.15.2-1-MANJARO #1 d68d158d4f98b4d55496e4b8ec4ea7ac9e330397
Nov 13 11:44:08 belphanior kernel: Hardware name: MSI MS-7917/Z97 GAMING 5 (MS-7917), BIOS V1.13 02/16/2016
Nov 13 11:44:08 belphanior kernel: Workqueue: events drm_fb_helper_damage_work
Nov 13 11:44:08 belphanior kernel: RIP: 0010:memcpy_toio+0x23/0x50
Nov 13 11:44:08 belphanior kernel: Code: c6 66 0f 1f 44 00 00 0f 1f 44 00 00 48 85 d2 74 28 40 f6 c7 01 75 33 48 83 fa 01 76 06 40 f6 c7 02 75 1f 48 89 d1 48 c1 e9 02 a5 f6 c2 02 74 02 66 a5 f6 c2 01 74 01 a4 31 d2 89 d1 89 d6 89
Nov 13 11:44:08 belphanior kernel: RSP: 0018:ffffbcf080153c70 EFLAGS: 00010206
Nov 13 11:44:08 belphanior kernel: RAX: 0000000000000800 RBX: ffffbcf0806eb800 RCX: 0000000000000080
Nov 13 11:44:08 belphanior kernel: RDX: 0000000000000640 RSI: ffffbcf080e84000 RDI: ffffbcf0806ebc40
Nov 13 11:44:08 belphanior kernel: RBP: ffffbcf080e83bc0 R08: 00000000000e8000 R09: 0000000036314752
Nov 13 11:44:08 belphanior kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000640
Nov 13 11:44:08 belphanior kernel: R13: ffff9a92037bd900 R14: 0000000000000008 R15: 0000000000000010
Nov 13 11:44:08 belphanior kernel: FS: 0000000000000000(0000) GS:ffff9a9706d00000(0000) knlGS:0000000000000000
Nov 13 11:44:08 belphanior kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 13 11:44:08 belphanior kernel: CR2: ffffbcf080e84000 CR3: 000000010548c001 CR4: 00000000001706e0
Nov 13 11:44:08 belphanior kernel: Call Trace:
Nov 13 11:44:08 belphanior kernel: drm_fb_memcpy_dstclip+0x6f/0xa0
Nov 13 11:44:08 belphanior kernel: drm_fb_blit_rect_dstclip+0xd0/0xf0
Nov 13 11:44:08 belphanior kernel: simpledrm_simple_display_pipe_update+0xc5/0xe0
Nov 13 11:44:08 belphanior kernel: drm_atomic_helper_commit_planes+0xc2/0x260
Nov 13 11:44:08 belphanior kernel: drm_atomic_helper_commit_tail+0x42/0x80
Nov 13 11:44:08 belphanior kernel: commit_tail+0xd8/0x130
Nov 13 11:44:08 belphanior kernel: drm_atomic_helper_commit+0x11f/0x150
Nov 13 11:44:08 belphanior kernel: drm_atomic_helper_dirtyfb+0x193/0x280
Nov 13 11:44:08 belphanior kernel: drm_fb_helper_damage_work+0x1cf/0x310
Nov 13 11:44:08 belphanior kernel: process_one_work+0x1e8/0x3c0
Nov 13 11:44:08 belphanior kernel: worker_thread+0x50/0x3c0
Nov 13 11:44:08 belphanior kernel: ? process_one_work+0x3c0/0x3c0
Nov 13 11:44:08 belphanior kernel: kthread+0x132/0x160
Nov 13 11:44:08 belphanior kernel: ? set_kthread_struct+0x50/0x50
Nov 13 11:44:08 belphanior kernel: ret_from_fork+0x22/0x30
Nov 13 11:44:08 belphanior kernel: Modules linked in: intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm snd_usb_audio snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio irqbypass snd_hda_codec_hdmi snd_usbmidi_lib snd_hda_intel crct10dif_pclmul snd_intel_dspcfg crc32_pclmul snd_rawmidi snd_intel_sdw_acpi ghash_clmulni_intel snd_seq_device snd_hda_codec aesni_intel mc iTCO_wdt snd_hda_core intel_pmc_bxt mei_hdcp iTCO_vendor_support snd_hwdep crypto_simd at24 mxm_wmi cryptd snd_pcm rapl intel_cstate snd_timer i2c_i801 intel_uncore snd i2c_smbus alx mousedev lpc_ich mdio mei_me soundcore mei rfkill mac_hid video wmi acpi_pad nct6775 hwmon_vid coretemp fuse ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usbhid crc32c_intel sr_mod cdrom xhci_pci nvidia_drm(POE) nvidia_uvm(POE) nvidia_modeset(POE) nvidia(POE)
Nov 13 11:44:08 belphanior kernel: CR2: ffffbcf080e84000
Nov 13 11:44:08 belphanior kernel: —[ end trace de3af12702481489 ]—
Nov 13 11:44:08 belphanior kernel: RIP: 0010:memcpy_toio+0x23/0x50
Nov 13 11:44:08 belphanior kernel: Code: c6 66 0f 1f 44 00 00 0f 1f 44 00 00 48 85 d2 74 28 40 f6 c7 01 75 33 48 83 fa 01 76 06 40 f6 c7 02 75 1f 48 89 d1 48 c1 e9 02 a5 f6 c2 02 74 02 66 a5 f6 c2 01 74 01 a4 31 d2 89 d1 89 d6 89
Nov 13 11:44:08 belphanior kernel: RSP: 0018:ffffbcf080153c70 EFLAGS: 00010206
Nov 13 11:44:08 belphanior kernel: RAX: 0000000000000800 RBX: ffffbcf0806eb800 RCX: 0000000000000080
Nov 13 11:44:08 belphanior kernel: RDX: 0000000000000640 RSI: ffffbcf080e84000 RDI: ffffbcf0806ebc40
Nov 13 11:44:08 belphanior kernel: RBP: ffffbcf080e83bc0 R08: 00000000000e8000 R09: 0000000036314752
Nov 13 11:44:08 belphanior kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000640
Nov 13 11:44:08 belphanior kernel: R13: ffff9a92037bd900 R14: 0000000000000008 R15: 0000000000000010
Nov 13 11:44:08 belphanior kernel: FS: 0000000000000000(0000) GS:ffff9a9706d00000(0000) knlGS:0000000000000000
Nov 13 11:44:08 belphanior kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 13 11:44:08 belphanior kernel: CR2: ffffbcf080e84000 CR3: 000000010548c001 CR4: 00000000001706e0
Nov 13 11:44:09 belphanior systemd[1]: lxdm.service: Main process exited, code=killed, status=9/KILL
Nov 13 11:44:09 belphanior systemd[1]: lxdm.service: Failed with result ‘signal’.
Nov 13 11:44:09 belphanior systemd[1]: systemd-udevd.service: Found left-over process 423 (systemd-udevd) in control group while starting unit. Ignoring.
Nov 13 11:44:09 belphanior systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Nov 13 11:44:09 belphanior systemd[1]: cronie.service: Main process exited, code=killed, status=9/KILL
Nov 13 11:44:09 belphanior systemd[1]: cronie.service: Failed with result ‘signal’.
Nov 13 11:44:09 belphanior systemd[1]: systemd-udevd.service: Main process exited, code=killed, status=9/KILL
Nov 13 11:44:09 belphanior systemd[1]: systemd-udevd.service: Failed with result ‘signal’.
Nov 13 11:44:09 belphanior systemd[1]: systemd-journald.service: Main process exited, code=killed, status=9/KILL
Nov 13 11:44:09 belphanior systemd[1]: systemd-journald.service: Failed with result ‘signal’.
Nov 13 11:44:09 belphanior kernel: Emergency Sync complete

1 Like

@philm can you check to remove DRM_SIMPLEDRM from config ?
see this : https://bugzilla.kernel.org/show_bug.cgi?id=214723

3 Likes