Zynthian Vangelis on V4
Sometimes (not always) it happens that Zynthian get frozen at start after pressing Select:
all buttons and switches do not respond but you can launch a reboot from Webconf
before rebooting can I do something to provide you more information, for example, by terminal?
Htop after it happens… Probably one cpu is at 100%. That’s useful.
This one is from a zynthian not doing a lot. . .
htop
These sorts of things are low level and there are normally no log entries to dissect.
But do have a look at logs…
There might be something relevant.
journalctl -fu zynthian
From those that dig into this sort of thing, what they need is a repeatable case.
So an exact set of steps that produced the fault.
If this involves loading an engine then it can be difficult to recreate situations.
But there are one or two quirks still in the guts that need flushing out.
@riban fixed the Chain Manager issue which was precisely of this type once it was able to be recreated.
in this moment Zynthian is frozen:
*root@zynthian://zynthian# journalctl -fu zynthian *
Jun 02 14:11:23 zynthian startx[3964]: ZynCore: Setting-up 4 x Zynpots (zyncoder
*s)… *
*Jun 02 14:11:23 zynthian startx[3964]: ZynCore->gpiod_start_callbacks: Callback *
*thread created successfully *
Jun 02 14:11:24 zynthian startx[3964]: Loaded libzynaudioplayer using libsndfile
*-1.2.0 *
*Jun 02 14:11:24 zynthian startx[3964]: Started zynmixer_chan *
*Jun 02 14:11:24 zynthian startx[3964]: Started zynmixer_bus *
*Jun 02 14:11:24 zynthian startx[3964]: Started libzynseq *
*Jun 02 14:11:24 zynthian startx[3964]: Started libzynsmf *
Jun 02 14:11:25 zynthian startx[3964]: WARNING:zynthian_autoconnect.cb_jack_xrun
*: Jack Audio XRUN! =>count: 1, delay: 72.0us *
Jun 02 14:11:25 zynthian startx[3964]: WARNING:zynthian_autoconnect.cb_jack_xrun
*: Jack Audio XRUN! =>count: 2, delay: 37641.0us *
Jun 02 14:11:25 zynthian startx[3964]: WARNING:zynthian_gui_brightness_config.in
it_ctrls: Can’t set display brightness!
Can you upload the snapshot?
sorry, done
If you need further info I stay in frozen status.
PS: I opened a ticket
after today update, now it seems fixed
Ooh! That’s exciting… but I am not sure what might have fixed it today or in recent commits!
I updated Zynthian on Saturday but the issue was still there.
Today update seems solving.
As I am preparing the song list of tomorrow concert (the first with Zynthian !!!) I am testing many snapshots and I will report if I have issues.
It is still broken. I just experienced it with my V4. It took a couple of reboots before it triggered and it was sitting for an hour or more after the last reboot before I tried the trigger. It had gone to low-power mode but pressing SELECT triggered the high CPU lockup.
I do not know if it is related, but Vangelis frequently - not always - hangs like this when adding the first chain. I do not think this ever happens when that hurdle was taken.
After the MIDI channel is selected, some other window briefly flashes, and then the UI returns to the MIDI channel selection screen - in a ftozen state.
The frozen MIDI channel selection window then can be either:
looking as usual, with the chosen channel selected or
having no selection at all. In this case, the red warning sign is present at the top rigjt of the screen.
@niels that is the same issue. (I am debugging and seeing the same trigger for both operations.) I am updating the ticket with debug progress. I am getting closer…
i remember similar issues some time ago, related with show_screen. The build_view can’t be concurrent and i added a lock.
