Jump to content

[77666.669616] rockchip-i2s ff890000.i2s: Fail to set mclk -22


Recommended Posts

Posted

Hi,

Do you know what may cause dmesg showing full wall of this error:

.
.
.
[77666.669616] rockchip-i2s ff890000.i2s: Fail to set mclk -22
[77666.669642] rockchip-i2s ff890000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff890000.i2s: -22
[77666.671123] rockchip-i2s ff8a0000.i2s: Fail to set mclk -22
[77666.671149] rockchip-i2s ff8a0000.i2s: ASoC: error at snd_soc_dai_set_sysclk on ff8a0000.i2s: -22
.
.
.

 

This error occurs every time I run java, but also in some other programs.

 

board: pine64 rockpro64

os: armbian ubuntu focal based image, but i deleted graphical environement and some other programs like libreoffice

Posted (edited)

It also looks like I'm getting SIGSEGV during apt update now:

 

  Reveal hidden contents

 

 

Nice...

Edited by TRS-80
put moderate length output inside spoiler
Posted

So I just found out that my NanoPI M4V2 is doing this too ...

 

Armbian monitor debug for the interested: http://ix.io/2P0s

 

[   21.144068] rockchip-i2s ff8a0000.i2s: Fail to set mclk -22
[   21.144731] rockchip-i2s ff8a0000.i2s: ASoC: error at snd_soc_dai_set_s

 

Maybe something up with the RK3399 device tree?

Posted

So, until I get more information on what's going on, I disabled both I2S devices on my M4V2 to shut them up.

 

There are some DTB differences between rockpi64 and M4V2, but they're pretty close. Perhaps this will work for you too, to at least stop the log spam. Save the below as "rk3399-disable-i2s.dts".

 

/dts-v1/;
/plugin/;

/ {
	compatible = "rk3399";

	fragment@0 {
		target = <&i2s1>;
		__overlay__ {
			status = "disabled";
		};
	};

	fragment@1 {
		target = <&i2s2>;
		__overlay__ {
			status = "disabled";
		};
	};
};

 

Then add as a user overlay on your system ...

 

tparys@m4v2:~$ sudo armbian-add-overlay rk3399-disable-i2s.dts 
Compiling the overlay
Copying the compiled overlay file to /boot/overlay-user/
Reboot is required to apply the changes

 

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines