×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

atik filter wheel driver crashes

  • Posts: 4
  • Thank you received: 0
Hello i'm new to ekos / indi.
I tried to connect my mount, rotator, camera atik16200 with filter wheel EWF3 (7 Filter) and Lodstar X2 guiding camera with ekos.
Successfully connected was mount, camera atik 16200 and Lodstar X2(guiding camera) and rotator.

The connection to the filter wheel did not work...
I tried to start from console (see following result). First the message that a child process died. After that i add some lines from kernel log
which mentioned a segfault in libc-2.31.so. I'm using an Ubuntu 20.04.1 LTS 64 Bit. I add also a log from ekos session but i didn't see more infos as below written.

Has maybe someone an idea what's going wrong?

Many thanks for any help.

Klaus

$indiserver -vvv indi_atik_wheel
2021-01-07T16:26:11: startup: indiserver -vvv indi_atik_wheel
2021-01-07T16:26:11: Driver indi_atik_wheel: pid=25755 rfd=3 wfd=6 efd=7
2021-01-07T16:26:11: listening to port 7624 on fd 4
2021-01-07T16:26:11: Driver indi_atik_wheel: sending msg copy 1 nq 1:
<getProperties version='1.7'/>

2021-01-07T16:26:13: Driver indi_atik_wheel: stderr EOF
Child process 25755 died

2021-01-07T16:26:13: Driver indi_atik_wheel: restart #1
2021-01-07T16:26:13: Driver indi_atik_wheel: pid=25763 rfd=0 wfd=6 efd=7
2021-01-07T16:26:13: Driver indi_atik_wheel: sending msg copy 1 nq 1:
<getProperties version='1.7'/>

2021-01-07T16:26:13: Driver indi_atik_wheel: stderr EOF
Child process 25763 died
2021-01-07T16:26:13: Driver indi_atik_wheel: restart #2
2021-01-07T16:26:13: Driver indi_atik_wheel: pid=25771 rfd=0 wfd=6 efd=7
2021-01-07T16:26:13: Driver indi_atik_wheel: sending msg copy 1 nq 1:
<getProperties version='1.7'/>

2021-01-07T16:26:18: Driver indi_atik_wheel: stderr EOF
Child process 25771 died


out of /var/log/kern.log
Jan 7 17:26:13 kv-XPS-15-9560 kernel: [34344.408379] indi_atik_wheel[25755]: segfault at 0 ip 00007f33b01bab82 sp 00007fff8d9582f8 error 4 in libc-2.31.so[7f33b0059000+178000]
Jan 7 17:26:13 kv-XPS-15-9560 kernel: [34344.408396] Code: ff ff e9 01 80 f3 ff 90 f3 0f 1e fa 89 f8 31 d2 c5 c5 ef ff 09 f0 25 ff 0f 00 00 3d 80 0f 00 00 0f 8f 52 03 00 00 c5 fe 6f 0f <c5> f5 74 06 c5 fd da c1 c5 fd 74 c7 c5 fd d7 c8 85 c9 74 7a f3 0f
Jan 7 17:26:13 kv-XPS-15-9560 kernel: [34344.639321] indi_atik_wheel[25763]: segfault at 0 ip 00007eff9e16cb82 sp 00007ffca63cbbe8 error 4 in libc-2.31.so[7eff9e00b000+178000]
Jan 7 17:26:13 kv-XPS-15-9560 kernel: [34344.639330] Code: ff ff e9 01 80 f3 ff 90 f3 0f 1e fa 89 f8 31 d2 c5 c5 ef ff 09 f0 25 ff 0f 00 00 3d 80 0f 00 00 0f 8f 52 03 00 00 c5 fe 6f 0f <c5> f5 74 06 c5 fd da c1 c5 fd 74 c7 c5 fd d7 c8 85 c9 74 7a f3 0f
Jan 7 17:26:17 kv-XPS-15-9560 kernel: [34348.800220] usb usb4-port1: Cannot enable. Maybe the USB cable is bad?
Jan 7 17:26:17 kv-XPS-15-9560 kernel: [34348.868376] indi_atik_wheel[25771]: segfault at 0 ip 00007f6663f3cb82 sp 00007ffeee8da3a8 error 4 in libc-2.31.so[7f6663ddb000+178000]
Jan 7 17:26:17 kv-XPS-15-9560 kernel: [34348.868393] Code: ff ff e9 01 80 f3 ff 90 f3 0f 1e fa 89 f8 31 d2 c5 c5 ef ff 09 f0 25 ff 0f 00 00 3d 80 0f 00 00 0f 8f 52 03 00 00 c5 fe 6f 0f <c5> f5 74 06 c5 fd da c1 c5 fd 74 c7 c5 fd d7 c8 85 c9 74 7a f3 0f
3 years 3 months ago #65545
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 269
  • Thank you received: 53
Checking USB cable would be a good start. Can you see the filter wheel with lsusb?
3 years 3 months ago #65569

Please Log in or Create an account to join the conversation.

  • Posts: 4
  • Thank you received: 0
Hi, thanks for your reply....
That was the first thing i had done... Yes it is viewable within USB....
I also tried another usb cable... By the way the error occur even the filter wheel is not connected...

Thanks
Klaus

this is the result for the filter wheel from lsusb -v

Bus 001 Device 088: ID 04d8:003f Microchip Technology, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x04d8 Microchip Technology, Inc.
idProduct 0x003f
bcdDevice 0.02
iManufacturer 1 Atik Instruments
iProduct 2 Filter Wheel 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0029
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 29
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0001
Self Powered
3 years 3 months ago #65579

Please Log in or Create an account to join the conversation.

I think it's a good idea to contact Atik regarding this since it's probably related to their SDK.
3 years 3 months ago #65583

Please Log in or Create an account to join the conversation.

  • Posts: 4
  • Thank you received: 0
Hi Jasem,

thanks for your reply.
I did a request to the tec support of ATIK...

The answer (see below) was not very helpful.. To connect the filter wheel only will not change the behavior. This will also lead to the segfault..
Anyone who can help me??

Thanks in advance
Klaus



  • "Hello Klaus,

    Thanks for your enquiry,

    Unfortunately we can't really help you with this as we only support Windows.

    It would be worth connecting the FW on its own without the cameras to see if that changes its behaviour

    Best Regards,

    Andrew

    Atik / QSI / Opus Service
    Unit 8 Lodge Farm Barns
    New Road
    Bawburgh
    Norwich
    NR9 3LZ
    UK
  • 3 years 3 months ago #65789

    Please Log in or Create an account to join the conversation.

    • Posts: 11
    • Thank you received: 0
    Hello,
    I'm having +/- the same issue ('INDI Driver crashed' from Kstars/Ekos), but with some additional information.
    To simplify my tests I did a minimal setup for Ekos:
    • CCD: Starlight Xpress SX CCD
    • Filter: Atik EFW (2.2)
    Under Linux Mint 19.3 / Ubuntu 18.04 on my tower PC, it's working perfectly.
    Exact same setting under Linux Mint 20 / Ubuntu Focal Fossa on my laptop crashed the INDI driver.
    I did a lot of tests: different cables, with or without a USB 3.0 hub, main or battery powered, connection before or after the PC or Kstars.
    Results: works consistently on my tower and consistently crashing on my laptop.
    I did run the same test using ekos-debugger. Maybe an expert could have a look to the resulting small .txt log files attached.

    File Attachment:

    File Name: indi_app_l...5-02.txt
    File Size:3 KB

    File Attachment:

    File Name: indi_debug...5-02.txt
    File Size:1 KB


    I'm unfortunately unable to analyse the logs to understand the root of the problem (and even if there are useful information in there).
    Also: I have exactly the same .txt file related to successfull attempts on my tower PC, in case it can help.
    Can someone help us ?
    Best regards
    3 years 1 month ago #67615
    Attachments:

    Please Log in or Create an account to join the conversation.

    • Posts: 4
    • Thank you received: 0
    Hi Saturne33,

    please check your kern.log (ubuntu ==> /var/log/kern.log) and look for the message coming up

    As you can see on my log i get a segfault out of libc-2.31.so.

    out of /var/log/kern.log Jan 7 17:26:13 kv-XPS-15-9560 kernel: [34344.408379] indi_atik_wheel[25755]: segfault at 0 ip 00007f33b01bab82 sp 00007fff8d9582f8 error 4 in libc-2.31.so[7f33b0059000+178000]

    It seems that there was a change in this library since Ubuntu 18.x to 20.x. Maybe a rebuild will help but could also may cause older versions to no longer work.

    I would also be happy if someone could come up with a solution.

    regards
    Klaus

    3 years 1 month ago #67617

    Please Log in or Create an account to join the conversation.

    • Posts: 11
    • Thank you received: 0
    Hi Klaus,
    Thanks for your message. I just checked the kern.log:
    On my laptop:
    Feb 21 15:21:35 didier-XPS-13-9343 kernel: [10250.013177] indi_atik_wheel[4610]: segfault at 0 ip 00007f231104cb82 sp 00007ffdc64eaef8 error 4 in libc-2.31.so[7f2310eeb000+178000]

    On my tower PC:
    No such 'segfault' message.

    Hoping that it may speaks to some experts to trigger a fixing...
    Best regards
    3 years 1 month ago #67623

    Please Log in or Create an account to join the conversation.

    • Posts: 10
    • Thank you received: 1
    I can reproduce this error exactly (on both 20.04 and 21.04, as well as on Fedora 33), and nothing provided by Atik seems to address the issue:

    Apr 24 22:30:29 astrolaptop kernel: [ 382.645496] indi_atik_wheel[3117]: segfault at 0 ip 00007f32893eab82 sp 00007ffd7acaa318 error 4 in libc-2.31.so[7f3289289000+178000]
    Apr 24 22:30:29 astrolaptop kernel: [ 382.645508] Code: ff ff e9 01 80 f3 ff 90 f3 0f 1e fa 89 f8 31 d2 c5 c5 ef ff 09 f0 25 ff 0f 00 00 3d 80 0f 00 00 0f 8f 52 03 00 00 c5 fe 6f 0f <c5> f5 74 06 c5 fd da c1 c5 fd 74 c7 c5 fd d7 c8 85 c9 74 7a f3 0f
    2 years 11 months ago #70504

    Please Log in or Create an account to join the conversation.

    • Posts: 10
    • Thank you received: 1
    Ok, so I have a partial workaround, but it's pretty clunky.

    Idea 1: Run another instance of indiserver in docker with Ubuntu 18.04, and connect to EFW remotely
    Problem: For reasons I only vaguely understand, docker doesn't sufficiently isolate the broken Atik library from the newer kernel, so the crash persists

    Idea 2: From a modern OS like Ubuntu 20.04, download Gnome Boxes and set up an Ubuntu 18.04 virtual machine, enable access to the EFW USB device in "preferences", install indiserver, and connect to the EFW remotely
    Problem: While this works within the VM, the driver on the client still crashes with a segfault even when connecting remotely. Is there a way in indi to connect to a remote driver without having the driver installed on a client?

    Idea 3: Give up on automatic control of the EFW, and just run a parallel instance of kstars in the 18.04 VM to control it.
    Problem: This obviously sucks, but at least it does work.

    I've messaged Atik about this, but only time will tell if they're willing to rebuild their driver for a non-archaic kernel. In the meantime:

    1. I might need to learn how to use wireshark to figure out how to talk to the EFW and write a proper open source driver. It's a pretty simple device after all...
    2. Does anyone know of solutions to the remote driver crash? That would be a decent workaround if it could be made to work.
    2 years 11 months ago #70521

    Please Log in or Create an account to join the conversation.

    • Posts: 456
    • Thank you received: 76
    I have the same problem. It was working fine until I did an update of kstars.
    Here's my kernel log

    Apr 25 22:25:47 hp-elite kernel: [   86.634417] aufs au_opts_verify:1623:dockerd[2778]: dirperm1 breaks the protection by the permission bits on the lower branch
    Apr 25 22:27:07 hp-elite kernel: [  166.683503] usb 3-2: new full-speed USB device number 4 using xhci_hcd
    Apr 25 22:27:07 hp-elite kernel: [  166.838512] usb 3-2: New USB device found, idVendor=0403, idProduct=6015
    Apr 25 22:27:07 hp-elite kernel: [  166.838516] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    Apr 25 22:27:07 hp-elite kernel: [  166.838518] usb 3-2: Product: FT230X Basic UART
    Apr 25 22:27:07 hp-elite kernel: [  166.838520] usb 3-2: Manufacturer: FTDI
    Apr 25 22:27:07 hp-elite kernel: [  166.838521] usb 3-2: SerialNumber: DN05ROJB
    Apr 25 22:27:07 hp-elite kernel: [  166.841793] ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected
    Apr 25 22:27:07 hp-elite kernel: [  166.841838] usb 3-2: Detected FT-X
    Apr 25 22:27:07 hp-elite kernel: [  166.842245] usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB1
    Apr 25 22:27:07 hp-elite kernel: [  167.011484] usb 3-1.1: new high-speed USB device number 5 using xhci_hcd
    Apr 25 22:27:07 hp-elite kernel: [  167.211601] usb 3-1.1: New USB device found, idVendor=20e7, idProduct=df31
    Apr 25 22:27:07 hp-elite kernel: [  167.211605] usb 3-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
    Apr 25 22:27:07 hp-elite kernel: [  167.535505] usb 3-1.3: new full-speed USB device number 6 using xhci_hcd
    Apr 25 22:27:08 hp-elite kernel: [  167.738476] usb 3-1.3: New USB device found, idVendor=04d8, idProduct=003f
    Apr 25 22:27:08 hp-elite kernel: [  167.738480] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    Apr 25 22:27:08 hp-elite kernel: [  167.738482] usb 3-1.3: Product: Filter Wheel 2
    Apr 25 22:27:08 hp-elite kernel: [  167.738484] usb 3-1.3: Manufacturer: Atik Instruments
    Apr 25 22:27:08 hp-elite kernel: [  168.009718] hidraw: raw HID events driver (C) Jiri Kosina
    Apr 25 22:27:08 hp-elite kernel: [  168.021838] usbcore: registered new interface driver usbhid
    Apr 25 22:27:08 hp-elite kernel: [  168.021839] usbhid: USB HID core driver
    Apr 25 22:27:08 hp-elite kernel: [  168.160085] hid-generic 0003:04D8:003F.0001: hiddev0,hidraw0: USB HID v1.11 Device [Atik Instruments Filter Wheel 2] on usb-0000:00:14.0-1.3/input0
    Apr 25 22:52:07 hp-elite kernel: [ 1667.199610] kstars[1998]: segfault at 6c ip 0000560b009d1c7d sp 00007ffc274b4e40 error 4 in kstars[560b005de000+d23000]
    2 years 11 months ago #70547

    Please Log in or Create an account to join the conversation.

    • Posts: 456
    • Thank you received: 76
    Actually my issue could be something else. I also cannot connect to my SX CCD or my Atik 383L+ camera after updating.
    2 years 11 months ago #70548

    Please Log in or Create an account to join the conversation.

    Time to create page: 0.721 seconds