Date: Sun, 17 Jun 2001 12:12:17 +0200 From: Jens Schweikhardt <schweikh@schweikhardt.net> To: FreeBSD current <freebsd-current@freebsd.org> Subject: mdconfig/umount Fatal trap 12 Message-ID: <20010617121217.A2453@schweikhardt.net>
next in thread | raw e-mail | index | archive | help
hello, world\n with a system cvsupped June 6th I can reliably reproduce a Fatal trap 12: page fault while in kernel mode fault virtual address = 0x22 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01b67e2 stack pointer = 0x10:0xc8f7aea0 frame pointer = 0x10:0xc8f7aea8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 832 (umount) panic: from debugger panic: from debugger Uptime: 10m3s dumping to dev da2s1b, offset 352280 when I try to unmount a deleted mdconfig device. Here's the recipe: # file iso is a Freebsd 4.3 Wind River CD image made with # dd if=/dev/cd0c of=file.iso bs=2048 mdconfig -a -t vnode -f file.iso mount -t cd9660 /dev/md0 /mnt/freebsd-cd mdconfig -d -u md0 umount /dev/md0 I'm not sure if this is the right fix but what about having the mdconfig -d fail with EBUSY in case someone tries to delete a mounted md device? Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010617121217.A2453>