Re: [ANNOUNCE] 3.0-rt3

[Maarten Lankhorst]

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: <none>/-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]  [<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
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/