Re: [PATCH 0/2] J2 Turtle Board fixes

[Rob Landley <rob@landley.net>]

On 2/28/25 16:34, John Paul Adrian Glaubitz wrote:
> Hi,
> 
> On Fri, 2025-02-28 at 16:19 -0600, Rob Landley wrote:
>> The march 2024 rebuild was in response to that Feb 2024 bugfix, so it
>> _should_ have the fix? (I'm waiting for another musl release to rebuild
>> them again...)
>>
>> I just downloaded the toolchain currently at that URL and built mkroot
>> and it worked for me:
>>
>> Run /init as init process
>> sntp: time.google.com:123: Try again
>> Type exit when done.
>> $ cat /proc/version
>> Linux version 6.14.0-rc3 (landley@driftwood) (sh2eb-linux-muslfdpic-cc
>> (GCC) 11.2.0, GNU ld (GNU Binutils) 2.33.1) #1 SMP Fri Feb 28 15:47:36
>> CST 2025
> 
> Is that on Toybox git HEAD?

Yes. Commit b4fd71d18f84.

>> And the failure _without_ the fix was deterministic rather than
>> intermittent, so...
>>
>> Keep in mind the init script has a 3 second timeout trying to call sntp
>> to set the clock, which will fail if the ethernet isn't connected (or no
>> driver, or no internet...)
> 
> I'll try again this weekend. Also, I will review and pick up the fix.

Ok. (I'm available Saturday if you need to poke me, but traveling sunday.)

>> P.S. Speaking of intermittent, I hit that hang after "clocksource:
>> Switched to clocksource jcore_pit_cs" on one attempt just now. I should
>> sit down with the engineers next time I'm in japan and try to root cause
>> it. The scheduler fires reliably, so it's _probably_ not a hardware
>> issue? We've had Linux uptime of over a year, not just idle but running
>> an energy monitoring app, so it's pretty stable in our systems...
> 
> I thought it was a software issue?

I agree. That's why I said it's probably not a hardware issue. (The 
config has NO_HZ_IDLE so if the PIT didn't fire reliably when 
reprogrammed the scheduler would flake, and it's not, so...)

> Adrian

Rob