Your message dated Wed, 22 Mar 2006 14:47:20 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#296594: fixed in lmbench 3.0-a5-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: lmbench
Severity: important
Script started on Wed Feb 23 15:05:58 2005
fzidpc73:/tmp# lmbench-run
=====================================================================
L M B E N C H C ON F I G U R A T I O N
----------------------------------------
You need to configure some parameters to lmbench. Once you have configured
these parameters, you may do multiple runs by saying
"make rerun"
in the src subdirectory.
NOTICE: please do not have any other activity on the system if you can
help it. Things like the second hand on your xclock or X perfmeters
are not so good when benchmarking. In fact, X is not so good when
benchmarking.
=====================================================================
Hang on, we are calculating your timing granularity.
./config-run: line 39: ../bin/i686-pc-linux-gnu/msleep: No such file or
directory
./config-run: line 40: ../bin/i686-pc-linux-gnu/enough: No such file or
directory
OK, it looks like you can time stuff down to usec resolution.
Hang on, we are calculating your timing overhead.
./config-run: line 45: ../bin/i686-pc-linux-gnu/msleep: No such file or
directory
./config-run: line 46: ../bin/i686-pc-linux-gnu/timing_o: No such file or
directory
OK, it looks like your gettimeofday() costs usecs.
Hang on, we are calculating your loop overhead.
./config-run: line 51: ../bin/i686-pc-linux-gnu/msleep: No such file or
directory
./config-run: line 52: ../bin/i686-pc-linux-gnu/loop_o: No such file or
directory
OK, it looks like your benchmark loop costs usecs.
=====================================================================
Several benchmarks operate on a range of memory. This memory should be
sized such that it is at least 4 times as big as the external cache[s]
on your system. It should be no more than 80% of your physical memory.
The bigger the range, the more accurate the results, but larger sizes
take somewhat longer to run the benchmark.
MB [default 347]
Checking to see if you have 347 MB; please wait for a moment...
./config-run: line 107: ../bin/i686-pc-linux-gnu/memsize: No such file or
directory
./config-run: line 108: ../bin/i686-pc-linux-gnu/memsize: No such file or
directory
./config-run: line 109: ../bin/i686-pc-linux-gnu/memsize: No such file or
directory
./config-run: line 110: [: -lt: unary operator expected
./config-run: line 114: [: -lt: unary operator expected
expr: syntax error
=====================================================================
This benchmark measures, by default, memory latency for a number of
different strides. That can take a long time and is most useful if you
are trying to figure out your cache line size or if your cache line size
is greater than 128 bytes.
If you are planning on sending in these results, please don't do a fast
run.
If you are measuring software only, you probably want to do a fast run,
so answer yes below. Answering yes means that we measure memory latency
with a 128 byte stride.
FASTMEM [default no]
=====================================================================
This benchmark measures, by default, file system latency. That can
take a long time on systems with old style file systems (i.e., UFS,
FFS, etc.). Linux' ext2fs and Sun's tmpfs are fast enough that this
test is not painful.
If you are planning on sending in these results, please don't do a fast
run.
If you want to skip the file system latency tests, answer "yes" below.
SLOWFS [default no]
=====================================================================
This benchmark can measure disk zone bandwidths and seek times. These can
be turned into whizzy graphs that pretty much tell you everything you might
need to know about the performance of your disk.
This takes a while and requires read access to a disk drive.
Write is not measured, see disk.c to see how if you want to do so.
If you want to skip the disk tests, hit return below.
If you want to include disk tests, then specify the path to the disk
device, such as /dev/sda. For each disk that is readable, you'll be
prompted for a one line description of the drive, i.e.,
Iomega IDE ZIP
or
HP C3725S 2GB on 10MB/sec NCR SCSI bus
DISKS [default none]
=====================================================================
Calculating mhz, please wait for a moment...
./config-run: line 224: ../bin/i686-pc-linux-gnu/mhz: No such file or directory
I think your CPU mhz is
but I am frequently wrong. If that is the wrong Mhz, type in your
best guess as to your processor speed. It doesn't have to be exact,
but if you know it is around 800, say 800.
Type in just the Mhz part, like 3060 or 2800 for 3.06GHz or 2.8GHz P4s.
Processor mhz [default ] 2800
=====================================================================
We need a place to store a Mbyte file as well as create and delete a
large number of small files. We default to /usr/tmp. If /usr/tmp is a
memory resident file system (i.e., tmpfs), pick a different place.
Please specify a directory that has enough space and is a local file
system.
FSDIR [default /tmp]
=====================================================================
If you are running on an idle network and there are other, identically
configured systems, on the same wire (no gateway between you and them),
and you have rsh access to them, then you should run the network part
of the benchmarks to them. Please specify any such systems as a space
separated list such as: ether-host fddi-host hippi-host.
REMOTE [default none]
=====================================================================
lmbench outputs status information as it runs various benchmarks.
By default this output is sent to /dev/tty, but you may redirect
it to any file you wish (such as /dev/null...).
Status output file [default /dev/tty]
=====================================================================
There is a database of benchmark results that is shipped with new
releases of lmbench. Your results can be included in the database
if you wish. The more results the better, especially if they include
remote networking. If your results are interesting, i.e., for a new
fast box, they may be made available on the lmbench web page, which is
http://www.bitmover.com/lmbench
Mail results [default yes] no
OK, no results mailed.
=====================================================================
Configuration done, thanks.
There is a mailing list for discussing lmbench hosted at BitMover.
Send mail to [EMAIL PROTECTED] to join the list.
./config-run: line 471: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 472: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 473: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 474: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 475: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 476: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 477: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 478: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 479: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 480: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 481: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 482: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 483: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 484: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 485: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 486: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 487: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 488: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 489: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 490: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 491: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
./config-run: line 492: ../bin/i686-pc-linux-gnu/CONFIG.fzidpc73: No such file
or directory
No config file?
Benchmark run finished....
Remember you can find the results of the benchmark
under /var/lib/lmbench//results
fzidpc73:/tmp# exit
exit
Script done on Wed Feb 23 15:06:31 2005
And as a result, there is no config in /var/lib/lmbench.
--
Regards,
Mario Lang
Graz University of Technology mailto:[EMAIL PROTECTED]
Department Computing http://www.ZID.TUGraz.at/lang/
Phone: +43 (0) 316 / 873 - 6897
--- End Message ---
--- Begin Message ---
Source: lmbench
Source-Version: 3.0-a5-1
We believe that the bug you reported is fixed in the latest version of
lmbench, which is due to be installed in the Debian FTP archive:
lmbench-doc_3.0-a5-1_all.deb
to pool/non-free/l/lmbench/lmbench-doc_3.0-a5-1_all.deb
lmbench_3.0-a5-1.dsc
to pool/non-free/l/lmbench/lmbench_3.0-a5-1.dsc
lmbench_3.0-a5-1.tar.gz
to pool/non-free/l/lmbench/lmbench_3.0-a5-1.tar.gz
lmbench_3.0-a5-1_i386.deb
to pool/non-free/l/lmbench/lmbench_3.0-a5-1_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Al Stone <[EMAIL PROTECTED]> (supplier of updated lmbench package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 21 Mar 2006 23:22:01 -0700
Source: lmbench
Binary: lmbench lmbench-doc
Architecture: source i386 all
Version: 3.0-a5-1
Distribution: unstable
Urgency: low
Maintainer: Al Stone <[EMAIL PROTECTED]>
Changed-By: Al Stone <[EMAIL PROTECTED]>
Description:
lmbench - Utilities to benchmark UNIX systems
lmbench-doc - Documentation for the lmbench benchmark suite
Closes: 296594 302662
Changes:
lmbench (3.0-a5-1) unstable; urgency=low
.
* Update to latest source (http://sourceforge.net.projects/lmbench).
* Toss out the old build method (dependent on BitKeeper) and replace
with patches to upstream tarball.
* Update Debian standards version.
* Closes: bug#296594: lmbench-run fails upon saving configuration
* Closes: bug#302662: 'man lmbench' typos: "fundemental"
Files:
8e9b904c9508962e7f6d3e7e1bf11d78 529 non-free/admin optional
lmbench_3.0-a5-1.dsc
234e4658fa3c306a931b9c9f1d79858e 430455 non-free/admin optional
lmbench_3.0-a5-1.tar.gz
ccfcc0d7b35fff469ff5f0263d491c7b 239662 non-free/admin optional
lmbench-doc_3.0-a5-1_all.deb
16c0e5360692ebdeec4768550bc25ffe 772628 non-free/admin optional
lmbench_3.0-a5-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFEIdMaso6+T7qY4V0RAsLOAJ9fLgVjPAT21KHhuv5gbRfEEvFReQCcDTJf
0jqTA6PwSnRKNrfxmqvBZw8=
=F7Hs
-----END PGP SIGNATURE-----
--- End Message ---
