msdosfs/vn trouble, doscmd nicety, fd trouble
Okay, I've got three separate problems today:
Doscmd is really only useable with X, and running doscmd -bx with a local X
server generates tons of trap 25 with interrupts disabled. I don't recall
this being the case many moons ago...
When I mount a floppy image (msdos, using the vn device), I soon get:
panic: zone: entry not free
syncing disks... 152 47 44 38 31 24 17 1 done
dumping to dev 30001, offset 73728
dump 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39
38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13
12 11 10 9 8 7 6 5 4 3 2 1
---
#0 boot (howto=256) at ../../kern/kern_shutdown.c:287
287 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=256) at ../../kern/kern_shutdown.c:287
#1 0xf0136fed in panic (fmt=0xf0213774 zone: entry not free)
at ../../kern/kern_shutdown.c:448
#2 0xf01afed3 in zerror (error=1) at ../../vm/vm_zone.c:455
#3 0xf015a650 in namei (ndp=0xf78f9f08) at ../../vm/vm_zone.h:91
#4 0xf0161238 in rename (p=0xf73731e0, uap=0xf78f9f84)
at ../../kern/vfs_syscalls.c:2461
#5 0xf01d9a2b in syscall (frame={tf_es = 47, tf_ds = 47, tf_edi = 134828010,
tf_esi = 134934656, tf_ebp = -272657172, tf_isp = -141582380,
tf_ebx = 134931436, tf_edx = -272640240, tf_ecx = 14, tf_eax = 128,
tf_trapno = 7, tf_err = 2, tf_eip = 672138692, tf_cs = 31,
tf_eflags = 582, tf_esp = -272657192, tf_ss = 47})
at ../../i386/i386/trap.c:1100
#6 0xf01cc4fc in Xint0x80_syscall ()
#7 0x8050ec1 in ?? ()
#8 0x8050703 in ?? ()
#9 0x80516cc in ?? ()
#10 0x8052ae0 in ?? ()
#11 0x8052b90 in ?? ()
#12 0x804e43d in ?? ()
#13 0x8068ebc in ?? ()
#14 0x804a491 in ?? ()
(kgdb)
(kgdb) frame 3
#3 0xf015a650 in namei (ndp=0xf78f9f08) at ../../vm/vm_zone.h:91
91 zerror(ZONE_ERROR_NOTFREE);
(kgdb) print *ndp
$1 = {ni_dirp = 0x80af080 .new.GraphBuil, ni_segflg = UIO_USERSPACE,
ni_startdir = 0xf78f9f30, ni_rootdir = 0xf012e469, ni_vp = 0xf05a0e00,
ni_dvp = 0xf73731e0, ni_pathlen = 4147589600,
ni_next = 0x5e9 Address 0x5e9 out of bounds, ni_loopcnt = 0, ni_cnd = {
cn_nameiop = 2, cn_flags = 4112, cn_proc = 0xf73731e0,
cn_cred = 0xf133c200, cn_pnbuf = 0xf73731e0 ?\022\221?,
cn_nameptr = 0x8000 Address 0x8000 out of bounds,
cn_namelen = 0, cn_hash = 134828010, cn_consume = -266186924}}
I'll try do some more testing on this... I really don't know if it's a problem
with msdosfs or vn. It will only show p (like this) with INVARIANTS on.
I also notice I can't seem to use my flopy drive anymore. The BIOS and BTX
can both use it, the kernel:
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
fd0: 1.44MB 3.5in
and I can hear the drive click-whir-buzz like normal, but if I try to use
the drive ({,r}fd0, etc), all I get is
fd0: recal failed ST0 70abnrml,seek_cmplt,equ_chck cyl 0
fd0: recal failed ST0 70abnrml,seek_cmplt,equ_chck cyl 0
fd0: recal failed ST0 70abnrml,seek_cmplt,equ_chck cyl 0
fd0: recal failed ST0 78abnrml,seek_cmplt,equ_chck,drive_notrdy cyl 0
fd0c: hard error reading fsbn 0 of 0-3 (No status)
With this, I'm wondering if everyone's floppy drives work fine and if their
drives work fine on an AcerLabs socket 7 motherboard. If so, maybe I can
scrounge up a different floppy drive and try it out, but it really seems
to not be a hardware problem.
Thanks in advance.
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org _ __ ___ | _ ) __| \
http://www.freebsd.org/ _ __ ___ | _ \__ \ |) |
FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: msdosfs/vn trouble, doscmd nicety, fd trouble
Doscmd is really only useable with X, and running doscmd -bx with a local X server generates tons of trap 25 with interrupts disabled. I don't recall this being the case many moons ago... Yeah, me too. I was told this is a bug in doscmd and the owner needs to fix it. I don't understand the inner parts of DOS VM86 as it relates to the x86 architecture or I'd take a crack at it. Instead, I hacked as follows to silence this specific error. This is not a good thing to do in general, but it lets me use doscmd to program EPROMs. I just use cvs instead of cvsup to update my working source tree so I don't lose this (and other) local mods. Don't know about the panic though - I haven't seen anything like it. I've never used vn to access the floppy under DOS. Instead I just point it to a 1.44Mb floppy image on the filesystem and a 10Mb hard-drive image on the filesystem, and it works fine for me. -- Parag Patel === # my ~/.doscmdrc assign A: /u/parag/dos/1.44M 1440 assign B: /dev/rfd0 1440 assign C: /u/parag/dos/10M 306 4 17 assign D: /cgt/src/bin/of/ppc assign E: /u/parag/tmp #assign lpt1: direct /dev/lpt0 # map in the parallel port for the EMP-10 portmap 0x378 8 boot c: === Index: trap.c === RCS file: /src/freebsd/src/sys/i386/i386/trap.c,v retrieving revision 1.133 diff -c -r1.133 trap.c *** trap.c 1999/01/06 23:05:36 1.133 --- trap.c 1999/01/16 18:32:46 *** *** 234,240 printf( pid %ld (%s): trap %d with interrupts disabled\n, (long)curproc-p_pid, curproc-p_comm, type); ! else if (type != T_BPTFLT type != T_TRCTRAP) /* * XXX not quite right, since this may be for a * multiple fault in user mode. --- 234,240 printf( pid %ld (%s): trap %d with interrupts disabled\n, (long)curproc-p_pid, curproc-p_comm, type); ! else if (type != T_BPTFLT type != T_TRCTRAP type != T_TSSFLT) /* * XXX not quite right, since this may be for a * multiple fault in user mode. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: msdosfs/vn trouble, doscmd nicety, fd trouble
On Sat, 6 Feb 1999, Brian Feldman wrote: When I mount a floppy image (msdos, using the vn device), I soon get: panic: zone: entry not free When I needed to copy some stuff onto a boot disk, this worked fine with my Feb 1 kernel. Installing Win95 on Bochs OTOH and mounting the resulting disk image (was a pain, didn't work) I'll try do some more testing on this... I really don't know if it's a problem with msdosfs or vn. It will only show p (like this) with INVARIANTS on. As I said above... it was rather weird that the hdd image I was using wouldn't mount when I vnconfig'd it and mount -tmsdosfs'd it.. it claimed the bpb was invalid.. Win95 under Bochs grok'd it.. With this, I'm wondering if everyone's floppy drives work fine and if their drives work fine on an AcerLabs socket 7 motherboard. If so, maybe I can scrounge up a different floppy drive and try it out, but it really seems to not be a hardware problem. The only floppy oddity I've noticed of late was when I tried making disk images of 1.68mb disks. dd if=/dev/fd0.1720.. worked fine and generated disk images fine.. but generated a LOT of error messages towards the end like: fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40abnrml ST1 4sec_not_fn d ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3364 of 3364-3367 (ST0 40abnrml ST1 4sec_not_fn d ST2 0 cyl 80 hd 0 sec 5) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40abnrml ST1 4sec_not_fn d ST2 10wrong_cyl cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40abnrml ST1 4sec_not_fn d ST2 10wrong_cyl cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3364 of 3364-3367 (ST0 40abnrml ST1 4sec_not_fn d ST2 10wrong_cyl cyl 80 hd 0 sec 5) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40abnrml ST1 4sec_not_fn d ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40abnrml ST1 4sec_not_fn d ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3364 of 3364-3367 (ST0 40abnrml ST1 4sec_not_fn d ST2 0 cyl 80 hd 0 sec 5) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40abnrml ST1 4sec_not_fn d ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40abnrml ST1 4sec_not_fn d ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3364 of 3364-3367 (ST0 40abnrml ST1 4sec_not_fn d ST2 0 cyl 80 hd 0 sec 5) - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: msdosfs/vn trouble, doscmd nicety, fd trouble
The panic() I'm getting is not what appears to be the fault of vn(4). I can vnconfig, newfs, and mount_ufs a filesystem to my heart's content, even running my nice file-system-beater-upper (TM). The problem only occurs when I try to use msdosfs, and then occurs when: I chdir into the msdosfs, then when I try to chdir out. On the second chdir, I get the lovely panic. With INVARIANTS on, this is easily reproducible. Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
