https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082010-09-13T03:28:16ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=89092010-09-13T03:28:16Zdillon
<ul></ul><p>:The exact message is:<br />:<br />:panic: Bad link elm 0xfffffffe5655be58 prev->next != elm<br />:<br />:It seems launching a browser and opening a bunch of tabs at once is enough<br />:to cause this panic.<br />:<br />:I have put a bunch of core and kernel files at<br />:http://www.wolfpond.org/crash.dfly/<br />:<br />:-- <br />:Francois Tigeot</p>
<pre><code>Your kernel is more recent then my fix as far as I can tell but I was<br /> sure I fixed that one. Try doing a full recompile of the kernel.</code></pre>
<pre><code>-Matt<br /> Matthew Dillon <br /> &lt;<a class="email" href="mailto:dillon@backplane.com">dillon@backplane.com</a>&gt;</code></pre> DragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=89102010-09-13T03:56:17Zdillon
<ul></ul><p>I went through the code in kern.26 and it was definitely up-to-date.</p>
<pre><code>I think this crash may be related to one Jan Lentfer is getting where<br /> a socket is getting ripped out from under some code that it shouldn't<br /> be getting ripped out from under.</code></pre>
<pre><code>-Matt<br /> Matthew Dillon <br /> &lt;<a class="email" href="mailto:dillon@backplane.com">dillon@backplane.com</a>&gt;</code></pre> DragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=89122010-09-13T10:09:37Zftigeot
<ul></ul><p>On Sun, Sep 12, 2010 at 01:54:47PM -0700, Matthew Dillon wrote:</p>
<blockquote>
<p>I went through the code in kern.26 and it was definitely up-to-date.</p>
<p>I think this crash may be related to one Jan Lentfer is getting where<br />a socket is getting ripped out from under some code that it shouldn't<br />be getting ripped out from under.</p>
</blockquote>
<p>I have upgraded anyway; hopefully the new socket assertions will help in<br />tracking this down.</p> DragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=89172010-09-13T13:27:47Zdillon
<ul></ul><p>:On Sun, Sep 12, 2010 at 01:54:47PM <del>0700, Matthew Dillon wrote:<br />:> I went through the code in kern.26 and it was definitely up-to-date.<br />:> <br />:> I think this crash may be related to one Jan Lentfer is getting where<br />:> a socket is getting ripped out from under some code that it shouldn't<br />:> be getting ripped out from under.<br />:<br />:I have upgraded anyway; hopefully the new socket assertions will help in<br />:tracking this down.<br />:<br />:-</del> <br />:Francois Tigeot</p>
<pre><code>I believe these should now be fixed for real. There was an additional<br /> issue with the list the inpcb was placed on that caused another MP<br /> race.</code></pre>
<pre><code>-Matt<br /> Matthew Dillon <br /> &lt;<a class="email" href="mailto:dillon@backplane.com">dillon@backplane.com</a>&gt;</code></pre> DragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=89182010-09-13T14:27:21Zftigeot
<ul></ul><p>On Sun, Sep 12, 2010 at 11:26:17PM -0700, Matthew Dillon wrote:</p>
<blockquote>
<p>I believe these should now be fixed for real. There was an additional<br />issue with the list the inpcb was placed on that caused another MP<br />race.</p>
</blockquote>
<p>Yep, this one can be closed.<br />I couldn't reproduce the crash with the last kernel.</p> DragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=89192010-09-13T14:37:19Zdillon
<ul></ul><p>:Yep, this one can be closed.<br />:I couldn't reproduce the crash with the last kernel.<br />:<br />:-- <br />:Francois Tigeot</p>
<pre><code>Ok, even more fixes committed, I missed two list corruption cases but<br /> I am definitely on the right track now.</code></pre>
<pre><code>-Matt<br /> Matthew Dillon <br /> &lt;<a class="email" href="mailto:dillon@backplane.com">dillon@backplane.com</a>&gt;</code></pre> DragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=89242010-09-14T07:40:52Zpavalos
<ul></ul><p>Original submitter says it can't be reproduced in recent kernel.</p> DragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=89282010-09-15T04:02:23Zthomas.nikolajsen
<ul></ul><p>I still get this panic, with HEAD from today: on SMP kernel<br />running a few buildkernels with /usr/src & /usr/obj NFS mounted.</p>
<p>Should I upload crash dump?</p>
<pre><code>-thomas</code></pre> DragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=89292010-09-15T11:24:49Zdillon
<ul></ul><p>:Thomas Nikolajsen <<a class="email" href="mailto:thomas.nikolajsen@mail.dk">thomas.nikolajsen@mail.dk</a>> added the comment:<br />:<br />:I still get this panic, with HEAD from today: on SMP kernel<br />:running a few buildkernels with /usr/src & /usr/obj NFS mounted.<br />:<br />:Should I upload crash dump?<br />:<br />: -thomas</p>
<pre><code>Yes, we're still trying to find this one.</code></pre>
<pre><code>-Matt<br /> Matthew Dillon <br /> &lt;<a class="email" href="mailto:dillon@backplane.com">dillon@backplane.com</a>&gt;</code></pre> DragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=89342010-09-16T12:10:08Zpeter
<ul></ul><p>On Tue, Sep 14, 2010 at 09:23:18PM -0700, Matthew Dillon wrote:</p>
<blockquote>
<p>:Thomas Nikolajsen <<a class="email" href="mailto:thomas.nikolajsen@mail.dk">thomas.nikolajsen@mail.dk</a>> added the comment:<br />:<br />:I still get this panic, with HEAD from today: on SMP kernel<br />:running a few buildkernels with /usr/src & /usr/obj NFS mounted.<br />:<br />:Should I upload crash dump?<br />:<br />: -thomas</p>
<p>Yes, we're still trying to find this one.</p>
</blockquote>
<p>I got one of these the past few days, and it looked like that was<br />actually a secondary panic. Can you verify that's the actual panic<br />message (the first one the gets displayed on the console)?</p>
<p>--Peter</p> DragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=89412010-09-16T17:20:53Zthomas.nikolajsen
<ul></ul><p>crash dump uploader to ~thomas/crash/19 on leaf.</p>
<p>I do think that subj was on console; but don't remember for sure,<br />please look into crash dump to decide primary reason.</p>
<p>I have a few more crash dumps w/ same panic string.</p>
<pre><code>-thomas</code></pre> DragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=89422010-09-17T00:07:13Zdillon
<ul></ul><p>:Thomas Nikolajsen <<a class="email" href="mailto:thomas.nikolajsen@mail.dk">thomas.nikolajsen@mail.dk</a>> added the comment:<br />:<br />:crash dump uploader to ~thomas/crash/19 on leaf.<br />:<br />:I do think that subj was on console; but don't remember for sure,<br />:please look into crash dump to decide primary reason.<br />:<br />:I have a few more crash dumps w/ same panic string.<br />:<br />: -thomas</p>
<pre><code>Thanks Thomas. It looks like I forgot to wrap the nfs_write()<br /> function with a token. I've pushed the fixes. Please update<br /> and tell us if it fixed the problem!</code></pre>
<pre><code>-Matt<br /> Matthew Dillon <br /> &lt;<a class="email" href="mailto:dillon@backplane.com">dillon@backplane.com</a>&gt;</code></pre> DragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=97952011-04-06T01:16:28Zdillon
<ul></ul><p>See issue 2037, possible fix committed.</p> DragonFlyBSD - Bug #1835: Panic: Bad link elm prev->next != elmhttps://bugs.dragonflybsd.org/issues/1835?journal_id=129732016-09-08T09:06:00Zftigeot
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/12973/diff?detail_id=2753">diff</a>)</li><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li></ul><p>Confirmation timeout, closed.</p>