Your message dated Wed, 28 Mar 2007 15:26:25 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#416498: lmbench: complains about all kinds of missing files
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
Version: 2.0-patch2-9
Severity: grave
Justification: renders package unusable
When invoking lmbench, it gives all kinds of errors about missing files.
See output:
keetweej:/home/folkert/t# 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 619]
Checking to see if you have 512 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.
...
=====================================================================
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.
..
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.keetweej: No such file
or directory
./config-run: line 472: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 473: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 474: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 475: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 476: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 477: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 478: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 479: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 480: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 481: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 482: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 483: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 484: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 485: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 486: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 487: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 488: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 489: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 490: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 491: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: No such file
or directory
./config-run: line 492: ../bin/i686-pc-linux-gnu/CONFIG.keetweej: 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
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19.1
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages lmbench depends on:
ii gcc 4:4.1.1-15 The GNU C compiler
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
ii perl 5.8.8-7 Larry Wall's Practical Extraction
Versions of packages lmbench recommends:
pn lmbench-doc <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.0-a7-1
On Wed, Mar 28, 2007 at 01:58:08PM +0200, Folkert van Heusden wrote:
> Package: lmbench
> Version: 2.0-patch2-9
> Severity: grave
> Justification: renders package unusable
> When invoking lmbench, it gives all kinds of errors about missing files.
Confirmed in testing; this appears to be fixed in the unstable version of
the package.
I'm content to let the new version of the package into etch, but it hasn't
been built yet on ia64 and sparc; that will need to be resolved before the
new package can be included in testing.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
