Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 6 Oct 2004 06:00:50 GMT
From:      Gleb Smirnoff <glebius@freebsd.org>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: misc/71603: "systat -v" enters infinite loop
Message-ID:  <200410060600.i9660o7u017829@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/71603; it has been noted by GNATS.

From: Gleb Smirnoff <glebius@freebsd.org>
To: David Kelly <dkelly@hiwaay.net>
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` <pid of systat process>
 
 in gdb prompt type "bt" command, and attach backtrace to this PR.
 
 -- 
 Totus tuus, Glebius.
 GLEBIUS-RIPN GLEB-RIPE



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410060600.i9660o7u017829>