[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f45c94b4-2949-4eac-5944-85d43a8afef5@collabora.com>
Date: Sat, 6 Feb 2021 13:40:13 +0000
From: Guillaume Tucker <guillaume.tucker@...labora.com>
To: Nicolin Chen <nicoleotsuka@...il.com>
Cc: will@...nel.org, linux-kernel@...r.kernel.org,
iommu@...ts.linux-foundation.org, linux-tegra@...r.kernel.org,
jonathanh@...dia.com, vdumpa@...dia.com, thierry.reding@...il.com,
joro@...tes.org, kernel@...labora.com,
Dmitry Osipenko <digetx@...il.com>,
"kernelci-results@...ups.io" <kernelci-results@...ups.io>
Subject: Re: [PATCH RESEND v2 4/5] iommu/tegra-smmu: Rework
tegra_smmu_probe_device()
On 05/02/2021 09:45, Nicolin Chen wrote:
> Hi Guillaume,
>
> On Thu, Feb 04, 2021 at 09:24:23PM -0800, Nicolin Chen wrote:
>>> Please let us know if you need any help debugging this issue or
>>> to try a fix on this platform.
>>
>> Yes, I don't have any Tegra124 platform to run. It'd be very nice
>> if you can run some debugging patch (I can provide you) and a fix
>> after I root cause the issue.
>
> Would it be possible for you to run with the given debugging patch?
>
> It'd be nicer if I can get both logs of the vanilla kernel (failing)
> and the commit-reverted version (passing), each applying this patch.
Sure, I've run 3 jobs:
* v5.11-rc6 as a reference, to see the original issue:
https://lava.collabora.co.uk/scheduler/job/3187848
* + your debug patch:
https://lava.collabora.co.uk/scheduler/job/3187849
* + the "breaking" commit reverted, passing the tests:
https://lava.collabora.co.uk/scheduler/job/3187851
You can see the history of the test branch I'm using here, with
the 3 revisions mentioned above:
https://gitlab.collabora.com/gtucker/linux/-/commits/linux-5.11-rc6-nyan-big-drm-read/
Hope that helps,
Guillaume
Powered by blists - more mailing lists