JVM Crash with Z-wave Dongle reset?

Add-ons Bindings
1

So I suspect it’s the Z-Wave USB dongle that is the issue? ZwaveMe USB

But any ideas before I get a new one and have to reconfigure my network :- ( (Any recommendations on a new controller)

I see that it disappears from the system, /dev/ttyACM0 goes, and reappears as a new device /dev/ttyACM1

Sep 03 22:25:25 openhab kernel: usb 1-1.4: USB disconnect, device number 4
Sep 03 22:25:26 openhab kernel: usb 1-1.4: new full-speed USB device number 5 using xhci_hcd
Sep 03 22:25:26 openhab kernel: usb 1-1.4: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
Sep 03 22:25:26 openhab kernel: usb 1-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 03 22:25:26 openhab kernel: cdc_acm 1-1.4:1.0: ttyACM1: USB ACM device
Sep 03 22:25:26 openhab mtp-probe[23334]: checking bus 1, device 5: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4"
Sep 03 22:25:26 openhab mtp-probe[23334]: bus: 1, device: 5 was not an MTP device
Sep 03 22:25:26 openhab mtp-probe[23335]: checking bus 1, device 5: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4"
Sep 03 22:25:26 openhab mtp-probe[23335]: bus: 1, device: 5 was not an MTP device
Sep 03 22:25:30 openhab karaf[579]: #
Sep 03 22:25:30 openhab karaf[579]: # A fatal error has been detected by the Java Runtime Environment:
Sep 03 22:25:30 openhab karaf[579]: #
Sep 03 22:25:30 openhab karaf[579]: #  SIGSEGV (0xb) at pc=0xb6801968, pid=579, tid=1010
Sep 03 22:25:30 openhab karaf[579]: #
Sep 03 22:25:30 openhab karaf[579]: # JRE version: OpenJDK Runtime Environment Zulu11.52+13-CA (11.0.13+8) (build 11.0.13+8-LTS)
Sep 03 22:25:30 openhab karaf[579]: # Java VM: OpenJDK Client VM Zulu11.52+13-CA (11.0.13+8-LTS, mixed mode, serial gc, linux-arm)
Sep 03 22:25:30 openhab karaf[579]: # Problematic frame:
Sep 03 22:25:30 openhab karaf[579]: # V  [libjvm.so+0x276968]  frame::sender_for_interpreter_frame(RegisterMap*) const+0xc0
Sep 03 22:25:30 openhab karaf[579]: #
Sep 03 22:25:30 openhab karaf[579]: # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
Sep 03 22:25:30 openhab karaf[579]: #
Sep 03 22:25:30 openhab karaf[579]: # An error report file with more information is saved as:
Sep 03 22:25:30 openhab karaf[579]: # /var/lib/openhab/hs_err_pid579.log
Sep 03 22:25:30 openhab karaf[579]: #
Sep 03 22:25:30 openhab karaf[579]: # If you would like to submit a bug report, please visit:
Sep 03 22:25:30 openhab karaf[579]: #   http://www.azul.com/support/
Sep 03 22:25:30 openhab karaf[579]: #

This seems to cause the JVM to crash.

any pointers on what to do?

2

Not an expert, but what looks odd is that mtp-probe messages. I have had my zstick in and out of my Pi3 and get your first five lines in dmesg only

[146880.495118] usb 1-1.3: USB disconnect, device number 4
[147324.187412] usb 1-1.3: new full-speed USB device number 5 using dwc_otg
[147324.320792] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[147324.320818] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[147324.324225] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
[242361.841417] usb 1-1.3: USB disconnect, device number 5
[244074.009538] usb 1-1.3: new full-speed USB device number 6 using dwc_otg
[244074.142840] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[244074.142866] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[244074.146629] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
[500813.044197] usb 1-1.3: USB disconnect, device number 6
[501945.011140] usb 1-1.3: new full-speed USB device number 7 using dwc_otg
[501945.144501] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[501945.144527] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[501945.145751] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
[505114.870203] usb 1-1.3: USB disconnect, device number 7
[505510.278834] usb 1-1.3: new full-speed USB device number 8 using dwc_otg
[505510.422136] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[505510.422162] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[505510.423380] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
[1371629.306849] usb 1-1.3: USB disconnect, device number 8
[1371750.178490] usb 1-1.3: new full-speed USB device number 9 using dwc_otg
[1371750.311777] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[1371750.311799] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[1371750.315721] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
[1635665.661657] usb 1-1.3: USB disconnect, device number 9
[1636097.465993] usb 1-1.3: new full-speed USB device number 10 using dwc_otg
[1636097.599334] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[1636097.599359] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[1636097.602328] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device

As to a new device, and depending on your zwave version, you can use a PC and the Silabs PC controller tool to copy your network to a zip file and then with the new zstick write your network back. With older versions you might have to use the Zensus PC backup tool. I have a Zooz controller (500 chip) and also use the silabs static controller from digikey.

3

Maybe this posting helps in pinning down the port to a fixed name

1 Like