mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Gondois <pierre.gondois@arm.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [ANNOUNCE] v6.8-rc4-rt4
Date: Fri, 23 Feb 2024 10:52:57 +0100	[thread overview]
Message-ID: <1ae5b9e6-9eb4-49a5-8cfc-46359c8d74c3@arm.com> (raw)
In-Reply-To: <20240214161130.ZT9RSWDc@linutronix.de>

Hello Sebastian,,

On 2/14/24 17:11, Sebastian Andrzej Siewior wrote:
> Dear RT folks!
> 
> I'm pleased to announce the v6.8-rc4-rt4 patch set.
> 
> Changes since v6.8-rc4-rt3:
> 
>    - The previous releases introduced a compiler warning for i915 driver
>      in the !i915 case. Reported by the kernel test robot.
> 
>    - An update to the printk series by John Ogness:
> 
>      - document new nbcon console callbacks:
>      
>      - add "threadprintk" boot argument for !PREEMPT_RT users that want a
>        fully threaded printk.
>      
>      - use thread callback (instead of atomic callback) for legacy printing
>        in task context.
>      
>      - sync with recently reviewed printk series.
> 
> Known issues
>       Pierre Gondois reported crashes on ARM64 together with "rtla timerlat
>       hist" as trigger. It is not yet understood. The report is at
> 	https://lore.kernel.org/70c08728-3d4f-47a6-8a3e-114e4877d120@arm.com

I recently tried to reproduce the issue using the same kernel version and platform,
but even after multiple resets and attempts to re-trigger it didn't show up.
As it doesn't seem anyone else reported anything similar, would it make sense
to drop the reference ?

Regards,
Pierre

  reply	other threads:[~2024-02-23  9:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14 16:11 Sebastian Andrzej Siewior
2024-02-23  9:52 ` Pierre Gondois [this message]
2024-02-23 13:40   ` Sebastian Andrzej Siewior

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=1ae5b9e6-9eb4-49a5-8cfc-46359c8d74c3@arm.com \
    --to=pierre.gondois@arm.com \
    --cc=bigeasy@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

all inboxes | Powered by JetHome®