Kernel hangs during msm init
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-snapdragon (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Bionic |
Fix Released
|
Critical
|
Unassigned | ||
Bug Description
Impact:
Ubuntu-
Sometimes we get the following stack trace, or the boot completes and the board hangs during reboot:
...
[ 8.113018] msm_dsi_
[ 8.131081] msm 1a00000.mdss: failed to bind 1a98000.dsi (ops dsi_ops [msm]): -517
[ 8.138234] msm 1a00000.mdss: master bind failed: -517
[ 8.145551] platform 1a01000.mdp: Dropping the link to 1ef0000.iommu
[ 8.150545] iommu: Removing device 1a01000.mdp from group 1
[ 8.157051] ------------[ cut here ]------------
[ 8.162369] WARNING: CPU: 1 PID: 1316 at /build/
+0x74/0x88
[ 8.167166] Modules linked in: adv7511_drm cec rc_core msm(+) mdt_loader
[ 8.181137] CPU: 1 PID: 1316 Comm: systemd-udevd Not tainted 4.15.0-
[ 8.188079] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[ 8.196501] pstate: 60400005 (nZCv daif +PAN -UAO)
[ 8.203356] pc : qcom_iommu_
[ 8.207955] lr : qcom_iommu_
[ 8.212727] sp : ffff00000cbeb680
[ 8.217412] x29: ffff00000cbeb680 x28: ffff8000396d84b8
[ 8.220713] x27: ffff8000396d84b0 x26: ffff8000396d84c0
[ 8.226096] x25: ffff80003d057c10 x24: ffff8000396d8420
[ 8.231391] x23: 0000000000000003 x22: ffff80003ce40258
[ 8.236686] x21: ffff80000203ad00 x20: ffff80000203af30
[ 8.241981] x19: ffff80000203af00 x18: ffffffffffffffff
[ 8.247275] x17: 0000000000000000 x16: 0000000000000004
[ 8.252570] x15: ffff000009549c08 x14: 0720072007200720
[ 8.257866] x13: 0720072007200720 x12: 0720072007200720
[ 8.263161] x11: ffff000009549e80 x10: ffff00000871d340
[ 8.268456] x9 : 0720072007200720 x8 : 0000000000000005
[ 8.273751] x7 : 0720072d072d072d x6 : 000000000000014c
[ 8.279046] x5 : ffff000008610250 x4 : 0000000000000000
[ 8.284345] x3 : 0000000000000000 x2 : a59fa8ece8469a00
[ 8.289637] x1 : 0000000000000000 x0 : 0000000000000024
[ 8.294932] Call trace:
[ 8.300227] qcom_iommu_
[ 8.302400] iommu_group_
[ 8.306914] kobject_
[ 8.310905] kobject_
[ 8.314292] kobject_
[ 8.318455] iommu_group_
[ 8.321756] qcom_iommu_
[ 8.326617] iommu_bus_
[ 8.331045] notifier_
[ 8.335210] blocking_
[ 8.339294] device_
[ 8.344066] platform_
[ 8.347539] platform_
[ 8.352410] of_platform_
[ 8.357087] device_
[ 8.361775] of_platform_
[ 8.366350] msm_pdev_
[ 8.370369] platform_
[ 8.374707] driver_
[ 8.378701] __driver_
[ 8.383042] bus_for_
[ 8.386598] driver_
[ 8.390418] bus_add_
[ 8.394237] driver_
[ 8.397797] __platform_
[ 8.401841] msm_drm_
[ 8.406481] do_one_
[ 8.410818] do_init_
[ 8.414463] load_module+
[ 8.418282] SyS_finit_
[ 8.422016] el0_svc_
[ 8.426095] ---[ end trace 800d0885aa276bfd ]---
Fix:
During the Ubuntu-
How to test:
Boot a patched kernel and check if that stracktrace shows up again.
Regression:
None, i'm reverting a patch that wasn't there before and clearly wasn't tested with our downstream BSP.
CVE References
| description: | updated |
| description: | updated |
| summary: |
- Kernel crash during msm init (or during shutdown) + Kernel hangs during msm init |
| Changed in linux-snapdragon (Ubuntu): | |
| status: | New → Invalid |
| Changed in linux-snapdragon (Ubuntu Bionic): | |
| status: | New → In Progress |
| importance: | Undecided → Critical |
| Khaled El Mously (kmously) wrote | #1 |
| Changed in linux-snapdragon (Ubuntu Bionic): | |
| status: | In Progress → Fix Committed |
| Naresh Kamboju (naresh-kamboju) wrote | #2 |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in linux-snapdragon (Ubuntu Bionic): | |
| status: | Fix Committed → Fix Released |
@Paolo: I'm just wondering if
a) There's some testing improvement we can do to catch this kind of thing pre-release
and
b) why that drm driver is getting this fix via stable updates but the driver itself would require "backport(ing) of the new msm dri driver (and all the relevant dependencies)".. Shouldn't that driver already be in our bionic tree if it's getting this fix via stable updates? (Although I just realized as I'm writing this that bionic gets updates from 4.16 too so maybe that's why. Still easier to just ask :) )