Date: Thu, 17 Feb 2000 22:02:48 -0500 From: Thomas Stromberg <tstromberg@rtci.com> To: freebsd-current@freebsd.org Subject: procfs crash in -CURRENT (multi-read) Message-ID: <38ACB658.70007@rtci.com>
next in thread | raw e-mail | index | archive | help
<html><head></head>
<body>Just letting you guys know, the nasty multiple-read bug in procfs still
exists. I'm preparing a new smashwidgets report for 4.0 (should be ready
for tommorow, will post here), and in the process happened to shoot myself
in the foot by having two breakwidgets scripts go simultaneously. breakwidgets
reads /proc quite a bit (actually, with a minimized copy of /usr/bin/killall),
and things go bad when "worlds collide".<br><br>So if any of you decide
to play with multiple /proc readers, use locks :0 Please note that this
crash is very very hard for me to duplicate.. this is after about 32 hours
of running the script that does the proc read. <br><br>(full vmcore, conf, and kernel.debug available on request)..<br><br>FreeBSD
karma.afterthought.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Feb 14 23:00:42
GMT 2000 <a href="mailto:chenresig@karma.afterthought.org:/usr/src/sys/compile/KARMA ">chenresig@karma.afterthought.org:/usr/src/sys/compile/KARMA </a>
i386<br><br>dumping to dev #ad/0x20001, offset 1109472<br>dump ata0: resetting devices .. done<br>128
127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110
109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89
88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65
64 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<br>---<br>#0 boot (howto=256) at ../../kern/kern_shutdown.c:304<br>304 dumppcb.pcb_cr3 = rcr3();<br>(kgdb) bt<br>#0 boot (howto=256) at ../../kern/kern_shutdown.c:304<br>#1 0xc014e194 in poweroff_wait (junk=0xc02b9480, howto=-871862272) at ../../kern/kern_shutdown.c:554<br>#2 0xc022d064 in vm_fault (map=0xc031ee28, vaddr=3423105024, fault_type=1 '\001', fault_flags=0) at ../../vm/vm_fault.c:240<br>#3 0xc02810d2 in trap_pfault (frame=0xcc136cc4, usermode=0, eva=3423108180) at ../../i386/i386/trap.c:788<br>#4 0xc0280d37 in trap (frame={tf_fs = -871170032, tf_es = -871170032, tf_ds = 16, tf_edi = -871142055, tf_esi = -871142025,<br>
tf_ebp = -871141804, tf_isp = -871142160, tf_ebx = -872323392, tf_edx
= 0, tf_ecx = -872323392, tf_eax = -871859336, tf_trapno = 12,<br> tf_err = 0, tf_eip = -1072160861, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = 0}) at ../../i386/i386/trap.c:423<br>#5
0xc0181fa3 in procfs_dostatus (curp=0xcc145e00, p=0xcc0166c0, pfs=0xc14abf60,
uio=0xcc136eec) at ../../miscfs/procfs/procfs_status.c:115<br>#6 0xc0182590 in procfs_rw (ap=0xcc136ea0) at ../../miscfs/procfs/procfs_subr.c:277<br>#7 0xc017dc0a in vn_read (fp=0xc14431c0, uio=0xcc136eec, cred=0xc1450700, flags=0, p=0xcc145e00) at vnode_if.h:334<br>#8
0xc015ac50 in dofileread (p=0xcc145e00, fp=0xc14431c0, fd=6, buf=0x8235000,
nbyte=4096, offset=-1, flags=0) at ../../sys/file.h:140<br>#9 0xc015ab57 in read (p=0xcc145e00, uap=0xcc136f80) at ../../kern/sys_generic.c:111<br>#10
0xc028167e in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi
= -1077946820, tf_esi = 672915688, tf_ebp = -1077946996,<br> tf_isp = -871141420, tf_ebx = 672858084, tf_edx = 672809512, tf_ecx = 136531968, tf_eax = 3, tf_trapno = 0, tf_err = 2,<br> tf_eip = 672818732, tf_cs = 31, tf_eflags = 659, tf_esp = -1077947040, tf_ss = 47}) at ../../i386/i386/trap.c:1055<br>#11 0xc0276646 in Xint0x80_syscall ()<br><br></body>
</html>
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?38ACB658.70007>