https://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082008-04-01T18:22:02ZDragonFlyBSD bugtrackerDragonFlyBSD - Bug #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=44442008-04-01T18:22:02Znant
<ul></ul><p>Can the memory image file be used as a core dump?</p>
<p>Cheers,<br />Nuno</p> DragonFlyBSD - Bug #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=44462008-04-02T05:50:03Zrumcic
<ul></ul><p>Hm:<br />"/home/var.vkernel/memimg.000000" is not a core dump: File format not<br />recognized" guess not? (tried it with gdb not kgdb)</p> DragonFlyBSD - Bug #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=44472008-04-02T12:43:01Znthery
<ul></ul><p>I'm afraid there is no way to capture vkernel core dumps currently.<br />Simon posted a debug-oriented wish list a while ago and, IIRC, vkernel<br />core dumps were part of it.</p> DragonFlyBSD - Bug #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=44482008-04-02T12:45:00Znthery
<ul></ul><p>I wonder how _sysref_put() can end up calling vget(). Any idea?</p> DragonFlyBSD - Bug #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=44492008-04-02T12:57:01Zdillon
<ul></ul><p>:Hm:<br />:"/home/var.vkernel/memimg.000000" is not a core dump: File format not<br />:recognized" guess not? (tried it with gdb not kgdb)</p>
<pre><code>Heh. No but you CAN gdb the live vkernel (assuming it dropped into<br /> db> it is still running).</code></pre>
<pre><code>In anycase, don't bother going that far. There's definitely a bug<br /> here. The vnode is supposed to have a VM object associated with it<br /> and clearly there must be a path where that vnode can be instantiated<br /> without one.</code></pre>
<pre><code>Can you by any chance reproduce the bug to test that this patch<br /> fixes the problem?</code></pre>
<pre><code>-Matt</code></pre>
<p>Index: ufs_inode.c
===================================================================<br />RCS file: /cvs/src/sys/vfs/ufs/ufs_inode.c,v<br />retrieving revision 1.24<br />diff <del>u -p -r1.24 ufs_inode.c<br />--</del> ufs_inode.c 2 Jan 2008 22:42:37 <del>0000 1.24<br />+<ins>+ ufs_inode.c 2 Apr 2008 05:51:41 -0000<br /><code>@ -87,6 +87,8 </code>@ if (!ufs_getinoquota(ip))<br /> (void)ufs_chkiq(ip, -1, NOCRED, FORCE);<br /> #endif<br /> /* Must have a VM object to truncate */<br /></ins> if (vp</del>>v_object == NULL)<br />+ vinitvmio(vp, 0);<br /> error = ffs_truncate(vp, (off_t)0, 0, NOCRED);<br /> ip->i_rdev = 0;<br /> mode = ip->i_mode;</p> DragonFlyBSD - Bug #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=44502008-04-02T12:58:01Zdillon
<ul></ul><p>:<br />:2008/4/1, Rumko <<a class="email" href="mailto:rumcic@gmail.com">rumcic@gmail.com</a>>:<br />:> vget(669232e8,672d4b1c,669232f8,672d4ab0,80e7e97) at 0x80e803b<br />:> _sysref_put(669232f8,672d4b5c,66964418,672d4af8,80df8a0) at 0x808260a<br />:<br />:I wonder how _sysref_put() can end up calling vget(). Any idea?</p>
<pre><code>I think that's just a backtrace snafu. The vkernrel's DDB support<br /> for backtraces is rather hacked up.</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 #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=44512008-04-02T13:53:01Zrumcic
<ul></ul><p>Matthew Dillon wrote:</p>
<p>I'll try to reproduce it, but since this is the first time I got this panic ...<br />I'll see if it can be done<br />-- <br />Regards,<br />Rumko</p> DragonFlyBSD - Bug #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=44522008-04-03T11:17:02Zdillon
<ul></ul><p>:> /* Must have a VM object to truncate */<br />:> + if (vp->v_object == NULL)<br />:> + vinitvmio(vp, 0);<br />:> error = ffs_truncate(vp, (off_t)0, 0, NOCRED);<br />:> ip->i_rdev = 0;<br />:> mode = ip->i_mode;<br />:<br />:I'll try to reproduce it, but since this is the first time I got this panic ...<br />:I'll see if it can be done<br />:-- <br />:Regards,<br />:Rumko</p>
<pre><code>Scrap that patch. It's bad. It causes more panics then it fixes.</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 #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=44532008-04-03T16:28:01Zrumcic
<ul></ul><p>Matthew Dillon wrote:</p>
<p>Ok ... I have yet to reproduce the panic (the vkernel is still building the<br />packages) so I have not applied the patch yet.<br />-- <br />Regards,<br />Rumko</p> DragonFlyBSD - Bug #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=44542008-04-04T14:10:01Zrumcic
<ul></ul><p>Rumko wrote:</p>
<p>Alrighty ... I triggered another panic (while checking out the pkgsrc tree ...<br />but it seems to me a different panic unrelated to this?</p>
<p>Checkout latest pkgsrc-current...<br />mode = 030721, inum = 64, fs =<br />panic: ffs_valloc: dup alloc<br />Trace beginning at frame 0x6565480c<br />panic(65654830,0,58583800,65c95300,656548ac) at 0x80a1777<br />panic(81ebe10,81eba88,31d1,40,585838d4) at 0x80a1777<br />ffs_valloc(65c27de8,81a4,63b08798,656548d0,65654bbc) at 0x81888fd<br />ufs_vnoperatespec(65654a60,fffffffe,65ca7c08,65654a08,81996cd) at 0x8199e28<br />ufs_vnoperatespec(65654a14,65654a3c,80efc2c,65654a14,820a370) at 0x819a11b<br />ufs_vnoperate(65654a14,820a370,5ee91fd0,2,65c27de8) at 0x81996cd<br />vop_old_create(5ee91fd0,65c27de8,65654bbc,65654a60,65654b10) at 0x80efc2c<br />vop_compat_ncreate(65654ab0,65654aa4,81996cd,65654ab0,65654ae4) at 0x80e05cd<br />vop_defaultop(65654ab0,65654ae4,80f09a3,65654ab0,820a4d0) at 0x80df3ef<br />ufs_vnoperate(65654ab0,820a4d0,5ee91fd0,6216700f,0) at 0x81996cd<br />vop_ncreate(5ee91fd0,65654c38,65c27de8,65654bbc,63b08798) at 0x80f09a3<br />vn_open(65654c38,63bc8778,20a,1a4,620c9400) at 0x80ef076<br />kern_open(65654c38,209,1b6,65654ca0,65ca7c08) at 0x80ec5ba<br />sys_open(65654ca0,6,0,0,63b2ed18) at 0x80ec78f<br />syscall2(65654d40,0,6,0,0) at 0x81bd7af<br />user_trap(65654d40,620c9400,81bd5b1,0,81bde4c) at 0x81bd982<br />go_user(65654d38,0,0,7b,0) at 0x81bdd01<br />Debugger("panic")<br />Stopped at 0x81bb3c9: movb $0,0x82a1074<br />-- <br />Regards,<br />Rumko</p> DragonFlyBSD - Bug #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=44552008-04-04T14:23:01Zdillon
<ul></ul><p>:Alrighty ... I triggered another panic (while checking out the pkgsrc tree ...<br />:but it seems to me a different panic unrelated to this?<br />:<br />:Checkout latest pkgsrc-current...<br />:mode = 030721, inum = 64, fs =<br />:panic: ffs_valloc: dup alloc<br />:Trace beginning at frame 0x6565480c</p>
<pre><code>That's a different, unrealted panic.</code></pre>
<pre><code>Did you at any time prior to the checkout fill up the filesystem?<br /> There's a bug in UFS that can cause corruption when the filesystem <br /> fills up which we haven't patched yet.</code></pre>
<pre><code>-Matt</code></pre> DragonFlyBSD - Bug #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=44562008-04-04T15:29:00Zrumcic
<ul></ul><p>Matthew Dillon wrote:</p>
<p>Er ... now that is a very good question ... I don't remember right now if I did<br />ever fill it up, but the base image which I copy (and abuse the copy) is very<br />old, so there is a possibility of that ... oh well, guess it's time to remake<br />the base image.<br />-- <br />Regards,<br />Rumko</p> DragonFlyBSD - Bug #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=45292008-05-02T06:26:36Zrumcic
<ul></ul><p>Well it's been a long time, but I have managed to get a panic with "panic:<br />getblk: vnode 0xf1fda768 has no object!" on my host machine this time.<br />The kernel.1 and vmcore.1 files are at leaf:~rumko/crash/01.05.2008</p>
<p>The backtrace:<br />#0 dumpsys () at ./machine/thread.h:83<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> 0xc0270739 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:375<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: K&R -> ANSI cleanup status (Closed)" href="https://bugs.dragonflybsd.org/issues/2">#2</a> 0xc02709fc in panic (fmt=0xc050659c "getblk: vnode %p has no object!") at<br />/usr/src/sys/kern/kern_shutdown.c:800<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: freebsds pipe-reverse test fails on dfly (Closed)" href="https://bugs.dragonflybsd.org/issues/3">#3</a> 0xc02ac5c6 in getblk (vp=0xf1fda768, loffset=-274945245184, size=16384,<br />blkflags=<value optimized out>, slptimeo=0)<br /> at /usr/src/sys/kern/vfs_bio.c:2350<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: Rework of nrelease (Closed)" href="https://bugs.dragonflybsd.org/issues/4">#4</a> 0xc03b0160 in ffs_indirtrunc (ip=0xf1389200, lbn=-16781326, dbn=-16793008,<br />lastbn=-1, level=2, countp=0xf18629c0)<br /> at /usr/src/sys/vfs/ufs/ffs_inode.c:465<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/dev cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/5">#5</a> 0xc03b0da5 in ffs_truncate (vp=0xf1fda768, length=0, flags=0, cred=0x0) at<br />/usr/src/sys/vfs/ufs/ffs_inode.c:333<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/emulation cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/6">#6</a> 0xc03bb472 in ufs_inactive (ap=0xf1862aa4) at<br />/usr/src/sys/vfs/ufs/ufs_inode.c:90<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: /sys/boot cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/7">#7</a> 0xc03bdffa in ufs_vnoperate (ap=0xf1862aa4) at<br />/usr/src/sys/vfs/ufs/ufs_vnops.c:2444<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: make upgrade broken (Closed)" href="https://bugs.dragonflybsd.org/issues/8">#8</a> 0xc02c2e56 in vop_inactive (ops=0xd3a14970, vp=0xf1fda768) at<br />/usr/src/sys/kern/vfs_vopops.c:610<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: panic with HEAD (Closed)" href="https://bugs.dragonflybsd.org/issues/9">#9</a> 0xc02badc8 in vnode_terminate (vp=0xf1fda768) at<br />/usr/src/sys/kern/vfs_lock.c:252<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: make buildworld broken (Closed)" href="https://bugs.dragonflybsd.org/issues/10">#10</a> 0xc0250670 in _sysref_put (sr=0xf1fda778) at /usr/src/sys/kern/kern_sysref.c:318<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: libstand cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/11">#11</a> 0xc02bac20 in vrele (vp=0x0) at /usr/src/sys/sys/sysref2.h:85<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: /sys/net cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/12">#12</a> 0xc02b25f0 in vop_compat_nresolve (ap=0xf1862b68) at<br />/usr/src/sys/kern/vfs_default.c:230<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Buildworld error/panic (Closed)" href="https://bugs.dragonflybsd.org/issues/13">#13</a> 0xc02b213b in vop_defaultop (ap=0xf1862b68) at<br />/usr/src/sys/kern/vfs_default.c:146<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: zombie processes waiting for a lock, smth to worry about? (Closed)" href="https://bugs.dragonflybsd.org/issues/14">#14</a> 0xc03bdffa in ufs_vnoperate (ap=0xf1862b68) at<br />/usr/src/sys/vfs/ufs/ufs_vnops.c:2444<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: savecore -z patch (Closed)" href="https://bugs.dragonflybsd.org/issues/15">#15</a> 0xc02c315b in vop_nresolve (ops=0xd3a14970, nch=0xf1862ba8, dvp=0xf2331168,<br />cred=0xe0b53318)<br /> at /usr/src/sys/kern/vfs_vopops.c:945<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: install: net/bridge/*.h: No such file or directory (Closed)" href="https://bugs.dragonflybsd.org/issues/16">#16</a> 0xc02af3be in cache_resolve (nch=0xf1862bd8, cred=0xe0b53318) at<br />/usr/src/sys/kern/vfs_cache.c:2065<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Minor typos (Closed)" href="https://bugs.dragonflybsd.org/issues/17">#17</a> 0xc02b6bc4 in nlookup (nd=0xf1862c84) at /usr/src/sys/kern/vfs_nlookup.c:397<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: extern uint64_t tsc_frequency missing (Closed)" href="https://bugs.dragonflybsd.org/issues/18">#18</a> 0xc02be82f in kern_stat (nd=0xf1862c84, st=0xf1862c1c) at<br />/usr/src/sys/kern/vfs_syscalls.c:2157<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: usched questions and a patch (Closed)" href="https://bugs.dragonflybsd.org/issues/19">#19</a> 0xc02be8d7 in sys_lstat (uap=0xf1862cf0) at<br />/usr/src/sys/kern/vfs_syscalls.c:2220<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: No detection of 8169S Gb interface (Closed)" href="https://bugs.dragonflybsd.org/issues/20">#20</a> 0xc048132d in syscall2 (frame=0xf1862d40) at<br />/usr/src/sys/platform/pc32/i386/trap.c:1348<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: /etc/network.subr list_net_interfaces() fix (Closed)" href="https://bugs.dragonflybsd.org/issues/21">#21</a> 0xc046e8b5 in Xint0x80_syscall () at<br />/usr/src/sys/platform/pc32/i386/exception.s:872<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: RealTek 8169S/8110S support. (Closed)" href="https://bugs.dragonflybsd.org/issues/22">#22</a> 0x0804e698 in ?? ()</p> DragonFlyBSD - Bug #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=71522009-08-24T18:40:23Ztuxillo
<ul></ul><p>Matt, if I recall correctly you managed to buildworld and buildkernel inside a<br />vkernel, right?</p> DragonFlyBSD - Bug #983: Panic in a vkernel: getblk: vnode 0x669232e8 has no object!https://bugs.dragonflybsd.org/issues/983?journal_id=103742011-12-18T18:54:27Zrumcic
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/10374/diff?detail_id=62">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li></ul><p>Been a long time since I was able to make a panic like this, consider resolved for now</p>