From: Maarten Lankhorst <m.b.lankhorst@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-rt3
Date: Sun, 24 Jul 2011 16:40:22 +0200 [thread overview]
Message-ID: <4E2C2ED6.4040904@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1107241223560.2702@ionos>
On 07/24/2011 12:33 PM, Thomas Gleixner wrote:
> Dear RT Folks,
>
> I'm pleased to announce the 3.0-rt3 release.
>
> Changes versus 3.0-rt2:
>
> * Fix earlyprintk really
>
> * AMD NB fix for allocation in smp function call, reported by Ed
>
> * Disabled a few config options on RT which have known issues
>
> Patch against 3.0 can be found here:
>
> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-3.0-rt3.patch.bz2
>
> The split quilt queue is available at:
>
> http://www.kernel.org/pub/linux/kernel/projects/rt/patches-3.0-rt3.tar.bz2
Oprofile seems to be upset at me, I swear I'm innocent!
[ 46.460786] oprofile: using NMI interrupt.
[ 47.492263] BUG: sleeping function called from invalid context at kernel/rtmutex.c:645
[ 47.492265] in_atomic(): 1, irqs_disabled(): 1, pid: 0, name: kworker/0:1
[ 47.492267] Pid: 0, comm: kworker/0:1 Tainted: G C 3.0.0-rt3-patser+ #39
[ 47.492269] Call Trace:
[ 47.492270] <IRQ> [<ffffffff8103fc0a>] __might_sleep+0xca/0xf0
[ 47.492279] [<ffffffff8160d424>] rt_spin_lock+0x24/0x40
[ 47.492282] [<ffffffff811476c7>] __kmalloc+0xc7/0x370
[ 47.492287] [<ffffffffa0275c85>] ? ppro_setup_ctrs+0x215/0x260 [oprofile]
[ 47.492291] [<ffffffffa0273de0>] ? oprofile_cpu_notifier+0x60/0x60 [oprofile]
[ 47.492295] [<ffffffffa0275c85>] ppro_setup_ctrs+0x215/0x260 [oprofile]
[ 47.492305] [<ffffffffa0273de0>] ? oprofile_cpu_notifier+0x60/0x60 [oprofile]
[ 47.492307] [<ffffffffa0273de0>] ? oprofile_cpu_notifier+0x60/0x60 [oprofile]
[ 47.492308] [<ffffffffa0273ea4>] nmi_cpu_setup+0xc4/0x110 [oprofile]
[ 47.492310] [<ffffffff81094455>] generic_smp_call_function_interrupt+0x95/0x190
[ 47.492313] [<ffffffff8101df77>] smp_call_function_interrupt+0x27/0x40
[ 47.492315] [<ffffffff81615093>] call_function_interrupt+0x13/0x20
[ 47.492316] <EOI> [<ffffffff8131d0c4>] ? plist_check_head+0x54/0xc0
[ 47.492321] [<ffffffff81371fe8>] ? intel_idle+0xc8/0x120
[ 47.492322] [<ffffffff81371fc7>] ? intel_idle+0xa7/0x120
[ 47.492324] [<ffffffff814a57b0>] cpuidle_idle_call+0xb0/0x230
[ 47.492326] [<ffffffff810011db>] cpu_idle+0x8b/0xe0
[ 47.492328] [<ffffffff815fc82f>] start_secondary+0x1d3/0x1d8
Also not sure where this one came from:
[ 37.456688] BUG: spinlock bad magic on CPU#3, threaded-ml/1619
[ 37.456690] lock: ffff8801fdc74d50, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0
[ 37.456692] Pid: 1619, comm: threaded-ml Tainted: G C 3.0.0-rt3-patser+ #39
[ 37.456693] Call Trace:
[ 37.456697] [<ffffffff81607a78>] spin_bug+0xa0/0xa8
[ 37.456699] [<ffffffff8132b412>] do_raw_spin_lock+0xa2/0x170
[ 37.456702] [<ffffffff8104a201>] ? get_parent_ip+0x11/0x50
[ 37.456704] [<ffffffff8160d783>] _raw_spin_lock+0x23/0x30
[ 37.456706] [<ffffffff810931ce>] rt_mutex_start_proxy_lock+0x2e/0xd0
[ 37.456708] [<ffffffff8109093a>] futex_requeue+0x47a/0x850
[ 37.456710] [<ffffffff8109138e>] do_futex+0xae/0xb00
[ 37.456712] [<ffffffff81157dcd>] ? fget_light+0x6d/0x110
[ 37.456714] [<ffffffff810b77b7>] ? audit_syscall_entry+0x2e7/0x310
[ 37.456715] [<ffffffff814c9375>] ? sys_recvmsg+0x75/0x90
[ 37.456717] [<ffffffff810923e6>] compat_sys_futex+0xf6/0x190
[ 37.456719] [<ffffffff8100e864>] ? syscall_trace_enter+0x184/0x210
[ 37.456721] [<ffffffff816158b3>] ia32_do_call+0x13/0x13
Running linux 3.0rt3 with (drm-preempt patched) nouveau out of tree.
next prev parent reply other threads:[~2011-07-24 14:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 10:33 [ANNOUNCE] 3.0-rt3 Thomas Gleixner
2011-07-24 14:40 ` Maarten Lankhorst [this message]
2011-07-24 16:12 ` Thomas Gleixner
2011-07-24 16:42 ` hermann
2011-07-24 16:44 ` Thomas Gleixner
2011-07-24 16:53 ` hermann
2011-07-24 17:23 ` Georgiewskiy Yuriy
2011-07-25 22:20 ` Darren Hart
2011-07-26 6:00 ` Darren Hart
2011-07-26 11:44 ` Maarten Lankhorst
2011-07-26 17:01 ` Darren Hart
2011-07-26 17:11 ` Maarten Lankhorst
2011-07-27 1:57 ` [ANNOUNCE] 3.0-rt3 (futex_requeue bad spinlock magic) Darren Hart
2011-07-27 8:25 ` Darren Hart
2011-07-26 9:01 ` [ANNOUNCE] 3.0-rt3 Thomas Gleixner
2011-07-25 22:55 ` Fernando Lopez-Lezcano
2011-07-26 9:13 ` Uwe Kleine-König
2011-07-26 23:52 ` Fernando Lopez-Lezcano
2011-07-26 23:57 ` Fernando Lopez-Lezcano
2011-07-26 3:11 ` Frank Rowand
2011-07-26 9:30 ` Uwe Kleine-König
2011-07-26 3:12 ` Frank Rowand
2011-07-26 9:19 ` Uwe Kleine-König
2011-07-26 9:25 ` Thomas Gleixner
2011-07-26 3:14 ` Frank Rowand
2011-07-26 3:49 ` Darren Hart
2011-07-26 6:20 ` Yong Zhang
2011-07-27 18:05 ` N, Mugunthan V
2011-07-27 18:32 ` Thomas Gleixner
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=4E2C2ED6.4040904@gmail.com \
--to=m.b.lankhorst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox