* Re: next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict (next-20171115)
[not found] <5a0c2169.c6a2df0a.13ea3.9c02@mx.google.com>
@ 2017-11-16 14:42 ` Guillaume Tucker
0 siblings, 0 replies; 8+ messages in thread
From: Guillaume Tucker @ 2017-11-16 14:42 UTC (permalink / raw)
To: Shawn Nematbakhsh
Cc: kernelci.org bot, kernel-build-reports-cunTk1MwBs8s++Sfvej+rw,
Tomeu Vizoso, Mark Brown, Enric Balletbo i Serra,
open list:TEGRA ARCHITECTURE SUPPORT,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
On 15/11/17 11:13, kernelci.org bot wrote:
> next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict (next-20171115)
>
> Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20171115/
> Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20171115/
>
> Tree: next
> Branch: master
> Git Describe: next-20171115
> Git Commit: 63fb091c80188ec51f53514d07de907c1dd3d61d
> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> Tested: 35 unique boards, 16 SoC families, 30 builds out of 213
>
> Boot Regressions Detected:
>
> arm:
[...]
> multi_v7_defconfig:
> tegra124-nyan-big:
> lab-collabora: failing since 11 days (last pass: next-20171102 - first fail: next-20171103)
I've run another automated bisection with some tweaks to remove
known failures and found this breaking change:
commit 859eb05676f67d4960130dff36d3368006716110
Author: Shawn Nematbakhsh <shawnn-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Date: Fri Sep 8 13:50:11 2017 -0700
platform/chrome: Use proper protocol transfer function
The bisection was run with CONFIG_MODULES and CONFIG_DRM_NOUVEAU
disabled and d89e2378a97fafdc74cbf997e7c88af75b81610a ("drivers:
flag buses which demand DMA configuration") reverted in each
iteration as these things are known to cause other boot failures.
See the full log here (from staging.kernelci.org Jenkins):
https://people.collabora.com/~gtucker/kernelci/bisections/20171116-nyan-big-next.txt
As the kernelci.org automated bisection tool is still
experimental, I then did a couple of checks to confirm whether
this commit was still an issue:
* 859eb056 with MODULES and DRM_NOUVEAU disabled, failed:
https://lava.collabora.co.uk/scheduler/job/992002
* same as above but with 859eb056 reverted in-place, passes:
https://lava.collabora.co.uk/scheduler/job/992003
* next-20171115 with MODULES and DRM_NOUVEAU disabled, and
d89e2378 reverted, fails:
https://lava.collabora.co.uk/scheduler/job/992004
* same as above but with 859eb056 reverted on top, passes:
https://lava.collabora.co.uk/scheduler/job/992005
So this shows the commit found by the bisection seems to be still
causing problems on tegra124-nyan-big. I haven't investigated
any further, I don't know if other platforms show the same
symptoms. At least this should narrow things down a bit.
Note: With this in mind, another possible bisection would be to
enable DRM_NOUVEAU again while reverting the 2 known breaking
commits and try to find what is actually causing the issue in
that driver. I'm not planning to do this right now though...
Hope this helps!
Guillaume
> ---
> For more info write to <info-ssFOTAMYnuFg9hUCZPvPmw@public.gmane.org>
>
>
>
> _______________________________________________
> Kernel-build-reports mailing list
> Kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org
> https://lists.linaro.org/mailman/listinfo/kernel-build-reports
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict (next-20171115)
@ 2017-11-16 14:42 ` Guillaume Tucker
0 siblings, 0 replies; 8+ messages in thread
From: Guillaume Tucker @ 2017-11-16 14:42 UTC (permalink / raw)
To: linux-arm-kernel
On 15/11/17 11:13, kernelci.org bot wrote:
> next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict (next-20171115)
>
> Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20171115/
> Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20171115/
>
> Tree: next
> Branch: master
> Git Describe: next-20171115
> Git Commit: 63fb091c80188ec51f53514d07de907c1dd3d61d
> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> Tested: 35 unique boards, 16 SoC families, 30 builds out of 213
>
> Boot Regressions Detected:
>
> arm:
[...]
> multi_v7_defconfig:
> tegra124-nyan-big:
> lab-collabora: failing since 11 days (last pass: next-20171102 - first fail: next-20171103)
I've run another automated bisection with some tweaks to remove
known failures and found this breaking change:
commit 859eb05676f67d4960130dff36d3368006716110
Author: Shawn Nematbakhsh <shawnn@chromium.org>
Date: Fri Sep 8 13:50:11 2017 -0700
platform/chrome: Use proper protocol transfer function
The bisection was run with CONFIG_MODULES and CONFIG_DRM_NOUVEAU
disabled and d89e2378a97fafdc74cbf997e7c88af75b81610a ("drivers:
flag buses which demand DMA configuration") reverted in each
iteration as these things are known to cause other boot failures.
See the full log here (from staging.kernelci.org Jenkins):
https://people.collabora.com/~gtucker/kernelci/bisections/20171116-nyan-big-next.txt
As the kernelci.org automated bisection tool is still
experimental, I then did a couple of checks to confirm whether
this commit was still an issue:
* 859eb056 with MODULES and DRM_NOUVEAU disabled, failed:
https://lava.collabora.co.uk/scheduler/job/992002
* same as above but with 859eb056 reverted in-place, passes:
https://lava.collabora.co.uk/scheduler/job/992003
* next-20171115 with MODULES and DRM_NOUVEAU disabled, and
d89e2378 reverted, fails:
https://lava.collabora.co.uk/scheduler/job/992004
* same as above but with 859eb056 reverted on top, passes:
https://lava.collabora.co.uk/scheduler/job/992005
So this shows the commit found by the bisection seems to be still
causing problems on tegra124-nyan-big. I haven't investigated
any further, I don't know if other platforms show the same
symptoms. At least this should narrow things down a bit.
Note: With this in mind, another possible bisection would be to
enable DRM_NOUVEAU again while reverting the 2 known breaking
commits and try to find what is actually causing the issue in
that driver. I'm not planning to do this right now though...
Hope this helps!
Guillaume
> ---
> For more info write to <info@kernelci.org>
>
>
>
> _______________________________________________
> Kernel-build-reports mailing list
> Kernel-build-reports at lists.linaro.org
> https://lists.linaro.org/mailman/listinfo/kernel-build-reports
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict (next-20171115)
2017-11-16 14:42 ` Guillaume Tucker
@ 2017-11-16 14:50 ` Guillaume Tucker
-1 siblings, 0 replies; 8+ messages in thread
From: Guillaume Tucker @ 2017-11-16 14:50 UTC (permalink / raw)
To: Shawn Nematbakhsh
Cc: kernelci.org bot, kernel-build-reports-cunTk1MwBs8s++Sfvej+rw,
Tomeu Vizoso, Mark Brown, Enric Balletbo i Serra,
open list:TEGRA ARCHITECTURE SUPPORT,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
On 16/11/17 14:42, Guillaume Tucker wrote:
> On 15/11/17 11:13, kernelci.org bot wrote:
>> next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict (next-20171115)
>>
>> Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20171115/
>> Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20171115/
>>
>> Tree: next
>> Branch: master
>> Git Describe: next-20171115
>> Git Commit: 63fb091c80188ec51f53514d07de907c1dd3d61d
>> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>> Tested: 35 unique boards, 16 SoC families, 30 builds out of 213
>>
>> Boot Regressions Detected:
>>
>> arm:
> [...]
>> multi_v7_defconfig:
>> tegra124-nyan-big:
>> lab-collabora: failing since 11 days (last pass: next-20171102 - first fail: next-20171103)
>
> I've run another automated bisection with some tweaks to remove
> known failures and found this breaking change:
>
> commit 859eb05676f67d4960130dff36d3368006716110
> Author: Shawn Nematbakhsh <shawnn-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
> Date: Fri Sep 8 13:50:11 2017 -0700
>
> platform/chrome: Use proper protocol transfer function
>
>
Should have added, this is essentially the kernel error:
[ 1.711581] kernel BUG at drivers/platform/chrome/cros_ec_proto.c:34!
[ 1.718004] Internal error: Oops - BUG: 0 [#1] SMP ARM
Please see the links to the LAVA jobs below for the full logs.
> The bisection was run with CONFIG_MODULES and CONFIG_DRM_NOUVEAU
> disabled and d89e2378a97fafdc74cbf997e7c88af75b81610a ("drivers:
> flag buses which demand DMA configuration") reverted in each
> iteration as these things are known to cause other boot failures.
> See the full log here (from staging.kernelci.org Jenkins):
>
> https://people.collabora.com/~gtucker/kernelci/bisections/20171116-nyan-big-next.txt
>
> As the kernelci.org automated bisection tool is still
> experimental, I then did a couple of checks to confirm whether
> this commit was still an issue:
>
> * 859eb056 with MODULES and DRM_NOUVEAU disabled, failed:
> https://lava.collabora.co.uk/scheduler/job/992002
>
> * same as above but with 859eb056 reverted in-place, passes:
> https://lava.collabora.co.uk/scheduler/job/992003
>
> * next-20171115 with MODULES and DRM_NOUVEAU disabled, and
> d89e2378 reverted, fails:
> https://lava.collabora.co.uk/scheduler/job/992004
>
> * same as above but with 859eb056 reverted on top, passes:
> https://lava.collabora.co.uk/scheduler/job/992005
>
> So this shows the commit found by the bisection seems to be still
> causing problems on tegra124-nyan-big. I haven't investigated
> any further, I don't know if other platforms show the same
> symptoms. At least this should narrow things down a bit.
>
> Note: With this in mind, another possible bisection would be to
> enable DRM_NOUVEAU again while reverting the 2 known breaking
> commits and try to find what is actually causing the issue in
> that driver. I'm not planning to do this right now though...
>
> Hope this helps!
>
> Guillaume
>
>> ---
>> For more info write to <info-ssFOTAMYnuFg9hUCZPvPmw@public.gmane.org>
>>
>>
>>
>> _______________________________________________
>> Kernel-build-reports mailing list
>> Kernel-build-reports-cunTk1MwBs8s++Sfvej+rw@public.gmane.org
>> https://lists.linaro.org/mailman/listinfo/kernel-build-reports
>>
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict (next-20171115)
@ 2017-11-16 14:50 ` Guillaume Tucker
0 siblings, 0 replies; 8+ messages in thread
From: Guillaume Tucker @ 2017-11-16 14:50 UTC (permalink / raw)
To: linux-arm-kernel
On 16/11/17 14:42, Guillaume Tucker wrote:
> On 15/11/17 11:13, kernelci.org bot wrote:
>> next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict (next-20171115)
>>
>> Full Boot Summary: https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20171115/
>> Full Build Summary: https://kernelci.org/build/next/branch/master/kernel/next-20171115/
>>
>> Tree: next
>> Branch: master
>> Git Describe: next-20171115
>> Git Commit: 63fb091c80188ec51f53514d07de907c1dd3d61d
>> Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>> Tested: 35 unique boards, 16 SoC families, 30 builds out of 213
>>
>> Boot Regressions Detected:
>>
>> arm:
> [...]
>> multi_v7_defconfig:
>> tegra124-nyan-big:
>> lab-collabora: failing since 11 days (last pass: next-20171102 - first fail: next-20171103)
>
> I've run another automated bisection with some tweaks to remove
> known failures and found this breaking change:
>
> commit 859eb05676f67d4960130dff36d3368006716110
> Author: Shawn Nematbakhsh <shawnn@chromium.org>
> Date: Fri Sep 8 13:50:11 2017 -0700
>
> platform/chrome: Use proper protocol transfer function
>
>
Should have added, this is essentially the kernel error:
[ 1.711581] kernel BUG at drivers/platform/chrome/cros_ec_proto.c:34!
[ 1.718004] Internal error: Oops - BUG: 0 [#1] SMP ARM
Please see the links to the LAVA jobs below for the full logs.
> The bisection was run with CONFIG_MODULES and CONFIG_DRM_NOUVEAU
> disabled and d89e2378a97fafdc74cbf997e7c88af75b81610a ("drivers:
> flag buses which demand DMA configuration") reverted in each
> iteration as these things are known to cause other boot failures.
> See the full log here (from staging.kernelci.org Jenkins):
>
> https://people.collabora.com/~gtucker/kernelci/bisections/20171116-nyan-big-next.txt
>
> As the kernelci.org automated bisection tool is still
> experimental, I then did a couple of checks to confirm whether
> this commit was still an issue:
>
> * 859eb056 with MODULES and DRM_NOUVEAU disabled, failed:
> https://lava.collabora.co.uk/scheduler/job/992002
>
> * same as above but with 859eb056 reverted in-place, passes:
> https://lava.collabora.co.uk/scheduler/job/992003
>
> * next-20171115 with MODULES and DRM_NOUVEAU disabled, and
> d89e2378 reverted, fails:
> https://lava.collabora.co.uk/scheduler/job/992004
>
> * same as above but with 859eb056 reverted on top, passes:
> https://lava.collabora.co.uk/scheduler/job/992005
>
> So this shows the commit found by the bisection seems to be still
> causing problems on tegra124-nyan-big. I haven't investigated
> any further, I don't know if other platforms show the same
> symptoms. At least this should narrow things down a bit.
>
> Note: With this in mind, another possible bisection would be to
> enable DRM_NOUVEAU again while reverting the 2 known breaking
> commits and try to find what is actually causing the issue in
> that driver. I'm not planning to do this right now though...
>
> Hope this helps!
>
> Guillaume
>
>> ---
>> For more info write to <info@kernelci.org>
>>
>>
>>
>> _______________________________________________
>> Kernel-build-reports mailing list
>> Kernel-build-reports at lists.linaro.org
>> https://lists.linaro.org/mailman/listinfo/kernel-build-reports
>>
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict (next-20171115)
2017-11-16 14:50 ` Guillaume Tucker
@ 2017-11-16 17:55 ` Jon Hunter
-1 siblings, 0 replies; 8+ messages in thread
From: Jon Hunter @ 2017-11-16 17:55 UTC (permalink / raw)
To: Guillaume Tucker, Shawn Nematbakhsh
Cc: kernelci.org bot, Tomeu Vizoso, kernel-build-reports,
open list:TEGRA ARCHITECTURE SUPPORT, Mark Brown,
Enric Balletbo i Serra, linux-arm-kernel
On 16/11/17 14:50, Guillaume Tucker wrote:
> On 16/11/17 14:42, Guillaume Tucker wrote:
>> On 15/11/17 11:13, kernelci.org bot wrote:
>>> next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict
>>> (next-20171115)
>>>
>>> Full Boot Summary:
>>> https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20171115/
>>>
>>> Full Build Summary:
>>> https://kernelci.org/build/next/branch/master/kernel/next-20171115/
>>>
>>> Tree: next
>>> Branch: master
>>> Git Describe: next-20171115
>>> Git Commit: 63fb091c80188ec51f53514d07de907c1dd3d61d
>>> Git URL:
>>> http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>> Tested: 35 unique boards, 16 SoC families, 30 builds out of 213
>>>
>>> Boot Regressions Detected:
>>>
>>> arm:
>> [...]
>>> multi_v7_defconfig:
>>> tegra124-nyan-big:
>>> lab-collabora: failing since 11 days (last pass:
>>> next-20171102 - first fail: next-20171103)
>>
>> I've run another automated bisection with some tweaks to remove
>> known failures and found this breaking change:
>>
>> commit 859eb05676f67d4960130dff36d3368006716110
>> Author: Shawn Nematbakhsh <shawnn@chromium.org>
>> Date: Fri Sep 8 13:50:11 2017 -0700
>>
>> platform/chrome: Use proper protocol transfer function
>>
>>
>
> Should have added, this is essentially the kernel error:
>
> [ 1.711581] kernel BUG at drivers/platform/chrome/cros_ec_proto.c:34!
> [ 1.718004] Internal error: Oops - BUG: 0 [#1] SMP ARM
>
> Please see the links to the LAVA jobs below for the full logs.
This one is a known issue (which I believe I have mentioned a couple
times). There is a fix available [0].
I am not sure that continuing to bisect this is going to bare any fruit
due to the number of issues plaguing this board at the moment. It seems
to be a DRM related issue and when I get sometime I will see if I can
figure out what is causing this. This is the furtherest I have gotten so
far [1].
Jon
[0] https://patchwork.kernel.org/patch/9974835/
[1] https://www.spinics.net/lists/arm-kernel/msg616616.html
--
nvpublic
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 8+ messages in thread
* next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict (next-20171115)
@ 2017-11-16 17:55 ` Jon Hunter
0 siblings, 0 replies; 8+ messages in thread
From: Jon Hunter @ 2017-11-16 17:55 UTC (permalink / raw)
To: linux-arm-kernel
On 16/11/17 14:50, Guillaume Tucker wrote:
> On 16/11/17 14:42, Guillaume Tucker wrote:
>> On 15/11/17 11:13, kernelci.org bot wrote:
>>> next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict
>>> (next-20171115)
>>>
>>> Full Boot Summary:
>>> https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20171115/
>>>
>>> Full Build Summary:
>>> https://kernelci.org/build/next/branch/master/kernel/next-20171115/
>>>
>>> Tree: next
>>> Branch: master
>>> Git Describe: next-20171115
>>> Git Commit: 63fb091c80188ec51f53514d07de907c1dd3d61d
>>> Git URL:
>>> http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>> Tested: 35 unique boards, 16 SoC families, 30 builds out of 213
>>>
>>> Boot Regressions Detected:
>>>
>>> arm:
>> [...]
>>> ??? multi_v7_defconfig:
>>> ??????? tegra124-nyan-big:
>>> ??????????? lab-collabora: failing since 11 days (last pass:
>>> next-20171102 - first fail: next-20171103)
>>
>> I've run another automated bisection with some tweaks to remove
>> known failures and found this breaking change:
>>
>> ? commit 859eb05676f67d4960130dff36d3368006716110
>> ? Author: Shawn Nematbakhsh <shawnn@chromium.org>
>> ? Date:?? Fri Sep 8 13:50:11 2017 -0700
>>
>> ????? platform/chrome: Use proper protocol transfer function
>>
>>
>
> Should have added, this is essentially the kernel error:
>
> [??? 1.711581] kernel BUG at drivers/platform/chrome/cros_ec_proto.c:34!
> [??? 1.718004] Internal error: Oops - BUG: 0 [#1] SMP ARM
>
> Please see the links to the LAVA jobs below for the full logs.
This one is a known issue (which I believe I have mentioned a couple
times). There is a fix available [0].
I am not sure that continuing to bisect this is going to bare any fruit
due to the number of issues plaguing this board at the moment. It seems
to be a DRM related issue and when I get sometime I will see if I can
figure out what is causing this. This is the furtherest I have gotten so
far [1].
Jon
[0] https://patchwork.kernel.org/patch/9974835/
[1] https://www.spinics.net/lists/arm-kernel/msg616616.html
--
nvpublic
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict (next-20171115)
2017-11-16 17:55 ` Jon Hunter
@ 2017-11-16 19:01 ` Guillaume Tucker
-1 siblings, 0 replies; 8+ messages in thread
From: Guillaume Tucker @ 2017-11-16 19:01 UTC (permalink / raw)
To: Jon Hunter, Shawn Nematbakhsh
Cc: kernel-build-reports-cunTk1MwBs8s++Sfvej+rw, Tomeu Vizoso,
Mark Brown, Enric Balletbo i Serra,
open list:TEGRA ARCHITECTURE SUPPORT,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r
On 16/11/17 17:55, Jon Hunter wrote:
>
> On 16/11/17 14:50, Guillaume Tucker wrote:
>> On 16/11/17 14:42, Guillaume Tucker wrote:
>>> On 15/11/17 11:13, kernelci.org bot wrote:
>>>> next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict
>>>> (next-20171115)
>>>>
>>>> Full Boot Summary:
>>>> https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20171115/
>>>>
>>>> Full Build Summary:
>>>> https://kernelci.org/build/next/branch/master/kernel/next-20171115/
>>>>
>>>> Tree: next
>>>> Branch: master
>>>> Git Describe: next-20171115
>>>> Git Commit: 63fb091c80188ec51f53514d07de907c1dd3d61d
>>>> Git URL:
>>>> http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>>> Tested: 35 unique boards, 16 SoC families, 30 builds out of 213
>>>>
>>>> Boot Regressions Detected:
>>>>
>>>> arm:
>>> [...]
>>>> multi_v7_defconfig:
>>>> tegra124-nyan-big:
>>>> lab-collabora: failing since 11 days (last pass:
>>>> next-20171102 - first fail: next-20171103)
>>>
>>> I've run another automated bisection with some tweaks to remove
>>> known failures and found this breaking change:
>>>
>>> commit 859eb05676f67d4960130dff36d3368006716110
>>> Author: Shawn Nematbakhsh <shawnn-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
>>> Date: Fri Sep 8 13:50:11 2017 -0700
>>>
>>> platform/chrome: Use proper protocol transfer function
>>>
>>>
>>
>> Should have added, this is essentially the kernel error:
>>
>> [ 1.711581] kernel BUG at drivers/platform/chrome/cros_ec_proto.c:34!
>> [ 1.718004] Internal error: Oops - BUG: 0 [#1] SMP ARM
>>
>> Please see the links to the LAVA jobs below for the full logs.
> This one is a known issue (which I believe I have mentioned a couple
> times). There is a fix available [0].
Right, it's true that this kernel error showed up in the previous
bisection I ran last week. As this time it found another commit
I thought it might be worthwhile sharing the result.
> I am not sure that continuing to bisect this is going to bare any fruit
> due to the number of issues plaguing this board at the moment. It seems
> to be a DRM related issue and when I get sometime I will see if I can
> figure out what is causing this. This is the furtherest I have gotten so
> far [1].
Thanks for the update. Please keep in mind that DRM_MOUVEAU was
disabled in every iteration this time, so there might also be
something else unrelated to DRM.
Agreed, it's not worth bisecting much further. In fact I found
these issues mostly as a side effect of working on the automatic
bisection mechanism in kernelci.org, and linux-next is especially
tricky to bisect. On this subject, we'll probably start by
enabling this on stable trees and mainline, then see what we can
do with linux-next and other tricky trees at a later stage.
Thanks,
Guillaume
> [0] https://patchwork.kernel.org/patch/9974835/
> [1] https://www.spinics.net/lists/arm-kernel/msg616616.html
^ permalink raw reply [flat|nested] 8+ messages in thread
* next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict (next-20171115)
@ 2017-11-16 19:01 ` Guillaume Tucker
0 siblings, 0 replies; 8+ messages in thread
From: Guillaume Tucker @ 2017-11-16 19:01 UTC (permalink / raw)
To: linux-arm-kernel
On 16/11/17 17:55, Jon Hunter wrote:
>
> On 16/11/17 14:50, Guillaume Tucker wrote:
>> On 16/11/17 14:42, Guillaume Tucker wrote:
>>> On 15/11/17 11:13, kernelci.org bot wrote:
>>>> next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict
>>>> (next-20171115)
>>>>
>>>> Full Boot Summary:
>>>> https://kernelci.org/boot/all/job/next/branch/master/kernel/next-20171115/
>>>>
>>>> Full Build Summary:
>>>> https://kernelci.org/build/next/branch/master/kernel/next-20171115/
>>>>
>>>> Tree: next
>>>> Branch: master
>>>> Git Describe: next-20171115
>>>> Git Commit: 63fb091c80188ec51f53514d07de907c1dd3d61d
>>>> Git URL:
>>>> http://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>>> Tested: 35 unique boards, 16 SoC families, 30 builds out of 213
>>>>
>>>> Boot Regressions Detected:
>>>>
>>>> arm:
>>> [...]
>>>> multi_v7_defconfig:
>>>> tegra124-nyan-big:
>>>> lab-collabora: failing since 11 days (last pass:
>>>> next-20171102 - first fail: next-20171103)
>>>
>>> I've run another automated bisection with some tweaks to remove
>>> known failures and found this breaking change:
>>>
>>> commit 859eb05676f67d4960130dff36d3368006716110
>>> Author: Shawn Nematbakhsh <shawnn@chromium.org>
>>> Date: Fri Sep 8 13:50:11 2017 -0700
>>>
>>> platform/chrome: Use proper protocol transfer function
>>>
>>>
>>
>> Should have added, this is essentially the kernel error:
>>
>> [ 1.711581] kernel BUG at drivers/platform/chrome/cros_ec_proto.c:34!
>> [ 1.718004] Internal error: Oops - BUG: 0 [#1] SMP ARM
>>
>> Please see the links to the LAVA jobs below for the full logs.
> This one is a known issue (which I believe I have mentioned a couple
> times). There is a fix available [0].
Right, it's true that this kernel error showed up in the previous
bisection I ran last week. As this time it found another commit
I thought it might be worthwhile sharing the result.
> I am not sure that continuing to bisect this is going to bare any fruit
> due to the number of issues plaguing this board at the moment. It seems
> to be a DRM related issue and when I get sometime I will see if I can
> figure out what is causing this. This is the furtherest I have gotten so
> far [1].
Thanks for the update. Please keep in mind that DRM_MOUVEAU was
disabled in every iteration this time, so there might also be
something else unrelated to DRM.
Agreed, it's not worth bisecting much further. In fact I found
these issues mostly as a side effect of working on the automatic
bisection mechanism in kernelci.org, and linux-next is especially
tricky to bisect. On this subject, we'll probably start by
enabling this on stable trees and mainline, then see what we can
do with linux-next and other tricky trees at a later stage.
Thanks,
Guillaume
> [0] https://patchwork.kernel.org/patch/9974835/
> [1] https://www.spinics.net/lists/arm-kernel/msg616616.html
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2017-11-16 19:01 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <5a0c2169.c6a2df0a.13ea3.9c02@mx.google.com>
[not found] ` <5a0c2169.c6a2df0a.13ea3.9c02-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org>
2017-11-16 14:42 ` next/master boot: 210 boots: 35 failed, 174 passed with 1 conflict (next-20171115) Guillaume Tucker
2017-11-16 14:42 ` Guillaume Tucker
[not found] ` <a21b88b2-663d-49fc-527a-87494a23087f-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2017-11-16 14:50 ` Guillaume Tucker
2017-11-16 14:50 ` Guillaume Tucker
2017-11-16 17:55 ` Jon Hunter
2017-11-16 17:55 ` Jon Hunter
[not found] ` <3ddf8ad5-e3d9-49cc-9e20-2d8cdbc9685f-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-11-16 19:01 ` Guillaume Tucker
2017-11-16 19:01 ` Guillaume Tucker
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.