Bug#485398: numactl fails, moaning that the arguments for -C are out of range

[Daniel Vetter]

Package: numactl
Version: 2.0.1-1
Severity: normal

When runnning

$ numactl -C 2,3 bash

on a system with 4 cores I get

libnuma: Warning: Cannot parse /proc/self/status
numactl: cpu argument 2,3 is out of range

and numactl terminates without starting up bash. The argument for -C
doesn't actuallay matter, moans for any legit affinity set I tested. The
version from testing (1.0.2-1) only emits the libnuma warning, but
proceeds as expected (and correctly sets cpu affinity).

The kernel is a self-build post-2.6.25-rc5.

-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-rc5-dirty (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_CH.utf8, LC_CTYPE=de_CH.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages numactl depends on:
ii libc6 2.7-12 GNU C Library: Shared libraries
ii libnuma1 2.0.1-1 Libraries for controlling NUMA pol

numactl recommends no packages.

-- no debconf information

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Daniel Vetter]

Unfortunately the bug still exists. Some more testing just showed that
only the -C option is affected, all options which take a node-id work as
expected. Furthermore reverting libnuma1 to the version in testing gets
rid of the libnuma1: warning, too.

But when running with a debian flavour 2.6.25-2-amd64 it works all right
(without any warning). So I will try to track down whether this is a
regression in upstream or not and tell you later what I've found out.

On a related note, I think numactl (2.0.1+20080610-1) needs a versioned
depends on libnuma1, because it doesn't work with at least libnuma1 from
testing (1.0.2-1). It fails with the following output:

numactl: /usr/lib/libnuma.so.1: no version information available (required by numactl)
numactl: /usr/lib/libnuma.so.1: no version information available (required by numactl)
numactl: relocation error: numactl: symbol numa_parse_cpustring, version libnuma_1.2 not defined in file libnuma.so.1 with link time reference

Thanks for your efforts, Daniel
--
Daniel Vetter
E-Mail: daniel...@ffwll.ch
Tel.: +41 (0)79 365 57 48

[Daniel Vetter]

I finally managed to do some further test:

The libnuma1 warning goes away if I enable CONFIG_CPUSETS in my
custum-built kernel.

But otherwise the problem persists (this is on 2.6.26-rc8) with
numactl 2.6.26-rc8-00023-g22a040b:

$ numactl -C 1 bash
numactl: cpu argument 1 is out of range

$ numactl -Call bash
sched_setaffinity: Invalid argument

The numactl from stable (0.9.11-2) still works fine (I couldn't get hold
of a 1.x version anymore). So I think the bug still exists.

--
Daniel Vetter
E-Mail: daniel...@ffwll.ch
Tel.: +41 (0)79 365 57 48

--