On Thu, May 29, 2014 at 11:30 PM, Andreas Färber <afaerber@xxxxxxx> wrote: > Hi Tarek, > > > And I reproducibly get failures for CPUs 1-3, resulting in only one CPU > in /proc/cpuinfo (compared to 4 on downstream 3.14): > > [ 0.045778] CPU: Testing write buffer coherency: ok > [ 0.045968] /cpus/cpu@0 missing clock-frequency property > [ 0.045993] /cpus/cpu@1 missing clock-frequency property > [ 0.046016] /cpus/cpu@2 missing clock-frequency property > [ 0.046040] /cpus/cpu@3 missing clock-frequency property > [ 0.046059] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 > [ 0.046135] Setting up static identity map for 0x403a8920 - 0x403a8978 > [ 2.075052] CPU1: failed to come online > [ 4.085095] CPU2: failed to come online > [ 6.095142] CPU3: failed to come online > [ 6.095237] Brought up 1 CPUs > [ 6.095269] SMP: Total of 1 processors activated. > [ 6.095303] CPU: All CPU(s) started in HYP mode. > [ 6.095336] CPU: Virtualization extensions available. > > I also notice another apparent device tree issue: > > [ 7.341814] of_get_named_gpiod_flags: can't parse gpios property of > node '/soc/mmc@12220000/slot@0[0]' > [ 7.341850] of_get_named_gpiod_flags: can't parse gpios property of > node '/soc/mmc@12220000/slot@0[0]' > > Are any of those known issues and being worked on? > (The CPU failures affected 5420 Arndale Octa as well iirc.) > Can you check after applying following two patches for Arndale-Octa ([1],[2])? In other words, a patch similar to [2] might be required for this board too if it is booting under secure mode. [1] http://www.spinics.net/lists/linux-samsung-soc/msg31776.html [PATCH v2 Resend 1/2] ARM: EXYNOS: Update secondary boot addr for secure mode [2] http://www.spinics.net/lists/linux-samsung-soc/msg31777.html [PATCH v2 Resend 2/2] ARM: dts: Add secure firmware support for Arndale-octa -- Tushar Behera -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
