From owner-freebsd-current@FreeBSD.ORG Wed Mar 3 10:31:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B59516A4CE for ; Wed, 3 Mar 2004 10:31:11 -0800 (PST) Received: from mail.komquats.com (h24-108-145-252.gv.shawcable.net [24.108.145.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AE2643D39 for ; Wed, 3 Mar 2004 10:31:11 -0800 (PST) (envelope-from Cy.Schubert@komquats.com) Received: from cwsys.cwsent.com (cwsys [10.1.1.1]) by mail.komquats.com (Postfix) with ESMTP id 139465A82F; Wed, 3 Mar 2004 10:31:11 -0800 (PST) Received: from cwsys (localhost [127.0.0.1]) by cwsys.cwsent.com (8.12.11/8.12.8) with ESMTP id i23IVBLq025540; Wed, 3 Mar 2004 10:31:11 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Message-Id: <200403031831.i23IVBLq025540@cwsys.cwsent.com> From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.komquats.com/ To: Garance A Drosihn In-Reply-To: Your message of "Wed, 03 Mar 2004 12:56:00 EST." Date: Wed, 03 Mar 2004 10:31:10 -0800 Sender: Cy.Schubert@komquats.com cc: freebsd-current@freebsd.org Subject: Re: ps Causes Hard Hang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Cy Schubert List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Mar 2004 18:31:11 -0000 In message , Garance A Drosihn writes: > At 9:21 AM -0800 3/3/04, Cy Schubert wrote: > >I'm running 5 -CURRENT systems. My firewall system, using IPF, hard > >hangs every time ps is entered -- totally unresponsive, requiring > >either a power cycle or reset switch to bring it back to life. > > Do you mean the 'ps' command? > or do you mean some form of power-save mode? The ps command and top both cause the hard hang. Userland and kernel are in sync too. Of the 5 -CURRENT systems I run, this is the only one with the problem. Prior to this I was using -CURRENT as of Feb 12. I upgraded on Feb 27, after which the problems started to occur. At the time WATCHDOG reset the system however as of yesterday's build SW_WATCHDOG doesn't work so I'm left with a hard hang. I thought it might be if_tun or ipf however I use those here at work, so that rules them out. So far the only thing I can think of is this: FreeBSD src repository Modified files: sys/kern kern_proc.c sys/sys sysctl.h Log: Add sysctls to allow showing threads for pgrp, tty, uid, ruid, and pid. Revision Changes Path 1.198 +31 -7 src/sys/kern/kern_proc.c 1.123 +4 -0 src/sys/sys/sysctl.h At one time earlier this year dc(4) stopped working until I removed atapicam from the kernel, which BTW, caused hang during boot of one of my other systems, so removing it resolved that problem last night, however it didn't resolve this issue. Cheers, -- Cy Schubert http://www.komquats.com/ BC Government . FreeBSD UNIX Cy.Schubert@osg.gov.bc.ca . cy@FreeBSD.org http://www.gov.bc.ca/ . http://www.FreeBSD.org/