From: Joerg Roedel <joro@8bytes.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Joerg Roedel <jroedel@suse.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org
Subject: Re: next/master bisection: baseline.login on jetson-tk1
Date: Thu, 14 May 2020 13:23:17 +0200 [thread overview]
Message-ID: <20200514112317.GH18353@8bytes.org> (raw)
In-Reply-To: <c9745450-a6d0-1944-a9af-ef9ce18fed12@collabora.com>
On Wed, May 13, 2020 at 11:16:14PM +0100, Guillaume Tucker wrote:
> 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
Okay, so ops is NULL. I queued a fix for that in the iommu-tree. If you
test the latest master branch the problem should be gone.
Thanks for the report,
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: linux-next@vger.kernel.org, iommu@lists.linux-foundation.org,
Joerg Roedel <jroedel@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: next/master bisection: baseline.login on jetson-tk1
Date: Thu, 14 May 2020 13:23:17 +0200 [thread overview]
Message-ID: <20200514112317.GH18353@8bytes.org> (raw)
In-Reply-To: <c9745450-a6d0-1944-a9af-ef9ce18fed12@collabora.com>
On Wed, May 13, 2020 at 11:16:14PM +0100, Guillaume Tucker wrote:
> 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
Okay, so ops is NULL. I queued a fix for that in the iommu-tree. If you
test the latest master branch the problem should be gone.
Thanks for the report,
Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-05-14 11:23 UTC|newest]
Thread overview: 8+ 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 6:05 ` Guillaume Tucker
2020-05-12 15:16 ` Joerg Roedel
2020-05-12 15:16 ` Joerg Roedel
2020-05-13 22:16 ` Guillaume Tucker
2020-05-13 22:16 ` Guillaume Tucker
2020-05-14 11:23 ` Joerg Roedel [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=20200514112317.GH18353@8bytes.org \
--to=joro@8bytes.org \
--cc=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 \
--cc=m.szyprowski@samsung.com \
/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.