Ran into an issue last night when plugging in my 40h for the first time in years where serialosc.maxpat was behaving erratically after plugging in the 40h. Running ps aux | grep serialosc showed that the 128 was discovered and connected correctly, but there was no process for the 40h.
After restarting the computer (this morning), I plugged my USB hub in, and which caught the 128 correctly, then crashed, and finally found the 40h on relaunch:
rkn11a:~() $ ps aux | grep serialosc 07.01.2017 [13:23:56]
kevin 361 0.0 0.0 2461544 1124 ?? U 1:23PM 0:00.00 /usr/local/bin/serialosc-detector
kevin 348 0.0 0.0 2462764 920 ?? S 1:23PM 0:00.01 /usr/local/bin/serialoscd
kevin 737 0.0 0.0 2443032 704 s000 R+ 1:24PM 0:00.00 grep serialosc
rkn11a:~() $ ps aux | grep serialosc 07.01.2017 [13:24:03]
kevin 361 0.0 0.0 2461544 1124 ?? U 1:23PM 0:00.00 /usr/local/bin/serialosc-detector
kevin 348 0.0 0.0 2462764 936 ?? S 1:23PM 0:00.01 /usr/local/bin/serialoscd
kevin 748 0.0 0.0 2434840 688 s000 R+ 1:24PM 0:00.00 grep serialosc
kevin 744 0.0 0.0 2446272 928 ?? S 1:24PM 0:00.01 /usr/local/bin/serialosc-devic /dev/tty.usbserial-m128-361
rkn11a:~() $ ps aux | grep serialosc 07.01.2017 [13:24:05]
kevin 768 0.0 0.0 2434840 676 s000 R+ 1:24PM 0:00.00 grep serialosc
rkn11a:~() $ ps aux | grep serialosc 07.01.2017 [13:24:10]
kevin 851 0.0 0.0 2433816 596 s000 R+ 1:24PM 0:00.00 grep serialosc
rkn11a:~() $ ps aux | grep serialosc 07.01.2017 [13:24:11]
kevin 919 0.0 0.0 2453272 824 s000 S+ 1:24PM 0:00.00 grep serialosc
kevin 892 0.0 0.0 2453440 916 ?? S 1:24PM 0:00.00 /usr/local/bin/serialosc-devic /dev/tty.usbserial-m128-361
kevin 891 0.0 0.0 2445248 912 ?? S 1:24PM 0:00.00 /usr/local/bin/serialosc-devic /dev/tty.usbserial-m40h0093
kevin 888 0.0 0.0 2453352 1128 ?? S 1:24PM 0:00.00 /usr/local/bin/serialosc-detector
kevin 887 0.0 0.0 2462764 932 ?? S 1:24PM 0:00.01 /usr/local/bin/serialoscd
Crash report
There were actually two crash reports in console, but they both show the same trace, at handle_device_msg + 20, so I've only included one of them here
tl;dr - It looks like there's a crash in
handle_device_msg
Background
Ran into an issue last night when plugging in my 40h for the first time in years where
serialosc.maxpat
was behaving erratically after plugging in the 40h. Runningps aux | grep serialosc
showed that the 128 was discovered and connected correctly, but there was no process for the 40h.After restarting the computer (this morning), I plugged my USB hub in, and which caught the 128 correctly, then crashed, and finally found the 40h on relaunch:
Crash report
There were actually two crash reports in console, but they both show the same trace, at
handle_device_msg + 20
, so I've only included one of them here