Re: Bus error on make allyesconfig, kernelbuild with HEAD

[Ben Gamari]

On Fri, 30 Jul 2010 16:43:53 +0800, AmÃrico Wang <xiyou.wangcong@xxxxxxxxx> wrote:
> This is useful. :) Looks like parse_dep_file() accesses out of
> the mmap'ed memory range...
> 
Did anything ever happen with this? I seem to be experiencing similar
issues while cross-compiling for ARM on x86-64. All tested kernels
(v2.6.35 to master) fail with,

$ make
  HOSTCC  scripts/basic/fixdep
In file included from /usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/include/stdlib.h:903,
                 from scripts/basic/fixdep.c:112:
/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/usr/include/bits/stdlib.h:65:  warning: no previous prototype for âptsname_râ
/bin/sh: line 1: 20831 Bus error               scripts/basic/fixdep  scripts/basic/.fixdep.d scripts/basic/fixdep 'gcc  -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wmissing-prototypes  -Wstrict-prototypes -O2 -fomit-frame-pointer     -o  scripts/basic/fixdep scripts/basic/fixdep.c  ' >  scripts/basic/.fixdep.tmp
make[2]: *** [scripts/basic/fixdep] Error 135
make[1]: *** [scripts_basic] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by  `include/config/kernel.release'.  Stop.

This seems to be the result of the same mmap misstep,

$  scripts/basic/fixdep scripts/basic/.fixdep.d scripts/basic/fixdep 'gcc -Wp,-MD,scripts/basic/.fixdep.d -Wall -Wmissing-prototypes -Wstrict-prototypes -O2 -fomit-frame-pointer     -o scripts/basic/fixdep scripts/basic/fixdep.c  ' >| scripts/basic/.fixdep.tmp
fixdep: mmap: Cannot allocate memory

Which valgrind reports as,

==20634== Process terminating with default action of signal 7 (SIGBUS)
==20634==  Non-existent physical address at address 0x51B2000
==20634==    at 0x400F30: parse_dep_file (in /home/bgamari/linux/scripts/basic/fixdep)
==20634==    by 0x401285: main (in /home/bgamari/linux/scripts/basic/fixdep)
==20634== 

Any ideas?

- Ben
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/