intel_reg:16734 intel_mmio-CRITICAL

amaro · 2022-12-04 09:58:29

Unexpectedly after a reboot (I rarely reboot) 'intel_reg write 0x61254 0x28962896' started throwing the following messages:

# intel_reg write 0x61254 0x28962896
Warning: register spec not found in '/usr/share/igt-gpu-tools/registers'. Using builtin register spec.
(intel_reg:16734) intel_mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../lib/intel_mmio.c:146:
(intel_reg:16734) intel_mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_reg:16734) intel_mmio-CRITICAL: Last errno: 1, Operation not permitted
(intel_reg:16734) intel_mmio-CRITICAL: Couldn't map MMIO region
Stack trace:
  #0 [__igt_fail_assert+0x113]
  #1 [intel_mmio_use_pci_bar+0xc4]
  #2 [intel_register_access_init+0x1b]
  #3 [<unknown>+0x8935eddb]
  #4 [<unknown>+0x8935d6f6]
  #5 [__libc_start_main+0xea]
  #6 [<unknown>+0x8935d7ba]
Test (null) failed.
**** DEBUG ****
(intel_reg:16734) intel_chipset-DEBUG: Test requirement passed: pci_dev
(intel_reg:16734) intel_mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../lib/intel_mmio.c:146:
(intel_reg:16734) intel_mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_reg:16734) intel_mmio-CRITICAL: Last errno: 1, Operation not permitted
(intel_reg:16734) intel_mmio-CRITICAL: Couldn't map MMIO region
(intel_reg:16734) igt_core-INFO: Stack trace:
(intel_reg:16734) igt_core-INFO:   #0 [__igt_fail_assert+0x113]
(intel_reg:16734) igt_core-INFO:   #1 [intel_mmio_use_pci_bar+0xc4]
(intel_reg:16734) igt_core-INFO:   #2 [intel_register_access_init+0x1b]
(intel_reg:16734) igt_core-INFO:   #3 [<unknown>+0x8935eddb]
(intel_reg:16734) igt_core-INFO:   #4 [<unknown>+0x8935d6f6]
(intel_reg:16734) igt_core-INFO:   #5 [__libc_start_main+0xea]
(intel_reg:16734) igt_core-INFO:   #6 [<unknown>+0x8935d7ba]
****  END  ****
FAIL (-1.000s)

The only thing kernel related I did lately was adding a few lines to '/etc/sysctl.conf' and a few options to '/etc/default/grub'

vm.mmap_rnd_bits = 32
vm.mmap_rnd_compat_bits = 16
fs.protected_fifos = 2
fs.protected_regular = 2
kernel.dmesg_restrict = 1
kernel.printk = 3 3 3 3
kernel.kexec_load_disabled = 1
kernel.unprivileged_bpf_disabled = 1
net.core.bpf_jit_harden = 2
vm.unprivileged_userfaultfd = 0
dev.tty.ldisc_autoload = 0

slab_nomerge init_on_alloc=1 init_on_free=1 page_alloc.shuffle=1 pti=on vsyscall=none debugfs=off oops=panic module.sig_enforce=1 lockdown=confidentiality loglevel=0

Any ideas are highly appreciated!

Head_on_a_Stick · 2022-12-04 10:31:10

https://bugs.launchpad.net/ubuntu/+sour … ug/1752194

Does reverting those GRUB & sysctl changes remove the error?

Btw I'm pretty sure kernel.dmesg_restrict is already enabled by default.

Last edited by Head_on_a_Stick (2022-12-04 10:31:31)

amaro · 2022-12-06 07:34:04

reverting those settings doesn't solve the problem
I installed intel-gpu-tools while using Devuan via the usb (live system) and 'intel_reg' worked fine there

Head_on_a_Stick · 2022-12-06 10:07:18

Try reinstalling the package then. There is also dpkg --verify.

amaro · 2022-12-11 11:10:32

'dpkg --verify' gives nothing and reinstalling the package and its dependencies was the first thing I did (before goooogling about the issue and before posting here)
I installed it on a different partition with fresh installation of Devuan and it works fine there

The officially official Devuan Forum!

#1 2022-12-04 09:58:29

intel_reg:16734 intel_mmio-CRITICAL

#2 2022-12-04 10:31:10

Re: intel_reg:16734 intel_mmio-CRITICAL

#3 2022-12-06 07:34:04

Re: intel_reg:16734 intel_mmio-CRITICAL

#4 2022-12-06 10:07:18

Re: intel_reg:16734 intel_mmio-CRITICAL

#5 2022-12-11 11:10:32

Re: intel_reg:16734 intel_mmio-CRITICAL

Board footer