linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Udo van den Heuvel <udovdh@xs4all.nl>
To: RT <linux-rt-users@vger.kernel.org>
Subject: Re: 5.4.3-rt1 mutex issue
Date: Fri, 20 Dec 2019 13:33:26 +0100	[thread overview]
Message-ID: <67d72f0c-d4d0-002e-b61a-0efb3e78d02a@xs4all.nl> (raw)
In-Reply-To: <fd438084-751c-3cb9-6697-d263a730bf91@xs4all.nl>

Hello,

I was slightly mistaken, 5.4.3 (sans rt) also shows this issue...


Udo

On 20-12-2019 13:29, Udo van den Heuvel wrote:
> Hello,
> 
> Just booted into 5.4.3-rt1.
> I noticed that this kernel still shows some mutex-related
> errors/warnings/etc during bootup.
> Unfortunately these are not found in dmesg nor in /var/log/messages at
> this time.
> 5.4.3 (sans rt) ran without this issue for over two weeks.
> 
> Kind regards,
> Udo
> 


      reply	other threads:[~2019-12-20 12:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 12:29 5.4.3-rt1 mutex issue Udo van den Heuvel
2019-12-20 12:33 ` Udo van den Heuvel [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=67d72f0c-d4d0-002e-b61a-0efb3e78d02a@xs4all.nl \
    --to=udovdh@xs4all.nl \
    --cc=linux-rt-users@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).