From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: John Ogness <john.ogness@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
francesco.dolcini@toradex.com
Subject: Re: [ANNOUNCE] v6.6-rt13
Date: Mon, 20 Nov 2023 13:27:08 +0100 [thread overview]
Message-ID: <20231120122708.UxA5Wf4b@linutronix.de> (raw)
In-Reply-To: <ZVJ0B9HYLTsLxxXw@francesco-nb.int.toradex.com>
On 2023-11-13 20:07:51 [+0100], Francesco Dolcini wrote:
> Hello Sebastian, hello John
Hi,
> During our weekly CI tests of rt-devel branch we noticed that commit
> 78f4b59c6faa ("printk: Update the printk series.") breaks booting on
> multiple NXP i.MX platforms (arm and arm64), likely related to
> drivers/tty/serial/imx.c.
>
> We are not planning any additional investigation at the moment and
> we have no debug outputs to share, just wanted to give you a head-up.
Thank you for the report.
As it turns out, the new bits never saw the lights of a 32bit machine.
The following hunk should fix it:
diff --git a/kernel/printk/printk_ringbuffer.c b/kernel/printk/printk_ringbuffer.c
index a949d02fbd174..b6a8306bfda89 100644
--- a/kernel/printk/printk_ringbuffer.c
+++ b/kernel/printk/printk_ringbuffer.c
@@ -1477,7 +1477,10 @@ static inline u64 __ulseq_to_u64seq(u32 ulseq)
* sequence. It needs to be expanded to 64bit. Get the first sequence
* number from the ringbuffer and fold it.
*/
- seq = rb_first_seq - ((u32)rb_first_seq - ulseq);
+ if (rb_first_seq == 0)
+ seq = ulseq;
+ else
+ seq = rb_first_seq - ((u32)rb_first_seq - ulseq);
return seq;
}
> Francesco
Sebastian
prev parent reply other threads:[~2023-11-20 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 15:23 [ANNOUNCE] v6.6-rt13 Sebastian Andrzej Siewior
2023-11-13 19:07 ` Francesco Dolcini
2023-11-20 12:27 ` Sebastian Andrzej Siewior [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231120122708.UxA5Wf4b@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox