From: Will Schmidt <will_schmidt@vnet.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
rt-users <linux-rt-users@vger.kernel.org>,
John Stultz <johnstul@us.ibm.com>, Nick Piggin <npiggin@suse.de>
Subject: Re: [ANNOUNCE] 2.6.33.5-rt23
Date: Wed, 09 Jun 2010 16:31:14 -0500 [thread overview]
Message-ID: <1276119074.15867.311.camel@lexx> (raw)
In-Reply-To: <alpine.LFD.2.00.1006091837410.2933@localhost.localdomain>
On Wed, 2010-06-09 at 18:44 +0200, Thomas Gleixner wrote:
> We are pleased to announce the next update to our new preempt-rt
> series.
>
<snip>
> Changes from 2.6.33.4-rt21 to 2.6.33.5-rt22:
>
> ef4afcc: Merge stable/linux-2.6.33.y into rt/2.6.33
>
> Changes from 2.6.33.5-rt22 to 2.6.33.5-rt23:
>
> ab774e8: drivers/hwmon/coretemp.c: get TjMax value from MSR
> e8bfcca: drivers/hwmon/coretemp.c: detect the thermal sensors by CPUID
> a06a867: dcache: Prevent d_genocide() from decrementing d_count more than once
> bdeadaf: nfs: Avoid igrab deadlock.
> 6976846: dcache: Fix select_parent dentry traversal locking
> 1f0f6ec: powerpc: chrp/time.c fix preprocessor conditional
I'm still on 2.6.33.5-rt22 on powerpc, and have run into a couple
"sleeping function called from invalid context..." BUGs. The first was
during system boot, second during a 'make'.
relevant code paths don't seem to have changed between -rt22 and -rt23,
so I think still valid.. :-)
This is on a POWER7 system, which may have opened up some timing
windows, wrt previous runs on POWER6 systems.
BUG: sleeping function called from invalid context at
kernel/rtmutex.c:684
pcnt: 1 0 in_atomic(): 1, irqs_disabled(): 1, pid: 3209, name: ip
Call Trace:
[c000000078cf28e0] [c000000000015550] .show_stack+0xd8/0x218
(unreliable)
[c000000078cf29c0] [c0000000006a99c8] .dump_stack+0x28/0x3c
[c000000078cf2a40] [c00000000006cea8] .__might_sleep+0x134/0x15c
[c000000078cf2ae0] [c0000000006a2f78] .rt_spin_lock+0x4c/0x9c
[c000000078cf2b70] [c0000000001799e8] ._slab_irq_disable+0x70/0xd8
[c000000078cf2c20] [c00000000017d1b4] .kmem_cache_alloc_node_notrace
+0x78/0x234
[c000000078cf2cf0] [c000000000131a04] .irq_to_desc_alloc_node+0xdc/0x2b8
[c000000078cf2db0] [c00000000000f238] .irq_setup_virq+0x44/0xe4
[c000000078cf2e50] [c00000000000f3f8] .irq_create_mapping+0x120/0x188
[c000000078cf2ef0] [c00000000002edfc] .ibmebus_request_irq+0x50/0xac
[c000000078cf2fa0] [c0000000004f3bd0] .ehea_up+0x314/0x69c
[c000000078cf30b0] [c0000000004f3fc8] .ehea_open+0x70/0x128
[c000000078cf3150] [c0000000005e504c] .dev_open+0x120/0x198
[c000000078cf31f0] [c0000000005e3ee8] .dev_change_flags+0x11c/0x21c
[c000000078cf32a0] [c0000000005f10ec] .do_setlink+0x2e0/0x400
[c000000078cf3380] [c0000000005f23a0] .rtnl_newlink+0x380/0x5b8
[c000000078cf3580] [c0000000005f1fd4] .rtnetlink_rcv_msg+0x258/0x2a4
[c000000078cf3630] [c000000000604094] .netlink_rcv_skb+0x84/0x120
[c000000078cf36d0] [c0000000005f1d58] .rtnetlink_rcv+0x38/0x5c
[c000000078cf3760] [c000000000603ba0] .netlink_unicast+0x31c/0x3fc
[c000000078cf3840] [c000000000604838] .netlink_sendmsg+0x2c8/0x30c
[c000000078cf3930] [c0000000005c8bdc] .sock_sendmsg+0xbc/0xfc
[c000000078cf3b10] [c0000000005c92fc] .SyS_sendmsg+0x20c/0x2a4
[c000000078cf3d50] [c0000000005c7f6c] .SyS_socketcall+0x238/0x2b0
[c000000078cf3e30] [c00000000000852c] syscall_exit+0x0/0x40
BUG: sleeping function called from invalid context at kernel/rtmutex.c:684
pcnt: 0 0 in_atomic(): 0, irqs_disabled(): 1, pid: 4760, name: make
Call Trace:
[c0000000792978b0] [c000000000015550] .show_stack+0xd8/0x218 (unreliable)
[c000000079297990] [c0000000006a99c8] .dump_stack+0x28/0x3c
[c000000079297a10] [c00000000006cea8] .__might_sleep+0x134/0x15c
[c000000079297ab0] [c0000000006a2f78] .rt_spin_lock+0x4c/0x9c
[c000000079297b40] [c0000000000a1ff0] .get_signal_to_deliver+0xcc/0x4ec
[c000000079297c50] [c000000000018604] .do_signal_pending.clone.0+0x6c/0x2e0
[c000000079297d90] [c0000000000188b0] .do_signal+0x38/0x74
[c000000079297e30] [c000000000008b40] user_work+0x24/0x28
>
> Bulk of changes comes from stable tree. The -rt related changes are
> mostly fixes for the vfs fallout the rest are fixlets all over the
> place and hardware enablement.
>
> Download locations:
>
> http://www.kernel.org/pub/linux/kernel/projects/rt/
>
> Git release branch:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33
>
> Gitweb:
> http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33
>
> Information on the RT patch can be found at:
>
> http://rt.wiki.kernel.org/index.php/Main_Page
>
> To build the 2.6.33.5-rt23 tree, the following patches should be
> applied:
>
> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.5.tar.bz2
> http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.5-rt23.bz2
>
> Enjoy !
>
> tglx
>
> --
> 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
next prev parent reply other threads:[~2010-06-09 21:31 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 16:52 [ANNOUNCE] 2.6.33-rc8-rt2 Thomas Gleixner
2010-02-24 22:38 ` Peter Zijlstra
2010-02-25 22:56 ` Peter Zijlstra
2010-02-26 19:44 ` Dan Carpenter
2010-02-27 8:10 ` Thomas Gleixner
2010-02-26 19:54 ` [ANNOUNCE] 2.6.33-rt3 Thomas Gleixner
2010-02-27 9:25 ` Xavier Miller
2010-02-27 10:10 ` GeunSik Lim
2010-02-27 11:53 ` Thomas Gleixner
2010-03-02 21:25 ` Fernando Lopez-Lezcano
2010-03-02 21:53 ` Thomas Gleixner
2010-02-27 9:50 ` GeunSik Lim
2010-03-12 10:44 ` [ANNOUNCE] 2.6.33-rt6 Thomas Gleixner
2010-03-12 12:17 ` 2.6.33-rt6 on Beagle Chatterjee, Amit
2010-03-15 9:20 ` Uwe Kleine-König
2010-03-15 11:23 ` What's the best way to create an embedded version of PREEMPT_RT Linux ? Armin Steinhoff
2010-03-21 11:06 ` [ANNOUNCE] 2.6.33.1-rt11 Thomas Gleixner
2010-04-07 14:24 ` [ANNOUNCE] 2.6.33.2-rt13 Thomas Gleixner
2010-04-27 15:52 ` [ANNOUNCE] 2.6.33.3-rt16 Thomas Gleixner
2010-04-30 10:00 ` [ANNOUNCE] 2.6.33.3-rt17 Thomas Gleixner
2010-05-02 19:18 ` [ANNOUNCE] 2.6.33.3-rt19 Thomas Gleixner
2010-06-09 16:44 ` [ANNOUNCE] 2.6.33.5-rt23 Thomas Gleixner
2010-06-09 21:31 ` Will Schmidt [this message]
2010-06-10 6:07 ` Thomas Gleixner
2010-06-10 15:56 ` Will Schmidt
2010-06-10 16:05 ` Darcy L. Watkins
2010-06-14 13:33 ` Thomas Gleixner
2010-06-14 13:34 ` Thomas Gleixner
2010-06-14 15:35 ` Will Schmidt
2010-07-13 15:54 ` [ANNOUNCE] 2.6.33.6-rt26 Thomas Gleixner
2010-07-13 16:52 ` Dhaval Giani
2010-07-13 18:04 ` Philipp Überbacher
2010-07-13 19:13 ` Darcy L. Watkins
2010-07-13 19:23 ` Philipp Überbacher
2010-07-14 13:47 ` Thomas Gleixner
2010-07-14 13:57 ` Ng Oon-Ee
2010-07-14 14:27 ` John Kacur
[not found] ` <AANLkTikRUp0IG8aMZ0eHxXcDmfUFTqW8HCSJcx8nQIZN@mail.gmail.com>
2010-07-15 5:25 ` Yang Jian
2010-07-15 11:45 ` Philipp Überbacher
2010-07-19 6:37 ` Barry Song
2010-07-31 13:33 ` [ANNOUNCE] 2.6.33.6-rt27 Thomas Gleixner
2010-08-03 9:23 ` [ANNOUNCE] 2.6.33.7-rt29 Thomas Gleixner
2010-12-21 13:52 ` Thomas Gleixner
2010-12-21 15:01 ` Mark Knecht
2010-12-21 15:48 ` Madovsky
2010-12-21 16:39 ` Dennis Borgmann
2010-12-22 16:38 ` Madovsky
2010-12-22 20:20 ` Remy Bohmer
2010-12-24 22:36 ` Fernando Lopez-Lezcano
2010-12-31 19:56 ` Fernando Lopez-Lezcano
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=1276119074.15867.311.camel@lexx \
--to=will_schmidt@vnet.ibm.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=npiggin@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).