From: Paolo Pisati <p.pisati@gmail.com>
To: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: msm8996: qcom-qmp: apq8096-db820c fails to boot, reset back to fastboot and locks up
Date: Mon, 10 Jun 2019 15:44:01 +0200 [thread overview]
Message-ID: <20190610134401.GA12964@harukaze> (raw)
From time to time, my apq8096-db820c fails to boot to userspace, reset back to
fastboot and locks up: to easily reproduce the issue, i'm boot looping using a
cron job with a 1 min reboot entry on the board while leaving a "while 1; do
fastboot boot boot.img; done" on the host pc.
The issue is present in mainline up to 5.2-rc4, using defconfig and:
CONFIG_SCSI_UFS_QCOM=y
CONFIG_PHY_QCOM_QMP=y
CONFIG_PHY_QCOM_UFS=y
but was present in previous releases too (e.g. 4.14., 4.19, etc qcom-lt or
mainline), where it's even easier to reproduce (e.g. takes way less reboots to
trigger it).
These are the last lines printed out:
...
[ 7.407209] qcom-qmp-phy 34000.phy: Registered Qcom-QMP phy
[ 7.448058] qcom-qmp-phy 7410000.phy: Registered Qcom-QMP phy
[ 7.461859] ufs_qcom_phy_qmp_14nm 627000.phy: invalid resource
[ 7.535434] qcom-qmp-phy 34000.phy: phy common block init timed-out
[ 7.538596] phy phy-34000.phy.0: phy init failed --> -110
[ 7.550891] qcom-pcie: probe of 600000.pcie failed with error -110
[ 7.619008] qcom-pcie 608000.pcie: 608000.pcie supply vddpe-3v3 not found,
using dummy regulator
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
...
Full boot here: https://pastebin.ubuntu.com/p/rtjVrD3yzk/
Any idea what is going on? Am i doing something wrong?
--
bye,
p.
next reply other threads:[~2019-06-10 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 13:44 Paolo Pisati [this message]
2019-06-11 17:12 ` msm8996: qcom-qmp: apq8096-db820c fails to boot, reset back to fastboot and locks up Niklas Cassel
2019-06-12 13:17 ` Niklas Cassel
2019-06-12 14:09 ` Paolo Pisati
2019-06-12 16:20 ` Niklas Cassel
2019-06-13 8:57 ` Paolo Pisati
2019-06-13 9:19 ` Marc Gonzalez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190610134401.GA12964@harukaze \
--to=p.pisati@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.