I don't know of any file system that supports hot-removal of its backing device. -Kip On Sun, 9 May 2004, Jonathan wrote: > FreeBSD 5.2-CURRENT #0: Sat May 8 17:45:59 CDT 2004 > > Hi: > > I get a kernel panic when I deliberately remove a umass storage device > that is still mounted. The machine panics after the halt command. I > recopied these messages. > > > umass0: at uhb1 port 2 (addr 2) disconnected > (pass0:umass-sim0:0:0:0): lost device > (pass0:umass-sim0:0:0:0): removing device entry > (pass0:umass-sim0:0:0:0): lost device > umass0: detached > > Fatal trap 12: page fault while in kernel mode > fault virtual address =0xb9a558c0 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc04437cb > stack pointer = 0x10:0xd6bebaa8 > frame pointer = 0x10:0xd6bebaac > code segement = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 1 (init) > trap number = 12 > panic: page fault > at line 815 in file /usr/src/sys/i386/i386/trap.c > > > > > > > On Wed, 2004-04-28 at 00:14, Jonathan wrote: > > uname: 5.2-CURRENT #0: Sun Apr 25 22:37 CDT > > i386 > > compiled using std make.conf ( only -O for optimization) > > > > > > While shutting down my FreeBSD laptop, I got this panic: > > > > panic: vinvalbuf: dirty bufs > > at line 921 in file /usr/src/sys/kern/vfs_subr.c > > > > I had just detached a USB mass storage device (umass) and then given the > > command "halt", when the panic happened. I may have forgotten to do > > umount /mnt, which may have caused the panic ? FreeBSD CURRENT has > > worked fine beside this first panic. > > _______________________________________________ > freebsd-current_at_freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" >Received on Sun May 09 2004 - 09:26:29 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:53 UTC