From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Joerg Roedel <jroedel@suse.de>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-next@vger.kernel.org
Subject: Re: next/master bisection: baseline.login on jetson-tk1
Date: Wed, 13 May 2020 23:16:14 +0100 [thread overview]
Message-ID: <c9745450-a6d0-1944-a9af-ef9ce18fed12@collabora.com> (raw)
In-Reply-To: <20200512151600.GD8135@suse.de>
On 12/05/2020 16:16, Joerg Roedel wrote:
> Hi Guillaume,
>
> thanks for the report!
>
> On Tue, May 12, 2020 at 07:05:13AM +0100, Guillaume Tucker wrote:
>>> Summary:
>>> Start: 4b20e7462caa6 Add linux-next specific files for 20200511
>>> Plain log: https://storage.kernelci.org/next/master/next-20200511/arm/tegra_defconfig/gcc-8/lab-collabora/baseline-tegra124-jetson-tk1.txt
>>> HTML log: https://storage.kernelci.org/next/master/next-20200511/arm/tegra_defconfig/gcc-8/lab-collabora/baseline-tegra124-jetson-tk1.html
>>> Result: 3eeeb45c6d044 iommu: Remove add_device()/remove_device() code-paths
>
> Okay, so it faults at
>
> PC is at __iommu_probe_device+0x20/0x1b8
>
> Can you translate that for me into a code-line, please? That would help
> finding the issue.
Sure, sorry for the delay. I've built my own image as vmlinux is
not stored by kernelci and reproduced the problem:
https://lava.collabora.co.uk/scheduler/job/2403076#L544
which this time gave me:
<4>[ 2.540558] PC is at iommu_probe_device+0x1c/0x15c
<4>[ 2.545606] LR is at of_iommu_configure+0x15c/0x1c4
<4>[ 2.550736] pc : [<c092e0e4>] lr : [<c0932c0c>] psr: a0000013
which in turn brings us to:
(gdb) l *0xc092e0e4
0xc092e0e4 is in iommu_probe_device (drivers/iommu/iommu.c:232).
227 int ret;
228
229 if (!dev_iommu_get(dev))
230 return -ENOMEM;
231
232 if (!try_module_get(ops->owner)) {
233 ret = -EINVAL;
234 goto err_out;
235 }
236
Hope this helps.
Guillaume
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-05-13 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5eb9fab4.1c69fb81.a1f1c.0e95@mx.google.com>
2020-05-12 6:05 ` next/master bisection: baseline.login on jetson-tk1 Guillaume Tucker
2020-05-12 15:16 ` Joerg Roedel
2020-05-13 22:16 ` Guillaume Tucker [this message]
2020-05-14 11:23 ` Joerg Roedel
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=c9745450-a6d0-1944-a9af-ef9ce18fed12@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).