From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751797Ab1GZRLZ (ORCPT ); Tue, 26 Jul 2011 13:11:25 -0400 Received: from mail-ey0-f171.google.com ([209.85.215.171]:39266 "EHLO mail-ey0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751064Ab1GZRLR (ORCPT ); Tue, 26 Jul 2011 13:11:17 -0400 Message-ID: <4E2EF532.20407@gmail.com> Date: Tue, 26 Jul 2011 19:11:14 +0200 From: Maarten Lankhorst User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110621 Fedora/3.1.11-1.fc15 Thunderbird/3.1.11 MIME-Version: 1.0 To: Darren Hart CC: Thomas Gleixner , LKML , linux-rt-users Subject: Re: [ANNOUNCE] 3.0-rt3 References: <4E2C2ED6.4040904@gmail.com> <4E2DEC1A.5070109@linux.intel.com> <4E2E57FF.7030206@linux.intel.com> <4E2EA89A.2020007@gmail.com> <4E2EF304.30601@linux.intel.com> In-Reply-To: <4E2EF304.30601@linux.intel.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/26/2011 07:01 PM, Darren Hart wrote: > > On 07/26/2011 04:44 AM, Maarten Lankhorst wrote: >> On 07/26/2011 08:00 AM, Darren Hart wrote: >>> On 07/25/2011 03:20 PM, Darren Hart wrote: >>>> On 07/24/2011 09:12 AM, Thomas Gleixner wrote: >>>>> On Sun, 24 Jul 2011, Maarten Lankhorst wrote: >>>> ... >>>> >>>>>> 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: /-1, .owner_cpu: 0 >>>>>> [ 37.456692] Pid: 1619, comm: threaded-ml Tainted: G C 3.0.0-rt3-patser+ #39 > Maarten, I'm finding fairly little out there on what threaded-ml might > be. What I do find suggests 3D visualization and real-time audio > playback. Are you working with something like this? If so, which > libraries are you using? If not, any idea what this is? threaded ml = from pulseaudio, src/pulse/thread-mainloop.c to be exact. But like I said it occurs with the functional broadcast test too, on the waker thread. >>>>>> [ 37.456693] Call Trace: >>>>>> [ 37.456697] [] spin_bug+0xa0/0xa8 >>>>>> [ 37.456699] [] do_raw_spin_lock+0xa2/0x170 >>>>>> [ 37.456702] [] ? get_parent_ip+0x11/0x50 >>>>>> [ 37.456704] [] _raw_spin_lock+0x23/0x30 >>>>>> [ 37.456706] [] rt_mutex_start_proxy_lock+0x2e/0xd0 >>>>>> [ 37.456708] [] futex_requeue+0x47a/0x850 >>>>>> [ 37.456710] [] do_futex+0xae/0xb00 > Maarten, could you provide the addr2line of the addresses from do_futex > to spin_bug ? This will help me trace the path. decodes to: linux/lib/spinlock_debug.c:72 linux/lib/spinlock_debug.c:79 linux/kernel/sched.c:4114 linux/kernel/spinlock.c:141 linux/kernel/rtmutex.c:100 linux/kernel/futex.c:1378 linux/kernel/futex.c:2662 ~Maarten