From nobody@FreeBSD.org Sat Sep 11 17:51:01 2004 Return-Path: Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AB5F16A4CE for ; Sat, 11 Sep 2004 17:51:01 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DA1B43D53 for ; Sat, 11 Sep 2004 17:51:01 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i8BHp1R6028917 for ; Sat, 11 Sep 2004 17:51:01 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.11/8.12.11/Submit) id i8BHp11U028916; Sat, 11 Sep 2004 17:51:01 GMT (envelope-from nobody) Message-Id: <200409111751.i8BHp11U028916@www.freebsd.org> Date: Sat, 11 Sep 2004 17:51:01 GMT From: David Kelly To: freebsd-gnats-submit@FreeBSD.org Subject: "systat -v" enters infinite loop X-Send-Pr-Version: www-2.3 >Number: 71603 >Category: bin >Synopsis: "systat -v" enters infinite loop >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Sep 11 18:00:47 GMT 2004 >Closed-Date: Wed Feb 28 12:21:54 GMT 2007 >Last-Modified: Wed Feb 28 12:21:54 GMT 2007 >Originator: David Kelly >Release: 5.2.1-p9 >Organization: >Environment: FreeBSD Opus.home 5.2.1-RELEASE-p9 FreeBSD 5.2.1-RELEASE-p9 #2: Fri Aug 27 22:13:02 CDT 2004 dkelly@Opus.home:/usr/obj/usr/src/sys/OPUS i386 >Description: Apparently triggered by some sort of load condition, "systat -v" will enter an infinite loop and consume all available CPU cycles. The application accepts key input but does not act on commands. Control-C cleanly kills the runaway systat. My Athlon 800 MHz system with same FreeBSD exhibits this problem more than my new Dell PE400SC P4-2.8G w/HT. Hyperthreading is disabled on the P4 in the BIOS. It sounds odd and unrelated but the P4 did not have this problem prior to upgrading to KDE 3.3.0 this past week. The Athlon still has kde-3.2.3. I usually run "systat -v" in a KDE Terminal. I don't believe it is related to swap activity as the 1GB machine is is using very little swap. >How-To-Repeat: I have not found a reliable means of creating the situation but it seems to happen under heavy disk activity with multiple processes using single drive, and each process is able to run the drive at its limits. Such as md5, par2, or urar. Does not seem to matter if the drive is on parallel ATA or serial ATA. >Fix: >Release-Note: >Audit-Trail: From: Gleb Smirnoff To: David Kelly Cc: freebsd-gnats-submit@freebsd.org Subject: Re: misc/71603: "systat -v" enters infinite loop Date: Wed, 6 Oct 2004 09:59:19 +0400 David, On Sat, Sep 11, 2004 at 05:51:01PM +0000, David Kelly wrote: D> >How-To-Repeat: D> I have not found a reliable means of creating the situation but it seems to happen under heavy disk activity with multiple processes using single drive, and each process is able to run the drive at its limits. Such as md5, par2, or urar. D> D> Does not seem to matter if the drive is on parallel ATA or serial ATA. can you build systat with debug flags: # echo CFLAGS+=-g >> /etc/make.conf # echo STRIP= >> /etc/make.conf # cd /usr/src/usr.bin/systat # make # make install Later, when you trigger this bug, try to attach to process using gdb: # gdb `which systat` in gdb prompt type "bt" command, and attach backtrace to this PR. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE State-Changed-From-To: open->closed State-Changed-By: remko State-Changed-When: Wed Feb 28 12:21:53 UTC 2007 State-Changed-Why: Feedback had been requested but never given, closing the ticket. Please report to me if this is still a problem and you have valuable feedback http://www.freebsd.org/cgi/query-pr.cgi?pr=71603 >Unformatted: