From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kukjin Kim Subject: RE: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable Date: Tue, 25 Nov 2014 10:50:53 +0900 Message-ID: <044101d00852$3f421420$bdc63c60$@kernel.org> References: <1414796382-5447-1-git-send-email-khilman@kernel.org> <000e01cffb39$5ef0a2d0$1cd1e870$@kernel.org> <7hegtaq26c.fsf@deeprootsystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from mailout1.samsung.com ([203.254.224.24]:47981 "EHLO mailout1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750784AbaKYBu4 (ORCPT ); Mon, 24 Nov 2014 20:50:56 -0500 Received: from epcpsbgr4.samsung.com (u144.gpu120.samsung.co.kr [203.254.230.144]) by mailout1.samsung.com (Oracle Communications Messaging Server 7u4-24.01 (7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTP id <0NFK000UJNSTK1B0@mailout1.samsung.com> for linux-samsung-soc@vger.kernel.org; Tue, 25 Nov 2014 10:50:54 +0900 (KST) In-reply-to: Content-language: ko Sender: linux-samsung-soc-owner@vger.kernel.org List-Id: linux-samsung-soc@vger.kernel.org To: 'Olof Johansson' , 'Kevin Hilman' Cc: 'Kukjin Kim' , linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linaro-kernel@lists.linaro.org, 'Javier Martinez Canillas' , 'Sachin Kamat' , 'Doug Anderson' , 'Bartlomiej Zolnierkiewicz' , 'Krzysztof Kozlowski' , Kukjin Kim Olof Johansson wrote: > > On Mon, Nov 24, 2014 at 5:37 PM, Olof Johansson wrote: > > On Mon, Nov 24, 2014 at 5:35 PM, Kevin Hilman wrote: > >> On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson wrote: > >>> On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman wrote: > >>>> Kukjin, > >>>> > >>>> On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman wrote: > >>>>> Kukjin Kim writes: > >>>>> > >>>>>> Kevin Hilman wrote: > >>>>>>> > >>>>>>> From: Kevin Hilman > >>>>>>> > >>>>>>> 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 , > >>>>>>> Cc: Javier Martinez Canillas , > >>>>>>> Cc: Sachin Kamat , > >>>>>>> Cc: Doug Anderson , > >>>>>>> Cc: Bartlomiej Zolnierkiewicz , > >>>>>>> Cc: Krzysztof Kozlowski , > >>>>>>> Cc: Tushar Behera , > >>>>>>> Cc: stable@vger.kernel.org # v3.17+ > >>>>>>> Signed-off-by: Kevin Hilman > >>>>>>> --- > >>>>>>> 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: kgene@kernel.org (Kukjin Kim) Date: Tue, 25 Nov 2014 10:50:53 +0900 Subject: [PATCH] ARM: exynos_defconfig: disable CONFIG_EXYNOS5420_MCPM; not stable In-Reply-To: References: <1414796382-5447-1-git-send-email-khilman@kernel.org> <000e01cffb39$5ef0a2d0$1cd1e870$@kernel.org> <7hegtaq26c.fsf@deeprootsystems.com> Message-ID: <044101d00852$3f421420$bdc63c60$@kernel.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Olof Johansson wrote: > > On Mon, Nov 24, 2014 at 5:37 PM, Olof Johansson wrote: > > On Mon, Nov 24, 2014 at 5:35 PM, Kevin Hilman wrote: > >> On Mon, Nov 24, 2014 at 4:25 PM, Olof Johansson wrote: > >>> On Mon, Nov 24, 2014 at 11:51 AM, Kevin Hilman wrote: > >>>> Kukjin, > >>>> > >>>> On Mon, Nov 10, 2014 at 11:35 AM, Kevin Hilman wrote: > >>>>> Kukjin Kim writes: > >>>>> > >>>>>> Kevin Hilman wrote: > >>>>>>> > >>>>>>> From: Kevin Hilman > >>>>>>> > >>>>>>> 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 , > >>>>>>> Cc: Javier Martinez Canillas , > >>>>>>> Cc: Sachin Kamat , > >>>>>>> Cc: Doug Anderson , > >>>>>>> Cc: Bartlomiej Zolnierkiewicz , > >>>>>>> Cc: Krzysztof Kozlowski , > >>>>>>> Cc: Tushar Behera , > >>>>>>> Cc: stable at vger.kernel.org # v3.17+ > >>>>>>> Signed-off-by: Kevin Hilman > >>>>>>> --- > >>>>>>> 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