Ah! I think I brought debugging to a whole new level here, including
developer interaction in the bissection. ;)

Thanks for the reports, they have been very useful to re-enable LTTng
for -rt kernels,

Mathieu

* [email protected] ([email protected]) wrote:
> Thanks Mathieu.  This was my fault .. I couldn't apply your patch
> (kept getting failures on hunks 2-8 for some reason) so I hand patched
> the file and in doing so, transposed a rcu unlock with an rcu lock
> (just as you suspected). So, after correcting that, all is well and
> I'm able to perform tracing under 2.6.33.2 RT.
> 
> Thanks Much!
> 
> JP
> 
> 
> -----Original Message-----
> From: Mathieu Desnoyers [mailto:[email protected]]
> Sent: Thu 5/13/2010 2:23 PM
> To: John P. Paul
> Cc: [email protected]; [email protected]; 
> [email protected]
> Subject: Re: [ltt-dev] lttctl locks up with RT Linux
>  
> Please double-check that you applied the last patch correctly. I tried
> building a lttng-enabled -rt tree here (x86 64 box), and it works (I can
> start/stop tracing and see the trace in lttv).
> 
> Note that I simply discarded the conflicting instrumentation patches for
> this quick test.
> 
> I'm pretty sure an error could have been inserted in async_wakeup()
> within ltt-tracer.c. Can you paste the code you have ?
> 
> Unbalanced rcu read lock/unlock could be causing this.
> 
> Thanks,
> 
> Mathieu
> 
> * [email protected] ([email protected]) wrote:
> > Turning off CONFIG_RCU_CPU_STALL_DETECTOR does not solve the issue with 
> > starting up "lttctl -C" ... that call never returns. I'm no longer getting 
> > the stack dumps in /var/log/messages and I still have to hard reboot the 
> > system as soft reboot doesn't work.
> > 
> > JP
> 
> --
> This is an e-mail from General Dynamics Robotic Systems. It is for the 
> intended recipient only and may contain confidential and privileged 
> information. No one else may read, print, store, copy, forward or act in 
> reliance on it or its attachments. If you are not the intended recipient, 
> please return this message to the sender and delete the message and any 
> attachments from your computer. Your cooperation is appreciated.
> 
> 
> _______________________________________________
> ltt-dev mailing list
> [email protected]
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> 

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com

_______________________________________________
ltt-dev mailing list
[email protected]
http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev

Reply via email to