lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 17 Jan 2019 13:16:01 +0000
From:   Dean Wallace <>
To:     Hans de Goede <>
Cc:     Mogens Jensen <>,
        Pierre-Louis Bossart <>,
        Andy Shevchenko <>,
        Stephen Boyd <>,
        Michael Turquette <>,
        linux-clk <>,
        Stable <>,
        Johannes Stezenbach <>,
        Carlo Caione <>,
        Andy Shevchenko <>,
        Linux Kernel Mailing List <>
Subject: Re: Regression found (Stop-marking-clocks-as-CLK_IS_CRITICAL)

On 17-01-19, Hans de Goede wrote:
> Mogens, Dean, can you please try the SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH
> driver, without reverting any patches, with the attached patch on top and
> see if that helps?

Hi Hans.   Just compiled 4.20.3 with your new patch and no other
patches.  First impressions are, this is now as stable as it has ever
been in my experiences with this baytrail drama.  A quick run down on my

No PLL messages on boot, good.
Played audio using mpd, all fine.  Plugged in headphones, switches,
stays stable, no messages.
Unplugged/plugged again few times, no issues.
Ran pavucontrol, stayed stable, no messages.
I can still make it lose the lock and turn on the dalek distortion by
switching profiles in pavucontrol (from stereo output to any other, like
putput + input) but that has always been the case afaik for this
machine.  So basically this is now back to working as it was before the
4.18.5 'clk' breakage.

One thing to mention, I don;t normally use UCM files, tho I have in the
past, which is where I assume my asound.state file has come from, which
makes my sound work /shrug.  Well I've just tested using the UCM, and
things are a little less stable regarding plugging/unplugging headset a
few times.  It loses lock, but, what's different now is after maybe 3-4
seconds it corrects itself.  Not sure if it matters, but shows things
are a little more stable with this patch than previously known.

I'll test a little longer and report (if) any problems.  It will be
interesting to see how my buddy who uses headset/mic a lot gets on, as
he needs to use usb audio device because internal sound and mic don't
work properly.


Powered by blists - more mailing lists