From: Darren Hart <dvhart@linux.intel.com>
To: Maarten Lankhorst <m.b.lankhorst@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0-rt3
Date: Tue, 26 Jul 2011 10:01:56 -0700 [thread overview]
Message-ID: <4E2EF304.30601@linux.intel.com> (raw)
In-Reply-To: <4E2EA89A.2020007@gmail.com>
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?
>>>>> [ 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.
Thanks,
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-07-26 17:01 UTC|newest]
Thread overview: 35+ 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 [this message]
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
2011-07-26 9:13 ` Uwe Kleine-König
2011-07-26 23:52 ` Fernando Lopez-Lezcano
2011-07-26 23:52 ` Fernando Lopez-Lezcano
2011-07-26 23:57 ` 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 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: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 16:52 ` Sebastian Ohl
2011-07-27 21:49 ` Thomas Gleixner
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=4E2EF304.30601@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=m.b.lankhorst@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.