Re: [PATCH v3] printk: fix zero-valued printk timestamps in early boot
Geert Uytterhoeven <[email protected]> Wed, 1 Apr 2026 09:36:14 +0200
| Newsgroups | org.kernel.vger.linux-embedded,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CAMuHMdXk+xG0r4vQii9LA4XuhD8qLRYrDbJGAO8-cGzHqXEM3Q@mail.gmail.com> |
On Wed, 1 Apr 2026 at 02:04, Steven Rostedt <[email protected]> wrote: > On Wed, 01 Apr 2026 01:36:26 +0200 > Thomas Gleixner <[email protected]> wrote: > > [ 12.289141] Run /init as init process > > 12 seconds! Holly crap, that would fail every Chromebook requirement we > have. In most cases, we shoot for a 3 second boot up and 8 second max. So that's why my Sony HD Handycam never boots Linux, but instead still resumes the system Tim suspended 18 years ago ;-) Looks like the old CE Linux Forum Boot Time Working Group needs more blood... Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected] In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds