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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <a917c1183f85bad8af1312994d330f141c57db04.camel@physik.fu-berlin.de>
Date: Fri, 28 Feb 2025 23:34:44 +0100
From: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To: Rob Landley <rob@...dley.net>, 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>, linux-sh@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] J2 Turtle Board fixes

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@...ftwood) (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?

> 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.

> 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?

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913