On 9/15/2024 11:07 PM, Jeffrey Hugo wrote:
On 9/5/2024 6:14 PM, Brian Masney wrote:
Hi Jeffrey,
On Thu, Aug 29, 2024 at 11:01 AM Jeffrey Hugo <quic_jhugo@xxxxxxxxxxx>
wrote:
Interesting, I haven't seen this in my testing. I'll go swing back and
try to figure out why.
For future reference, I'm still supporting Amberwing/QDF2400.
Addressing emails to me is a good way to get my attention.
I also see an unrelated error when booting the Qualcomm Amberwing with
6.11.0-rc5:
[ 14.159483] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.1.auto: error
-EINVAL: invalid resource (null)
[ 14.167076] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.1.auto: probe with
driver arm-smmu-v3-pmcg failed with error -22
[ 14.177707] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.2.auto: error
-EINVAL: invalid resource (null)
[ 14.185557] arm-smmu-v3-pmcg arm-smmu-v3-pmcg.2.auto: probe with
driver arm-smmu-v3-pmcg failed with error -22
...
I spent 20 minutes troubleshooting this in the arm smmu driver,
however I didn't see anything obvious. I attached the full dmesg.
Ernesto: Are you seeing that on your Amberwing?
Yes, looks like it first pops up 6.11-rc1.
Nothing is jumping out at me. I'm running a bisect to see if it gives a
clue.
Bisect pointed to the following which makes zero sense -
commit 5db755fbb1a0de4a4cfd5d5edfaa19853b9c56e6
Author: Christoph Hellwig <hch@xxxxxx>
Date: Fri May 31 09:47:56 2024 +0200
ubd: refactor the interrupt handler
Instead of a separate handler function that leaves no work in the
interrupt hanler itself, split out a per-request end I/O helper and
clean up the coding style and variable naming while we're at it.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Reviewed-by: Martin K. Petersen <martin.petersen@xxxxxxxxxx>
Acked-By: Anton Ivanov <anton.ivanov@xxxxxxxxxxxxxxxxxx>
Link: https://lore.kernel.org/r/20240531074837.1648501-2-hch@xxxxxx
Signed-off-by: Jens Axboe <axboe@xxxxxxxxx>
arch/um/drivers/ubd_kern.c | 49
+++++++++++++++++-----------------------------
1 file changed, 18 insertions(+), 31 deletions(-)
I wonder if bisect-ability got broken somehow.
I'm going to try to do a bit of a manual bisect to see if I can avoid
whatever glitch (possibly self induced) I seem to have hit.
-Jeff
