[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f574808500e2c5fb733c1e5d9b4d17c2884d1b9f.camel@physik.fu-berlin.de>
Date: Thu, 27 Feb 2025 08:52:09 +0100
From: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To: Artur Rojek <contact@...ur-rojek.eu>, Yoshinori Sato
<ysato@...rs.sourceforge.jp>, Rich Felker <dalias@...c.org>, Daniel Lezcano
<daniel.lezcano@...aro.org>, Thomas Gleixner <tglx@...utronix.de>, Uros
Bizjak <ubizjak@...il.com>
Cc: Geert Uytterhoeven <geert+renesas@...der.be>, "D . Jeff Dionne"
<jeff@...esemi.io>, Rob Landley <rob@...dley.net>,
linux-sh@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] J2 Turtle Board fixes
Hi Artur,
On Sun, 2025-02-16 at 18:55 +0100, Artur Rojek wrote:
> this series fixes boot issues and allows J2 Turtle Board to boot
> upstream Linux again.
>
> Patch [1/2] enforces 8-byte alignment for the dtb offset.
>
> Patch [2/2] resolves a problem with PIT interrupts failing to register.
I can confirm that this series makes my J2 Turtle Board boot again!
> Even with the above fixes, Turtle Board is prone to occasional freezes
> related to clock source transition from periodic to hrtimers. I however
> decided to send those two patches ahead and debug the third issue at a
> later time.
Yep, it just got stuck for me right after these messages at my first boot attempt:
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
futex hash table entries: 512 (order: 1, 8192 bytes, linear)
NET: Registered PF_NETLINK/PF_ROUTE protocol family
clocksource: Switched to clocksource jcore_pit_cs
It boots past these messages on second attempt, although it's now stuck trying to start
/init. However, it's still echoing <RETURN> strokes, so it might be an issue with Toybox.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Powered by blists - more mailing lists