[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250620214408.11028-1-aishwarya.tcv@arm.com>
Date: Fri, 20 Jun 2025 22:44:08 +0100
From: Aishwarya <aishwarya.tcv@....com>
To: quic_nitirawa@...cinc.com
Cc: James.Bottomley@...senPartnership.com,
aishwarya.tcv@....com,
andersson@...nel.org,
bvanassche@....org,
dmitry.baryshkov@....qualcomm.com,
kishon@...nel.org,
konrad.dybcio@....qualcomm.com,
linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-phy@...ts.infradead.org,
linux-scsi@...r.kernel.org,
manivannan.sadhasivam@...aro.org,
martin.petersen@...cle.com,
neil.armstrong@...aro.org,
quic_cang@...cinc.com,
quic_rdwivedi@...cinc.com,
vkoul@...nel.org,
broonie@...nel.org
Subject: Re: [PATCH V6 10/10] scsi: ufs: qcom : Refactor phy_power_on/off calls
Hi Nitin,
To clarify — the defconfig kernel does boot successfully on our Arm64
Qualcomm platforms (RB5 and DB845C). However, starting from
next-20250613, we are seeing the following three test failures in the
`bootrr` baseline test in our CI environment:
- baseline.bootrr.scsi-disk-device0-probed
- dmesg.alert
- dmesg.emerg
Test suite:
https://github.com/kernelci/bootrr/tree/main
These failures are due to kernel alerts seen in the boot logs. A relevant
snippet is shown below:
kern :alert : Unable to handle kernel NULL pointer dereference at
virtual address 0000000000000000
kern :alert : Mem abort info:
kern :alert : ESR = 0x0000000096000004
kern :alert : EC = 0x25: DABT (current EL), IL = 32 bits
kern :alert : SET = 0, FnV = 0
kern :alert : EA = 0, S1PTW = 0
kern :alert : FSC = 0x04: level 0 translation fault
kern :alert : Data abort info:
kern :alert : ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
kern :alert : CM = 0, WnR = 0, TnD = 0, TagAccess = 0
kern :alert : GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
kern :alert : user pgtable: 4k pages, 48-bit VAs, pgdp=0000000109c41000
kern :alert : [0000000000000000] pgd=0000000000000000
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=alert RESULT=fail UNITS=lines
MEASUREMENT=13>
kern :emerg : Internal error: Oops: 0000000096000004 [#1] SMP
kern :emerg : Code: a90157f3 aa0003f3 f90013f6 f9405c15 (f94002b6)
<LAVA_SIGNAL_TESTCASE TEST_CASE_ID=emerg RESULT=fail UNITS=lines
MEASUREMENT=2>
Please let me know if you need full logs or further details to help
with debugging.
Thanks,
Aishwarya
Powered by blists - more mailing lists