Cmt: [SRU][O][PATCH 00/18] Lenovo X13s fails to boot kernel 6.11 (LP: #2089237)
Magali Lemes
magali.lemes at canonical.com
Thu Dec 12 18:42:01 UTC 2024
On 26/11/2024 05:49, Juerg Haefliger wrote:
> BugLink: https://bugs.launchpad.net/bugs/2089237
>
> [ Impact ]
>
> Upgraded to Oracular, rebooted, the kernel (6.11) started to run and then the
> display went blank and the machine eventually crashed.
>
> [ Test Plan ]
>
> Install kernel, boot X13s.
>
> [ Where Problems Could Occur ]
>
> Breakage of Qualcomm Snapdragon based machines. All commits are very specific to
> Qualcomm HW so only users with that HW should be affected. Mainly sc8280xp SoC users.
>
>
> Bryan O'Donoghue (1):
> arm64: dts: qcom: sc8280xp-x13s: Drop redundant clock-lanes from
> camera at 10
>
> Douglas Anderson (3):
> soc: qcom: geni-se: add GP_LENGTH/IRQ_EN_SET/IRQ_EN_CLEAR registers
> serial: qcom-geni: fix arg types for qcom_geni_serial_poll_bit()
> serial: qcom-geni: introduce qcom_geni_serial_poll_bitfield()
>
> Johan Hovold (13):
> arm64: dts: qcom: sc8280xp-crd: disable PCIe perst pull downs
> arm64: dts: qcom: sc8280xp-crd: clean up PCIe2a pinctrl node
> dt-bindings: PCI: qcom: Allow 'vddpe-3v3-supply' again
> serial: qcom-geni: fix fifo polling timeout
> serial: qcom-geni: fix false console tx restart
> serial: qcom-geni: fix console corruption
> serial: qcom-geni: disable interrupts during console writes
Should we also add fa103d2599e1 ("serial: qcom-geni: fix receiver
enable"), which fixes the commit above?
> serial: qcom-geni: fix polled console corruption
> clk: qcom: videocc-sm8350: use HW_CTRL_TRIGGER for vcodec GDSCs
> phy: qcom: qmp-usb: fix NULL-deref on runtime suspend
> phy: qcom: qmp-usb-legacy: fix NULL-deref on runtime suspend
> phy: qcom: qmp-usbc: fix NULL-deref on runtime suspend
> phy: qcom: qmp-combo: move driver data initialisation earlier
>
> Vladimir Zapolskiy (1):
> UBUNTU: SAUCE: arm64: dts: qcom: sc8280xp: Fix interrupt type of camss
> interrupts
>
> .../bindings/pci/qcom,pcie-common.yaml | 3 +
> .../bindings/pci/qcom,pcie-sc7280.yaml | 3 -
> .../bindings/pci/qcom,pcie-sc8280xp.yaml | 3 -
> .../devicetree/bindings/pci/qcom,pcie.yaml | 3 +
> arch/arm64/boot/dts/qcom/sc8280xp-crd.dts | 16 +-
> .../qcom/sc8280xp-lenovo-thinkpad-x13s.dts | 1 -
> arch/arm64/boot/dts/qcom/sc8280xp.dtsi | 40 ++---
> drivers/clk/qcom/videocc-sm8350.c | 4 +-
> drivers/phy/qualcomm/phy-qcom-qmp-combo.c | 3 +-
> .../phy/qualcomm/phy-qcom-qmp-usb-legacy.c | 1 +
> drivers/phy/qualcomm/phy-qcom-qmp-usb.c | 1 +
> drivers/phy/qualcomm/phy-qcom-qmp-usbc.c | 1 +
> drivers/tty/serial/qcom_geni_serial.c | 137 ++++++++++--------
> include/linux/soc/qcom/geni-se.h | 9 ++
> 14 files changed, 127 insertions(+), 98 deletions(-)
>
Patches 5-10 and 12 are already in master-next and patches 14-16 should
also be applied as part of upstream stable updates v6.11.7 sent today.
Other than my question above, the rest of the patchset LGTM.
More information about the kernel-team
mailing list