From: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org> To: Guillaume Tucker <guillaume.tucker-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>, Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, "kernelci.org bot" <bot-ssFOTAMYnuFg9hUCZPvPmw@public.gmane.org>, kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org Subject: Re: next/master boot: 273 boots: 63 failed, 209 passed with 1 untried/unknown (next-20171106) Date: Wed, 8 Nov 2017 15:55:38 +0000 [thread overview] Message-ID: <7ce29bba-485c-b063-961a-3a745718357f@arm.com> (raw) In-Reply-To: <613bcd63-a215-acbe-9150-c1495f7604f6-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org> On 08/11/17 15:19, Guillaume Tucker wrote: > On 07/11/17 11:43, Guillaume Tucker wrote: >> On 07/11/17 10:55, Mark Brown wrote: >>> On Tue, Nov 07, 2017 at 10:12:59AM +0000, Jon Hunter wrote: >>>> On 06/11/17 19:17, Mark Brown wrote: >>> >>>>>> multi_v7_defconfig: >>>>>> tegra124-nyan-big: >>>>>> lab-collabora: failing since 2 days (last pass: >>>>>> next-20171102 - first fail: next-20171103) >>> >>>> Thanks for the report. I have been looking into a failure on nyan-big >>>> [0], but this one looks like a new failure. I will take a look. >>> >>> Guillaume Tucker has been bisecting this with the shiny new bisection >>> code he's testing, he was saying on IRC he thinks he's found the >>> offending commit: >>> >>> >>> https://people.collabora.com/~gtucker/tmp/bisect-tegra-4.14.rc8-next-20171106.txt >>> >>> >>> (not CCing Johannes yet) >> >> Please take this with a pinch of salt, I'm now running some extra >> boot tests to prove it. If you look at this log, all the boots >> passed which is a bit suspicious. I did build and boot the >> revision it found with multi_v7_defconfig on tegra124 and it >> passed, so it looks like this commit may not have anything to do >> with the boot failure. The automated bisection is still experimental. >> >> Passing LAVA boot test with this revision: >> >> https://lava.collabora.co.uk/scheduler/job/976375 >> >> I've started a slightly different bisection job now on >> next-20171107 and the common ancestor between next and mainline, >> results can take a few hours to come back. > > After a few more automated bisection attempts and a bug fix in > LAVA, I've now found at least one potentially breaking commit: > > commit d89e2378a97fafdc74cbf997e7c88af75b81610a > Author: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org> > Date: Thu Oct 12 16:56:14 2017 +0100 > > drivers: flag buses which demand DMA configuration > > > I've run some boot tests manually with this revision and then > also after reverting it in-place, these respectively failed and > passed: > > * d89e2378, failed: > https://lava.collabora.co.uk/scheduler/job/978968 > > * d89e2378 reverted, passed: > https://lava.collabora.co.uk/scheduler/job/978969 > > > I then went on and tried the same but on top of next-20171108 and > found that they both failed > > * next-20171108, failed: > https://lava.collabora.co.uk/scheduler/job/979063 > > * next-20171108 with d89e2378 reverted, failed as well: > https://lava.collabora.co.uk/scheduler/job/979167 > > > So this shows there is almost certainly another offending commit > in -next. The errors in both cases are not quite the same, the > last one is triggered by a BUG whereas the first one is a NULL > pointer (I haven't looked any further). Also I don't think > there's any fix for d89e2378a97fafdc74cbf997e7c88af75b81610a > which is currently still in next. The fix was actually posted before said commit was even written: https://patchwork.kernel.org/patch/9967847/ What is currently queued in the DMA tree fell out of the discussion on patch 2 of that series, but I kind of assumed the host1x folks would still take patch 1; I guess that hasn't happened. Robin. > > Note: This happens to be a very good example of running a > kernelci.org bisection on a real issue, it's quite a bit of a > pipe cleaner. I'll now see if there's a way to bisect what looks > like another breaking change in-between. > > Guillaume
WARNING: multiple messages have this Message-ID (diff)
From: robin.murphy@arm.com (Robin Murphy) To: linux-arm-kernel@lists.infradead.org Subject: next/master boot: 273 boots: 63 failed, 209 passed with 1 untried/unknown (next-20171106) Date: Wed, 8 Nov 2017 15:55:38 +0000 [thread overview] Message-ID: <7ce29bba-485c-b063-961a-3a745718357f@arm.com> (raw) In-Reply-To: <613bcd63-a215-acbe-9150-c1495f7604f6@collabora.com> On 08/11/17 15:19, Guillaume Tucker wrote: > On 07/11/17 11:43, Guillaume Tucker wrote: >> On 07/11/17 10:55, Mark Brown wrote: >>> On Tue, Nov 07, 2017 at 10:12:59AM +0000, Jon Hunter wrote: >>>> On 06/11/17 19:17, Mark Brown wrote: >>> >>>>>> ??? multi_v7_defconfig: >>>>>> ??????? tegra124-nyan-big: >>>>>> ??????????? lab-collabora: failing since 2 days (last pass: >>>>>> next-20171102 - first fail: next-20171103) >>> >>>> Thanks for the report. I have been looking into a failure on nyan-big >>>> [0], but this one looks like a new failure. I will take a look. >>> >>> Guillaume Tucker has been bisecting this with the shiny new bisection >>> code he's testing, he was saying on IRC he thinks he's found the >>> offending commit: >>> >>> >>> https://people.collabora.com/~gtucker/tmp/bisect-tegra-4.14.rc8-next-20171106.txt >>> >>> >>> (not CCing Johannes yet) >> >> Please take this with a pinch of salt, I'm now running some extra >> boot tests to prove it.? If you look at this log, all the boots >> passed which is a bit suspicious.? I did build and boot the >> revision it found with multi_v7_defconfig on tegra124 and it >> passed, so it looks like this commit may not have anything to do >> with the boot failure.? The automated bisection is still experimental. >> >> Passing LAVA boot test with this revision: >> >> ? https://lava.collabora.co.uk/scheduler/job/976375 >> >> I've started a slightly different bisection job now on >> next-20171107 and the common ancestor between next and mainline, >> results can take a few hours to come back. > > After a few more automated bisection attempts and a bug fix in > LAVA, I've now found at least one potentially breaking commit: > > ? commit d89e2378a97fafdc74cbf997e7c88af75b81610a > ? Author: Robin Murphy <robin.murphy@arm.com> > ? Date:?? Thu Oct 12 16:56:14 2017 +0100 > > ????? drivers: flag buses which demand DMA configuration > > > I've run some boot tests manually with this revision and then > also after reverting it in-place, these respectively failed and > passed: > > ? * d89e2378, failed: > ??? https://lava.collabora.co.uk/scheduler/job/978968 > > ? * d89e2378 reverted, passed: > ??? https://lava.collabora.co.uk/scheduler/job/978969 > > > I then went on and tried the same but on top of next-20171108 and > found that they both failed > > ? * next-20171108, failed: > ??? https://lava.collabora.co.uk/scheduler/job/979063 > > ? * next-20171108 with d89e2378 reverted, failed as well: > ??? https://lava.collabora.co.uk/scheduler/job/979167 > > > So this shows there is almost certainly another offending commit > in -next.? The errors in both cases are not quite the same, the > last one is triggered by a BUG whereas the first one is a NULL > pointer (I haven't looked any further).? Also I don't think > there's any fix for d89e2378a97fafdc74cbf997e7c88af75b81610a > which is currently still in next. The fix was actually posted before said commit was even written: https://patchwork.kernel.org/patch/9967847/ What is currently queued in the DMA tree fell out of the discussion on patch 2 of that series, but I kind of assumed the host1x folks would still take patch 1; I guess that hasn't happened. Robin. > > Note: This happens to be a very good example of running a > kernelci.org bisection on a real issue, it's quite a bit of a > pipe cleaner.? I'll now see if there's a way to bisect what looks > like another breaking change in-between. > > Guillaume
next prev parent reply other threads:[~2017-11-08 15:55 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <5a0055f1.85a8500a.98d54.a4e4@mx.google.com> 2017-11-06 18:47 ` next/master boot: 273 boots: 63 failed, 209 passed with 1 untried/unknown (next-20171106) Mark Brown 2017-11-07 2:17 ` Will Deacon 2017-11-07 11:30 ` Mark Brown [not found] ` <5a0055f1.85a8500a.98d54.a4e4-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org> 2017-11-06 19:17 ` Mark Brown 2017-11-06 19:17 ` Mark Brown 2017-11-07 10:12 ` Jon Hunter 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 2017-11-07 10:55 ` Mark Brown [not found] ` <20171107105501.7x74gdqzhr7uulp2-GFdadSzt00ze9xe1eoZjHA@public.gmane.org> 2017-11-07 11:43 ` Guillaume Tucker 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 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 [this message] 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 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 16:47 ` Robin Murphy 2017-11-08 15:57 ` Jon Hunter 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-08 16:42 ` Guillaume Tucker 2017-11-09 9:55 ` Jon Hunter 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 10:43 ` Guillaume Tucker 2017-11-09 11:29 ` Jon Hunter 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 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 13:17 ` Arnd Bergmann 2017-11-09 15:23 ` Jon Hunter 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 19:03 ` Guillaume Tucker 2017-11-09 21:45 ` Jon Hunter 2017-11-09 21:45 ` Jon Hunter 2017-11-09 22:54 ` Jon Hunter 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 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 2017-11-10 11:26 ` Jon Hunter 2017-11-06 19:26 ` Mark Brown
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=7ce29bba-485c-b063-961a-3a745718357f@arm.com \ --to=robin.murphy-5wv7dgnigg8@public.gmane.org \ --cc=bot-ssFOTAMYnuFg9hUCZPvPmw@public.gmane.org \ --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \ --cc=guillaume.tucker-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \ --cc=jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \ --cc=kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \ --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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: linkBe 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.