NAK: [PATCH 0/5] [SRU][C/master] Reduce boot noise on Dragonboard

Seth Forshee seth.forshee at canonical.com
Mon Oct 15 15:42:28 UTC 2018


On Wed, Oct 10, 2018 at 05:51:27PM +0200, Paolo Pisati wrote:
> BugLink: https://bugs.launchpad.net/bugs/1797154
> 
> Impact:
> 
> During boot on a Dragonboard410c using a recent Bionic or Cosmic kernel,
> there's some noise like:
> 
> ...
> [ 3.665431] msm_dsi_phy 1a98300.dsi-phy: Failed to get supply 'vddio':
> -517
> [ 3.669243] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_regulator_init: failed
> to init regulator, ret=-517
> [ 3.676180] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_driver_probe: failed to
> init regulator
> ...
> 
> or
> 
> ...
> [ 4.192280] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916 at 1:codec at f000:
> Failed to get supply 'vdd-cdc-io': -517
> [ 4.195660] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916 at 1:codec at f000:
> Failed to get regulator supplies -517
> ...
> 
> and similar.
> 
> This is mainly due to DRM_MSM* and SND_QCOM_MSM* that were built-in, and
> try to initialize before the voltage regulators are ready to work,
> resulting in a noisy bootlog.
> 
> These patches factor out some code as modules, so when the kmods are
> loaded and initialized, regulators are already present and ready to
> attach - all these config changes shave around ~3K bytes from dmesg,
> making the bootlog easir to parse.
> 
> Fix:
> 
> Apply the attached patches and recompile
> 
> How to test:
> 
> Boot a patched kernel and check for the above noise in dmesg
> 
> Regression potential:
> 
> None, we are just turning some code into kmods, and turning off a couple
> of not used feature for this flavour - all the other flavours are
> untouched.

The first patch has a couple of changes that look entirely unrelated:

-CONFIG_CC_HAS_SANE_STACKPROTECTOR=y
-CONFIG_MPROFILE_KERNEL=y

They seem to come back for me on updateconfigs, but all the same they
don't belong in the patch.

Thanks,
Seth




More information about the kernel-team mailing list