* arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1)
[not found] <5760acd0.571a1c0a.34a58.7333@mx.google.com>
@ 2016-06-15 9:10 ` Arnd Bergmann
2016-06-15 9:18 ` Alexandre Belloni
2016-06-15 18:07 ` Kevin Hilman
0 siblings, 2 replies; 6+ messages in thread
From: Arnd Bergmann @ 2016-06-15 9:10 UTC (permalink / raw)
To: linux-arm-kernel
On Tuesday, June 14, 2016 6:18:08 PM CEST kernelci. org bot wrote:
> arm:
>
> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
> exynos5410-odroidxu: 1 failed lab
>
> multi_v7_defconfig+CONFIG_LKDTM=y:
> exynos5410-odroidxu: 1 failed lab
>
> multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y+CONFIG_ARM_MODULE_PLTS=y:
> exynos5410-odroidxu: 1 failed lab
>
> multi_v7_defconfig+CONFIG_EFI=y:
> exynos5410-odroidxu: 1 failed lab
>
> exynos_defconfig:
> exynos5410-odroidxu: 1 failed lab
>
> multi_v7_defconfig+CONFIG_ARM_LPAE=y:
> exynos5410-odroidxu: 1 failed lab
>
> multi_v7_defconfig:
> exynos5410-odroidxu: 1 failed lab
>
> multi_v5_defconfig:
> at91sam9261ek: 1 failed lab
> at91sam9m10g45ek: 1 failed lab
> at91sam9x25ek: 1 failed lab
> at91sam9x35ek: 1 failed lab
These all seem to have broken after yesterday's merges, adding
Alexandre and Krzysztof to Cc here so they can have a look.
Arnd
^ permalink raw reply [flat|nested] 6+ messages in thread
* arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1)
2016-06-15 9:10 ` arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1) Arnd Bergmann
@ 2016-06-15 9:18 ` Alexandre Belloni
2016-06-15 10:50 ` Arnd Bergmann
2016-06-15 18:07 ` Kevin Hilman
1 sibling, 1 reply; 6+ messages in thread
From: Alexandre Belloni @ 2016-06-15 9:18 UTC (permalink / raw)
To: linux-arm-kernel
On 15/06/2016 at 11:10:29 +0200, Arnd Bergmann wrote :
> On Tuesday, June 14, 2016 6:18:08 PM CEST kernelci. org bot wrote:
> > arm:
> >
> > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
> > exynos5410-odroidxu: 1 failed lab
> >
> > multi_v7_defconfig+CONFIG_LKDTM=y:
> > exynos5410-odroidxu: 1 failed lab
> >
> > multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y+CONFIG_ARM_MODULE_PLTS=y:
> > exynos5410-odroidxu: 1 failed lab
> >
> > multi_v7_defconfig+CONFIG_EFI=y:
> > exynos5410-odroidxu: 1 failed lab
> >
> > exynos_defconfig:
> > exynos5410-odroidxu: 1 failed lab
> >
> > multi_v7_defconfig+CONFIG_ARM_LPAE=y:
> > exynos5410-odroidxu: 1 failed lab
> >
> > multi_v7_defconfig:
> > exynos5410-odroidxu: 1 failed lab
> >
> > multi_v5_defconfig:
> > at91sam9261ek: 1 failed lab
> > at91sam9m10g45ek: 1 failed lab
> > at91sam9x25ek: 1 failed lab
> > at91sam9x35ek: 1 failed lab
>
> These all seem to have broken after yesterday's merges, adding
> Alexandre and Krzysztof to Cc here so they can have a look.
>
Well, multi_v5 is not broken, this is an issue with the lab setup that
is being solved right now.
As for multi_v7, as the 8250 driver is included in multi_v5, the Atmel
UARTs are called ttyATx instead of ttySx. Until now,
"console=ttyS0,115200" was passed to the kernel, hence no output was
present on the UART but the boards are booting fine.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1)
2016-06-15 9:18 ` Alexandre Belloni
@ 2016-06-15 10:50 ` Arnd Bergmann
0 siblings, 0 replies; 6+ messages in thread
From: Arnd Bergmann @ 2016-06-15 10:50 UTC (permalink / raw)
To: linux-arm-kernel
On Wednesday, June 15, 2016 11:18:06 AM CEST Alexandre Belloni wrote:
> On 15/06/2016 at 11:10:29 +0200, Arnd Bergmann wrote :
> > On Tuesday, June 14, 2016 6:18:08 PM CEST kernelci. org bot wrote:
> > > arm:
> > >
> > > multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
> > > exynos5410-odroidxu: 1 failed lab
> > >
> > > multi_v7_defconfig+CONFIG_LKDTM=y:
> > > exynos5410-odroidxu: 1 failed lab
> > >
> > > multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y+CONFIG_ARM_MODULE_PLTS=y:
> > > exynos5410-odroidxu: 1 failed lab
> > >
> > > multi_v7_defconfig+CONFIG_EFI=y:
> > > exynos5410-odroidxu: 1 failed lab
> > >
> > > exynos_defconfig:
> > > exynos5410-odroidxu: 1 failed lab
> > >
> > > multi_v7_defconfig+CONFIG_ARM_LPAE=y:
> > > exynos5410-odroidxu: 1 failed lab
> > >
> > > multi_v7_defconfig:
> > > exynos5410-odroidxu: 1 failed lab
> > >
> > > multi_v5_defconfig:
> > > at91sam9261ek: 1 failed lab
> > > at91sam9m10g45ek: 1 failed lab
> > > at91sam9x25ek: 1 failed lab
> > > at91sam9x35ek: 1 failed lab
> >
> > These all seem to have broken after yesterday's merges, adding
> > Alexandre and Krzysztof to Cc here so they can have a look.
> >
>
> Well, multi_v5 is not broken, this is an issue with the lab setup that
> is being solved right now.
> As for multi_v7, as the 8250 driver is included in multi_v5, the Atmel
> UARTs are called ttyATx instead of ttySx. Until now,
> "console=ttyS0,115200" was passed to the kernel, hence no output was
> present on the UART but the boards are booting fine.
Ok, thanks for having a look!
Arnd
^ permalink raw reply [flat|nested] 6+ messages in thread
* arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1)
2016-06-15 9:10 ` arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1) Arnd Bergmann
2016-06-15 9:18 ` Alexandre Belloni
@ 2016-06-15 18:07 ` Kevin Hilman
2016-06-15 19:12 ` Krzysztof Kozlowski
1 sibling, 1 reply; 6+ messages in thread
From: Kevin Hilman @ 2016-06-15 18:07 UTC (permalink / raw)
To: linux-arm-kernel
Arnd Bergmann <arnd@arndb.de> writes:
> On Tuesday, June 14, 2016 6:18:08 PM CEST kernelci. org bot wrote:
>> arm:
>>
>> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
>> exynos5410-odroidxu: 1 failed lab
>>
>> multi_v7_defconfig+CONFIG_LKDTM=y:
>> exynos5410-odroidxu: 1 failed lab
>>
>> multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y+CONFIG_ARM_MODULE_PLTS=y:
>> exynos5410-odroidxu: 1 failed lab
>>
>> multi_v7_defconfig+CONFIG_EFI=y:
>> exynos5410-odroidxu: 1 failed lab
>>
>> exynos_defconfig:
>> exynos5410-odroidxu: 1 failed lab
>>
>> multi_v7_defconfig+CONFIG_ARM_LPAE=y:
>> exynos5410-odroidxu: 1 failed lab
>>
>> multi_v7_defconfig:
>> exynos5410-odroidxu: 1 failed lab
>>
>> multi_v5_defconfig:
>> at91sam9261ek: 1 failed lab
>> at91sam9m10g45ek: 1 failed lab
>> at91sam9x25ek: 1 failed lab
>> at91sam9x35ek: 1 failed lab
>
> These all seem to have broken after yesterday's merges, adding
> Alexandre and Krzysztof to Cc here so they can have a look.
The exynos5410 fails look like the UART3 issue reported earlier and
which is also happening in linux-next.
Krzysztof posted a fix[1] that was tested by Javier and myself that
fixed the problem, but I don't see that upstream yet.
Krzysztof: did you get that fix submitted yet?
Kevin
[1] http://marc.info/?l=linux-kernel&m=146469459503940&w=2
^ permalink raw reply [flat|nested] 6+ messages in thread
* arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1)
2016-06-15 18:07 ` Kevin Hilman
@ 2016-06-15 19:12 ` Krzysztof Kozlowski
2016-06-15 20:08 ` Kevin Hilman
0 siblings, 1 reply; 6+ messages in thread
From: Krzysztof Kozlowski @ 2016-06-15 19:12 UTC (permalink / raw)
To: linux-arm-kernel
On Wed, Jun 15, 2016 at 11:07:50AM -0700, Kevin Hilman wrote:
> Arnd Bergmann <arnd@arndb.de> writes:
>
> > On Tuesday, June 14, 2016 6:18:08 PM CEST kernelci. org bot wrote:
> >> arm:
> >>
> >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
> >> exynos5410-odroidxu: 1 failed lab
> >>
> >> multi_v7_defconfig+CONFIG_LKDTM=y:
> >> exynos5410-odroidxu: 1 failed lab
> >>
> >> multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y+CONFIG_ARM_MODULE_PLTS=y:
> >> exynos5410-odroidxu: 1 failed lab
> >>
> >> multi_v7_defconfig+CONFIG_EFI=y:
> >> exynos5410-odroidxu: 1 failed lab
> >>
> >> exynos_defconfig:
> >> exynos5410-odroidxu: 1 failed lab
> >>
> >> multi_v7_defconfig+CONFIG_ARM_LPAE=y:
> >> exynos5410-odroidxu: 1 failed lab
> >>
> >> multi_v7_defconfig:
> >> exynos5410-odroidxu: 1 failed lab
> >>
> >> multi_v5_defconfig:
> >> at91sam9261ek: 1 failed lab
> >> at91sam9m10g45ek: 1 failed lab
> >> at91sam9x25ek: 1 failed lab
> >> at91sam9x35ek: 1 failed lab
> >
> > These all seem to have broken after yesterday's merges, adding
> > Alexandre and Krzysztof to Cc here so they can have a look.
>
> The exynos5410 fails look like the UART3 issue reported earlier and
> which is also happening in linux-next.
>
> Krzysztof posted a fix[1] that was tested by Javier and myself that
> fixed the problem, but I don't see that upstream yet.
>
> Krzysztof: did you get that fix submitted yet?
>
> Kevin
>
> [1] http://marc.info/?l=linux-kernel&m=146469459503940&w=2
The v2 of it is here:
https://patchwork.kernel.org/patch/9144897/
I do not recall receiving any feedback nor confirmation of applying the patch.
I guess it is time to resend. I'll do it on Thursday.
Best regards,
Krzysztof
^ permalink raw reply [flat|nested] 6+ messages in thread
* arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1)
2016-06-15 19:12 ` Krzysztof Kozlowski
@ 2016-06-15 20:08 ` Kevin Hilman
0 siblings, 0 replies; 6+ messages in thread
From: Kevin Hilman @ 2016-06-15 20:08 UTC (permalink / raw)
To: linux-arm-kernel
Krzysztof Kozlowski <k.kozlowski@samsung.com> writes:
> On Wed, Jun 15, 2016 at 11:07:50AM -0700, Kevin Hilman wrote:
>> Arnd Bergmann <arnd@arndb.de> writes:
>>
>> > On Tuesday, June 14, 2016 6:18:08 PM CEST kernelci. org bot wrote:
>> >> arm:
>> >>
>> >> multi_v7_defconfig+CONFIG_PROVE_LOCKING=y:
>> >> exynos5410-odroidxu: 1 failed lab
>> >>
>> >> multi_v7_defconfig+CONFIG_LKDTM=y:
>> >> exynos5410-odroidxu: 1 failed lab
>> >>
>> >> multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y+CONFIG_ARM_MODULE_PLTS=y:
>> >> exynos5410-odroidxu: 1 failed lab
>> >>
>> >> multi_v7_defconfig+CONFIG_EFI=y:
>> >> exynos5410-odroidxu: 1 failed lab
>> >>
>> >> exynos_defconfig:
>> >> exynos5410-odroidxu: 1 failed lab
>> >>
>> >> multi_v7_defconfig+CONFIG_ARM_LPAE=y:
>> >> exynos5410-odroidxu: 1 failed lab
>> >>
>> >> multi_v7_defconfig:
>> >> exynos5410-odroidxu: 1 failed lab
>> >>
>> >> multi_v5_defconfig:
>> >> at91sam9261ek: 1 failed lab
>> >> at91sam9m10g45ek: 1 failed lab
>> >> at91sam9x25ek: 1 failed lab
>> >> at91sam9x35ek: 1 failed lab
>> >
>> > These all seem to have broken after yesterday's merges, adding
>> > Alexandre and Krzysztof to Cc here so they can have a look.
>>
>> The exynos5410 fails look like the UART3 issue reported earlier and
>> which is also happening in linux-next.
>>
>> Krzysztof posted a fix[1] that was tested by Javier and myself that
>> fixed the problem, but I don't see that upstream yet.
>>
>> Krzysztof: did you get that fix submitted yet?
>>
>> Kevin
>>
>> [1] http://marc.info/?l=linux-kernel&m=146469459503940&w=2
>
> The v2 of it is here:
> https://patchwork.kernel.org/patch/9144897/
oops, yeah. That's the one Javier and I tested.
> I do not recall receiving any feedback nor confirmation of applying the patch.
> I guess it is time to resend. I'll do it on Thursday.
Yeah, add the tested-by, and since this fixes a known regression, I
guess it should go in unless there are any objections.
Kevin
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2016-06-15 20:08 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <5760acd0.571a1c0a.34a58.7333@mx.google.com>
2016-06-15 9:10 ` arm-soc boot: 619 boots: 11 failed, 605 passed with 2 offline, 1 conflict (v4.7-rc3-216-gec0776a212c1) Arnd Bergmann
2016-06-15 9:18 ` Alexandre Belloni
2016-06-15 10:50 ` Arnd Bergmann
2016-06-15 18:07 ` Kevin Hilman
2016-06-15 19:12 ` Krzysztof Kozlowski
2016-06-15 20:08 ` Kevin Hilman
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.