<div dir="ltr"><div><div>Hello <br><br></div>you can try to print running task backtrack information in kernel/lockdep.c<br><br></div>Regards<br>Sanjeev Sharma <br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 27, 2015 at 11:27 AM, manty kuma <span dir="ltr"><<a href="mailto:mantykuma@gmail.com" target="_blank">mantykuma@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi All,<br><br></div>Currently I am looking into an issue which is holding the printk lock(logbuf_lock)<br><div><div><br>logbuf_lock = {<br> raw_lock = {<br> owner = 0, <br> next = 4<br> }<br>}<br><br>I read about ticketing spinlocks to understand the above output. I understood that 4 cpu's are waiting for the lock while someone already has it.<br><br></div><div>I would like to know who has it? Is there a way I can know which process is acquiring a given spinlock? Is the information not stored in it?<br><br></div><div>I am using crash tool to analyse the dump<br></div><div><br></div><div>Regards,<br>Manty<br></div></div></div>
<br>_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
<br></blockquote></div><br></div>