Rebuilding locally with after moving CONFIG_PINCTRL_SC7280 and
CONFIG_INTERCONNECT_QCOM_SC7280 to builtin was already enough to get it
to boot, rest were all loaded as module successfully.
diff --git a/debian.master/config/annotations b/debian.master/config/annotations
index 4844d54c4a7832..1ff306096ef209 100644
--- a/debian.master/config/annotations
+++ b/debian.master/config/annotations
@@ -6943,7 +6943,7 @@ CONFIG_INTERCONNECT_MTK_DVFSRC_EMI
policy<{'arm64': 'm', 'armhf': '
CONFIG_INTERCONNECT_MTK_MT8183 policy<{'arm64': 'm', 'armhf':
'm'}>
CONFIG_INTERCONNECT_MTK_MT8195 policy<{'arm64': 'm', 'armhf':
'm'}>
CONFIG_INTERCONNECT_QCOM policy<{'arm64': 'y', 'armhf':
'y'}>
-CONFIG_INTERCONNECT_QCOM_BCM_VOTER policy<{'arm64': 'm', 'armhf':
'm'}>
+CONFIG_INTERCONNECT_QCOM_BCM_VOTER policy<{'arm64': 'y', 'armhf':
'y'}>
CONFIG_INTERCONNECT_QCOM_MSM8909 policy<{'arm64': 'm', 'armhf':
'm'}>
CONFIG_INTERCONNECT_QCOM_MSM8916 policy<{'arm64': 'm', 'armhf':
'm'}>
CONFIG_INTERCONNECT_QCOM_MSM8937 policy<{'arm64': 'm', 'armhf':
'm'}>
@@ -6958,12 +6958,12 @@ CONFIG_INTERCONNECT_QCOM_QCS404
policy<{'arm64': 'm', 'armhf': '
CONFIG_INTERCONNECT_QCOM_QCS615 policy<{'arm64': 'm', 'armhf':
'm'}>
CONFIG_INTERCONNECT_QCOM_QCS8300 policy<{'arm64': 'm', 'armhf':
'm'}>
CONFIG_INTERCONNECT_QCOM_QDU1000 policy<{'arm64': 'm', 'armhf':
'm'}>
-CONFIG_INTERCONNECT_QCOM_RPMH policy<{'arm64': 'm', 'armhf':
'm'}>
+CONFIG_INTERCONNECT_QCOM_RPMH policy<{'arm64': 'y', 'armhf':
'y'}>
CONFIG_INTERCONNECT_QCOM_RPMH_POSSIBLE policy<{'arm64': 'y', 'armhf':
'y'}>
CONFIG_INTERCONNECT_QCOM_SA8775P policy<{'arm64': 'm', 'armhf':
'm'}>
CONFIG_INTERCONNECT_QCOM_SAR2130P policy<{'arm64': 'm', 'armhf':
'm'}>
CONFIG_INTERCONNECT_QCOM_SC7180 policy<{'arm64': 'm', 'armhf':
'm'}>
-CONFIG_INTERCONNECT_QCOM_SC7280 policy<{'arm64': 'm', 'armhf':
'm'}>
+CONFIG_INTERCONNECT_QCOM_SC7280 policy<{'arm64': 'y', 'armhf':
'y'}>
CONFIG_INTERCONNECT_QCOM_SC8180X policy<{'arm64': 'm', 'armhf':
'm'}>
CONFIG_INTERCONNECT_QCOM_SC8280XP policy<{'arm64': 'm', 'armhf':
'm'}>
CONFIG_INTERCONNECT_QCOM_SDM660 policy<{'arm64': 'm', 'armhf':
'm'}>
@@ -10475,7 +10475,7 @@ CONFIG_PINCTRL_SA8775P
policy<{'arm64': 'm'}>
CONFIG_PINCTRL_SAMSUNG policy<{'armhf': 'y'}>
CONFIG_PINCTRL_SAR2130P policy<{'arm64': 'm'}>
CONFIG_PINCTRL_SC7180 policy<{'arm64': 'm'}>
-CONFIG_PINCTRL_SC7280 policy<{'arm64': 'm'}>
+CONFIG_PINCTRL_SC7280 policy<{'arm64': 'y'}>
CONFIG_PINCTRL_SC7280_LPASS_LPI policy<{'arm64': 'm'}>
CONFIG_PINCTRL_SC8180X policy<{'arm64': 'm'}>
CONFIG_PINCTRL_SC8280XP policy<{'arm64': 'm'}>
Will send the patch.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2106681
Title:
Plucky preinstalled server fails to boot on rb3gen2
Status in linux package in Ubuntu:
New
Bug description:
Testing https://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/current/plucky-preinstalled-server-arm64.img.xz on
Qualcomm RB3Gen2 and it fails to boot, getting stuck during the boot
process.
Looks like a certain number of critical kernel configs are enabled as
module, which should be set as builtin instead (e.g. pinctrl).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106681/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
