rtsoliday

Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • in reply to: Green screen after updating to 6.10.12 #27553
    rtsoliday
    Participant

    I updated to the latest drivers and tested it with hardware decoding. Got the green screen still. I’m fine with this disabled.

    in reply to: Green screen after updating to 6.10.12 #27544
    rtsoliday
    Participant

    Update, I have tried again and got it to work. Clicking “Disable client side hardware decoding” leaves a green screen, however if I disconnect and then reconnect, it works. I’m including the compressed log file from when it was a green screen just in-case it helps at all.

    Attachments:
    in reply to: Green screen after updating to 6.10.12 #27500
    rtsoliday
    Participant

    I have found an older version in my Downloads directory. After uninstalling the new version, rebooting, removing the .nx directory, installing the old version and deleting all my old sessions, it is working again. I have also disabled the auto-update for now.

    in reply to: Green screen after updating to 6.10.12 #27499
    rtsoliday
    Participant

    I am attaching the log files.

    in reply to: Green screen after updating to 6.10.12 #27498
    rtsoliday
    Participant

    I also am stuck at a green screen now. I have two monitors remotely and locally. All 1920 x 1200. This was not a problem with the previous version. I was able to get one session spanning both monitors. Now I get a green screen regardless of the client side hardware decoding being selected or not.

    in reply to: Virtual memory question #22702
    rtsoliday
    Participant

    The session file and the request for the debugging version has been sent to the email. Thanks.

    in reply to: Virtual memory question #22668
    rtsoliday
    Participant

    (gdb) b mmap64 if $rsi=47244640256
    Breakpoint 1 at 0x7f29b2f2c330
    (gdb) c
    Continuing.
    [New Thread 0x7f2980ff9700 (LWP 2786)]
    [Switching to Thread 0x7f29a37fe700 (LWP 29781)]

    Breakpoint 1, 0x00007f29b2f2c330 in mmap64 () from /lib64/libc.so.6
    (gdb) bt
    #0  0x00007f29b2f2c330 in mmap64 () from /lib64/libc.so.6
    #1  0x00007f29b2eb5ca2 in sysmalloc () from /lib64/libc.so.6
    #2  0x00007f29b2eb6aba in _int_malloc () from /lib64/libc.so.6
    #3  0x00007f29b2eb91ac in malloc () from /lib64/libc.so.6
    #4  0x00007f29b19a59f8 in operator new(unsigned long) () from /usr/NX/lib/libstdc++.so.6
    #5  0x00007f29b17161fb in NXShadowCreate () from /usr/NX/lib/libnxdimi.so
    #6  0x00007f29b3c16fc0 in nxagentShadowInit () from /usr/NX/lib/libnxdiag.so
    #7  0x00007f29b3bf7a5b in nxagentShadowClientCallback () from /usr/NX/lib/libnxdiag.so
    #8  0x00007f29b14045dc in _CallCallbacks () from /usr/NX/lib/libnxdifb.so
    #9  0x00007f29b13ff1df in NextAvailableClient () from /usr/NX/lib/libnxdifb.so
    #10 0x00007f29b146fced in ?? () from /usr/NX/lib/libnxdifb.so
    #11 0x00007f29b1470d7e in EstablishNewConnections () from /usr/NX/lib/libnxdifb.so
    #12 0x00007f29b1404101 in ProcessWorkQueue () from /usr/NX/lib/libnxdifb.so
    #13 0x00007f29b146a898 in WaitForSomething () from /usr/NX/lib/libnxdifb.so
    #14 0x00007f29b13ff677 in Dispatch () from /usr/NX/lib/libnxdifb.so
    #15 0x00007f29b13ecb1b in _NXDisplayMain () from /usr/NX/lib/libnxdifb.so
    #16 0x00007f29b2424844 in ?? () from /usr/NX/lib/libnxc.so
    #17 0x00007f29b3208dd5 in start_thread () from /lib64/libpthread.so.0
    #18 0x00007f29b2f31ead in clone () from /lib64/libc.so.6

    (gdb) p $rsi
    $1 = 47244640256
    (gdb) p $rdx
    $2 = 3
    (gdb) p $rcx
    $3 = 34
    (gdb) p $r8
    $4 = 4294967295

    I didn’t see anything related to 4294967295 in the lsof output, but here it is:
    https://ops.aps.anl.gov/downloads/nxnode.lsof.txt

    in reply to: Virtual memory question #22656
    rtsoliday
    Participant

    Here is is before I connect:
    https://ops.aps.anl.gov/downloads/nxnode.pmap.initial.txt

    And here it is after I connect and disconnect:
    https://ops.aps.anl.gov/downloads/nxnode.pmap.txt

    You can see a huge memory chunk at:
    0000000200000000 46137344K —–   [ anon ]

Viewing 8 posts - 1 through 8 (of 8 total)