https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082006-07-20T05:43:02ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=9412006-07-20T05:43:02Zdillon
<ul></ul><p>:I updated world/kernel this morning and all seemed good until<br />:I exited from my gnome X session. Here is what kgdb says:<br />:<br />:(kgdb) bt<br />:#0 lwkt_switch () at thread2.h:177<br />:#1 0xc02e2384 in trap (frame=Error accessing memory address 0x8: Bad address.<br />:) at /usr/src/sys/i386/i386/trap.c:349<br />:Previous frame inner to this frame (corrupt stack?)</p>
<pre><code>Hmm. Upload the core, I might be able to salvage it.</code></pre>
<pre><code>Is it repeatable ?</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 #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=9422006-07-20T08:05:07Zwa1ter
<ul></ul><p>Matthew Dillon wrote:</p>
<blockquote>
<p>:I updated world/kernel this morning and all seemed good until<br />:I exited from my gnome X session. Here is what kgdb says:<br />:<br />:(kgdb) bt<br />:#0 lwkt_switch () at thread2.h:177<br />:#1 0xc02e2384 in trap (frame=Error accessing memory address 0x8: Bad address.<br />:) at /usr/src/sys/i386/i386/trap.c:349<br />:Previous frame inner to this frame (corrupt stack?)</p>
<p>Hmm. Upload the core, I might be able to salvage it.</p>
</blockquote>
<p>It's in my crash directory on leaf.</p>
<blockquote>
<p>Is it repeatable ?</p>
</blockquote>
<p>Definitely, but not immediately after a reboot -- I need to mess<br />around for awhile in an X session, and then exit from X.</p> DragonFlyBSD - Bug #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=9442006-07-20T21:30:02Zschlesinger
<ul></ul><p>Am Donnerstag, 20. Juli 2006 00:08 schrieb walt:</p>
<blockquote>
<p>I updated world/kernel this morning and all seemed good until<br />I exited from my gnome X session. Here is what kgdb says:</p>
<p>(kgdb) bt<br />#0 lwkt_switch () at thread2.h:177<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> 0xc02e2384 in trap (frame=Error accessing memory address 0x8: Bad<br />address. ) at /usr/src/sys/i386/i386/trap.c:349<br />Previous frame inner to this frame (corrupt stack?)</p>
</blockquote>
<p>I've updated the kernel yesterday, too, and my machine rebooted while working <br />in a KDE session. Unfortunately, I do not have more informations. Maybe it's <br />the same as walt's problem.</p>
<p>Thomas</p> DragonFlyBSD - Bug #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=9452006-07-20T22:34:02Zdillon
<ul></ul><p>:It's in my crash directory on leaf.<br />:<br />:> Is it repeatable ?<br />:<br />:Definitely, but not immediately after a reboot -- I need to mess<br />:around for awhile in an X session, and then exit from X.</p>
<pre><code>I need the kernel binary as well.</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 #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=9512006-07-21T00:29:03Zwa1ter
<ul></ul><p>On Thu, 20 Jul 2006, Matthew Dillon wrote:</p>
<blockquote>
<p>:It's in my crash directory on leaf.<br />:<br />:> Is it repeatable ?<br />:<br />:Definitely, but not immediately after a reboot -- I need to mess<br />:around for awhile in an X session, and then exit from X.</p>
<p>I need the kernel binary as well.</p>
</blockquote>
<p>Done. I already deleted /var/crash/* so I sent /kernel instead.</p> DragonFlyBSD - Bug #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=9542006-07-21T03:23:02Zdillon
<ul></ul><p>:..<br />:> :<br />:> :Definitely, but not immediately after a reboot -- I need to mess<br />:> :around for awhile in an X session, and then exit from X.<br />:><br />:> I need the kernel binary as well.<br />:<br />:Done. I already deleted /var/crash/* so I sent /kernel instead.</p>
<pre><code>Fixed. My VOP vector cleanup indirected through a mount point without<br /> checking to see if the vnode was dead or not.</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 #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=9552006-07-21T03:26:02Zschlesinger
<ul></ul><p>Am Donnerstag, 20. Juli 2006 16:24 schrieb Thomas Schlesinger:</p>
<blockquote>
<p>Am Donnerstag, 20. Juli 2006 00:08 schrieb walt:</p>
<blockquote>
<p>I updated world/kernel this morning and all seemed good until<br />I exited from my gnome X session. Here is what kgdb says:</p>
<p>(kgdb) bt<br />#0 lwkt_switch () at thread2.h:177<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> 0xc02e2384 in trap (frame=Error accessing memory address 0x8: Bad<br />address. ) at /usr/src/sys/i386/i386/trap.c:349<br />Previous frame inner to this frame (corrupt stack?)</p>
</blockquote>
<p>I've updated the kernel yesterday, too, and my machine rebooted while<br />working in a KDE session. Unfortunately, I do not have more informations.<br />Maybe it's the same as walt's problem.</p>
<p>Thomas</p>
</blockquote>
<p>I've had two more to sudden reboots, one after >5hrs of KDE usage and one <br />after a few minutes.</p>
<p>Thomas</p> DragonFlyBSD - Bug #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=9562006-07-21T06:52:03Zdillon
<ul></ul><p>:I've had two more to sudden reboots, one after >5hrs of KDE usage and one <br />:after a few minutes.<br />:<br />:Thomas</p>
<pre><code>Try HEAD as of today. I committed a fix a little earlier in the day.</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 #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=13802006-10-02T21:06:19Zcorecode
<ul></ul><p>Is this fixed?</p> DragonFlyBSD - Bug #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=13852006-10-02T22:38:01Zwa1ter
<ul></ul><p>Simon 'corecode' Schubert wrote:</p>
<blockquote>
<p>Simon 'corecode' Schubert <<a class="email" href="mailto:corecode@fs.ei.tum.de">corecode@fs.ei.tum.de</a>> added the comment:</p>
<p>Is this fixed?</p>
<p>_<em><i></em></i>__<em>_</em>___________________________________________<br />DragonFly issue tracker <<a class="email" href="mailto:issues@chlamydia.fs.ei.tum.de">issues@chlamydia.fs.ei.tum.de</a>><br /><<a class="external" href="http://bugs.dragonflybsd.org/issue251">http://bugs.dragonflybsd.org/issue251</a>><br />_<em><i></em></i>__<em>_</em>___________________________________________</p>
</blockquote>
<p>Yes. I should mention that I posted a different bug with<br />the same title on 9-23-2006 which is not yet fixed.</p> DragonFlyBSD - Bug #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=14172006-10-05T01:00:01Zdillon
<ul></ul><p>:Yes. I should mention that I posted a different bug with<br />:the same title on 9-23-2006 which is not yet fixed.</p>
<pre><code>I'll get the second one fixed right now. I see your core on leaf.</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 #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=14182006-10-05T01:08:00Zdillon
<ul></ul><p>It crashed on a NULL pointer indirection trying to mmap() ucanner0.</p>
<pre><code>Do you have a USB scanner connected? I can do a NULL check easily<br /> enough but it should not have been able to open a descriptor in the<br /> first place if there was no scanner. Or, if there was a scanner, <br /> maybe it got unplugged at some point before the mmap (though that<br /> shouldn't have NULLed out the field either).</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 #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=14192006-10-05T01:25:01Zdillon
<ul></ul><p>I think the descriptor might have gotten revoked with revoke(). Since<br /> it is a VCHR device, that would have succeeded. But mmap() doesn't<br /> have the correct check for a revoked device descriptor so I will go<br /> ahead and add the check.</p>
<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 #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=14222006-10-05T06:05:01Zwa1ter
<ul></ul><p>Yes, there is a USB scanner plugged in, and I never unplugged it.</p>
<p>What is a VCHR device?</p> DragonFlyBSD - Bug #251: Panic on -currenthttps://bugs.dragonflybsd.org/issues/251?journal_id=14232006-10-05T06:09:00Zdillon
<ul></ul><p>:Yes, there is a USB scanner plugged in, and I never unplugged it.<br />:<br />:What is a VCHR device?</p>
<pre><code>Its just the #define used to identify a CHR device, which is <br /> basically everything in /dev.</code></pre>
<pre><code>In anycase, the latest HEAD should fix the issue. I'm guessing<br /> that one of those GUI programs is revoke()ing access to the<br /> device while another one has an open descriptor to it and then<br /> tries to mmap() it.</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>