public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Guillaume Tucker <guillaume.tucker@collabora.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Robin Murphy <robin.murphy@arm.com>,
	bskeggs@redhat.com
Cc: "open list:TEGRA ARCHITECTURE SUPPORT"
	<linux-tegra@vger.kernel.org>, Mark Brown <broonie@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	"kernelci.org bot" <bot@kernelci.org>,
	Kernel Build Reports Mailman List
	<kernel-build-reports@lists.linaro.org>
Subject: Re: next/master boot: 273 boots: 63 failed, 209 passed with 1 untried/unknown (next-20171106)
Date: Thu, 9 Nov 2017 21:45:07 +0000	[thread overview]
Message-ID: <2038e32a-de4a-a683-462e-555e991a2111@nvidia.com> (raw)
In-Reply-To: <bfed6e80-44a7-6e96-c6a6-bc9793a1937a@collabora.com>


On 09/11/17 19:03, Guillaume Tucker wrote:
...

> Alright, so here's all the results I got all based on
> next-20171109 and running on tegra124-nyan-big:
> 
>   * plain multi_v7_defconfig, passes:
>     https://lava.collabora.co.uk/scheduler/job/981295
> 
>   * CONFIG_MODULES disabled, fails:
>     https://lava.collabora.co.uk/scheduler/job/981342
> 
>   * CONFIG_MODULES and CONFIG_DRM_NOUVEAU disabled, also fails:
>     https://lava.collabora.co.uk/scheduler/job/981343

This is the crash in the EC driver that I mentioned before. You need to
add the fix for the EC driver to avoid this BUG_ON.

I was able to bisect this manually dancing around the various bugs and
it points to this commit ...

commit 7313cfa4f6e30384fa04083698d1e865cf812a6a
Author: Ben Skeggs <bskeggs@redhat.com>
Date:   Wed Nov 1 03:56:19 2017 +1000

    drm/nouveau/bar: move bar1 initialisation into its own function


Unfortunately, I cannot revert cleanly on top of next-20171109 and so I
cannot confirm.

Ben, we are seeing a hang on Tegra when booting with CONFIG_DRM_NOUVEAU
enabled. Apart from the above bisect result, I don't have much else to
go on at the moment. Let me know if you have any thoughts or anything to
test.

Cheers
Jon

-- 
nvpublic

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2017-11-09 21:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5a0055f1.85a8500a.98d54.a4e4@mx.google.com>
     [not found] ` <5a0055f1.85a8500a.98d54.a4e4-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org>
2017-11-06 19:17   ` next/master boot: 273 boots: 63 failed, 209 passed with 1 untried/unknown (next-20171106) Mark Brown
2017-11-07 10:12     ` Jon Hunter
     [not found]       ` <d8e21d87-776b-beff-62af-34e5ad1febc3-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-07 10:55         ` Mark Brown
     [not found]           ` <20171107105501.7x74gdqzhr7uulp2-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2017-11-07 11:43             ` Guillaume Tucker
     [not found]               ` <a384e96c-27c7-782b-75b9-7525714f5831-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2017-11-08 15:19                 ` Guillaume Tucker
     [not found]                   ` <613bcd63-a215-acbe-9150-c1495f7604f6-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2017-11-08 15:55                     ` Robin Murphy
     [not found]                       ` <7ce29bba-485c-b063-961a-3a745718357f-5wv7dgnIgG8@public.gmane.org>
2017-11-08 16:23                         ` Mikko Perttunen
     [not found]                           ` <cdac9d47-42ce-b5c2-b325-68726d194888-/1wQRMveznE@public.gmane.org>
2017-11-08 16:47                             ` Robin Murphy
2017-11-08 15:57                   ` Jon Hunter
     [not found]                     ` <5740b853-4898-2ebc-f67d-0808d1b44c36-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-08 16:42                       ` Guillaume Tucker
2017-11-09  9:55                         ` Jon Hunter
     [not found]                           ` <7cdfa633-d9c6-881a-ae5f-f94f7e6413ee-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-09 10:43                             ` Guillaume Tucker
2017-11-09 11:29                               ` Jon Hunter
     [not found]                                 ` <15792a16-6b57-a6ad-92dc-0ffaba0354db-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-09 12:51                                   ` Guillaume Tucker
     [not found]                                     ` <1eb4e14f-4728-d4f7-95a6-0a6308760d7a-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2017-11-09 13:17                                       ` Arnd Bergmann
2017-11-09 15:23                                         ` Jon Hunter
     [not found]                                           ` <18ef379f-0c23-0cbf-4228-30d5c46c690f-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-09 19:03                                             ` Guillaume Tucker
2017-11-09 21:45                                               ` Jon Hunter [this message]
2017-11-09 22:54                                                 ` Jon Hunter
     [not found]                                                   ` <5505affd-58a5-857f-051d-5b93257e175d@redhat.com>
     [not found]                                                     ` <5505affd-58a5-857f-051d-5b93257e175d-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-11-10  9:18                                                       ` Jon Hunter
     [not found]                                                         ` <1040af29-4d15-4e8a-29ab-40952523535c-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-10 11:26                                                           ` Jon Hunter

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=2038e32a-de4a-a683-462e-555e991a2111@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=arnd@arndb.de \
    --cc=bot@kernelci.org \
    --cc=broonie@kernel.org \
    --cc=bskeggs@redhat.com \
    --cc=guillaume.tucker@collabora.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=robin.murphy@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox