On 31-10-18, Pierre-Louis Bossart wrote:
Just thought it worth mentioning, this new patch that fixes sound again, seems to have ressurected an old issue with PLL unlock. I'm seeing journal entries after fresh boot ......
picard kernel: max98090 i2c-193C9890:00: PLL unlocked picard systemd[462]: Started Sound Service. picard kernel: max98090 i2c-193C9890:00: PLL unlocked picard kernel: max98090 i2c-193C9890:00: PLL unlocked picard kernel: max98090 i2c-193C9890:00: PLL unlocked picard kernel: max98090 i2c-193C9890:00: PLL unlocked picard kernel: max98090 i2c-193C9890:00: PLL unlocked picard kernel: max98090 i2c-193C9890:00: PLL unlocked picard kernel: max98090 i2c-193C9890:00: PLL unlocked picard kernel: max98090 i2c-193C9890:00: PLL unlocked picard kernel: max98090_pll_work: 141 callbacks suppressed picard kernel: max98090 i2c-193C9890:00: PLL unlockedsound is ok, but sometimes plugging in headphones spams journal with those PLL messages, and sound turns into "daleks", and I have to remove/insert headphones few times or stop/start audio to fix it. It's a very old issue, maybe you'd know more about it.
I noticed this error on my Orco device used for tests many moons ago, but I could never find out what led to this error case, it wasn't deterministic and didn't impact the audio quality. All I could do is rate_limit it... If we have an A vs. B situation it'd be really helpful to diagnose further.
Is there really a causality between the changes from Hans and this PLL unlock error? Are you 100% sure this was not present in the previous install you used (4.18.14 as mentioned earlier in the thread)?
Thanks
-Pierre
Hi Pierre. I'm not overly bothered by it, I lived with it for a long time when it was worse pre cht_bsw days. It's very hit and miss, like I have just done a few reboots and nothing is coming up in journal and switching to headphones works fine. Was quite a frequent issue back before it was switched to chtmax, but after that, for me anyway, it was all but nonexistant, apart from a very rare occassion once maybe twice. It's always been slightly unstable I guess, but seeing those messages in journal, something I look at frequently, and not seeing them for a long time, hmmm. I'll do some more tests with older kernel see how it compares and report back. Then again, I could just ignore it :) Regards
-Dean