[Kernel-packages] [Bug 1752194] Re: Intel GPU tools crash with "Couldn't map MMIO region"

[simone-c]

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)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1752194

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

Status in intel-gpu-tools package in Ubuntu:
  Confirmed

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 [+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 [+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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1752194/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1857385] Re: xHCI host controller not responding, assume dead via USB-C docking station

[simone-c]

Lenovo X1 Extreme Gen2
Docking Lenovo Thunderbolt 3 Gen2

Was getting similar random disconnects every 2-5 minutes:

[125028.443102] pcieport :05:01.0: pciehp: Slot(1): Link Down
[125028.443108] pcieport :05:01.0: pciehp: Slot(1): Card not present
[125028.443122] pcieport :08:04.0: can't change power state from D3cold to 
D0 (config space inaccessible)
[125028.444133] xhci_hcd :09:00.0: remove, state 1
[125028.444151] usb usb6: USB disconnect, device number 1
[125028.444156] usb 6-2: USB disconnect, device number 2
[125028.444162] usb 6-2.1: USB disconnect, device number 3
[125028.444167] usb 6-2.1.2: USB disconnect, device number 5
[125028.444369] xhci_hcd :09:00.0: xHCI host controller not responding, 
assume dead
..
.

Fixed by connecting two power supplies to both laptop and docking
(2x135W).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1857385

Title:
  xHCI host controller not responding, assume dead via USB-C docking
  station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C 
(https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the 
laptop from the docking station, the USB Hub disconnects all the local laptop 
USB ports and they are unusable.
  If I try to re-attach the laptop to the docking station nothing change, the 
ports (docking and laptop) are still disconnected, the hdmi/lan/power is 
working good. Sometimes it happens also when the laptop is docked and I'm 
working.

  The issue seems similar of the bug 1766076:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076

  but here no thunderbolt, it's a ryzen cpu.
  As written in the bug 1766076, the only way to have the USB in working 
condition is unbinding/binding the xhci or using the unit/systemd workaround 
described on post 83 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with 
some modification, sometimes is still not working at all.

  The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu
  18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs
  installed from kernel.org) and on Fedora 31 too. In Windows everything
  is working fine.

  The bios and firmware of the docking station are updated to the last
  one (1 month ago).

  The dmesg when I undock the laptop:

  [  305.299725] usb 2-1: USB disconnect, device number 2
  [  305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 
77]
  [  305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] 
[master: 8e933bad]
  [  305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] 
[master: 8e933bad]
  [  305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] 
[master: 8e933bad]
  [  305.362012] r8169 :03:00.0 enp3s0f0: Link is Down
  [  305.464627] usb 3-4: USB disconnect, device number 2
  [  305.464642] usb 3-4.2: USB disconnect, device number 3
  [  305.472691] usb 2-4: USB disconnect, device number 4
  [  305.472704] usb 2-4.2: USB disconnect, device number 5
  [  305.472712] usb 2-4.2.4: USB disconnect, device number 7
  [  306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  ...hundreds of line - the same
  [  310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop 
endpoint command.
  [  310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  hundreds of line - the same
  [  310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, 
assume dead
  [  310.532379] xhci_hcd :05:00.3: HC died; cleaning up
  [  310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure 
endpoint command
  [  310.670248] usb 2-4.3: USB disconnect, device number 6
  [  310.834039] usb 2-4.5: USB disconnect, device number 8
  [  310.835017] usb 2-2: USB disconnect, device number 10

  When I re-attach the latop to the docking:

  [  343.111212] r8169 :03:00.0 enp3s0f0: Link is Up - 100Mbps/Full - flow 
control rx/tx
  [  344.272052] [drm] DM_MST: starting TM on aconnector: 8e933bad [id: 
77]
  [  344.365795] [drm] DM_MST: added connector: e2f1a7b4 [id: 100] 
[master: 8e933bad]
  [  344.365857] [drm] DM_MST: added