I've got a brand new QHY 5L-II mono and I'm trying to capture and image in the Ekos CCD dialog with the default settings. Sadly everytime I run the sequence the qhy driver crashes. I've tried using the newest ubuntu packages and compiling the git version of libindi myself, no difference. I've attached the gdb output and my dmesg logs.
I would gladly help out with more logs and testing if needed.
I'd be interested in any views on this as I have a similar issue with QHY5-II-M, my segfault also being in memcpy (see journal below). The issue occurs the moment I attempt to grab an image. This is with latest indilib and 3rd party drivers (retrieved from github a few days ago).
Since QHY was just as troublesome when I paused working on this 6 months ago, I'm wondering if it's time to give up on QHY and find another CCD that is similar but less troublesome. Views?
Dec 3114:50:37 AstroOne kernel: usb 2-1.1.1: New USB device found, idVendor=1618, idProduct=0921
Dec 3114:50:37 AstroOne kernel: usb 2-1.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 3114:50:37 AstroOne kernel: usb 2-1.1.1: Product: QHY5-II
Dec 3114:50:37 AstroOne kernel: usb 2-1.1.1: Manufacturer: QHY-CCD
Dec 3114:51:19 AstroOne systemd[1]: Started Indi server.
Dec 3114:51:19 AstroOne indiserver[868]: 2016-12-31T14:51:19: Driver indi_eqmod_telescope: EnumeratePlugins - found plugin SVD Math Plugin
Dec 3114:51:29 AstroOne indiserver[868]: 2016-12-31T14:51:29: Driver indi_qhy_ccd: recorder: setpixelformat 1497715271
Dec 3114:51:29 AstroOne indiserver[868]: 2016-12-31T14:51:29: Driver indi_qhy_ccd: recorder: setsize 1280x1024
Dec 3114:51:29 AstroOne indiserver[868]: 2016-12-31T14:51:29: Driver indi_qhy_ccd: recorder: setsize 1280x1024
Dec 3114:51:47 AstroOne systemd[1]: Started Process Core Dump (PID 880/UID 0).
Dec 3114:51:49 AstroOne indiserver[868]: 2016-12-31T14:51:49: Driver indi_qhy_ccd: stdin EOF
Dec 3114:51:49 AstroOne indiserver[868]: 2016-12-31T14:51:49: Driver indi_qhy_ccd: restart #1
Dec 3114:51:49 AstroOne indiserver[868]: Child process 871 died
Dec 3114:51:49 AstroOne indiserver[868]: 2016-12-31T14:51:49: select(18): Interrupted system call
Dec 3114:51:49 AstroOne indiserver[868]: 2016-12-31T14:51:49: good bye
Dec 3114:51:49 AstroOne systemd[1]: indi.service: Main process exited, code=exited, status=1/FAILURE
Dec 3114:51:49 AstroOne systemd[1]: indi.service: Unit entered failed state.
Dec 3114:51:49 AstroOne systemd[1]: indi.service: Failed with result 'exit-code'.
Dec 3114:51:50 AstroOne systemd-coredump[881]: Process 871(indi_qhy_ccd) of user 0 dumped core.
Stack trace of thread 871:
#0 0x000000006d81db20 memcpy (libc.so.6)
I experienced INDI crashing issue under the most recent stable Kubuntu. Everything worked fine before on other machines and software. For a while I solved the problem by using Lin-Guider instead of internal guiding utility. Now I switched to Ubuntu MATE and problem disappeared. Laptop and other hardware is identical.
Ubuntu Mate has also other advantage - it's available in several variants supporting various hardware, including Raspberry Pi (see latest tutorial - it's really working and last test I made proved usable response, download time for QHY9s is around 10s which is almost as fast as download time on fast notebook: core i7, 8GB RAM...).
I'm not running on a desktop or a Raspberry Pi I'm afraid, I'm on a Hummingboard Pro (a bit like a Pi but with a different processor and much faster IO) with Arch Linux. It isn't Indi that is crashing (though that is the net effect), it's the indi_qhy driver with what looks like a buffer overrun. Changing my Linux distribution to fix it seems like over kill.