Is there a hardware reset procedure?

[J.Luszczek]

I left the Raspberry Pi running today for about 10 hours and when I got home the audio was not working. The Octo is still recognized as ALSA device, but inputs 1-4 are totally silent, while inputs 5-6 have noise on them with nothing plugged in. The noise is around -58dB. Jack is not starting either.

Is there a command or some procedure to reset the card? Or, am I out of luck and have a dead card?

I noticed that my menus were re-organized, items removed, etc. So It's possible that this is software issue. Does Raspberry Pi update itself with no confirmation needed?

[ktb]

I don't know of a reset procedure for the Octo. Does dmesg have anything interesting to say?

Have you tried rebooting? Does sound work then? It would be interesting see dmesg output before you tried rebooting (after the problem occurred) and after rebooting.

What power supply are you using to power the Pi (model?)?

Raspbian doesn't normally do any sort of automatic updates. The menu changes seem odd. You might try deleting everything in the ~/.cache directory to see if the menus return to normal. Did the X server/session crash? Is it possible some application you were running was leaking memory?

[J.Luszczek]

I don't know of a reset procedure for the Octo. Does dmesg have anything interesting to say?

Actually yes. Looks like some sort of sync issue.
Here are the last 4 lines:

[ 65.871605] random: crng init done
[ 286.137709] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[ 286.139103] bcm2835-i2s 3f203000.i2s: I2S SYNC error!
[ 393.774078] bcm2835-dma 3f007000.dma: DMA transfer could not be terminated


I did reboot couple of times with no change.
The power supply is a 2.5A 5.0V CanaKit.

I will try the cache cleanup and report back.

Thanks for all the suggestions.

[J.Luszczek]

Here is my JACK Control log. It's the same every time I try to run it.

21:40:20.319 Patchbay deactivated.
21:40:20.321 Statistics reset.
21:40:20.345 ALSA connection change.
21:40:20.360 JACK is starting...
21:40:20.361 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p256 -n3 -i6 -o8 -zs
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
21:40:20.379 ALSA connection graph change.
21:40:20.476 JACK was started with PID=19247.
jackdmp 1.9.10
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|256|3|48000|6|8|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 256 frames (5.3 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: cannot set channel count to 6 for capture
ALSA: cannot configure capture channel
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server
21:40:20.814 JACK was stopped
21:40:22.576 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started

[ktb]

I get the "I2S SYNC error!" messages also, but my Octo seems to mostly be working. flatmax said those messages were nothing to worry about and they occur with all I2S sound cards on the Pi's. I get the DMA transfer could not be terminated" messages as well, and from what I've read those might indicate a legitimate kernel/firmware problem. I don't think they're specific to the Octo, but I could be wrong. And again my Octo is mostly working OK despite those messages. I say mostly because I've had some power supply issues that I don't think I can blame on the Octo.

[flatmax]

Yep, I can confirm what KTB has mentioned.

With jackd, best to open with 8 outputs and 8 inputs. Two of the inputs will be empty channels.

Sounds like a curious problem you experienced. What does cat /proc/version report ? Which kernel version ?

Not sure how to help you exactly, so lets discuss this a little more.

How many cards are registered ? What does your /boot/config.txt look like for audio overlays and audio related entries ?

thanks
Matt

[J.Luszczek]

I'm back in business. I basically reinitialized my Pi and started from scratch.
I don't know what happened. I can only speculate that the one audio related repository that I added to my system in order to download some plugins and hosts was responsible.
I might have added some software that is not compatible with the Pi and it scrambled some audio settings.
For now I'm sticking with Reaper and its native plugins because it's really stable, efficient and it has everything I need to make crossovers.
If I need some additional features in the future, I will be more careful what I'm installing.

Thanks for all your help.