From: Yong Zhang <yong.zhang0@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0-rt2
Date: Sun, 24 Jul 2011 09:09:33 +0800 [thread overview]
Message-ID: <20110724010932.GA2133@zhy> (raw)
In-Reply-To: <alpine.LFD.2.02.1107231706380.2702@ionos>
[-- Attachment #1: Type: text/plain, Size: 1990 bytes --]
On Sat, Jul 23, 2011 at 05:13:30PM +0200, Thomas Gleixner wrote:
> Dear RT Folks,
>
> 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
>
> Patch against 3.0 can be found here:
>
> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-3.0-rt2.patch.bz2
>
> The split quilt queue is available at:
>
> http://www.kernel.org/pub/linux/kernel/projects/rt/patches-3.0-rt2.tar.bz2
>
I get below bug on my notebook:
[ 1244.912596] BUG: sleeping function called from invalid context at kernel/rtmutex.c:645
[ 1244.912599] in_atomic(): 1, irqs_disabled(): 0, pid: 1713, name: chromium-browse
[ 1244.912603] Pid: 1713, comm: chromium-browse Not tainted 3.0.0-rt2-00236-g4cf2acd #59
[ 1244.912605] Call Trace:
[ 1244.912613] [<c15cee54>] ? printk+0x1d/0x21
[ 1244.912618] [<c1036086>] __might_sleep+0xe6/0x110
[ 1244.912621] [<c15d151c>] rt_spin_lock+0x1c/0x40
[ 1244.912626] [<c111f763>] mem_cgroup_split_huge_fixup+0x43/0xd0
[ 1244.912629] [<c11195d8>] split_huge_page+0x208/0x770
[ 1244.912632] [<c15d1a25>] ? _raw_spin_lock+0x15/0x30
[ 1244.912635] [<c1040362>] ? migrate_enable+0xc2/0x130
[ 1244.912638] [<c111a20b>] __split_huge_page_pmd+0x7b/0xc0
[ 1244.912641] [<c10fadb5>] unmap_vmas+0x5a5/0x620
[ 1244.912645] [<c10e5e73>] ? lru_add_drain+0xe3/0x1d0
[ 1244.912648] [<c10faeaa>] zap_page_range+0x7a/0xa0
[ 1244.912651] [<c15d0d5f>] ? rt_mutex_lock+0x1f/0x50
[ 1244.912653] [<c10f81a4>] sys_madvise+0x294/0x5f0
[ 1244.912656] [<c10fe520>] ? remove_vma+0x50/0x70
[ 1244.912660] [<c15d7ddf>] sysenter_do_call+0x12/0x2d
And kernel config is attached.
Thanks,
Yong
[-- Attachment #2: config.gz --]
[-- Type: application/octet-stream, Size: 24475 bytes --]
next prev parent reply other threads:[~2011-07-24 1:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 15:13 [ANNOUNCE] 3.0-rt2 Thomas Gleixner
2011-07-23 15:41 ` Kim Leyendecker
2011-07-23 16:03 ` Thomas Gleixner
2011-07-23 16:27 ` Kim Leyendecker
2011-07-23 17:17 ` Ed Tomlinson
2011-07-23 17:34 ` Ed Tomlinson
2011-07-23 17:41 ` Thomas Gleixner
2011-07-24 1:09 ` Yong Zhang [this message]
2011-07-24 10:05 ` Thomas Gleixner
2011-07-25 1:57 ` Yong Zhang
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=20110724010932.GA2133@zhy \
--to=yong.zhang0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.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.