[PATCH 2/4] 2.6.1-mm2: sched-domain

[Andrew Morton]

Nick Piggin <piggin at cyberone.com.au> wrote:
>
> This is the core sched domains patch.

I'm having a ton of trouble with this on the 4-way ppc64 box.  Symptoms are
similar to memory corruption: gcc falls over with sig11, filenames
corrupted, etc.  Often it fails to get through the initscripts without
userspace processes failing randomly.

One example:

 cc -Wall  -Wall -I../include    -c -o search_path.o search_path.c
make[1]: B<lots of random binary garbage>: Command not found
make[1]: *** [search_path.o] Error 127
make[1]: Leaving directory `/mnt/sdb5/ltp-full-20040108/lib'
make: *** [libltp.a] Error 2

and

cc -O -Wall  -w -o  test ./test.c
cc -c -Wall  -w -o  test_arch.o ./test.c
cc -Wall  -w -o  test_D ./test.c
make[4]: *** [test] Segmentation fault
make[4]: *** Deleting file `test'


I'm surprised that nobody else has noticed it.  The results of a binary
search through my current patch queue:

local_bh_enable-warning-fix.patch			OK
pnp-8250_pnp-fix.patch
pnp-resource-flags-reorganisation.patch
pnp-BIOS-workaround.patch
pnp-avoid-static-allocations.patch
pnp-move-ID-declarations.patch
pnp-file2alias-update.patch
pnp-update-matching-code.patch
pnp-additional-sysfs-info.patch
pnp-config-cleanup.patch				OK
sched-find_busiest_node-resolution-fix.patch		OK
sched-domains.patch					BAD
sched-clock-fixes.patch					BAD
sched-build-fix.patch					BAD
sched-sibling-map-to-cpumask.patch
p4-clockmod-sibling-map-fix.patch
p4-clockmod-more-than-two-siblings.patch
sched-domains-i386-ht.patch
sched-find_busiest_group-fix.patch			BAD
sched-domain-tweak.patch
sched-no-drop-balance.patch
sched-arch_init_sched_domains-fix.patch
sched-find_busiest_group-clarification.patch
sched-remove-noisy-printks.patch
sched-directed-migration.patch
sched-domain-debugging.patch
acpi-numa-printk-level-fixes.patch			BAD

points the finger at the core sched-domains patch.

But Anton says that he's using your scheduler patches without problems.

mnm:/usr/src/25-power4> /usr/local/ppc64/bin/powerpc-linux-gcc --version
powerpc-linux-gcc (GCC) 3.2.3 20030211 (prerelease)

I tried a kernel compiled with -O1 and it failed in the same way, which
somewhat rules out a compiler bug.

Anyone have any suggestions as to a next step?


** Sent via the linuxppc64-dev mail list. See http://lists.linuxppc.org/