Allo Piano, Allo Kali incompatibility with the official Raspberry Pi kernel 6.6.56 or newer

Help and Support
41

The most recent update did not work for me, so I am doing a fresh install on my RPi 3 Model B.

After burning the image of v3.779 to a fresh SD card, my RPi 3 Model B boots up fine, connects to the network, and is assigned an address, but I cannot connect to it via the webUI.

Specifically, although I normally run Volumio headless, I have booted with a monitor attached to see what’s happening, and the bootup seems fine, taking me to a login prompt with the message ‘WebUI available at volumio.local (192.168.0.145)’
Unfortunately, I’m not able to connect to the WebUI via either volumio.local or via 192.168.0.145 (tried both http and https for both). Therefore I’m stuck with an RPi brick.

Any advice on how to make the WebUI connection, or any other way to move through the install, would be appreciated.

Some more info:
-I’m using an eero router, and the RPi is hardwired to the network
-The router shows that ‘volumio’ device is connected, and has the address 192.168.0.145 (consistent with the login screen)
-ping’ing the address gets a response
-ssh’ing to the address tells me that the connection is refused (also seems to indicate the host is up)
-I’m trying to connect via mac and iPhone (both connecting on WiFi)
-the volumio iPhone app that ‘looks for’ volumio devices on the network also cannot find the device either (just endless looping on the screen)
-previously I have disabled WiFi and bluetooth on this RPi, and I’m guessing that those settings will have stuck

Finally, I’ll say that I have been using Volumio (quite happily) for a LONG time (and mpd direct on RPi before that) so this is not my first rodeo. I’ve definitely done my share of Volumio installs and troubleshooting, but this one has me stumped (and quite annoyed).

Many thanks for any help or advice with this.

42

FWIW; it would appear that the issue is to do with the current version v3.779. When I re-installed v3.631 (after considerable effort searching) the device went back to working fine. But if I upgraded from there, the device was once again bricked. So I’ve spent a few hours testing all of that and then getting back to v3.631

I’ll admit that my device might not be terribly standard, (RPi 3B with Kali reclocker and Piano 2.1), but at this point, I think I’m done with this platform. It’s been great working with it, but the number of bricked updates and the wasted time just makes no sense. I ordered a Wiim today, and hope that will go well.

All the best and I hope that the proprietary devices work out great for everyone.

43

Have you checked this.

44

for everyone using Allo Piano and experiencing issues with the latest stable version

Unfortunately it is a regression of the kernel 6.6.x.
Volumio makes use of the kernel provided by Raspberry Pi foundation “as-it-is”, this problem was not found during the internal QA because nobody of the team has an Allo Piano to test with, apologizes for that.

The temporary workaround is to use the previous stable version 3.757 (with kernel 6.1.x), until a fix for kernel 6.6.x is found.
https://updates.volumio.org/pi/volumio/3.757/Volumio-3.757-2024-09-17-pi.zip

If someone is willing to help testing, there is a new beta version with updated kernel (6.6.62).
It would be very helpful to understand if the problem is still there with this new kernel version, or if it’s been solved by Raspberry Pi engineers.
Here below the download link to this new beta version:
https://updates.volumio.org/pi/volumio/3.782/Volumio-3.782-2024-11-25-pi.zip

@Zhapox @mregazzi

1 Like
45

Hi @Darmur ,

Thanks for looking into this issue! I flashed the beta verison you provided. Unfortunately it still crashes once the DAC is selected, same behavior. Below you can find 2 dmesg dumps.

  1. Taken after selecting the DAC at the initial configuration setup:
    dmesg_after_setup.txt (25.8 KB)

  2. Taken 5 minutes after another reboot:
    dmesg_5min_after_rb.txt (29.8 KB)

These errors seem to be new:

Screenshot 2024-11-25 180909
Screenshot 2024-11-25 180909837×307 13.7 KB

Let me know if there is anything else I can provide.

I also gladly volunteer if you ever need a Piano 2.1 test candidate for significant updates like this in future.

Best regards
Kevin

1 Like
46

Same Problem here. Update to the new Version crashed Volumio and SD Card. Installe dit on a new SD Card.

I can access WEB UI but :slight_smile:

  • No Tidal access
  • Cant search for music anymore
  • If i want install plugins i get the mess<ge "Logi toi your volumio account " but im already lgged in

I use a Pi 3b and Premoium lifetim licence.

47

please check if the date on the rpi3 is correct.

48

Since it is clear that an update to V3.799 is doomed to failure in the case of Allo’s Piano 2.1, it would be good if users willing to update were somehow informed in advance. Of course, it would be ideal if the update to this version was not even offered for this combination, but this is probably not so easy to realise

49

Good to see that people are looking into this problem. I’d be willing to help testing, first posted result however isn’t looking too good yet. I’ll keep following this topic and next update I’ll give it a go. Having some standard testing procedures (besides jsut checking if it’ll work) and knowing which output do people need to evaluate, would be helpful.

1 Like
50

Is it possible to trigger this update from the CLI after logging in via ssh?

51

yes, it is possible with the following commands

volumio updater testmode
volumio updater forceupdate
1 Like
52

Tnx!

Any idea how to make it update to a specific version?
Seems like I need version 3.757

53

I tried the beta version https://updates.volumio.org/pi/volumio/3.782/Volumio-3.782-2024-11-25-pi.zip (plugins excluded) and I didn’t notice any problems with the Raspberry 3B+

54

do you use with an Allo Piano?

55

A recent update broke the services (it is by now a known problem with the combination of Volumio and an Allo Piano DAC on recent kernels).

I can access the Volumio through ssh and a helpful forum member pointed out the volumio updater command, but that seems to only support rolling forward.

I would like to rollback to a specific version number (version 3.757 in my case).

Alternatively, I could download a specific zip manually and instruct the update code to install the archive (using a zip download).

Are there ways to achieve this if you can ssh to Volumio?

56

*it’s not possible to downgrade, the only option is to flash the older image from scratch

as a side note, dev team is getting hands on the Allo Piano hardware, for trying to fix this problem

3 Likes
57

The error trace indicates a problem in the Linux kernel, specifically during the execution of a close system call (sys_close). The call stack points to a deadlock or blocking issue in the read-write semaphore (rwsem_down_write_slowpath). Here’s an analysis and suggestions for resolution:

Problem Context:

  • The stack trace originates from the snd_ctl_release function in the snd (sound) module, which is part of the Advanced Linux Sound Architecture (ALSA) subsystem.
  • The issue occurs when the system attempts to acquire a write lock on a semaphore during resource cleanup (snd_ctl_release function).

Potential Causes:

  • Semaphore Contention: A deadlock or long blocking situation might occur if other threads or processes hold the read or write lock on the semaphore.
  • Improper Locking: If locks are not acquired or released correctly, this can lead to a deadlock or race condition.
  • Resource Mismanagement: The snd_ctl_release function might be trying to release resources that are already held or incorrectly initialized.
  • Kernel Bug or Driver Issue: This could be due to a bug in the ALSA driver, specifically in how the sound control resources are handled.
  • High Latency Path: A slow path in rwsem_down_write_slowpath suggests contention or delays in acquiring the write lock.

Potential Issues Based on Error Logs

Deadlock in snd_ctl_release

The error trace suggests a potential deadlock or blocking issue occurring in snd_ctl_release. This function is invoked during resource release, and deadlocks can result from improper handling of locks or semaphores.

The code uses glb_pool.lock in several functions (e.g., snd_allo_piano_dsp_program).

Possible causes:

    A lock (mutex_lock) is not being released correctly (mutex_unlock missing in error paths).
    Nested locks or conflicting locks in different threads could cause a deadlock.

Use of mutex_lock in snd_allo_piano_dsp_program

The function snd_allo_piano_dsp_program uses mutex_lock to protect shared resources but does not ensure the mutex is released in all error scenarios. This can lead to deadlock during resource release or driver unload.

Suggestion:

mutex_lock(&glb_ptr->lock);
ret = __snd_allo_piano_dsp_program(rtd, mode, rate, lowpass);
mutex_unlock(&glb_ptr->lock);

If __snd_allo_piano_dsp_program returns an error, ensure mutex_unlock is always executed.

Next steps:

After extensive efforts to investigate and address the reported issue, I have reached a point where further progress is not feasible without direct access to the problematic hardware or hands-on assistance from someone who owns the affected hardware and has kernel development expertise.

To move forward, one of the following will be necessary:

  1. A volunteer who owns the problematic hardware and possesses kernel development skills to step in and collaborate on debugging and resolving the issue.
  2. Shipping the problematic hardware to me so I can perform an in-depth investigation and testing directly.

At this stage, these are the only viable options for making meaningful progress. Unfortunately, without meeting one of these conditions, the issue cannot be addressed further from my end.

Kind Regards,

2 Likes
58

Dear Volumionauts,

I am updating the thread subject to better align with the specific problem at hand. This should help maintain focus and clarity as we work toward a resolution.

Kind Regards,

59

Hi.

Is it possible to know where you live, if shipping has to be considered?
I would check shipping cost from France to ?
In any case, that won t be just right now: if i do ship it, i need first to have another solution than my current setup.
I assume you would ship the Piano back?

Regards

60

Hey @laluciol6990,

As you can see from my profile, I am across the channel from you:

image

This is for granted. Direct hardware access is to understand what the problem is and provide a fix (if fix is possible).

Kind Regards,

1 Like