<html><head><meta http-equiv="Content-Type" content="text/html charset=GB2312"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Interesting. I wonder if vmware exposes an unusual. Does the crash persist if you comment out the printf()?</div><div><br></div><div>-Glenn</div><div><br></div><div><br></div><div><div><div>On Sep 13, 2013, at 12:54 AM, Lily <<a href="mailto:just4thin@gmail.com">just4thin@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi Glenn,<div><br></div><div>I've followed your guidance, and got this result:</div><div><br></div><div><div><font face="courier new, monospace">0xffffffff81234216 is in init_topology (litmus/affinity.c:28).</font></div>
<div><font face="courier new, monospace">23<span class="" style="white-space:pre"> </span>} else {</font></div><div><font face="courier new, monospace">24<span class="" style="white-space:pre"> </span>/* size = num bits in mask */</font></div>
<div><font face="courier new, monospace">25<span class="" style="white-space:pre"> </span>neigh_info[cpu].size[i] =</font></div><div><font face="courier new, monospace">26<span class="" style="white-space:pre"> </span>cpumask_weight((struct cpumask *)&neigh_info[cpu].neighbors[i]);</font></div>
<div><font face="courier new, monospace">27<span class="" style="white-space:pre"> </span>}</font></div><div><font face="courier new, monospace">28<span class="" style="white-space:pre"> </span>printk("CPU %d has %d neighbors at level %d. (mask = %lx)\n",</font></div>
<div><font face="courier new, monospace">29<span class="" style="white-space:pre"> </span>cpu, neigh_info[cpu].size[i], i,</font></div><div><font face="courier new, monospace">30<span class="" style="white-space:pre"> </span>*cpumask_bits(neigh_info[cpu].neighbors[i]));</font></div>
<div><font face="courier new, monospace">31<span class="" style="white-space:pre"> </span>}</font></div><div><font face="courier new, monospace">32</font></div><div><font face="courier new, monospace"><br></font></div><div style="">
<font face="courier new, monospace">Thx, regards.</font></div><div style=""><font face="courier new, monospace">-Bob</font></div><br>在 2013年9月12日星期四，Glenn Elliott 写道：<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi Bob,<br>
<br>
It looks like you've compiled with CONFIG_DEBUG_INFO, right? Let's do the following:<br>
<br>
> cd litmus-rt<br>
> gdb vmlinux<br>
> (gdb) l *0xffffffff81234216 // that's a lower-case L, followed by the address of the line where the crash occurred (it immediately follows "RIP" in the panic message)<br>
<br>
This should print out a line number of where the crash happened.<br>
<br>
-Glenn<br>
<br>
<br>
On Sep 12, 2013, at 5:38 AM, Lily <<a>just4thin@gmail.com</a>> wrote:<br>
<br>
> Dear litmus-rt developers:<br>
><br>
> I'm new to Litmus-rt and I am just beginning to get started, but I encountered some problems during installing the litmus-rt. I downloaded the most recently version of litmus-rt, 2013.1, and followed the installation instruction provided by wiki web. Somehow after I finished the first step, and reboot to get into the new kernel, it failed.<br>
><br>
> My approach:<br>
> #cd /usr/src<br>
> #tar jxvf linux-3.10.5.tar.bz2<br>
> #mv linux-3.10.5 litmus-rt<br>
> #cd litmus-rt<br>
> #patch -p1 <../litmus-rt-2013.1.patch<br>
> #make menuconfig ///where I chose all litmus options<br>
> #make -j8<br>
> #make modules_install install<br>
><br>
> My OS is RHEL 6.0, and I run it in vmware. I've tried to build kernel without litmus-rt, and it worked successfully. The screen snap is in the attachment, I was wondering whether this is caused by function init_topology(), so I posted my CPU information as well.<br>
><br>
> Hope for your grateful help.<br>
><br>
> Regards.<br>
> Bob Wu<br>
><br>
> <cpuinfo.txt><Other 64-bit-2013-09-12-15-45-38.png>_______________________________________________<br>
> litmus-dev mailing list<br>
> <a>litmus-dev@lists.litmus-rt.org</a><br>
> <a href="https://lists.litmus-rt.org/listinfo/litmus-dev" target="_blank">https://lists.litmus-rt.org/listinfo/litmus-dev</a><br>
<br>
<br>
_______________________________________________<br>
litmus-dev mailing list<br>
<a>litmus-dev@lists.litmus-rt.org</a><br>
<a href="https://lists.litmus-rt.org/listinfo/litmus-dev" target="_blank">https://lists.litmus-rt.org/listinfo/litmus-dev</a><br>
</blockquote></div>
</div>
_______________________________________________<br>litmus-dev mailing list<br><a href="mailto:litmus-dev@lists.litmus-rt.org">litmus-dev@lists.litmus-rt.org</a><br>https://lists.litmus-rt.org/listinfo/litmus-dev<br></blockquote></div><br></div></body></html>