public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Subject: Re: [ANNOUNCE] 3.0-rt3
Date: Mon, 25 Jul 2011 15:55:21 -0700	[thread overview]
Message-ID: <4E2DF459.3030509@localhost> (raw)
In-Reply-To: <alpine.LFD.2.02.1107241223560.2702@ionos>

[-- Attachment #1: Type: text/plain, Size: 3270 bytes --]

On 07/24/2011 03:33 AM, Thomas Gleixner wrote:
> Dear RT Folks,
>
> I'm pleased to announce the 3.0-rt3 release.

Thanks!!... testing on a dual core laptop, fedora 15, 32 bit:

[   32.169727] BUG: MAX_LOCKDEP_ENTRIES too low!
[   32.169730] turning off the locking correctness validator.

(where do I change this?)

[   32.169733] Pid: 830, comm: iptables-restor Not tainted 
3.0.0-1.rt3.1.fc14.ccrma.i686.rtPAE #1
[   32.169735] Call Trace:
[   32.169742]  [<c086c6f3>] ? printk+0x2d/0x32
[   32.169746]  [<c047689e>] add_lock_to_list.clone.11.clone.17+0x41/0x9e
[   32.169749]  [<c047927d>] __lock_acquire+0xac3/0xc2f
[   32.169753]  [<c046abe4>] ? sched_clock_cpu+0x13d/0x14d
[   32.169756]  [<c0476300>] ? lock_is_held+0x5b/0x7d
[   32.169760]  [<c040e748>] ? native_sched_clock+0x4d/0x52
[   32.169762]  [<c047614c>] ? trace_hardirqs_off+0xb/0xd
[   32.169765]  [<c040e755>] ? sched_clock+0x8/0xb
[   32.169767]  [<c046a8ea>] ? sched_clock_local+0x12/0x16b
[   32.169770]  [<c086dd67>] ? rt_spin_lock_slowlock+0x31/0x170
[   32.169772]  [<c04798a9>] lock_acquire+0xde/0x11d
[   32.169775]  [<c086dd67>] ? rt_spin_lock_slowlock+0x31/0x170
[   32.169778]  [<c086ea7b>] _raw_spin_lock+0x45/0x72
[   32.169780]  [<c086dd67>] ? rt_spin_lock_slowlock+0x31/0x170
[   32.169783]  [<c086dd67>] rt_spin_lock_slowlock+0x31/0x170
[   32.169787]  [<c047e4df>] rt_spin_lock_fastlock.clone.8+0x23/0x26
[   32.169789]  [<c086e392>] rt_spin_lock+0x13/0x43
[   32.169792]  [<c0442acd>] ? migrate_disable+0xf1/0x100
[   32.169796]  [<c04d6047>] __local_lock_irqsave+0x29/0x72
[   32.169799]  [<c04d8827>] get_page_from_freelist+0x113/0x432
[   32.169803]  [<c04d8de6>] __alloc_pages_nodemask+0x160/0x6ce
[   32.169806]  [<c086ed7d>] ? _raw_spin_unlock_irqrestore+0x56/0x63
[   32.169809]  [<c0439644>] ? task_rq_unlock+0x20/0x24
[   32.169812]  [<c04428e4>] ? migrate_enable+0x11f/0x12e
[   32.169816]  [<c04f66d1>] ? kmalloc_node.clone.13+0xd/0xf
[   32.169819]  [<c04f7e2b>] __vmalloc_node_range+0x103/0x174
[   32.169821]  [<c04f7fdd>] ? vzalloc+0x15/0x17
[   32.169824]  [<c04f7eec>] __vmalloc_node+0x50/0x58
[   32.169826]  [<c04f7fdd>] ? vzalloc+0x15/0x17
[   32.169829]  [<c04f7fdd>] ? vzalloc+0x15/0x17
[   32.169831]  [<c04f7fae>] __vmalloc_node_flags+0x30/0x36
[   32.169834]  [<c04f7fdd>] ? vzalloc+0x15/0x17
[   32.169836]  [<c04f7fdd>] vzalloc+0x15/0x17
[   32.169840]  [<c08044bb>] do_ipt_get_ctl+0xfd/0x2e2
[   32.169842]  [<c047691b>] ? put_lock_stats.clone.12+0x12/0x1d
[   32.169845]  [<c04769db>] ? lock_release_holdtime+0xb5/0xba
[   32.169847]  [<c04797a5>] ? lock_release+0x19f/0x1c5
[   32.169851]  [<c07c25d4>] nf_sockopt+0x179/0x1df
[   32.169854]  [<c07c2663>] nf_getsockopt+0x29/0x2f
[   32.169857]  [<c07ce9ed>] ip_getsockopt+0x79/0xa4
[   32.169861]  [<c07e6dfc>] raw_getsockopt+0x2e/0xb0
[   32.169865]  [<c07936b6>] sock_common_getsockopt+0x23/0x29
[   32.169867]  [<c0792c1f>] sys_getsockopt+0x70/0x89
[   32.169870]  [<c0793231>] sys_socketcall+0x21c/0x29c
[   32.169873]  [<c0874654>] ? sysenter_exit+0xf/0x1e
[   32.169877]  [<c0603370>] ? trace_hardirqs_on_thunk+0xc/0x10
[   32.169879]  [<c087461f>] sysenter_do_call+0x12/0x38
[   32.733546] ip6_tables: (C) 2000-2006 Netfilter Core Team

complete dmesg and kernel config attached...

-- Fernando

[-- Attachment #2: config.bz2 --]
[-- Type: application/x-bzip, Size: 28847 bytes --]

[-- Attachment #3: dmesg.bz2 --]
[-- Type: application/x-bzip, Size: 20330 bytes --]

  parent reply	other threads:[~2011-07-25 22:55 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
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 [this message]
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=4E2DF459.3030509@localhost \
    --to=nando@ccrma.stanford.edu \
    --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