Board fails to boot after "apt upgrade"

Products Support DragonBoard 820c
#1

Hey,
I am using 382 snapshot, and after doing “apt upgrade” the board is going to ram-dump mode. I could reproduce the same issue in 228 snapshot also.(Snapshots 385-392 fails to boot and are giving the same log, without any changes).

From the boot up log I was able to find that board goes to ram-dump mode trying to load the ath10k_pci firmware,

[   30.766941] ath10k_pci 0000:01:00.0: Unknown eventid: 3  
    Format: Log Type - Time(microsec) - Message - Optional Info
    Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
    S - QC_IMAGE_VERSION_STRING=BOOT.XF.1.0-00301
    S - IMAGE_VARIANT_STRING=M8996LAB
    S - OEM_IMAGE_VERSION_STRING=crm-ubuntu68
    S - Boot Interface: UFS
    S - Secure Boot: Off
    S - Boot Config @ 0x00076044 = 0x000001c9
    S - JTAG ID @ 0x000760f4 = 0x100640e1
    S - OEM ID @ 0x000760f8 = 0x00000000
    S - Serial Number @ 0x00074138 = 0x9e999481
    S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
    S - OEM Config Row 1 @ 0x00074190 = 0x0000000000000000
    S - Feature Config Row 0 @ 0x000741a0 = 0x0050000010000100
    S - Feature Config Row 1 @ 0x000741a8 = 0x00fff00001ffffff
    S - Core 0 Frequency, 1228 MHz
    B -         0 - PBL, Start
    B -     10411 - bootable_media_detect_entry, Start
    B -     49766 - bootable_media_detect_success, Start
    B -     49767 - elf_loader_entry, Start
    B -     50803 - auth_hash_seg_entry, Start
    B -     50906 - auth_hash_seg_exit, Start
    B -     82752 - elf_segs_hash_verify_entry, Start
    B -     85250 - PBL, End
    B -     87291 - SBL1, Start
    B -    183274 - usb: hs_phy_nondrive_start
    B -    183640 - usb: PLL lock success - 0x3
    B -    186629 - usb: hs_phy_nondrive_finish
    B -    190747 - boot_flash_init, Start
    D -        30 - boot_flash_init, Delta
    B -    197853 - sbl1_ddr_set_default_params, Start
    D -         0 - sbl1_ddr_set_default_params, Delta
    B -    205844 - boot_config_data_table_init, Start
    D -    103822 - boot_config_data_table_init, Delta - (60 Bytes)
    B -    314211 - CDT Version:3,Platform ID:8,Major ID:1,Minor ID:0,Subtype:0
    B -    318908 - Image Load, Start
    D -     22326 - PMIC Image Loaded, Delta - (37272 Bytes)
    B -    341234 - pm_device_init, Start
    B -    347029 - PON REASON:PM0:0x200020021 PM1:0x200020021 
    B -    383385 - PM_SET_VAL:Skip
    D -     40016 - pm_device_init, Delta
    B -    385306 - pm_driver_init, Start
    D -      2928 - pm_driver_init, Delta
    B -    391894 - pm_sbl_chg_init, Start
    B -    395524 - BOOTUP: Battery is GOOD
    D -      3446 - pm_sbl_chg_init, Delta
    B -    402478 - vsense_init, Start
    D -        30 - vsense_init, Delta
    B -    409981 - Pre_DDR_clock_init, Start
    D -       396 - Pre_DDR_clock_init, Delta
    B -    415837 - ddr_initialize_device, Start
    B -    419527 - 8996 Pro v1.x detected, Max frequency = 1.8 GHz
    B -    427122 - ddr_initialize_device, Delta
    B -    429470 - Basic DDR tests done
    B -   1990308 - clock_init, Start
    D -       244 - clock_init, Delta
    B -   1992321 - Image Load, Start
    D -      6496 - QSEE Dev Config Image Loaded, Delta - (48192 Bytes)
    B -   1999244 - Image Load, Start
    D -      5216 - APDP Image Loaded, Delta - (0 Bytes)
    B -   2026298 - usb: fedl, vbus_low
    B -   2026359 - Image Load, Start
    D -     10644 - XBLRamDump Image Loaded, Delta - (342782 Bytes)
    B -   2091568 - usb: init start
    B -   2093398 - usb: PLL lock success , 0x2
    B -   2515579 - usb: HIGH , 0x900e
    B -   2599515 - usb: HIGH , 0x900e
    B -   2700043 - usb: ENUM success

Before the upgrade the corresponding firmware was properly loaded with log,
[ 30.986191] ath10k_pci 0000:01:00.0 wlp1s0: renamed from wlan0

How can I solve this issue :confused: ?

#2

can you share the first log (the one leading to the ramdump reboot) using e.g. pastebin.

#4

https://pastebin.com/2n5Rj7tA (boot log after doing apt upgrade).

#5

Indeed, I also reproduce the issue, a temp workaround could be to blacklist athk_pci module (if you don’t need wifi).

echo "root=/dev/disk/by-partlabel/rootfs rw rootwait console=tty0 console=ttyMSM0,115200n8 module_blacklist=ath10k_pci" > dbootimg -u cmdline boot-linaro-buster-dragonboard-820c-392.img

dbootimg: https://github.com/96boards/dt-update/tree/master/tools/dbootimg

Comparing boot logs, it seems the old working images have:

ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb

The new ones have:

ath10k_pci 0000:01:00.0: firmware ver RM.4.4.1.c2-00057-QCARMSWP-1 api 6 features wowlan,ignore-otp,no-4addr-pad,raw-mode crc32 e061250a

Replacing /lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin by an older one fixes the issue. going to check that internaly.

#6

Thanks, i was able to boot the board with this change. :slight_smile:

#7

This should also be fixed upcoming snapshots…

1 Like