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 12:28:44 +0200 [thread overview]
Message-ID: <CAJjrzcWdSxHoHFP1THs4_jbFGAOCfds73W0fjFkNFib97TAQ6g@mail.gmail.com> (raw)
In-Reply-To: <20190628115739.7fec552c@archlinux>
On Fri, 28 Jun 2019 at 11:58, Ralf Mardorf <ralf.mardorf@alice-dsl.net> wrote:
>
> On Fri, 28 Jun 2019 11:28:27 +0200, Arve Barsnes wrote:
> >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.
>
> Perhaps you accidentally used the wrong config to build the kernel?
>
> What does
>
> zgrep PREE /proc/config.gz
> grep PREE /lib/modules/5.0.21-rt1*/build/.config
>
> show?
>
> You might have a config in /boot/ or somewhere else.
This is a relatively new box that haven't really been used much for
audio work yet, so I seem to have completely failed to set up preempt
at the moment.
CONFIG_HAVE_PREEMPT_LAZY=y
CONFIG_PREEMPT_VOLUNTARY=y
Other configs not set.
But before I removed my -rt14 config I did a diff between it and the
-rt13 config, and they were identical, so at least the config is not
the cause of my boot trouble. I might have done something otherwise
wrong though, I will try to redo the upgrade from the beginning after
the weekend.
next prev parent reply other threads:[~2019-06-28 10: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
2019-06-28 9:57 ` Ralf Mardorf
2019-06-28 10:28 ` Arve Barsnes [this message]
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=CAJjrzcWdSxHoHFP1THs4_jbFGAOCfds73W0fjFkNFib97TAQ6g@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).