public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Ed Tomlinson <edt@aei.ca>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0-rt2
Date: Sat, 23 Jul 2011 19:41:53 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1107231936400.2702@ionos> (raw)
In-Reply-To: <201107231334.23216.edt@aei.ca>

On Sat, 23 Jul 2011, Ed Tomlinson wrote:

> On Saturday 23 July 2011 13:17:04 Ed Tomlinson wrote:
> > On Saturday 23 July 2011 11:13:30 Thomas Gleixner wrote:
> > > I'm pleased to announce the 3.0-rt2 release.
> > > 
> > > Changes versus 3.0-rt1:
> > > 
> > >   * mqueue fix (Yoshitake Kobayashi)
> > > 
> > >   * dca locking fix (Mike Galbraith)
> > > 
> > >   * trace updates (Carsten Emde)
> > > 
> > >   * Fixed vprintk wreckage and rcutorture (tglx)
> > > 
> > > Known issues:
> > > 
> > >   * Some weird "console=..." commandline + config dependent
> > >     interactions which have been not yet investigated down to their
> > >     root cause. Result in a boot hang. YMMV
> 
> Got this warning too.  Was a change was missed?
> 
> [  364.392603] NOHZ: local_softirq_pending 08

Forgot to disable NOHZ for now, have not yet had time to investigate
that local_softirq_pending warning.

> [  905.155441] WARNING: at kernel/trace/trace.c:2729 tracing_ctrl_write+0x203/0x220()
> [  905.155447] Hardware name: System Product Name
> [  905.155452] tracing_enabled is deprecated. Use tracing_on

     		 ^^^^
Thanks,

	tglx

  reply	other threads:[~2011-07-23 17:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23 15:13 [ANNOUNCE] 3.0-rt2 Thomas Gleixner
2011-07-23 17:17 ` Ed Tomlinson
2011-07-23 17:34   ` Ed Tomlinson
2011-07-23 17:41     ` Thomas Gleixner [this message]
2011-07-24  1:09 ` Yong Zhang
2011-07-24 10:05   ` Thomas Gleixner
2011-07-25  1:57     ` Yong Zhang

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=alpine.LFD.2.02.1107231936400.2702@ionos \
    --to=tglx@linutronix.de \
    --cc=edt@aei.ca \
    --cc=linux-kernel@vger.kernel.org \
    --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