Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NVidia: Core dump with --gpu option when connecting #360

Open
Ra2-IFV opened this issue Dec 2, 2024 · 12 comments
Open

NVidia: Core dump with --gpu option when connecting #360

Ra2-IFV opened this issue Dec 2, 2024 · 12 comments
Labels
bug Something isn't working

Comments

@Ra2-IFV
Copy link

Ra2-IFV commented Dec 2, 2024 •
edited
Loading

Useful information:

Please, try to gather as much of useful information as possible and follow
these instructions:

  • Version:
wayvnc: v0.9.1-e4ec935 (makepkg)
neatvnc: v0.9.1-cc19604 (makepkg)
aml: v0.3.0-0-gb83f357 (makepkg)
  • Try to reproduce while capturing a trace log:
Info: Capturing output DP
Info: >> 0000000000000 (DP) 1920x1080+0x0 Power:UNKNOWN
DEBUG: ../wayvnc/src/ctl-server.c: 809: Initializing wayvncctl socket: /run/user/1000/wayvncctl
DEBUG: ../wayvnc/src/ctl-server.c: 778: Connecting to existing socket in case it's stale
DEBUG: ../wayvnc/src/ctl-server.c: 785: Connect failed: Connection refused
Warning: ../wayvnc/src/ctl-server.c: 788: Deleting stale control socket path "/run/user/1000/wayvncctl"
DEBUG: ../neatvnc/src/server.c: 2114: Trying address: 0.0.0.0
DEBUG: ../neatvnc/src/server.c: 2129: Successfully bound to address
Info: Listening for connections on 0.0.0.0:5901
Info: New client connection from 127.0.0.1: 0x574e94a77620
DEBUG: ../neatvnc/src/server.c: 357: Client chose security type: 1
DEBUG: ../wayvnc/src/main.c: 1640: Configuring cursor capturing
DEBUG: ../wayvnc/src/main.c: 1656: Failed to capture cursor
Info: Starting screen capture
DEBUG: ../wayvnc/src/main.c: 1030: Acquired power state management. Waiting for power event to start capturing
DEBUG: ../wayvnc/src/main.c: 1383: Client connected, new client count: 1
DEBUG: ../wayvnc/src/ctl-server.c: 941: Enqueueing client-connected event: {"id":"1","address":"127.0.0.1","username":null,"seat":"seat0","connection_count":1}
DEBUG: ../wayvnc/src/ctl-server.c: 968: Enqueued client-connected event for 0 clients
Info: Client 0x574e94a77620 initialised. MIN-RTT during handshake was 0 ms
DEBUG: ../neatvnc/src/server.c: 673: Client 0x574e94a77620 set encodings: cursor,desktop-size,extended-desktop-size,qemu-led-state,vmware-led-state,extended-clipboard,continuous-updates,fence,qemu-extended-key-event,tight,copyrect,open-h264,zrle,hextile,rre,copyrect,raw
DEBUG: ../neatvnc/src/server.c: 2686: Keyboard LED state changed: ffffffff -> 0
Info: Choosing tight encoding for client 0x574e94a77620
DEBUG: ../neatvnc/src/server.c: 1630: Sending extended desktop resize rect: 1920x1080
DEBUG: ../wayvnc/src/buffer.c: 606: Reconfiguring buffer pool
DEBUG: ../wayvnc/src/buffer.c: 552: Using render node: /dev/dri/renderD128
DEBUG: ../neatvnc/src/server.c: 2686: Keyboard LED state changed: 0 -> 2
Segmentation fault (core dumped)
  • Get the stack trace:
Stack trace of thread 10000:
#0  0x00007bd52d680581 n/a (libc.so.6 + 0x16c581)
#1  0x00007bd52d786d5a nvnc_display_feed_buffer (libneatvnc.so.0 + 0x18d5a)
#2  0x000058c7d3306eab n/a (wayvnc + 0xbeab)
#3  0x000058c7d330bdba n/a (wayvnc + 0x10dba)
#4  0x00007bd52d50e596 n/a (libffi.so.8 + 0x7596)
#5  0x00007bd52d50b00e n/a (libffi.so.8 + 0x400e)
#6  0x00007bd52d50dbd3 ffi_call (libffi.so.8 + 0x6bd3)
#7  0x00007bd52d7a58b0 n/a (libwayland-client.so.0 + 0x48b0)
#8  0x00007bd52d7a6139 n/a (libwayland-client.so.0 + 0x5139)
#9  0x00007bd52d7a6553 wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x5553)
#10 0x000058c7d33094fd n/a (wayvnc + 0xe4fd)
#11 0x00007bd52d7da61f aml_dispatch (libaml.so.0 + 0x361f)
#12 0x000058c7d33015b1 n/a (wayvnc + 0x65b1)
#13 0x00007bd52d539e08 n/a (libc.so.6 + 0x25e08)
#14 0x00007bd52d539ecc __libc_start_main (libc.so.6 + 0x25ecc)
#15 0x000058c7d3302405 n/a (wayvnc + 0x7405)
  • Describe how to reproduce the problem

Command

  • wayvnc --gpu

Config

address=0.0.0.0
port=5901
use_relative_paths=true
@Ra2-IFV Ra2-IFV added the bug Something isn't working label Dec 2, 2024
@any1 any1 changed the title Core dump with --gpu option when connecting NVidia: Core dump with --gpu option when connecting Dec 2, 2024
@any1
Copy link
Owner

any1 commented Dec 2, 2024

Sadly, that stack trace is useless to me without line numbers. Please follow the instructions to get a useful strack trace.

@Ra2-IFV
Copy link
Author

Ra2-IFV commented Dec 3, 2024

GDB tells no debug symbols found. How to enable them? I didn't see options for this while compiling.
And could you tell me how to get the dump after wayvnc is terminated, if you are generous enough?

@Ra2-IFV
Copy link
Author

Ra2-IFV commented Feb 7, 2025

any help is appreciated...

@any1
Copy link
Owner

any1 commented Feb 7, 2025

Follow the build instructions in README.md. Instead of meson build, say meson setup build --buildtype=debug.

@net147
Copy link

net147 commented Feb 8, 2025 •
edited
Loading

wayvnc: v0.9.1-e4ec935 (makepkg)
neatvnc: v0.9.2-4c37ae9 (makepkg)
aml: v0.3.0-0-gb83f357 (makepkg)

Here is a stack trace with line numbers:

#0  __memcpy_evex_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:265
#1  0x00007ffff7da4574 in memcpy (__dest=<optimized out>, __src=<optimized out>, __len=<optimized out>, __dest=<optimized out>, __src=<optimized out>, __len=<optimized out>) at /usr/include/bits/string_fortified.h:29
#2  XXH_memcpy (dest=<optimized out>, src=0x80, size=<optimized out>) at ../neatvnc/include/xxhash.h:2361
#3  XXH3_update (state=<optimized out>, input=0x80 <error: Cannot access memory at address 0x80>, len=<optimized out>, f_acc=<optimized out>, f_scramble=<optimized out>) at ../neatvnc/include/xxhash.h:6282
#4  XXH3_64bits_update (state=<optimized out>, input=0x80, len=<optimized out>) at ../neatvnc/include/xxhash.h:6336
#5  damage_hash_tile (self=<optimized out>, tx=<optimized out>, ty=<optimized out>, buffer=<optimized out>) at ../neatvnc/src/damage-refinery.c:91
#6  damage_refine_tile (self=<optimized out>, refined=0x7fffffff3980, tx=<optimized out>, ty=<optimized out>, buffer=<optimized out>) at ../neatvnc/src/damage-refinery.c:109
#7  damage_refine (self=<optimized out>, refined=0x7fffffff3980, hint=0x80, buffer=<optimized out>) at ../neatvnc/src/damage-refinery.c:156
#8  nvnc_display_feed_buffer (self=<optimized out>, fb=<optimized out>, damage=damage@entry=0x7fffffff3a90) at ../neatvnc/src/display.c:128
#9  0x000055555555e468 in wayvnc_process_frame (self=0x7fffffff4230, buffer=0x5555555d55b0) at ../wayvnc/src/main.c:1148
#10 on_capture_done (result=<optimized out>, buffer=0x5555555d55b0, userdata=0x7fffffff4230) at ../wayvnc/src/main.c:1170
#11 0x0000555555560ff6 in screencopy_ready (data=0x5555555d1e10, frame=<optimized out>, sec_hi=<optimized out>, sec_lo=<optimized out>, nsec=<optimized out>) at ../wayvnc/src/screencopy.c:228
#12 0x00007ffff7b06596 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#13 0x00007ffff7b0300e in ffi_call_int (cif=cif@entry=0x7fffffff3d10, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>, closure=closure@entry=0x0) at ../src/x86/ffi64.c:673
#14 0x00007ffff7b05bd3 in ffi_call (cif=cif@entry=0x7fffffff3d10, fn=<optimized out>, rvalue=rvalue@entry=0x0, avalue=avalue@entry=0x7fffffff3de0) at ../src/x86/ffi64.c:710
#15 0x00007ffff7dbf8b0 in wl_closure_invoke (closure=closure@entry=0x5555555c7e30, target=<optimized out>, target@entry=0x5555555d1ef0, opcode=opcode@entry=0x2, data=<optimized out>, flags=0x1) at ../wayland-1.23.1/src/connection.c:1228
#16 0x00007ffff7dc0139 in dispatch_event (display=display@entry=0x5555555c1fd0, queue=queue@entry=0x5555555c20c8) at ../wayland-1.23.1/src/wayland-client.c:1674
#17 0x00007ffff7dc0553 in dispatch_queue (display=0x5555555c1fd0, queue=0x5555555c20c8) at ../wayland-1.23.1/src/wayland-client.c:1820
#18 wl_display_dispatch_queue_pending (display=0x5555555c1fd0, queue=0x5555555c20c8) at ../wayland-1.23.1/src/wayland-client.c:2062
#19 0x00007ffff7dc05c1 in wl_display_dispatch_pending (display=<optimized out>) at ../wayland-1.23.1/src/wayland-client.c:2125
#20 0x000055555556436d in on_wayland_event (obj=<optimized out>) at ../wayvnc/src/main.c:520
#21 0x00007ffff7dea61f in aml__handle_event (self=<optimized out>, obj=0x5555555c7230) at ../aml/src/aml.c:801
#22 aml_dispatch (self=self@entry=0x5555555c1d30) at ../aml/src/aml.c:853
#23 0x000055555555a470 in main (argc=<optimized out>, argv=<optimized out>) at ../wayvnc/src/main.c:2146

@wayzaction
Copy link

I've got almost absolutely the same stuff. Running wayvnc with --gpu flag results in crash with this log:

Info: Capturing output HDMI-A-1
Info: >> Samsung Electric Company LF27T35 H4ZR900240 (HDMI-A-1) 1920x1080+0x0 Power:UNKNOWN
DEBUG: ../wayvnc/src/ctl-server.c: 809: Initializing wayvncctl socket: /run/user/1000/wayvncctl
DEBUG: ../neatvnc/src/server.c: 2128: Trying address: 192.168.1.77
DEBUG: ../neatvnc/src/server.c: 2143: Successfully bound to address
Info: Listening for connections on 192.168.1.77:5900
Info: New client connection from 192.168.1.4: 0x57dca8b99050
DEBUG: ../neatvnc/src/server.c: 357: Client chose security type: 1
DEBUG: ../wayvnc/src/main.c: 1640: Configuring cursor capturing
DEBUG: ../wayvnc/src/main.c: 1656: Failed to capture cursor
Info: Starting screen capture
DEBUG: ../wayvnc/src/main.c: 1030: Acquired power state management. Waiting for power event to start capturing
DEBUG: ../wayvnc/src/main.c: 1383: Client connected, new client count: 1
DEBUG: ../wayvnc/src/ctl-server.c: 941: Enqueueing client-connected event: {"id":"1","address":"192.168.1.4","username":null,"seat":"Hyprland","connection_count":1}
DEBUG: ../wayvnc/src/ctl-server.c: 968: Enqueued client-connected event for 0 clients
Info: Client 0x57dca8b99050 initialised. MIN-RTT during handshake was 1 ms
DEBUG: ../wayvnc/src/buffer.c: 606: Reconfiguring buffer pool
DEBUG: ../wayvnc/src/buffer.c: 552: Using render node: /dev/dri/renderD128
DEBUG: ../neatvnc/src/server.c: 676: Client 0x57dca8b99050 set encodings: zrle,trle,hextile,rre,raw,copyrect,cursor,desktop-size
DEBUG: ../neatvnc/src/server.c: 539: Using color palette for client 0x57dca8b99050
DEBUG: ../neatvnc/src/server.c: 553: Client 0x57dca8b99050 chose pixel format: RGB222
Info: Choosing zrle encoding for client 0x57dca8b99050
DEBUG: ../neatvnc/src/server.c: 676: Client 0x57dca8b99050 set encodings: raw,zrle,trle,hextile,rre,copyrect,cursor,desktop-size
Info: Choosing raw encoding for client 0x57dca8b99050
DEBUG: ../neatvnc/src/server.c: 676: Client 0x57dca8b99050 set encodings: zrle,trle,hextile,rre,raw,copyrect,cursor,desktop-size
DEBUG: ../neatvnc/src/server.c: 539: Using color palette for client 0x57dca8b99050
DEBUG: ../neatvnc/src/server.c: 553: Client 0x57dca8b99050 chose pixel format: XRGB8888
Info: Choosing zrle encoding for client 0x57dca8b99050
[1]    1855 segmentation fault (core dumped)  wayvnc 192.168.1.77 5900 -Ltrace --gpu |
       1856 done                              tee wayvnc-crash.log

WayVnc Version:

wayvnc: v0.9.1-e4ec935 (makepkg)
neatvnc: v0.9.2-4c37ae9 (makepkg)
aml: v0.3.0-0-gb83f357 (makepkg)

@Ra2-IFV
Copy link
Author

Ra2-IFV commented Mar 14, 2025

Do we have enough information for now?

@any1
Copy link
Owner

any1 commented Mar 14, 2025

Neat VNC v0.9.4 has some bug fixes, so you're probably better off running that. However, I suspect that these may be due to out of bounds access to DMA-BUFs from the GPU.

@Ra2-IFV
Copy link
Author

Ra2-IFV commented Mar 30, 2025 via email

@Ra2-IFV
Copy link
Author

Ra2-IFV commented Mar 30, 2025 via email •
edited
Loading

@any1
Copy link
Owner

any1 commented Mar 30, 2025

Do you have multiple GPUs on the system?

@Ra2-IFV
Copy link
Author

Ra2-IFV commented Mar 30, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@net147 @any1 @Ra2-IFV @wayzaction