panic: cleaned vnode isn't

Francois Tigeot ftigeot at wolfpond.org
Thu Feb 4 13:01:52 PST 2010


On Sat, Jan 30, 2010 at 10:21:23AM -0800, Matthew Dillon wrote:
> :Even though I entered "call dumpsys" on the db prompt, there was no crash dump
> :after the next boot.
> 
>     If you saw it dump then you should be able to recover the crash dump
>     by doing a manual savecore as root.  If you haven't used any swap yet
>     that might still work.
> 
>     Definitely keep a watch on it.  I definitely want to try to get a dump
>     of it if it occurs again.

I've got a dump.
The DragonFly version has been updated. It is now v2.5.1.676.gf2b2e-DEVELOPMENT.

You can get the files from here: http://www.wolfpond.org/crash.dfly/

For what it's worth, savecore(8) was trying to read /kernel and exited before
saving the dump:

  $ savecore -k -v
  savecore: reboot after panic: cleaned vnode isn't
  savecore: /kernel: No such file or directory
  savecore: writing kernel to kern.0
  savecore: /kernel: Bad file descriptor
  savecore: WARNING: kernel may be incomplete

I had to create a symbolic link from /boot/kernel to /kernel to make it happy.

-- 
Francois Tigeot





More information about the Bugs mailing list