protonscr

Getting Error 307 on Arch Linux using Valve Index

steamvropen
ValveSoftware/SteamVR-for-Linux#205 · opened 2019-06-28 by dylanmtaylor · updated 2019-09-27 · 19 comments · github
Ddylanmtaylor 2019-06-28 github

How To Collect SteamVR System Information:

  1. Click the 'SteamVR beta' menu in the upper left of the SteamVR Status window
  2. Click 'Create System Report'
  3. Click 'Copy to Clipboard'
  4. Browse to https://gist.github.com/
  5. Click in the text entry box (by the 1)
  6. Paste clipboard contents
  7. Click 'Create Public Gist'
  8. Add URL of your new Gist below

Your system information

  • Steam client version (build number or date): Latest 6/28/19
  • Distribution (e.g. Ubuntu): Arch
  • Graphics driver version (run nvidia-settings): Mesa 19.1.1 (Radeon VII)
  • Gist for SteamVR System Information: https://gist.github.com/dylanmtaylor/c847a5937cc94882f39dd2ace5a698fe
  • Opted into Steam client beta?: [Yes/No] Yes
  • Opted into SteamVR beta?: [Yes/No] No
  • Have you checked for system updates?: [Yes/No] No

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist

Steps for reproducing this issue:

  1. Attach headset to system
  2. Turn on controllers
  3. Make sure lighthouses are on
  4. Start steam and steamvr

image

Llostgoat 2019-06-28 github

Your vrcompositor.txt log ends abruptly. This probably means that it is crashing or aborting during init.

Can you clear your dmesg, sudo dmesg -c, start steamvr and then tell us what dmesg output was generated? Maybe there will be SIGSEGV notice in there.

If you can attach gdb to get a backtrace when it dies that could also be helpful. Are you running steam-native or steam-runtime?

Mmatthi4s 2019-09-27 github

I'm getting the same error on Manjaro (Arch). This might be the same issue, so I'm following up on this issue instead of creating a new one.

Your system information
Steam client version (build number or date): Sep 19 2019, at 01:52:58
Distribution (e.g. Ubuntu): Manjaro
Graphics driver version (run nvidia-settings): 430.40
Gist for SteamVR System Information: https://gist.github.com/matthi4s/d7a18926fd3426ca279ceb7a87d1060d
Opted into Steam client beta?: [Yes/No] No
Opted into SteamVR beta?: [Yes/No] No (but tried as well, same result)
Have you checked for system updates?: [Yes/No] Yes

Issue and steps are the same.

Now to answer your comment @lostgoat, here is the dmesg output:

[ 4684.093578] vrcompositor[26615]: segfault at 10 ip 00007f4734013d14 sp 00007fffbd1bb578 error 4 in libpthread-2.29.so[7f473400f000+f000]
[ 4684.093586] Code: ff 48 8d 0d 6e a9 00 00 ba 4f 02 00 00 48 8d 35 f7 a7 00 00 48 8d 3d 0d a8 00 00 e8 46 ba ff ff 66 0f 1f 44 00 00 f3 0f 1e fa <8b> 47 10 49 89 f8 89 c2 81 e2 7f 01 00 00 83 e0 7c 0f 85 a5 00 00
[ 4684.093652] audit: type=1701 audit(1569596923.186:127): auid=1000 uid=1000 gid=1000 ses=2 pid=26615 comm="vrcompositor" exe="/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor" sig=11 res=1
[ 4684.108446] audit: type=1130 audit(1569596923.203:128): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@19-26638-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 4684.738753] audit: type=1131 audit(1569596923.833:129): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@19-26638-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 4686.757567] vrcompositor[26812]: segfault at 10 ip 00007fbf0f328d14 sp 00007ffd6519a588 error 4 in libpthread-2.29.so[7fbf0f324000+f000]
[ 4686.757572] Code: ff 48 8d 0d 6e a9 00 00 ba 4f 02 00 00 48 8d 35 f7 a7 00 00 48 8d 3d 0d a8 00 00 e8 46 ba ff ff 66 0f 1f 44 00 00 f3 0f 1e fa <8b> 47 10 49 89 f8 89 c2 81 e2 7f 01 00 00 83 e0 7c 0f 85 a5 00 00
[ 4686.757593] audit: type=1701 audit(1569596925.849:130): auid=1000 uid=1000 gid=1000 ses=2 pid=26812 comm="vrcompositor" exe="/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor" sig=11 res=1
[ 4686.765141] audit: type=1130 audit(1569596925.859:131): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@20-26836-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 4687.376623] audit: type=1131 audit(1569596926.469:132): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@20-26836-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Llostgoat 2019-09-27 github

Hi,

On arch you should have access to coredumpctl. Can you run coredumpctl info -S -1d vrcompositor and paste the output here. That will give us stack traces from vrcompositor from your last day.

Alternatively, you can collect your minidumps for us by:

  • deleting everything in /tmp/dumps/
  • run SteamVR
  • zip /tmp/dumps and upload it somewhere you can share with us
Mmatthi4s 2019-09-27 github

Thank you for your quick reply!

Here is the coredumpctl output:

           PID: 26615 (vrcompositor)
           UID: 1000 (matthias)
           GID: 1000 (matthias)
        Signal: 11 (SEGV)
     Timestamp: Fri 2019-09-27 17:08:43 CEST (59min ago)
  Command Line: /home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor
    Executable: /home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor
 Control Group: /user.slice/user-1000.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-1000.slice
       Session: 2
     Owner UID: 1000 (matthias)
       Boot ID: 654eb88ff7824670aad5532c1b291a36
    Machine ID: a8f7e2a8ac784b6cb788adc8fa512b59
      Hostname: mcomp
       Storage: /var/lib/systemd/coredump/core.vrcompositor.1000.654eb88ff7824670aad5532c1b291a36.26615.1569596923000000.>
       Message: Process 26615 (vrcompositor) of user 1000 dumped core.
                
                Stack trace of thread 26615:
                #0  0x00007f4734013d14 __pthread_mutex_lock (libpthread.so.0)
                #1  0x000000000045056a n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #2  0x0000000000577a0f n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #3  0x000000000043d4ae n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #4  0x000000000041e967 n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #5  0x000000000047364e n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #6  0x00000000004757ef n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #7  0x000000000040e5d5 n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #8  0x00007f4733e6bee3 __libc_start_main (libc.so.6)
                #9  0x000000000040f43d n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>

           PID: 26812 (vrcompositor)
           UID: 1000 (matthias)
           GID: 1000 (matthias)
        Signal: 11 (SEGV)
     Timestamp: Fri 2019-09-27 17:08:45 CEST (59min ago)
  Command Line: /home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor
    Executable: /home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor
 Control Group: /user.slice/user-1000.slice/session-2.scope
          Unit: session-2.scope
         Slice: user-1000.slice
       Session: 2
     Owner UID: 1000 (matthias)
       Boot ID: 654eb88ff7824670aad5532c1b291a36
    Machine ID: a8f7e2a8ac784b6cb788adc8fa512b59
      Hostname: mcomp
       Storage: /var/lib/systemd/coredump/core.vrcompositor.1000.654eb88ff7824670aad5532c1b291a36.26812.1569596925000000.>
       Message: Process 26812 (vrcompositor) of user 1000 dumped core.
                
                Stack trace of thread 26812:
                #0  0x00007fbf0f328d14 __pthread_mutex_lock (libpthread.so.0)
                #1  0x000000000045056a n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #2  0x0000000000577a0f n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #3  0x000000000043d4ae n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #4  0x000000000041e967 n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #5  0x000000000047364e n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #6  0x00000000004757ef n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #7  0x000000000040e5d5 n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
                #8  0x00007fbf0f180ee3 __libc_start_main (libc.so.6)
                #9  0x000000000040f43d n/a (/home/matthias/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcomp>
Llostgoat 2019-09-27 github

Well, that was less info than I expected.

Could you use the alternative approach with the minidumps? Sorry for the double work.

Mmatthi4s 2019-09-27 github

Sure, no problem.

This should be the dump files: https://drive.google.com/open?id=1bKfinzfZpEK8i_twHlsSOh64XSPPjl22

Llostgoat 2019-09-27 github

Hey @matthi4s

I can see two problems:

  1. Your headset isn't detected by the nvidia driver. So we end up falling back into extended mode.

    • This should be the most important issue to fix.
    • It might be due to a loose DP connection or something similar.

  2. The extended mode path is failing on your system.

    • I'm adding some extra debug info here, and also some speculative fixes for the next beta. But extended move provides a really poor user experience, so we should focus on why 1 is going wrong.
Llostgoat 2019-09-27 github

Note, you can run the following command to check which monitors your gpu has detected:

andres@andres-nv:~$ nvidia-xconfig --query-gpu-info
Number of GPUs: 1
GPU #0:
Name      : GeForce RTX 2070
UUID      : GPU-e54fb3ef-b184-7764-a84d-e9138072bb8c
PCI BusID : PCI:1:0:0
Number of Display Devices: 1
Display Device 0 (TV-5):
EDID Name             : Valve Corporation Index HMD
Minimum HorizSync     : 231.757 kHz
Maximum HorizSync     : 232.128 kHz
Minimum VertRefresh   : 79 Hz
Maximum VertRefresh   : 144 Hz
Maximum PixelClock    : 687.100 MHz
Maximum Width         : 2880 pixels
Maximum Height        : 1600 pixels
Mmatthi4s 2019-09-27 github

Hmm, the output of the command lists the headset:

Number of GPUs: 1

GPU #0:
  Name      : GeForce RTX 2080
  UUID      : GPU-46e5ec12-375f-f52b-80f8-ea966d0b7e7d
  PCI BusID : PCI:1:0:0

  Number of Display Devices: 3

  Display Device 0 (TV-0):
      EDID Name             : Samsung U28E590
      Minimum HorizSync     : 30.000 kHz
      Maximum HorizSync     : 135.000 kHz
      Minimum VertRefresh   : 56 Hz
      Maximum VertRefresh   : 75 Hz
      Maximum PixelClock    : 600.000 MHz
      Maximum Width         : 3840 pixels
      Maximum Height        : 2160 pixels
      Preferred Width       : 3840 pixels
      Preferred Height      : 2160 pixels
      Preferred VertRefresh : 60 Hz
      Physical Width        : 610 mm
      Physical Height       : 350 mm

  Display Device 1 (TV-3):
      EDID Name             : Valve Corporation Index HMD
      Minimum HorizSync     : 231.757 kHz
      Maximum HorizSync     : 232.128 kHz
      Minimum VertRefresh   : 79 Hz
      Maximum VertRefresh   : 144 Hz
      Maximum PixelClock    : 687.100 MHz
      Maximum Width         : 2880 pixels
      Maximum Height        : 1600 pixels

  Display Device 2 (TV-5):
      EDID Name             : Samsung U28E590
      Minimum HorizSync     : 30.000 kHz
      Maximum HorizSync     : 135.000 kHz
      Minimum VertRefresh   : 56 Hz
      Maximum VertRefresh   : 75 Hz
      Maximum PixelClock    : 600.000 MHz
      Maximum Width         : 3840 pixels
      Maximum Height        : 2160 pixels
      Preferred Width       : 3840 pixels
      Preferred Height      : 2160 pixels
      Preferred VertRefresh : 60 Hz
      Physical Width        : 610 mm
      Physical Height       : 350 mm

I've now also switched around the ports and nothing changed.

Llostgoat 2019-09-27 github

Weird. From the logs we get zero reported displays from the nvidia vulkan driver:

Fri Sep 27 2019 17:00:02.740030 - Tried to find direct display through RandR: (nil)
Fri Sep 27 2019 17:00:02.740038 - Looking for direct display through Vulkan WSI
Fri Sep 27 2019 17:00:02.740047 - Tried to find direct display through Vulkan WSI: (nil)
Fri Sep 27 2019 17:00:02.740055 - CHmdWindowSDL: Failed to create direct mode surface

Does this work in the stable SteamVR branch?
Does it work with a different nvidia driver version?
Did it previously work and something else got updated changed?

Llostgoat 2019-09-27 github

Note: for AMD we take the RandR path. For nvidia we take the Vulkan WSI path. So the RandR path returning null is expected for your case. But we should see some displays being enumerated in the Vulkan WSI case.

Mmatthi4s 2019-09-27 github

Does this work in the stable SteamVR branch?
I've tried both, stable and beta and all files/outputs above are from the stable branch.

Does it work with a different nvidia driver version?
I've now changed the driver version to 435.21 with the same result. Any specific version I should try?

Did it previously work and something else got updated changed?
No, I've just got the Index today.

Llostgoat 2019-09-27 github

@matthi4s A few more questions.

What color are your Index lights?

What is the output of xrandr --verbose?

Since this seems to be a system configuration problem, you might also want to hop on to the #vronlinux channel in freenode IRC. Some other users might be able to reply faster there than I can here.

Mmatthi4s 2019-09-27 github

What color are your Index lights?
Blue

What is the output of xrandr --verbose?
https://gist.github.com/matthi4s/d26af6f17f1a9a4b0df14e66cedd371f

Llostgoat 2019-09-27 github

Hi @matthi4s,

Are you on a wayland based system?

Llostgoat 2019-09-27 github

There is no Wayland + direct display support from the graphics drivers. So if that is the case what you might need to do is start an X based session instead of a Wayland session.

Mmatthi4s 2019-09-27 github

No, I'm running the default Manjaro Gnome, which uses X.

Llostgoat 2019-09-27 github

There was some MUTTER metadata in your xrandr output which is what led me to believe you were in a wayland session.

Mmatthi4s 2019-09-27 github

I managed to get it to work with a clean OS installation on a different SSD. At least it's not a hardware problem, but I'm still wondering what's causing this and how I could fix it on my main installation.

Nothing extracted yet.