https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082012-02-03T08:30:52ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #2298: computer reboots for no apparent reasonhttps://bugs.dragonflybsd.org/issues/2298?journal_id=105932012-02-03T08:30:52Zahuete.devel
<ul></ul><p>Hi Pierre,</p>
<p>If it reboots maybe there is something in dmesg, can you please upload <br />the output of 'dmesg -a' somewhere?</p>
<p>Thanks,<br />Antonio Huete</p>
<blockquote>
<p>Issue <a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: computer reboots for no apparent reason (Closed)" href="https://bugs.dragonflybsd.org/issues/2298">#2298</a> has been reported by Pierre Abbat.</p>
<p>----------------------------------------<br />Bug <a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: computer reboots for no apparent reason (Closed)" href="https://bugs.dragonflybsd.org/issues/2298">#2298</a>: computer reboots for no apparent reason<br /><a class="external" href="http://bugs.dragonflybsd.org/issues/2298">http://bugs.dragonflybsd.org/issues/2298</a></p>
<p>Author: Pierre Abbat<br />Status: New<br />Priority: High<br />Assignee:<br />Category:<br />Target version:</p>
<p>This has happened twice apparently during the nightly hammer run, but also happens at other times. The computer reboots, without dumping a kernel core, so I have no way to tell what causes it. It happens at least once every two days and started recently. I'm running v3.1.0.93.g7ca562-DEVELOPMENT.</p>
</blockquote> DragonFlyBSD - Bug #2298: computer reboots for no apparent reasonhttps://bugs.dragonflybsd.org/issues/2298?journal_id=105942012-02-03T09:15:13Zphma
<ul><li><strong>File</strong> <a href="/attachments/905">dmesg.txt</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/905/dmesg.txt">dmesg.txt</a> added</li></ul><p>Here's the output of dmesg -a. I doubt it has anything useful, as the computer rebooted when I was asleep, waited for the password, continued booting, and failed to start X, so I had to reboot it again.</p> DragonFlyBSD - Bug #2298: computer reboots for no apparent reasonhttps://bugs.dragonflybsd.org/issues/2298?journal_id=106002012-02-04T03:27:25Zrobgar
<ul></ul><p>turn off cstates in bios, and let me know what happens.</p> DragonFlyBSD - Bug #2298: computer reboots for no apparent reasonhttps://bugs.dragonflybsd.org/issues/2298?journal_id=106012012-02-05T03:47:29Zphma
<ul><li><strong>File</strong> <a href="/attachments/907">periodic.1yzLDY4pdN</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/907/periodic.1yzLDY4pdN">periodic.1yzLDY4pdN</a> added</li><li><strong>File</strong> <a href="/attachments/908">periodic.XTA5spE1qs</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/908/periodic.XTA5spE1qs">periodic.XTA5spE1qs</a> added</li><li><strong>File</strong> <a href="/attachments/909">periodic.zyJHMxiIjA</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/909/periodic.zyJHMxiIjA">periodic.zyJHMxiIjA</a> added</li></ul><p>Here are three partially written periodic files. Each one shows that hammer got to the reblock phase of maintaning a filesystem, but not the recopy phase. None of them got to /crypt0, which is a pfs in /crypt/.</p>
<p>Also, typing "mount" to see what's mounted triggers either the kernel debugger or a reboot.</p> DragonFlyBSD - Bug #2298: computer reboots for no apparent reasonhttps://bugs.dragonflybsd.org/issues/2298?journal_id=106022012-02-05T05:24:17Zphma
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>I got a dump! I switched to the text console a few minutes before the periodic job was scheduled to start. A few minutes later, I got the kernel debugger. I called dumpsys and rebooted. It said "LK_RELEASE: no lock held." I'll pass it to Matt as soon as I can get a hold of him.</p> DragonFlyBSD - Bug #2298: computer reboots for no apparent reasonhttps://bugs.dragonflybsd.org/issues/2298?journal_id=106032012-02-05T07:02:21Zvsrinivasvsrinivas@ops101.org
<ul></ul><p>Could you post the backtrace from core.txt or from a kgdb session on the kernel dump? That'd be pretty useful to tracking down the errant LK_RELEASE.</p>
<p>Thanks!</p> DragonFlyBSD - Bug #2298: computer reboots for no apparent reasonhttps://bugs.dragonflybsd.org/issues/2298?journal_id=106042012-02-05T08:32:51Zvsrinivasvsrinivas@ops101.org
<ul></ul><p>Okay; the backtrace here:</p>
<p>panic: lockmgr: LK_RELEASE: no lock held<br />cpuid = 1<br />Trace beginning at frame 0xd35e6a44<br />panic(ffffffff,1,c06d3d58,d35e6a78,cc99f560) at panic+0x19e 0xc03839b3 <br />panic(c06d3d58,ccb86be0,d35e6af0,ccb86e04,d35e6a9c) at panic+0x19e 0xc03839b3 <br />lockmgr(d9f18eb0,6,d35e6ab8,c03ec45f,d9f18dd8) at lockmgr+0x4d0 0xc037550a <br />vn_unlock(d9f18dd8,ccb86be0,d35e6b24,c03e6d80,d9f18dd8) at vn_unlock+0x1e 0xc03f81cd <br />vput(d9f18dd8,d9f18dd8,c03d7fd1,c304d598,c2e881d8) at vput+0x12 0xc03ec45f <br />nlookup(d35e6c70,c03e73b6,ce173f68,d35e6c78,d08a02e0) at nlookup+0x5fa 0xc03e6d80 <br />kern_statfs(d35e6c70,d35e6b70,0,1,8c) at kern_statfs+0x29 0xc03f1bac <br />sys_statfs(d35e6cf0,d35e6d00,8,0,0) at sys_statfs+0x52 0xc03f1cf4 <br />syscall2(d35e6d40) at syscall2+0x270 0xc065e28c <br />Xint0x80_syscall() at Xint0x80_syscall+0x36 0xc062d2d6 <br />Debugger("panic")<br />;</p>
<p>We were finding an unlocked vnode of VT_PROCFS; it turned out to be the root vnode from linprocfs.</p>
<p>linprocfs_allocvp contained a vx_unlock() of the vnode it had just allocated in the new-vnode case; this should be removed. (linprocfs_subr.c:223); it should be returned a locked vnode here. If not, the root vnode was not locked when we were in the namecache.</p>
<p>linprocfs also should use a vhold_interlock() around its vget() loop, and perhaps shouldn't synchronize with the pfs_token. It is likely still racy; probably the same fixes done to procfs this release cycle should be applied to it?</p> DragonFlyBSD - Bug #2298: computer reboots for no apparent reasonhttps://bugs.dragonflybsd.org/issues/2298?journal_id=106092012-02-07T02:17:27Zvsrinivasvsrinivas@ops101.org
<ul></ul><p>Any update on this?</p> DragonFlyBSD - Bug #2298: computer reboots for no apparent reasonhttps://bugs.dragonflybsd.org/issues/2298?journal_id=106102012-02-07T22:20:08Zphma
<ul></ul><p>I had forgotten to leave linprocfs mounted while hammer runs. I have verified that typing "mount" when linprocfs is mounted no longer causes a problem. It is mounted now; I'll let you know what happens tonight.</p>
<p>I have, since the fix, seen the computer reboot for no apparent reason when I tried to log on to an X session as another user. Any idea why?</p> DragonFlyBSD - Bug #2298: computer reboots for no apparent reasonhttps://bugs.dragonflybsd.org/issues/2298?journal_id=106132012-02-08T19:09:47Zphma
<ul></ul><p>The computer ran its periodic and stayed up all night.</p> DragonFlyBSD - Bug #2298: computer reboots for no apparent reasonhttps://bugs.dragonflybsd.org/issues/2298?journal_id=106312012-02-16T10:19:44Zherrgard
<ul></ul><p>Can this be closed?</p> DragonFlyBSD - Bug #2298: computer reboots for no apparent reasonhttps://bugs.dragonflybsd.org/issues/2298?journal_id=106382012-02-16T17:51:51Zphma
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li></ul><p>Yes.</p>