Date: Fri, 22 Jan 1999 07:53:01 -0500 (EST) From: Brian Feldman <green@unixhelp.org> To: current@FreeBSD.ORG Subject: kldload of procfs panics Message-ID: <Pine.BSF.4.05.9901220746230.29327-100000@janus.syracuse.net>
next in thread | raw e-mail | index | archive | help
I'm having a bit of trouble with 4.0-CURRENT as of last night. After fully
updating my system, on reboot procfs (a KLD module) panics the system as
follows: (more explanation after bt)
#9 0xf01d9c1a in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -142545460,
tf_esi = -250596864, tf_ebp = -142545512, tf_isp = -142545640,
tf_ebx = 0, tf_edx = 0, tf_ecx = 0, tf_eax = 10, tf_trapno = 12,
tf_err = 0, tf_eip = -266759770, tf_cs = 8, tf_eflags = 66134,
tf_esp = 880, tf_ss = -147665856}) at ../../i386/i386/trap.c:437
#10 0xf01991a6 in ffs_read (ap=0xf780edb0) at ../../ufs/ufs/ufs_readwrite.c:97
#11 0xf0161bbd in vn_rdwr (rw=UIO_READ, vp=0xf732cc40, base=0xf1104000 "",
len=880, offset=0x0000000000004418, segflg=UIO_SYSSPACE, ioflg=8,
---Type <return> to continue, or q <return> to quit---
cred=0xf05a0280, aresid=0xf780ee90, p=0xf7333620) at vnode_if.h:331
#12 0xf012d11f in link_elf_load_file (filename=0xf10a8d90 "procfs.ko",
result=0xf780ef2c) at ../../kern/link_elf.c:635
#13 0xf012cb76 in link_elf_load_module (filename=0xf10a8d90 "procfs.ko",
result=0xf780ef2c) at ../../kern/link_elf.c:340
#14 0xf012afa3 in linker_load_file (filename=0xf1104c00 "procfs",
result=0xf780ef4c) at ../../kern/kern_linker.c:263
#15 0xf012b782 in kldload (p=0xf7333620, uap=0xf780ef84)
at ../../kern/kern_linker.c:655
#16 0xf01da56f in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -272638612,
tf_esi = -1, tf_ebp = -272638580, tf_isp = -142544940,
tf_ebx = -272638324, tf_edx = 99, tf_ecx = 10, tf_eax = 304,
tf_trapno = 12, tf_err = 2, tf_eip = 134517080, tf_cs = 31,
tf_eflags = 662, tf_esp = -272638620, tf_ss = 39})
at ../../i386/i386/trap.c:1100
#17 0xf01ccf2c in Xint0x80_syscall ()
#18 0x8048245 in ?? ()
#19 0x80480e9 in ?? ()
(kgdb) frame 10
#10 0xf01991a6 in ffs_read (ap=0xf780edb0) at ../../ufs/ufs/ufs_readwrite.c:97
97 if ((u_int64_t)uio->uio_offset > fs->fs_maxfilesize)
(kgdb) printf "%p\n", fs
0x0
Now fs is part of strucct inode in the vnode, but struct inode seems to be
TOTALLY ZERO! After rebooting, a fsck fixes all filesystems and the system
boots fine, but on any _clean_ boot, procfs panics. I have absolutely no idea
what could be causing this, but that I know procfs is the first module loaded
and if I use the boot loader to load kernel+procfs first, nothing panics (e.g.
kernfs). Anyone have an idea?
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9901220746230.29327-100000>