All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Carsten Emde <C.Emde@osadl.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	rostedt@goodmis.org, John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 4.0.4-rt1
Date: Wed, 20 May 2015 09:12:53 +0200	[thread overview]
Message-ID: <555C33F5.5070208@linutronix.de> (raw)
In-Reply-To: <555BBA52.9030809@osadl.org>

On 05/20/2015 12:33 AM, Carsten Emde wrote:
> Hi Sebastian,

Hi Carsten,

>> Known issues:
>>        - My AMD box throws a lot of "cpufreq_stat_notifier_trans: No
>>          policy found" warnings after boot. It is gone after manually
>>          setting the policy (to something else than reported).
> Same here, probably a minor issue. The messages disappear after setting
> cpufreq to performance, but they reappear when setting cpufreq back to
> ondemand.

Okay. Didn't try to set it back but yes, the messages gets back here,
too.

> On a side note: We need teach cyclictest 4.0 - right now, it says:
> WARN: Running on unknown kernel version...YMMV

Ah. Just posted a patch. I had in my rt-tests repo and forgot about it…

> Thanks, Sebastian, for the good work!

Thank you.

> 
>     -Carsten.
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Carsten Emde <C.Emde@osadl.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	rostedt@goodmis.org, John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 4.0.4-rt1
Date: Wed, 20 May 2015 09:12:53 +0200	[thread overview]
Message-ID: <555C33F5.5070208@linutronix.de> (raw)
In-Reply-To: <555BBA52.9030809@osadl.org>

On 05/20/2015 12:33 AM, Carsten Emde wrote:
> Hi Sebastian,

Hi Carsten,

>> Known issues:
>>        - My AMD box throws a lot of "cpufreq_stat_notifier_trans: No
>>          policy found" warnings after boot. It is gone after manually
>>          setting the policy (to something else than reported).
> Same here, probably a minor issue. The messages disappear after setting
> cpufreq to performance, but they reappear when setting cpufreq back to
> ondemand.

Okay. Didn't try to set it back but yes, the messages gets back here,
too.

> On a side note: We need teach cyclictest 4.0 - right now, it says:
> WARN: Running on unknown kernel version...YMMV

Ah. Just posted a patch. I had in my rt-tests repo and forgot about it…

> Thanks, Sebastian, for the good work!

Thank you.

> 
>     -Carsten.
Sebastian

  parent reply	other threads:[~2015-05-20  7:12 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 21:39 [ANNOUNCE] 4.0.4-rt1 Sebastian Andrzej Siewior
2015-05-19 22:33 ` Carsten Emde
2015-05-19 22:51   ` Pavel Vasilyev
2015-05-20  7:12   ` Sebastian Andrzej Siewior [this message]
2015-05-20  7:12     ` Sebastian Andrzej Siewior
2015-05-20 13:18   ` Daniel Wagner
2015-05-19 22:48 ` Pavel Vasilyev
2015-05-20  3:14 ` Mike Galbraith
2015-05-20 10:06 ` Pavel Vasilyev
2015-06-11 12:09   ` Sebastian Andrzej Siewior
2015-05-23 11:57 ` Pavel Vasilyev
2015-06-11 12:08   ` Sebastian Andrzej Siewior
2015-05-24 20:59 ` Fernando Lopez-Lezcano
2015-06-11 12:22   ` [PATCH] ASoC: Intel: sst: use ; instead of , at the of a C statement Sebastian Andrzej Siewior
2015-06-11 13:04     ` Mats Karrman
2015-06-11 13:14       ` [PATCH v2] " Sebastian Andrzej Siewior
2015-06-12  7:22         ` Vinod Koul
2015-06-12 10:37         ` Mark Brown
2015-05-26 13:34 ` [ANNOUNCE] 4.0.4-rt1 Clark Williams
2015-05-26 13:38   ` Steven Rostedt
2015-05-26 13:48     ` Clark Williams
2015-05-26 14:49       ` Mike Galbraith
2015-05-26 15:19       ` Steven Rostedt
2015-05-26 15:43         ` Clark Williams
2015-05-26 19:41           ` Fernando Lopez-Lezcano
2015-05-29  1:56             ` Fernando Lopez-Lezcano
2015-06-09 16:45               ` Fernando Lopez-Lezcano
2015-06-09 16:45                 ` Fernando Lopez-Lezcano
2015-06-09 22:05                 ` Pavel Vasilyev
2015-06-10  2:41                   ` Mike Galbraith
2015-06-10  2:41                     ` Mike Galbraith
2015-06-10  3:10                   ` Fernando Lopez-Lezcano
2015-06-10  3:10                     ` Fernando Lopez-Lezcano
2015-06-09 22:10                 ` Pavel Vasilyev
2015-06-09 22:10                   ` Pavel Vasilyev
2015-06-11 12:38               ` Sebastian Andrzej Siewior
2015-06-11 12:38                 ` Sebastian Andrzej Siewior
2015-05-28  8:41           ` Joakim Hernberg
2015-06-11 12:34           ` Sebastian Andrzej Siewior
2015-05-27  9:44 ` Joakim Hernberg
2015-05-27 10:19   ` Jeremy Jongepier
2015-05-28  8:33     ` Joakim Hernberg
2015-05-28  8:33       ` Joakim Hernberg
2015-05-27 15:50   ` Ralf Mardorf

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=555C33F5.5070208@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=C.Emde@osadl.org \
    --cc=jkacur@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.