From: Arve Barsnes <arve.barsnes@gmail.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] v5.0.21-rt14
Date: Fri, 28 Jun 2019 11:28:27 +0200 [thread overview]
Message-ID: <CAJjrzcUBU5PPSzwXwm6wD8vT_mAakE-mepN1+CQuCoPNMWwgzw@mail.gmail.com> (raw)
In-Reply-To: <20190628103435.0d95ebe8@archlinux>
On Fri, 28 Jun 2019 at 10:35, Ralf Mardorf <ralf.mardorf@alice-dsl.net> wrote:
>
> On Fri, 28 Jun 2019 08:05:12 +0200, Arve Barsnes wrote:
> >I don't know if this helps
>
> Hi,
>
> I also don't know. However, you did not mention what hardware, even not
> the architecture ;). It might make a difference, if it happens on a
> "PC" or a "Raspberry".
>
> It seems to be ok on my Intel based x86_64 machine.
>
> [root@archlinux rocketmouse]# uname -a
> Linux archlinux 5.0.21-rt14-0-rt-cornflower #1 SMP PREEMPT RT Wed Jun 26 20:13:44 CEST 2019 x86_64 GNU/Linux
> [root@archlinux rocketmouse]# hwinfo --cpu | grep Model | sort -u
> Model: 6.60.3 "Intel(R) Celeron(R) CPU G1840 @ 2.80GHz"
> [root@archlinux rocketmouse]# dmidecode -t 2 | grep -eManu -eName
> Manufacturer: Gigabyte Technology Co., Ltd.
> Product Name: B85M-D3H
It should be a fairly standard PC :)
$ uname -a
Linux gentoo 5.0.21-rt13 #1 SMP Tue Jun 25 13:06:55 CEST 2019 x86_64
Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz GenuineIntel GNU/Linux
I don't have those other commands installed, but outside of my trouble
with -rt14, it's interesting that my uname output does not mention
PREEMPT RT.
Regards,
Arve
next prev parent reply other threads:[~2019-06-28 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 16:18 [ANNOUNCE] v5.0.21-rt14 Sebastian Andrzej Siewior
2019-06-28 6:05 ` Arve Barsnes
2019-06-28 7:10 ` Allen
2019-06-28 8:34 ` Ralf Mardorf
2019-06-28 9:28 ` Arve Barsnes [this message]
2019-06-28 9:57 ` Ralf Mardorf
2019-06-28 10:28 ` Arve Barsnes
2019-07-03 9:31 ` 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=CAJjrzcUBU5PPSzwXwm6wD8vT_mAakE-mepN1+CQuCoPNMWwgzw@mail.gmail.com \
--to=arve.barsnes@gmail.com \
--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).