Hello,

Working on the artiq-system in Eindhoven, I ran into the following problem. Help is welcome, let me know if more debug information is required.

Description
On windows 10 PC, I upgraded the Artiq software from v7.8116 to Artiq v7.8123 and now can no longer run led.py on our QUARTIQ/SINARA system. The following error occurs:

ConnectionResetError: Core device connection closed unexpectedly

However going back to the old software version, there is no problem. Also connecting & running it via linux does work.
Furthermore if I run artiq_coremgmt log, I see the following:
[676541.526912s] INFO(kernel): panic at ksupport/lib.rs:523:5: Exception(LoadFault) at PC 0x450602a4, trap value 0x45061014
[676541.536888s] ERROR(runtime::session): session aborted: unexpected request RunAborted from kernel CPU

How can I prevent the device from quitting unexpectedly with the latest artiq software version?

System
Windows 10, Artiq v7.8123
hardware: QUARTIQ/SINARA eindhoven version

Longer Error report
(artiqt3) C:\Users\farubidium\Documents\artiqTryout>artiq_run led.py
Traceback (most recent call last):
File "C:\Users\farubidium\Anaconda3\envs\artiqt3\Scripts\artiq_run-script.py", line 9, in <module>
sys.exit(main())
File "C:\Users\farubidium\Anaconda3\envs\artiqt3\lib\site-packages\artiq\frontend\artiq_run.py", line 224, in main
return run(with_file=True)
File "C:\Users\farubidium\Anaconda3\envs\artiqt3\lib\site-packages\artiq\frontend\artiq_run.py", line 210, in run
raise exn
File "C:\Users\farubidium\Anaconda3\envs\artiqt3\lib\site-packages\artiq\frontend\artiq_run.py", line 203, in run
exp_inst.run()
File "C:\Users\farubidium\Anaconda3\envs\artiqt3\lib\site-packages\artiq\language\core.py", line 54, in run_on_core
return getattr(self, arg).run(run_on_core, ((self,) + k_args), k_kwargs)
File "C:\Users\farubidium\Anaconda3\envs\artiqt3\lib\site-packages\artiq\coredevice\core.py", line 140, in run
self._run_compiled(kernel_library, embedding_map, symbolizer, demangler)
File "C:\Users\farubidium\Anaconda3\envs\artiqt3\lib\site-packages\artiq\coredevice\core.py", line 130, in _run_compiled
self.comm.serve(embedding_map, symbolizer, demangler)
File "C:\Users\farubidium\Anaconda3\envs\artiqt3\lib\site-packages\artiq\coredevice\comm_kernel.py", line 706, in serve
self._read_header()
File "C:\Users\farubidium\Anaconda3\envs\artiqt3\lib\site-packages\artiq\coredevice\comm_kernel.py", line 249, in _read_header
sync_byte = self._read(1)[0]
File "C:\Users\farubidium\Anaconda3\envs\artiqt3\lib\site-packages\artiq\coredevice\comm_kernel.py", line 237, in _read
raise ConnectionResetError("Core device connection closed unexpectedly")
ConnectionResetError: Core device connection closed unexpectedly

    RianneSL I upgraded the Artiq software from v7.8116 to Artiq v7.8123

    Is any of those versions a beta version? (The full version string would tell)
    If so, you might need to also keep the firmware in sync.

    Full string is v7.8123.3038639 and the older v7.8116.eba143a. Will have look at which firmware version we are having, and try to do a firmware upgrade in the afternoon

    May well be unrelated, but I'm also seeing faults (StoreFaults) on simple experiments with ARTIQ beta, i.e. current master. These do a loop and and usually fault after within minutes. I'll try minimizing.

    [     2.679476s]  INFO(board_artiq::si5324):   ...locked
    [     2.683115s]  INFO(runtime::rtio_clocking::crg): Using internal RTIO clock
    [     2.715512s]  INFO(runtime): network addresses: MAC=80-1f-12-7c-86-ed IPv4=10.34.16.100 IPv6-LL=fe80::821f:12ff:fe7c:86ed IPv6=no configured address
    [     2.729405s]  INFO(runtime::mgmt): management interface active
    [     2.755642s]  INFO(runtime::session): accepting network sessions
    [     2.768724s]  INFO(runtime::session): running startup kernel
    [     2.773171s]  INFO(runtime::session): no startup kernel found
    [     2.778979s]  INFO(runtime::session): no connection, starting idle kernel
    [     2.785807s]  INFO(runtime::session): no idle kernel found
    [   540.236063s]  INFO(runtime::session): new connection from 10.34.16.10:44810
    [   570.834796s]  INFO(kernel): panic at ksupport/lib.rs:523:5: Exception(StoreFault) at PC 0x450000e0, trap value 0x45069000
    [   570.844879s] ERROR(runtime::session): session aborted: unexpected request RunAborted from kernel CPU
    [   570.855193s]  INFO(runtime::session): no connection, starting idle kernel
    [   570.860862s]  INFO(runtime::session): no idle kernel found
    [   757.514659s]  INFO(runtime::session): new connection from 10.34.16.10:36504
    [   784.696305s]  INFO(runtime::session): no connection, starting idle kernel
    [   784.702071s]  INFO(runtime::session): no idle kernel found
    [   787.567344s]  INFO(runtime::session): new connection from 10.34.16.10:56294
    [   827.447082s]  INFO(runtime::session): no connection, starting idle kernel
    [   827.452850s]  INFO(runtime::session): no idle kernel found
    [   830.064125s]  INFO(runtime::session): new connection from 10.34.16.10:36842
    [   860.606540s]  INFO(runtime::session): no connection, starting idle kernel
    [   860.612303s]  INFO(runtime::session): no idle kernel found
    [   863.319597s]  INFO(runtime::session): new connection from 10.34.16.10:47246
    [  1059.319679s]  INFO(runtime::session): no connection, starting idle kernel
    [  1059.325447s]  INFO(runtime::session): no idle kernel found
    [  1093.426273s]  INFO(runtime::session): new connection from 10.34.16.10:53902
    [  1152.862769s]  INFO(kernel): panic at ksupport/lib.rs:523:5: Exception(StoreFault) at PC 0x450000e0, trap value 0x45069000
    [  1152.872846s] ERROR(runtime::session): session aborted: unexpected request RunAborted from kernel CPU
    [  1152.883117s]  INFO(runtime::session): no connection, starting idle kernel
    [  1152.888781s]  INFO(runtime::session): no idle kernel found
    [  1238.428273s]  INFO(runtime::session): new connection from 10.34.16.10:58780
    [  1243.557733s]  INFO(runtime::session): no connection, starting idle kernel
    [  1243.563502s]  INFO(runtime::session): no idle kernel found

    Current firmware=7.8123.3038639, however error remains
    The old firmware was 7.8116.eba143a

    20 days later

    Thank you @jpagett; this indeed worked! So for the solution/work around see above mentioned post.