Intel GPU tools crash with "Couldn't map MMIO region"

Bug #1752194 reported by Robert Markovski on 2018-02-27
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
intel-gpu-tools (Ubuntu)
Undecided
Unassigned

Bug Description

Trying to run anything in intel-gpu-tools (tested intel_gpu_top, intel_gpu_time and intel_backlight) on my laptop (which has hybrid graphics, GTX 760m (proprietary nvidia driver not installed right now) + Intel 4th gen iGPU) as root yields the following output:
(intel_gpu_top:23021) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:23021) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:23021) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted
(intel_gpu_top:23021) intel-mmio-CRITICAL: Couldn't map MMIO region
Stack trace:
  #0 [_init+0x1753f]
  #1 [_init+0xc978]
  #2 [_init+0x118d]
  #3 [__libc_start_main+0xf1]
  #4 [_init+0x1fba]
  #5 [<unknown>+0x1fba]
Test (null) failed.
**** DEBUG ****
(intel_gpu_top:23021) intel-chipset-DEBUG: Test requirement passed: pci_dev
(intel_gpu_top:23021) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:23021) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:23021) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted
(intel_gpu_top:23021) intel-mmio-CRITICAL: Couldn't map MMIO region
(intel_gpu_top:23021) igt-core-INFO: Stack trace:
(intel_gpu_top:23021) igt-core-INFO: #0 [_init+0x1753f]
(intel_gpu_top:23021) igt-core-INFO: #1 [_init+0xc978]
(intel_gpu_top:23021) igt-core-INFO: #2 [_init+0x118d]
(intel_gpu_top:23021) igt-core-INFO: #3 [__libc_start_main+0xf1]
(intel_gpu_top:23021) igt-core-INFO: #4 [_init+0x1fba]
(intel_gpu_top:23021) igt-core-INFO: #5 [<unknown>+0x1fba]
**** END ****
FAIL (-1.000s)

Happens under bot Wayland and XOrg.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: intel-gpu-tools 1.20-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 28 00:30:15 2018
InstallationDate: Installed on 2015-11-25 (825 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: intel-gpu-tools
UpgradeStatus: Upgraded to artful on 2017-11-01 (118 days ago)

description: updated
description: updated
John Yang (johnyang2000) wrote :

I have exactly the same "Couldn't map MMIO region: Operation not permitted" problem with Ubuntu 14.04.5 with 1.3-0ubuntu2.1 build. My CPU is Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz on my ASUS VivoMini PC.

Robert Hooker (sarvatt) wrote :

They need to be run under sudo. also the intel-gpu-tools in 14.04 shouldn't have support for an i7-7700.

John Yang (johnyang2000) wrote :

Yes I did run with sudo. The error message is different without sudo. I think the new 14.04.5 fixed a lot of problems with the new intel cpu. At least it fixed all my graphics card driver issue in one shot. However, how do I find out what is supported with intel-gpu-tools?

John Yang (johnyang2000) wrote :

but of course the intel-gpu-tool for trusty hasn't been updated since 2014 so likely it doesn't support i7-7700 (released in 2017) as you described. However it's the same MIMO error message I am getting. I'm hoping the same fix will be updated to the version for trusty.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in intel-gpu-tools (Ubuntu):
status: New → Confirmed
lak (matt-kowalczyk) wrote :

Hitting this on 18.04 with Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz and i915 driver.

Package: intel-gpu-tools
Architecture: amd64
Version: 1.22-1
Priority: optional
Section: x11
Origin: Ubuntu
Maintainer: Ubuntu Developers <email address hidden>
Original-Maintainer: Debian X Strike Force <email address hidden>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 9347
Depends: libc6 (>= 2.15), libcairo2 (>= 1.6.0), libdrm-intel1 (>= 2.4.36), libdrm2 (>= 2.4.62), libglib2.0-0 (>= 2.35.9), libkmod2 (>= 5~), libpciaccess0 (>= 0.8.0+git20071002), libprocps6, libudev1 (>= 183), libunwind8, libx11-6 (>= 2:1.4.99.1), libxext6, libxrandr2 (>= 2:1.2.99.2), libxv1, zlib1g (>= 1:1.1.4)
Conflicts: xserver-xorg-video-intel (<< 2.9.1)
Filename: pool/main/i/intel-gpu-tools/intel-gpu-tools_1.22-1_amd64.deb
Size: 1033260
MD5sum: 682636c82781d71504be3be8469b2baa
SHA1: 04e5b1be2e7f8884bf620108480f7304c409a5f5
SHA256: 15885babb16990f050017be5e8e130b1a7d335d528955805c07a7b850b512561
Homepage: https://01.org/linuxgraphics/
Description-en: tools for debugging the Intel graphics driver
 intel-gpu-tools is a package of tools for debugging the Intel graphics driver,
 including a GPU hang dumping program, performance monitor, and performance
 microbenchmarks for regression testing the DRM.
Description-md5: 564f3bda44ca25bdb6227f2b18149b73
Task: ubuntukylin-desktop
Supported: 5y

Li Xiaolong (sxpc722) wrote :

I have exactly the same "Couldn't map MMIO region: Operation not permitted" problem with Ubuntu 19.04.
======================
(intel_gpu_top:23801) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:23801) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:23801) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted
(intel_gpu_top:23801) intel-mmio-CRITICAL: Couldn't map MMIO region
Stack trace:
  #0 [_init+0x7b87]
  #1 [_init+0x5420]
  #2 [_init+0xe85]
  #3 [__libc_start_main+0xeb]
  #4 [_init+0x1c92]
Test (null) failed.
**** DEBUG ****
(intel_gpu_top:23801) intel-chipset-DEBUG: Test requirement passed: pci_dev
(intel_gpu_top:23801) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:23801) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:23801) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted
(intel_gpu_top:23801) intel-mmio-CRITICAL: Couldn't map MMIO region
(intel_gpu_top:23801) igt-core-INFO: Stack trace:
(intel_gpu_top:23801) igt-core-INFO: #0 [_init+0x7b87]
(intel_gpu_top:23801) igt-core-INFO: #1 [_init+0x5420]
(intel_gpu_top:23801) igt-core-INFO: #2 [_init+0xe85]
(intel_gpu_top:23801) igt-core-INFO: #3 [__libc_start_main+0xeb]
(intel_gpu_top:23801) igt-core-INFO: #4 [_init+0x1c92]
**** END ****
FAIL (-1.000s)

James (oz0) wrote :

I've hit this too on 18.04.
It may be related to kernel lockdown in UEFI secure boot.
https://bugs.freedesktop.org/show_bug.cgi?id=93199

simone-c (simone-c) wrote :

Ubuntu 18, Intel(R) UHD Graphics 620

$ sudo intel_gpu_top
(intel_gpu_top:832) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:832) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:832) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted
(intel_gpu_top:832) intel-mmio-CRITICAL: Couldn't map MMIO region
Stack trace:
  #0 [_init+0x7b87]
  #1 [_init+0x5420]
  #2 [_init+0xe85]
  #3 [__libc_start_main+0xe7]
  #4 [_init+0x1c92]
Test (null) failed.
**** DEBUG ****
(intel_gpu_top:832) intel-chipset-DEBUG: Test requirement passed: pci_dev
(intel_gpu_top:832) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145:
(intel_gpu_top:832) intel-mmio-CRITICAL: Failed assertion: !(error != 0)
(intel_gpu_top:832) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted
(intel_gpu_top:832) intel-mmio-CRITICAL: Couldn't map MMIO region
(intel_gpu_top:832) igt-core-INFO: Stack trace:
(intel_gpu_top:832) igt-core-INFO: #0 [_init+0x7b87]
(intel_gpu_top:832) igt-core-INFO: #1 [_init+0x5420]
(intel_gpu_top:832) igt-core-INFO: #2 [_init+0xe85]
(intel_gpu_top:832) igt-core-INFO: #3 [__libc_start_main+0xe7]
(intel_gpu_top:832) igt-core-INFO: #4 [_init+0x1c92]
**** END ****
FAIL (-1.000s)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.