| Message ID | 1414796382-5447-1-git-send-email-khilman@kernel.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
Kevin Hilman wrote: > > From: Kevin Hilman <khilman@linaro.org> > > The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts > during boot testing, causing various userspace startup failures. > > Disable until it has gotten more testing. > > Cc: Kukjin Kim <kgene.kim@samsung.com>, > Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>, > Cc: Sachin Kamat <sachin.kamat@samsung.com>, > Cc: Doug Anderson <dianders@chromium.org>, > Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, > Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>, > Cc: Tushar Behera <tushar.behera@linaro.org>, > Cc: stable@vger.kernel.org # v3.17+ > Signed-off-by: Kevin Hilman <khilman@linaro.org> > --- > This has been reported by a few people[1], but not investigated or fixed, so it's > time to disable this feature until it can be fixed. > Hi Kevin, Yeah I agree with your opinion. But as you can see my tree, I've queued regarding mcpm patches for 3.19 will be shown in -next in this weekend. Anyway let me apply this into -fixes and then let's enable after test its functionality in -next in a couple of days. Thanks, Kukjin > [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/288344.html > > arch/arm/configs/exynos_defconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig > index 72058b8a6f4d..a250dcbf34cd 100644 > --- a/arch/arm/configs/exynos_defconfig > +++ b/arch/arm/configs/exynos_defconfig > @@ -10,7 +10,7 @@ CONFIG_MODULE_UNLOAD=y > CONFIG_PARTITION_ADVANCED=y > CONFIG_ARCH_EXYNOS=y > CONFIG_ARCH_EXYNOS3=y > -CONFIG_EXYNOS5420_MCPM=y > +CONFIG_EXYNOS5420_MCPM=n > CONFIG_SMP=y > CONFIG_BIG_LITTLE=y > CONFIG_BL_SWITCHER=y > -- > 2.1.0
Kukjin Kim <kgene@kernel.org> writes: > Kevin Hilman wrote: >> >> From: Kevin Hilman <khilman@linaro.org> >> >> The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts >> during boot testing, causing various userspace startup failures. >> >> Disable until it has gotten more testing. >> >> Cc: Kukjin Kim <kgene.kim@samsung.com>, >> Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>, >> Cc: Sachin Kamat <sachin.kamat@samsung.com>, >> Cc: Doug Anderson <dianders@chromium.org>, >> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, >> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>, >> Cc: Tushar Behera <tushar.behera@linaro.org>, >> Cc: stable@vger.kernel.org # v3.17+ >> Signed-off-by: Kevin Hilman <khilman@linaro.org> >> --- >> This has been reported by a few people[1], but not investigated or fixed, so it's >> time to disable this feature until it can be fixed. >> > Hi Kevin, > > Yeah I agree with your opinion. > > But as you can see my tree, I've queued regarding mcpm patches for 3.19 will > be shown in -next in this weekend. Which of the recently queued patches are expected to address the imprecise abort issue? I'd be happy to test them out. > Anyway let me apply this into -fixes and > then let's enable after test its functionality in -next in a couple of days. Yes, I think this needs to be applied until these aborts are understood and fixed. Thanks, Kevin
Kukjin, On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman <khilman@kernel.org> wrote: > Kukjin Kim <kgene@kernel.org> writes: > >> Kevin Hilman wrote: >>> >>> From: Kevin Hilman <khilman@linaro.org> >>> >>> The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts >>> during boot testing, causing various userspace startup failures. >>> >>> Disable until it has gotten more testing. >>> >>> Cc: Kukjin Kim <kgene.kim@samsung.com>, >>> Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>, >>> Cc: Sachin Kamat <sachin.kamat@samsung.com>, >>> Cc: Doug Anderson <dianders@chromium.org>, >>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, >>> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>, >>> Cc: Tushar Behera <tushar.behera@linaro.org>, >>> Cc: stable@vger.kernel.org # v3.17+ >>> Signed-off-by: Kevin Hilman <khilman@linaro.org> >>> --- >>> This has been reported by a few people[1], but not investigated or fixed, so it's >>> time to disable this feature until it can be fixed. >>> >> Hi Kevin, >> >> Yeah I agree with your opinion. >> >> But as you can see my tree, I've queued regarding mcpm patches for 3.19 will >> be shown in -next in this weekend. > > Which of the recently queued patches are expected to address the > imprecise abort issue? I'd be happy to test them out. Exynos5 MCPM is still broken in linux-next and still causing an imprecise abort. What is the status of $SUBJECT patch? >> Anyway let me apply this into -fixes and >> then let's enable after test its functionality in -next in a couple of days. > > Yes, I think this needs to be applied until these aborts are understood > and fixed. Is anyone at Samsung actually looking into these MCPM issues? Kevin
On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman <khilman@kernel.org> wrote: > Kukjin, > > On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman <khilman@kernel.org> wrote: >> Kukjin Kim <kgene@kernel.org> writes: >> >>> Kevin Hilman wrote: >>>> >>>> From: Kevin Hilman <khilman@linaro.org> >>>> >>>> The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts >>>> during boot testing, causing various userspace startup failures. >>>> >>>> Disable until it has gotten more testing. >>>> >>>> Cc: Kukjin Kim <kgene.kim@samsung.com>, >>>> Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>, >>>> Cc: Sachin Kamat <sachin.kamat@samsung.com>, >>>> Cc: Doug Anderson <dianders@chromium.org>, >>>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, >>>> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>, >>>> Cc: Tushar Behera <tushar.behera@linaro.org>, >>>> Cc: stable@vger.kernel.org # v3.17+ >>>> Signed-off-by: Kevin Hilman <khilman@linaro.org> >>>> --- >>>> This has been reported by a few people[1], but not investigated or fixed, so it's >>>> time to disable this feature until it can be fixed. >>>> >>> Hi Kevin, >>> >>> Yeah I agree with your opinion. >>> >>> But as you can see my tree, I've queued regarding mcpm patches for 3.19 will >>> be shown in -next in this weekend. >> >> Which of the recently queued patches are expected to address the >> imprecise abort issue? I'd be happy to test them out. > > Exynos5 MCPM is still broken in linux-next and still causing an imprecise abort. > > What is the status of $SUBJECT patch? > >>> Anyway let me apply this into -fixes and >>> then let's enable after test its functionality in -next in a couple of days. >> >> Yes, I think this needs to be applied until these aborts are understood >> and fixed. > > Is anyone at Samsung actually looking into these MCPM issues? Hi Kevin, What hardware are you having problems with? 5420 or 5422/5800? -Olof
On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson <olof@lixom.net> wrote: > On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman <khilman@kernel.org> wrote: >> Kukjin, >> >> On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman <khilman@kernel.org> wrote: >>> Kukjin Kim <kgene@kernel.org> writes: >>> >>>> Kevin Hilman wrote: >>>>> >>>>> From: Kevin Hilman <khilman@linaro.org> >>>>> >>>>> The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts >>>>> during boot testing, causing various userspace startup failures. >>>>> >>>>> Disable until it has gotten more testing. >>>>> >>>>> Cc: Kukjin Kim <kgene.kim@samsung.com>, >>>>> Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>, >>>>> Cc: Sachin Kamat <sachin.kamat@samsung.com>, >>>>> Cc: Doug Anderson <dianders@chromium.org>, >>>>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, >>>>> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>, >>>>> Cc: Tushar Behera <tushar.behera@linaro.org>, >>>>> Cc: stable@vger.kernel.org # v3.17+ >>>>> Signed-off-by: Kevin Hilman <khilman@linaro.org> >>>>> --- >>>>> This has been reported by a few people[1], but not investigated or fixed, so it's >>>>> time to disable this feature until it can be fixed. >>>>> >>>> Hi Kevin, >>>> >>>> Yeah I agree with your opinion. >>>> >>>> But as you can see my tree, I've queued regarding mcpm patches for 3.19 will >>>> be shown in -next in this weekend. >>> >>> Which of the recently queued patches are expected to address the >>> imprecise abort issue? I'd be happy to test them out. >> >> Exynos5 MCPM is still broken in linux-next and still causing an imprecise abort. >> >> What is the status of $SUBJECT patch? >> >>>> Anyway let me apply this into -fixes and >>>> then let's enable after test its functionality in -next in a couple of days. >>> >>> Yes, I think this needs to be applied until these aborts are understood >>> and fixed. >> >> Is anyone at Samsung actually looking into these MCPM issues? > > Hi Kevin, > > What hardware are you having problems with? 5420 or 5422/5800? Yes. :) exynos5420-arndale-octa: http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5420-arndale-octa.html exynos5422-odroid-xu3: http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5422-odroid-xu3.html My boot tests seem to pass fine because I have such a minimal userspace, but Tyler Baker reported that with a "real" userspace, he can't boot to a shell: http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/286203.html Kevin
On Mon, Nov 24, 2014 at 5:35 PM, Kevin Hilman <khilman@kernel.org> wrote: > On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson <olof@lixom.net> wrote: >> On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman <khilman@kernel.org> wrote: >>> Kukjin, >>> >>> On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman <khilman@kernel.org> wrote: >>>> Kukjin Kim <kgene@kernel.org> writes: >>>> >>>>> Kevin Hilman wrote: >>>>>> >>>>>> From: Kevin Hilman <khilman@linaro.org> >>>>>> >>>>>> The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts >>>>>> during boot testing, causing various userspace startup failures. >>>>>> >>>>>> Disable until it has gotten more testing. >>>>>> >>>>>> Cc: Kukjin Kim <kgene.kim@samsung.com>, >>>>>> Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>, >>>>>> Cc: Sachin Kamat <sachin.kamat@samsung.com>, >>>>>> Cc: Doug Anderson <dianders@chromium.org>, >>>>>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, >>>>>> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>, >>>>>> Cc: Tushar Behera <tushar.behera@linaro.org>, >>>>>> Cc: stable@vger.kernel.org # v3.17+ >>>>>> Signed-off-by: Kevin Hilman <khilman@linaro.org> >>>>>> --- >>>>>> This has been reported by a few people[1], but not investigated or fixed, so it's >>>>>> time to disable this feature until it can be fixed. >>>>>> >>>>> Hi Kevin, >>>>> >>>>> Yeah I agree with your opinion. >>>>> >>>>> But as you can see my tree, I've queued regarding mcpm patches for 3.19 will >>>>> be shown in -next in this weekend. >>>> >>>> Which of the recently queued patches are expected to address the >>>> imprecise abort issue? I'd be happy to test them out. >>> >>> Exynos5 MCPM is still broken in linux-next and still causing an imprecise abort. >>> >>> What is the status of $SUBJECT patch? >>> >>>>> Anyway let me apply this into -fixes and >>>>> then let's enable after test its functionality in -next in a couple of days. >>>> >>>> Yes, I think this needs to be applied until these aborts are understood >>>> and fixed. >>> >>> Is anyone at Samsung actually looking into these MCPM issues? >> >> Hi Kevin, >> >> What hardware are you having problems with? 5420 or 5422/5800? > > Yes. :) > > exynos5420-arndale-octa: > http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5420-arndale-octa.html > exynos5422-odroid-xu3: > http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5422-odroid-xu3.html > > My boot tests seem to pass fine because I have such a minimal > userspace, but Tyler Baker reported that with a "real" userspace, he > can't boot to a shell: > > http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/286203.html I'm not surprised that 5420 has issues, but I have not seen any external aborts on neither Chromebook that I have in my farm. Sounds like the secondary cpus should be disabled on those device trees instead, doesn't it? -Olof
On Mon, Nov 24, 2014 at 5:37 PM, Olof Johansson <olof@lixom.net> wrote: > On Mon, Nov 24, 2014 at 5:35 PM, Kevin Hilman <khilman@kernel.org> wrote: >> On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson <olof@lixom.net> wrote: >>> On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman <khilman@kernel.org> wrote: >>>> Kukjin, >>>> >>>> On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman <khilman@kernel.org> wrote: >>>>> Kukjin Kim <kgene@kernel.org> writes: >>>>> >>>>>> Kevin Hilman wrote: >>>>>>> >>>>>>> From: Kevin Hilman <khilman@linaro.org> >>>>>>> >>>>>>> The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts >>>>>>> during boot testing, causing various userspace startup failures. >>>>>>> >>>>>>> Disable until it has gotten more testing. >>>>>>> >>>>>>> Cc: Kukjin Kim <kgene.kim@samsung.com>, >>>>>>> Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>, >>>>>>> Cc: Sachin Kamat <sachin.kamat@samsung.com>, >>>>>>> Cc: Doug Anderson <dianders@chromium.org>, >>>>>>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, >>>>>>> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>, >>>>>>> Cc: Tushar Behera <tushar.behera@linaro.org>, >>>>>>> Cc: stable@vger.kernel.org # v3.17+ >>>>>>> Signed-off-by: Kevin Hilman <khilman@linaro.org> >>>>>>> --- >>>>>>> This has been reported by a few people[1], but not investigated or fixed, so it's >>>>>>> time to disable this feature until it can be fixed. >>>>>>> >>>>>> Hi Kevin, >>>>>> >>>>>> Yeah I agree with your opinion. >>>>>> >>>>>> But as you can see my tree, I've queued regarding mcpm patches for 3.19 will >>>>>> be shown in -next in this weekend. >>>>> >>>>> Which of the recently queued patches are expected to address the >>>>> imprecise abort issue? I'd be happy to test them out. >>>> >>>> Exynos5 MCPM is still broken in linux-next and still causing an imprecise abort. >>>> >>>> What is the status of $SUBJECT patch? >>>> >>>>>> Anyway let me apply this into -fixes and >>>>>> then let's enable after test its functionality in -next in a couple of days. >>>>> >>>>> Yes, I think this needs to be applied until these aborts are understood >>>>> and fixed. >>>> >>>> Is anyone at Samsung actually looking into these MCPM issues? >>> >>> Hi Kevin, >>> >>> What hardware are you having problems with? 5420 or 5422/5800? >> >> Yes. :) >> >> exynos5420-arndale-octa: >> http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5420-arndale-octa.html >> exynos5422-odroid-xu3: >> http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5422-odroid-xu3.html >> >> My boot tests seem to pass fine because I have such a minimal >> userspace, but Tyler Baker reported that with a "real" userspace, he >> can't boot to a shell: >> >> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/286203.html > > I'm not surprised that 5420 has issues, but I have not seen any > external aborts on neither Chromebook that I have in my farm. > > Sounds like the secondary cpus should be disabled on those device > trees instead, doesn't it? Er, cluster, not cpus. -Olof
Olof Johansson wrote: > > On Mon, Nov 24, 2014 at 5:37 PM, Olof Johansson <olof@lixom.net> wrote: > > On Mon, Nov 24, 2014 at 5:35 PM, Kevin Hilman <khilman@kernel.org> wrote: > >> On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson <olof@lixom.net> wrote: > >>> On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman <khilman@kernel.org> wrote: > >>>> Kukjin, > >>>> > >>>> On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman <khilman@kernel.org> wrote: > >>>>> Kukjin Kim <kgene@kernel.org> writes: > >>>>> > >>>>>> Kevin Hilman wrote: > >>>>>>> > >>>>>>> From: Kevin Hilman <khilman@linaro.org> > >>>>>>> > >>>>>>> The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts > >>>>>>> during boot testing, causing various userspace startup failures. > >>>>>>> > >>>>>>> Disable until it has gotten more testing. > >>>>>>> > >>>>>>> Cc: Kukjin Kim <kgene.kim@samsung.com>, > >>>>>>> Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>, > >>>>>>> Cc: Sachin Kamat <sachin.kamat@samsung.com>, > >>>>>>> Cc: Doug Anderson <dianders@chromium.org>, > >>>>>>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, > >>>>>>> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>, > >>>>>>> Cc: Tushar Behera <tushar.behera@linaro.org>, > >>>>>>> Cc: stable@vger.kernel.org # v3.17+ > >>>>>>> Signed-off-by: Kevin Hilman <khilman@linaro.org> > >>>>>>> --- > >>>>>>> This has been reported by a few people[1], but not investigated or fixed, so it's > >>>>>>> time to disable this feature until it can be fixed. > >>>>>>> > >>>>>> Hi Kevin, > >>>>>> > >>>>>> Yeah I agree with your opinion. > >>>>>> > >>>>>> But as you can see my tree, I've queued regarding mcpm patches for 3.19 will > >>>>>> be shown in -next in this weekend. > >>>>> > >>>>> Which of the recently queued patches are expected to address the > >>>>> imprecise abort issue? I'd be happy to test them out. > >>>> > >>>> Exynos5 MCPM is still broken in linux-next and still causing an imprecise abort. > >>>> > >>>> What is the status of $SUBJECT patch? > >>>> > >>>>>> Anyway let me apply this into -fixes and > >>>>>> then let's enable after test its functionality in -next in a couple of days. > >>>>> > >>>>> Yes, I think this needs to be applied until these aborts are understood > >>>>> and fixed. > >>>> > >>>> Is anyone at Samsung actually looking into these MCPM issues? > >>> > >>> Hi Kevin, > >>> > >>> What hardware are you having problems with? 5420 or 5422/5800? > >> > >> Yes. :) > >> > >> exynos5420-arndale-octa: > >> http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5420- > arndale-octa.html > >> exynos5422-odroid-xu3: > >> http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5422- > odroid-xu3.html > >> > >> My boot tests seem to pass fine because I have such a minimal > >> userspace, but Tyler Baker reported that with a "real" userspace, he > >> can't boot to a shell: > >> > >> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/286203.html > > Hmm...his report was in Sep...I think it should be fine with current -next? To be honest, since I don't have the exynos5420 arndale, chromebook...but smdk which has different bootloader, I couldn't test it...I'll try to make a test farm like you guys... > > I'm not surprised that 5420 has issues, but I have not seen any Sorry. > > external aborts on neither Chromebook that I have in my farm. > > > > Sounds like the secondary cpus should be disabled on those device > > trees instead, doesn't it? > > Er, cluster, not cpus. - Kukjin
On Mon, Nov 24, 2014 at 5:37 PM, Olof Johansson <olof@lixom.net> wrote: > On Mon, Nov 24, 2014 at 5:35 PM, Kevin Hilman <khilman@kernel.org> wrote: >> On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson <olof@lixom.net> wrote: >>> On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman <khilman@kernel.org> wrote: >>>> Kukjin, >>>> >>>> On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman <khilman@kernel.org> wrote: >>>>> Kukjin Kim <kgene@kernel.org> writes: >>>>> >>>>>> Kevin Hilman wrote: >>>>>>> >>>>>>> From: Kevin Hilman <khilman@linaro.org> >>>>>>> >>>>>>> The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts >>>>>>> during boot testing, causing various userspace startup failures. >>>>>>> >>>>>>> Disable until it has gotten more testing. >>>>>>> >>>>>>> Cc: Kukjin Kim <kgene.kim@samsung.com>, >>>>>>> Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>, >>>>>>> Cc: Sachin Kamat <sachin.kamat@samsung.com>, >>>>>>> Cc: Doug Anderson <dianders@chromium.org>, >>>>>>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, >>>>>>> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>, >>>>>>> Cc: Tushar Behera <tushar.behera@linaro.org>, >>>>>>> Cc: stable@vger.kernel.org # v3.17+ >>>>>>> Signed-off-by: Kevin Hilman <khilman@linaro.org> >>>>>>> --- >>>>>>> This has been reported by a few people[1], but not investigated or fixed, so it's >>>>>>> time to disable this feature until it can be fixed. >>>>>>> >>>>>> Hi Kevin, >>>>>> >>>>>> Yeah I agree with your opinion. >>>>>> >>>>>> But as you can see my tree, I've queued regarding mcpm patches for 3.19 will >>>>>> be shown in -next in this weekend. >>>>> >>>>> Which of the recently queued patches are expected to address the >>>>> imprecise abort issue? I'd be happy to test them out. >>>> >>>> Exynos5 MCPM is still broken in linux-next and still causing an imprecise abort. >>>> >>>> What is the status of $SUBJECT patch? >>>> >>>>>> Anyway let me apply this into -fixes and >>>>>> then let's enable after test its functionality in -next in a couple of days. >>>>> >>>>> Yes, I think this needs to be applied until these aborts are understood >>>>> and fixed. >>>> >>>> Is anyone at Samsung actually looking into these MCPM issues? >>> >>> Hi Kevin, >>> >>> What hardware are you having problems with? 5420 or 5422/5800? >> >> Yes. :) >> >> exynos5420-arndale-octa: >> http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5420-arndale-octa.html >> exynos5422-odroid-xu3: >> http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5422-odroid-xu3.html >> >> My boot tests seem to pass fine because I have such a minimal >> userspace, but Tyler Baker reported that with a "real" userspace, he >> can't boot to a shell: >> >> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/286203.html > > I'm not surprised that 5420 has issues, but I have not seen any > external aborts on neither Chromebook that I have in my farm. > > Sounds like the secondary cpus should be disabled on those device > trees instead, doesn't it? That's possible. Unfortunately, I've gotten very little support from Samsung on this and it was originally reported 2.5 months ago[2], so I think that the 5420 MCPM should be disabled until they can propose the right fix, and actually test it. Also, I tried disabling some CPUs at boot time, but the exynos5422-odroid-xu3 wont' even boot with nr_cpus=1 or 4 (or anything less than 8) Kevin [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/286203.html
On Mon, Nov 24, 2014 at 5:50 PM, Kukjin Kim <kgene@kernel.org> wrote: > Olof Johansson wrote: >> >> On Mon, Nov 24, 2014 at 5:37 PM, Olof Johansson <olof@lixom.net> wrote: >> > On Mon, Nov 24, 2014 at 5:35 PM, Kevin Hilman <khilman@kernel.org> wrote: >> >> On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson <olof@lixom.net> wrote: >> >>> On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman <khilman@kernel.org> wrote: >> >>>> Kukjin, >> >>>> >> >>>> On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman <khilman@kernel.org> wrote: >> >>>>> Kukjin Kim <kgene@kernel.org> writes: >> >>>>> >> >>>>>> Kevin Hilman wrote: >> >>>>>>> >> >>>>>>> From: Kevin Hilman <khilman@linaro.org> >> >>>>>>> >> >>>>>>> The option CONFIG_EXYNOS5420_MCPM is causing imprecise external aborts >> >>>>>>> during boot testing, causing various userspace startup failures. >> >>>>>>> >> >>>>>>> Disable until it has gotten more testing. >> >>>>>>> >> >>>>>>> Cc: Kukjin Kim <kgene.kim@samsung.com>, >> >>>>>>> Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>, >> >>>>>>> Cc: Sachin Kamat <sachin.kamat@samsung.com>, >> >>>>>>> Cc: Doug Anderson <dianders@chromium.org>, >> >>>>>>> Cc: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, >> >>>>>>> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>, >> >>>>>>> Cc: Tushar Behera <tushar.behera@linaro.org>, >> >>>>>>> Cc: stable@vger.kernel.org # v3.17+ >> >>>>>>> Signed-off-by: Kevin Hilman <khilman@linaro.org> >> >>>>>>> --- >> >>>>>>> This has been reported by a few people[1], but not investigated or fixed, so it's >> >>>>>>> time to disable this feature until it can be fixed. >> >>>>>>> >> >>>>>> Hi Kevin, >> >>>>>> >> >>>>>> Yeah I agree with your opinion. >> >>>>>> >> >>>>>> But as you can see my tree, I've queued regarding mcpm patches for 3.19 will >> >>>>>> be shown in -next in this weekend. >> >>>>> >> >>>>> Which of the recently queued patches are expected to address the >> >>>>> imprecise abort issue? I'd be happy to test them out. >> >>>> >> >>>> Exynos5 MCPM is still broken in linux-next and still causing an imprecise abort. >> >>>> >> >>>> What is the status of $SUBJECT patch? >> >>>> >> >>>>>> Anyway let me apply this into -fixes and >> >>>>>> then let's enable after test its functionality in -next in a couple of days. >> >>>>> >> >>>>> Yes, I think this needs to be applied until these aborts are understood >> >>>>> and fixed. >> >>>> >> >>>> Is anyone at Samsung actually looking into these MCPM issues? >> >>> >> >>> Hi Kevin, >> >>> >> >>> What hardware are you having problems with? 5420 or 5422/5800? >> >> >> >> Yes. :) >> >> >> >> exynos5420-arndale-octa: >> >> http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5420- >> arndale-octa.html >> >> exynos5422-odroid-xu3: >> >> http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5422- >> odroid-xu3.html >> >> >> >> My boot tests seem to pass fine because I have such a minimal >> >> userspace, but Tyler Baker reported that with a "real" userspace, he >> >> can't boot to a shell: >> >> >> >> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/286203.html >> > > Hmm...his report was in Sep...I think it should be fine with current -next? No, it is still broken in linux-next (as I stated above.) Moreover, earlier in this thread you mentioned you were merging some MCPM patches that should address this, but did not respond when I asked which patches you thing should address this issue > To be honest, since I don't have the exynos5420 arndale, chromebook...but smdk > which has different bootloader, I couldn't test it...I'll try to make a test > farm like you guys... Do you have some colleagues with any other 542x hardware? I had assumed that linux-next was being better tested on the publicaly available, and widely available boards like odroid-xu3 and Chromebook2, but I've come to realize the hard way that that is not the case. You mention your board has a different bootloader. Do you suspect there's a bootloader issue on these other platforms? If so, could you elaborate on possible fixes? I'm more than willing to test any proposed fixes, but I'm not familiar enough yet with these SoCs to figure out the underlying issues alone. Until you have a working board farm, you could start having a closer look at the boot logs we're already producing. Admittedly linux-next broken in many ways besides this one for exynos currently, but it has been having these imprecise aborts well before the other recent issues. Also, It's very possible that this issue is not even MCPM related at all, and MCPM is just uncovering a previously hidden bug. It would be very helpful if people more familiar with this hardware and SoC would investigate bug reports like these. Kevin
On pon, 2014-11-24 at 19:20 -0800, Kevin Hilman wrote: > On Mon, Nov 24, 2014 at 5:50 PM, Kukjin Kim <kgene@kernel.org> wrote: > > Olof Johansson wrote: > >> > >> On Mon, Nov 24, 2014 at 5:37 PM, Olof Johansson <olof@lixom.net> wrote: > >> > On Mon, Nov 24, 2014 at 5:35 PM, Kevin Hilman <khilman@kernel.org> wrote: > >> >> On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson <olof@lixom.net> wrote: > >> >>> On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman <khilman@kernel.org> wrote: > >> >>>> > >> >>>> Is anyone at Samsung actually looking into these MCPM issues? > >> >>> > >> >>> Hi Kevin, > >> >>> > >> >>> What hardware are you having problems with? 5420 or 5422/5800? > >> >> > >> >> Yes. :) > >> >> > >> >> exynos5420-arndale-octa: > >> >> http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5420- > >> arndale-octa.html > >> >> exynos5422-odroid-xu3: > >> >> http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5422- > >> odroid-xu3.html > >> >> > >> >> My boot tests seem to pass fine because I have such a minimal > >> >> userspace, but Tyler Baker reported that with a "real" userspace, he > >> >> can't boot to a shell: > >> >> > >> >> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/286203.html > >> > > > Hmm...his report was in Sep...I think it should be fine with current -next? > > No, it is still broken in linux-next (as I stated above.) > > Moreover, earlier in this thread you mentioned you were merging some > MCPM patches that should address this, but did not respond when I > asked which patches you thing should address this issue > > > To be honest, since I don't have the exynos5420 arndale, chromebook...but smdk > > which has different bootloader, I couldn't test it...I'll try to make a test > > farm like you guys... > > Do you have some colleagues with any other 542x hardware? I had > assumed that linux-next was being better tested on the publicaly > available, and widely available boards like odroid-xu3 and > Chromebook2, but I've come to realize the hard way that that is not > the case. You mention your board has a different bootloader. Do you > suspect there's a bootloader issue on these other platforms? If so, > could you elaborate on possible fixes? I'm more than willing to test > any proposed fixes, but I'm not familiar enough yet with these SoCs to > figure out the underlying issues alone. > > Until you have a working board farm, you could start having a closer > look at the boot logs we're already producing. Admittedly linux-next > broken in many ways besides this one for exynos currently, but it has > been having these imprecise aborts well before the other recent > issues. > > Also, It's very possible that this issue is not even MCPM related at > all, and MCPM is just uncovering a previously hidden bug. It would be > very helpful if people more familiar with this hardware and SoC would > investigate bug reports like these. Interesting thing can be found in exynos5420.dtsi: mdma1: mdma@11C10000 { ... /* * MDMA1 can support both secure and non-secure * AXI transactions. When this is enabled in the kernel * for boards that run in secure mode, we are getting * imprecise external aborts causing the kernel to oops. */ status = "disabled"; }; I am booting Arndale Octa on some other config and exynos. However with or without MCPM the imprecise aborts are still present (but not fatal, shell comes up). My board boots also under secure firmware (I am using Linaro's ubuntu image). Maybe that is the cause? Best regards, Krzysztof
On wto, 2014-11-25 at 09:47 +0100, Krzysztof Kozlowski wrote: > On pon, 2014-11-24 at 19:20 -0800, Kevin Hilman wrote: > > On Mon, Nov 24, 2014 at 5:50 PM, Kukjin Kim <kgene@kernel.org> wrote: > > > Olof Johansson wrote: > > >> > > >> On Mon, Nov 24, 2014 at 5:37 PM, Olof Johansson <olof@lixom.net> wrote: > > >> > On Mon, Nov 24, 2014 at 5:35 PM, Kevin Hilman <khilman@kernel.org> wrote: > > >> >> On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson <olof@lixom.net> wrote: > > >> >>> On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman <khilman@kernel.org> wrote: > > >> >>>> > > >> >>>> Is anyone at Samsung actually looking into these MCPM issues? > > >> >>> > > >> >>> Hi Kevin, > > >> >>> > > >> >>> What hardware are you having problems with? 5420 or 5422/5800? > > >> >> > > >> >> Yes. :) > > >> >> > > >> >> exynos5420-arndale-octa: > > >> >> http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5420- > > >> arndale-octa.html > > >> >> exynos5422-odroid-xu3: > > >> >> http://storage.armcloud.us/kernel-ci/mainline/v3.18-rc6/arm-exynos_defconfig/boot-exynos5422- > > >> odroid-xu3.html > > >> >> > > >> >> My boot tests seem to pass fine because I have such a minimal > > >> >> userspace, but Tyler Baker reported that with a "real" userspace, he > > >> >> can't boot to a shell: > > >> >> > > >> >> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-September/286203.html > > >> > > > > Hmm...his report was in Sep...I think it should be fine with current -next? > > > > No, it is still broken in linux-next (as I stated above.) > > > > Moreover, earlier in this thread you mentioned you were merging some > > MCPM patches that should address this, but did not respond when I > > asked which patches you thing should address this issue > > > > > To be honest, since I don't have the exynos5420 arndale, chromebook...but smdk > > > which has different bootloader, I couldn't test it...I'll try to make a test > > > farm like you guys... > > > > Do you have some colleagues with any other 542x hardware? I had > > assumed that linux-next was being better tested on the publicaly > > available, and widely available boards like odroid-xu3 and > > Chromebook2, but I've come to realize the hard way that that is not > > the case. You mention your board has a different bootloader. Do you > > suspect there's a bootloader issue on these other platforms? If so, > > could you elaborate on possible fixes? I'm more than willing to test > > any proposed fixes, but I'm not familiar enough yet with these SoCs to > > figure out the underlying issues alone. > > > > Until you have a working board farm, you could start having a closer > > look at the boot logs we're already producing. Admittedly linux-next > > broken in many ways besides this one for exynos currently, but it has > > been having these imprecise aborts well before the other recent > > issues. > > > > Also, It's very possible that this issue is not even MCPM related at > > all, and MCPM is just uncovering a previously hidden bug. It would be > > very helpful if people more familiar with this hardware and SoC would > > investigate bug reports like these. > > Interesting thing can be found in exynos5420.dtsi: > mdma1: mdma@11C10000 { > ... > /* > * MDMA1 can support both secure and non-secure > * AXI transactions. When this is enabled in the kernel > * for boards that run in secure mode, we are getting > * imprecise external aborts causing the kernel to oops. > */ > status = "disabled"; > }; > > I am booting Arndale Octa on some other config and exynos. However with > or without MCPM the imprecise aborts are still present (but not fatal, > shell comes up). > > My board boots also under secure firmware (I am using Linaro's ubuntu > image). Maybe that is the cause? One update: some fatal imprecise aborts (hanging boot) happen also on exynos_defconfig without MCPM. It looks random... one boot fails, next succeeds (however also with "imprecise external abort" message but shell comes up). Best regards, Krzysztof
diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig index 72058b8a6f4d..a250dcbf34cd 100644 --- a/arch/arm/configs/exynos_defconfig +++ b/arch/arm/configs/exynos_defconfig @@ -10,7 +10,7 @@ CONFIG_MODULE_UNLOAD=y CONFIG_PARTITION_ADVANCED=y CONFIG_ARCH_EXYNOS=y CONFIG_ARCH_EXYNOS3=y -CONFIG_EXYNOS5420_MCPM=y +CONFIG_EXYNOS5420_MCPM=n CONFIG_SMP=y CONFIG_BIG_LITTLE=y CONFIG_BL_SWITCHER=y