Am 23.06.2014 20:32, schrieb Kevin Hilman:
On Sun, Jun 22, 2014 at 8:56 PM, Tushar Behera trblinux@gmail.com wrote:
Adding linux-samsung-soc and linux-arm-kernel ML for wider audience.
On 06/19/2014 04:12 PM, Tushar Behera wrote:
On 06/19/2014 03:02 PM, Tushar Behera wrote:
On 06/18/2014 09:22 AM, Kevin Hilman wrote:
On Tue, Jun 17, 2014 at 8:26 PM, Tushar Behera trblinux@gmail.com wrote:
On 06/17/2014 10:23 PM, Kevin Hilman wrote: > Sachin, > > On Mon, Jun 16, 2014 at 11:16 PM, Kevin's boot bot khilman@linaro.org wrote: >> >> Tree/Branch: mainline >> Git describe: v3.16-rc1-2-gebe0618 >> Failed boot tests (console logs at the end) >> =========================================== >> exynos5420-arndale-octa: FAIL: arm-exynos_defconfig >> ste-snowball: FAIL: arm-u8500_defconfig > > FYI... these failures are getting more consistent on my octa board, > but still not failing every time. > > Kevin >
Hi Kevin,
Same here.
Observation: If you soft-reset the board (through the jumpers) after getting this problem, the problem keeps repeating. But if you hard-reset the board (by removing the power cord), the problem doesn't occur during next iteration.
I don't ever use the soft-reset, I only toggle the wall power. I don't ever actually remove the power cord though, I'm using a USB-controlled relay to toggle the wall power.
Kevin
Laura,
We are getting following kernel panic [1] (not always, but quite regularly) while booting Arndale-Octa (based on Samsung's Exynos5420) board with upstream kernel. I haven't observed this issue with other boards yet.
This issue is observed when I am booting with uImage + dtb (within roughly ~10 iterations).
Some more information:
The boot logs are provided in pastebin, okay[2] and failed[3].
In case of boot failures, I am getting a higher value for vm_total_pages (684424 in [3]). In case of successful boot on my board, it is always 521232 [2] on my board.
I can confirm that reverting the "Get rid of meminfo" patch gets the Octa board booting reliably again for me also.
Confirming that the revert [1] fixes also the issue I was reporting for my Arndale Octa. I'm using zImage + dtb and had been resetting via J10.
Regards, Andreas
[1] https://github.com/afaerber/linux/commits/arndale-octa-next