| Summary: | "systat -v" enters infinite loop | ||
|---|---|---|---|
| Product: | Base System | Reporter: | dkelly <dkelly> |
| Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
dkelly
2004-09-11 19:00:47 UTC
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 State Changed From-To: open->closed 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 |