Julius Werner has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/44868 )
Change subject: trogdor: report hardware watchdog reset after reboot ......................................................................
Patch Set 2:
(1 comment)
https://review.coreboot.org/c/coreboot/+/44868/1/src/soc/qualcomm/sc7180/soc... File src/soc/qualcomm/sc7180/soc.c:
https://review.coreboot.org/c/coreboot/+/44868/1/src/soc/qualcomm/sc7180/soc... PS1, Line 30: printk(BIOS_INFO, "AOSS_CC_RESET_STATUS[%x]..[%x]\n", AOSS_CC_RESET_STATUS, aoss);
Comment above added in error, 0x200 refers to PS_HOLD_STATUS not WDOG expiration. […]
Hmm... sorry, I updated to the newest kernel, still does nothing for me. It doesn't seem to have KGDB enabled:
localhost ~ # zcat /proc/config.gz | grep KGDB CONFIG_HAVE_ARCH_KGDB=y # CONFIG_KGDB is not set localhost ~ # grep R87 /etc/lsb-release CHROMEOS_RELEASE_BUILDER_PATH=trogdor-release/R87-13446.0.0 localhost ~ # dmesg | grep "Linux version" [ 0.000000] Linux version 5.4.61-07894-g8809b414e5aa (chrome-bot@chromeos-ci-legacy-us-central2-d-x32-73-coyy) (Chromium OS 11.0_pre394483_p20200618-r11 clang version 11.0.0 (/var/cache/chromeos-cache/distfiles/egit-src/llvm-project b726d071b4aa46004228fc38ee5bfd167f999bfe)) #1 SMP PREEMPT Wed Sep 2 01:48:30 PDT 2020
After the watchdog trigger procedure described above I still get this on boot:
SOC: AOSS_CC_RESET_STATUS : 0 AOSS_CC_RESET_STATUS[c2f0020]..[0]
I'm using a Lazor-rev0. Is there any reason this would only work on a rev1?