I upgraded my -CURRENT system (kernel and userland) not too long ago
(from 2.99.* to 3.99.3) and noticed a day or so afterwards the panic
"panic: m_copydata: m == 0, len 1" had occurred.  I decided to ignore it
unless it happened again.  Well, it happened again, today, ~1 week since
the last occurrence.

This is what I have in my dmesg:

panic: m_copydata: m == 0, len 1
syncing disks... 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 giving up

dumping to dev 16,9 offset 262015
dump device bad


rebooting...

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 3.99.3 (CHUMBY) #1: Wed Apr 20 23:30:36 EDT 2005
        paul@chumby.dlib.vt.edu:/usr/obj/sys/arch/alpha/compile/CHUMBY
AlphaServer 1000A 5/300, 300MHz, s/n 
8192 byte page size, 1 processor.
total memory = 128 MB
[[...]]


(My swap is on a RAIDframe RAID 1 device.  Is that why it is rejected as
a "bad" dump device?)

Has anyone else noticed this panic?  I guess I could try updating to a
newer -CURRENT and hope this was just a transient problem in the code
base.

Cheers,

Paul.
-- 
e-mail: paul@gromit.dlib.vt.edu

"Without music to decorate it, time is just a bunch of boring production
 deadlines or dates by which bills must be paid."
        --- Frank Vincent Zappa