From owner-freebsd-questions Mon Sep 11 11:49:14 2000 Delivered-To: freebsd-questions@freebsd.org Received: from parodius.com (pentarou.parodius.com [205.149.163.62]) by hub.freebsd.org (Postfix) with ESMTP id 600CF37B424 for ; Mon, 11 Sep 2000 11:49:09 -0700 (PDT) Received: from localhost (dpk@localhost) by parodius.com (8.11.0/8.11.0) with ESMTP id e8BInKh87424 for ; Mon, 11 Sep 2000 11:49:21 -0700 (PDT) (envelope-from dpk@parodius.com) Date: Mon, 11 Sep 2000 11:49:20 -0700 (PDT) From: David Kirchner To: freebsd-questions@freebsd.org Subject: Strange procfs bug(?) 3.2-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been trying to track down a procfs bug which has semi-recently popped up. I'm not 100% certain it is a bug in procfs, but it seems to be the most likely candidate. We first noticed the bug when we used the 'killall' command to kill off processes. Whenever we'd run it, the machine would panic. We assumed it was because we might have been killing something that was in a weird state. But later on when I was trying to figure out something else on the same box, I was running 'more /proc/*/status' and it panic'd. Just now, I ran a little script: cd /proc for i in * do ps -uxp $i >> /root/killallfindbug.log 2>&1 sync;sync cat /proc/$i/status >> /root/killallfindbug.log 2>&1 sync;sync done which also caused a panic (double panic, this time). The last line in the log file was: www 1756 0.0 0.8 5900 4364 ?? S 11:14AM 0:00.22 /usr/local/bin/http (That would have been /usr/local/bin/httpd -f /usr/local/www/server/conf/httpd.conf if I added -w to the ps flags) This is on a 3.2-RELEASE machine. We haven't rebuilt the kernels on these boxes in a long time, and they haven't been modified (been watching with tripwire) to our knowledge anyhow. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message