From: Darren Hart <dvhart@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Jason Wessel <jason.wessel@windriver.com>
Subject: Re: [ANNOUNCE] 3.0-rt6 (kgdb working)
Date: Fri, 29 Jul 2011 08:57:31 -0700 [thread overview]
Message-ID: <4E32D86B.70301@linux.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1107282213000.31246@ionos>
On 07/28/2011 02:43 PM, Thomas Gleixner wrote:
> Dear RT Folks,
>
> I'm pleased to announce the 3.0-rt6 release.
>
> Changes versus 3.0-rt4 (I pushed out a rt5 w/o announce)
>
> * pin_cpu fix (Yong Zhang)
>
> * Various compile fixes (Yong Zhang & myself)
>
> * Serial fix for omap
>
> * Clocksource lockless watchdog reset
>
> * Reenabled CONFIG_RCU_BOOST (problem is unreproducible and maybe
> related to NO_HZ, which is still disabled. Paul is working on it!)
>
> * KGDB work^Whackaround (Jason Wessel)
>
> The kgdb workaround is really a hack and wants to be replaced by a
> proper overhaul for the console/tty maze.
> See: kgb-serial-hackaround.patch
I just confirmed that this resolves the issue I was seeing while trying
to single step through futex_requeue() on a 2 socket E5680.
Thanks Thomas and Jason,
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-07-29 15:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 21:43 [ANNOUNCE] 3.0-rt6 Thomas Gleixner
2011-07-28 23:33 ` Peter W. Morreale
2011-07-29 0:56 ` Thomas Gleixner
2011-07-29 6:05 ` Mike Galbraith
2011-07-29 14:03 ` Paul E. McKenney
2011-07-29 15:57 ` Darren Hart [this message]
2011-07-30 15:49 ` Remy Bohmer
2011-07-30 20:21 ` Remy Bohmer
2011-08-07 10:44 ` Remy Bohmer
2011-08-01 8:42 ` Rolando Martins
2011-08-01 10:34 ` Mike Galbraith
2011-08-01 10:45 ` Rolando Martins
2011-08-01 11:06 ` Peter Zijlstra
2011-08-01 11:10 ` Rolando Martins
2011-08-04 6:34 ` Fernando Lopez-Lezcano
2011-08-04 9:42 ` Peter Zijlstra
2011-08-04 19:05 ` Fernando Lopez-Lezcano
2011-08-04 20:15 ` Uwe Kleine-König
2011-08-05 9:28 ` Uwe Kleine-König
2011-08-05 16:03 ` Fernando Lopez-Lezcano
2011-08-08 17:25 ` Fernando Lopez-Lezcano
2011-08-04 16:34 ` [ANNOUNCE] 3.0-rt6 : BUG at kernel/trmutex.c:724! Tim Sander
2011-08-04 16:37 ` Peter Zijlstra
2011-08-04 17:04 ` Tim Sander
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=4E32D86B.70301@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox