【SDX65】WCN6856启动出现系统崩溃问题

问题log

cache.mount: Failed to connect stdout to the journal socket, ignoring: No such file or directory
[  OK  ] Started USB daemon Service.
usbd.service: Failed to connect stdout to the journal socket, ignoring: No such file or directory
         Starting adpl service...
[   30.105786] UBIFS (ubi0:2): Mounting in unauthenticated mode
[  OK  ] Started Atfwd_daemon Service.
[   30.180109] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 827
adpld.service: Failed to connect stdout to the journal socket, ignoring: No such file or directory
atfwd.service: Failed to connect stdout to the journal socket, ignoring: No such file or directory
         Starting System Logging Service...
busybox-syslog.service: Failed to connect stdout to the journal socket, ignoring: No such file or directory
[  OK  ] Started Charger Policy Service.
chg-policy.service: Failed to connect stdout to the journal socket, ignoring: No such file or directory
         Starting chgrp-diag Service...
chgrp-diag.service: Failed to connect stdout to the journal socket, ignoring: No such file or directory
[  OK  ] Started data-init service.
data-init.service: Failed to connect stdout to the journal socket, ignoring: No such file or directory
         Starting diagrebootapp service...
[   30.646627] UBIFS (ubi0:2): recovery needed
diag-reboot-app.service: Failed to connect stdout to the journal socket, ignoring: No such file or directory
[  OK  ] Started fs-scrub-daemon Service.
fs-scrub-daemon.service: Failed to connect stdout to the journal socket, ignoring: No such file or directory
         Starting logd logging service...
logd.service: Failed to connect stdout to the journal socket, ignoring: No such file or directory
[   30.922916] MAIN_MGR: hvdcp_opti Version: 3:0:0
[   30.926544] MAIN_MGR: capset failed: Permission denied
[   30.961040] UBIFS (ubi0:2): recovery completed
[   30.961283] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "cachefs"
[   30.964374] UBIFS (ubi0:2): LEB size: 253952 bytes (248 KiB), min./max. I/O unit sizes: 4096 bytes/4096 bytes
         Starting QTI Mobile Broadband Service (Non Optimized)...
mbimd_nonopt.service: Failed to connect stdout to the journal socket, ignoring: No such file or directory
mbimd_nonopt.service: Failed to connect stdout to the journal socket, ignoring: No such file or directory
[   31.200086] cnss: fatal: Timeout waiting for RDDM notification
[   31.200147] cnss: fatal: mhi_read_reg: current read ID: 0xffff, record ID: 0x1103
[   31.204814] cnss: fatal: mhi_read_reg: PCI device ID mismatch, link possibly down, current read ID: 0xffff, record ID: 0x1103
[   31.212409] cnss: fatal: mhi_read_reg: current read ID: 0xffff, record ID: 0x1103
[   31.223661] cnss: fatal: mhi_read_reg: PCI device ID mismatch, link possibly down, current read ID: 0xffff, record ID: 0x1103
[   31.231139] cnss: fatal: mhi_read_reg: current read ID: 0xffff, record ID: 0x1103
[   31.242409] cnss: fatal: mhi_read_reg: PCI device ID mismatch, link possibly down, current read ID: 0xffff, record ID: 0x1103
[   31.250098] subsys-restart: subsystem_restart_dev(): Restart sequence requested for wlan, restart_level = SYSTEM.
[   31.261952] UBIFS (ubi0:2): FS size: 13205504 bytes (12 MiB, 52 LEBs), journal size 2031617 bytes (1 MiB, 6 LEBs)
[   31.356228] UBIFS (ubi0:2): reserved for root: 623728 bytes (609 KiB)
[   31.356259] UBIFS (ubi0:2): media format: w5/r0 (latest is w5/r0), UUID 19CEFE13-FFB0-4B32-9338-8912787AF02F, small LPT model
[   31.460115] Kernel panic - not syncing: subsys-restart: Resetting the SoC - wlan crashed.
[   31.460152] CPU: 0 PID: 332 Comm: kworker/0:3 Tainted: G        W  OE     5.4.147 #1
[   31.467268] Hardware name: Qualcomm Technologies, Inc. SDXLEMUR (Flattened Device Tree)
[   31.475092] Workqueue: events device_restart_work_hdlr
[   31.482816] [<b010f7cc>] (unwind_backtrace) from [<b010c810>] (show_stack+0x10/0x14)
[   31.488018] [<b010c810>] (show_stack) from [<b011c5bc>] (panic+0x114/0x328)
[   31.495917] [<b011c5bc>] (panic) from [<b0500568>] (subsys_remove_restart_order+0x0/0x80)
[   31.502602] [<b0500568>] (subsys_remove_restart_order) from [<b678d800>] (0xb678d800)
[   31.511000] ipa ipa3_panic_notifier:7082 IPA clk off not saving the IPA registers
[   31.718754] cnss: Crash shutdown with driver_state 0x146600
[   31.718771] cnss: Device is already powered off, skip
[   31.723119] ipa ipa3_active_clients_panic_notifier:645 
[   31.723119] ---- Active Clients Table ----
[   31.723119] TAG_PROCESS                              -5  SPECIAL
[   31.723119] 
[   31.723119] Total active clients count: 0
[   31.723119] 
[   31.728344] msm_nand_bam_panic_notifier: Dumping APSS bam pipes register dumps
[   31.751339] Rebooting in 5 seconds..
[   36.757490] Triggering late bite
[   36.757506] msm_watchdog 17817000.qcom,wdt: Causing a QCOM Apps Watchdog bite!
[   36.759772] msm_watchdog 17817000.qcom,wdt: Wdog - STS: 0xa7b14, CTL: 0x3, BARK TIME: 0x77fd3, BITE TIME: 0x77fd3

问题分析

[   31.200086] cnss: fatal: Timeout waiting for RDDM notification
[   31.200147] cnss: fatal: mhi_read_reg: current read ID: 0xffff, record ID: 0x1103
[   31.204814] cnss: fatal: mhi_read_reg: PCI device ID mismatch, link possibly down, current read ID: 0xffff, record ID: 0x1103
[   31.212409] cnss: fatal: mhi_read_reg: current read ID: 0xffff, record ID: 0x1103
[   31.223661] cnss: fatal: mhi_read_reg: PCI device ID mismatch, link possibly down, current read ID: 0xffff, record ID: 0x1103
[   31.231139] cnss: fatal: mhi_read_reg: current read ID: 0xffff, record ID: 0x1103
[   31.242409] cnss: fatal: mhi_read_reg: PCI device ID mismatch, link possibly down, current read ID: 0xffff, record ID: 0x1103

从以上log可以看到读取的ID是0xffff，pcie里面记录的是0x1103，所以导致wifi启动失败，这是由于pci读取到的设备是0x1103，但是在驱动加载初始化的时候无法读取到设备ID导致。问题根本原因是由于pcie初始化阶段读取到了wifi设备，但是驱动加载的时候没有读取到wifi设备，我遇到问题是由于供电不足，导致wifi初始化失败。

解决方案

        只需要确保wifi供电足够即可