From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kacur Subject: [BUG REPORT] MAX_STACK_TRACE_ENTRIES too low! in v2.6.33-rt6 Date: Fri, 12 Mar 2010 14:09:31 +0100 Message-ID: <520f0cf11003120509j1dd6f2cicb1d87b0a16d31dd@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: RT , LKML To: Thomas Gleixner Return-path: Received: from mail-ew0-f216.google.com ([209.85.219.216]:55341 "EHLO mail-ew0-f216.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752223Ab0CLNJd (ORCPT ); Fri, 12 Mar 2010 08:09:33 -0500 Sender: linux-rt-users-owner@vger.kernel.org List-ID: This is just fyi: Note, I do have a large number of debug options turned on, that could influence this. This occurred on a Lenovo T500 Laptop, and x86_64 v2.6.33-rt6 BUG: MAX_STACK_TRACE_ENTRIES too low! turning off the locking correctness validator. Pid: 3334, comm: pulseaudio Not tainted 2.6.33-rt6 #1 Call Trace: [] save_trace+0xab/0xb3 [] add_lock_to_list+0x82/0xc2 [] ? rt_mutex_adjust_prio+0x1f/0x3e [] __lock_acquire+0xbdc/0xda3 [] ? finish_task_switch+0x77/0xf4 [] ? finish_task_switch+0x0/0xf4 [] lock_acquire+0xd8/0xf5 [] ? rt_mutex_adjust_prio+0x1f/0x3e [] _raw_spin_lock_irqsave+0x47/0x7f [] ? rt_mutex_adjust_prio+0x1f/0x3e [] rt_mutex_adjust_prio+0x1f/0x3e [] rt_mutex_slowunlock+0x6d/0x76 [] rt_mutex_unlock+0x9/0xb [] rt_up_read+0x3b/0x40 [] ? exit_mm+0xd4/0x156 [] exit_mm+0xe7/0x156 [] ? audit_free_context+0xa7/0xd0 [] do_exit+0x1fe/0x784 [] ? trace_hardirqs_on_caller+0x113/0x13e [] ? audit_syscall_entry+0x114/0x140 [] complete_and_exit+0x0/0x1f [] system_call_fastpath+0x16/0x1b