From owner-freebsd-current Sat Feb 6 12:24:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19382 for freebsd-current-outgoing; Sat, 6 Feb 1999 12:24:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19377 for ; Sat, 6 Feb 1999 12:24:44 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id PAA11341 for ; Sat, 6 Feb 1999 15:24:36 -0500 (EST) Date: Sat, 6 Feb 1999 15:24:36 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: msdosfs/vn trouble, doscmd "nicety", fd trouble Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id MAA19378 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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
, ni_loopcnt = 0, ni_cnd = { cn_nameiop = 2, cn_flags = 4112, cn_proc = 0xf73731e0, cn_cred = 0xf133c200, cn_pnbuf = 0xf73731e0 "à\022\221÷", cn_nameptr = 0x80000000
, 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 70 cyl 0 fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 70 cyl 0 fd0: recal failed ST0 78 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 _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message