Re: ld segfault at end of 2.6.6 compile

[Geoff Mishkin]

I couldn't find exactly what I was looking for in the BIOS utility (IBM
ThinkPad T42), but I turned on Diagnostics mode and the RAM check, so at
boot it checked the RAM, which all turned out okay.

Still having the problem, though.

			--Geoff Mishkin <gmishkin@xxxxxx>


On Wed, 2004-06-16 at 02:13, Harald Dunkel wrote:
> Geoff Mishkin wrote:
> > I'm getting the
> > 
> > make: *** [.tmp_vmlinux1] Error 139
> > 
> > problem with kernel 2.6.6.  It works fine on one of my computer, but not
> > the other.
> > 
> > The full line is
> > 
> > ld -m elf_i386  -T arch/i386/kernel/vmlinux.lds.s
> > arch/i386/kernel/head.o arch/i386/kernel/init_task.o   init/built-in.o
> > --start-group  usr/built-in.o arch/i386/kernel/built-in.o 
> > arch/i386/mm/built-in.o  arch/i386/mach-default/built-in.o 
> > kernel/built-in.o  mm/built-in.o  fs/built-in.o  ipc/built-in.o 
> > security/built-in.o  crypto/built-in.o  lib/lib.a  arch/i386/lib/lib.a 
> > lib/built-in.o  arch/i386/lib/built-in.o  drivers/built-in.o 
> > sound/built-in.o  arch/i386/pci/built-in.o  arch/i386/power/built-in.o 
> > net/built-in.o --end-group  -o .tmp_vmlinux1
> > make: *** [.tmp_vmlinux1] Error 139
> > 
> 
> Error 139 is a SEGV somewhere in a subprocess. Linker errors
> like this might be an indicator for problems with your physical
> memory.
> 
> My suggestion would be to enter your PC's BIOS setup at boot
> time and verify the RAM access timing. Maybe it was set too
> optimistic.
> 
> 
> Good luck
> 
> Harri

-
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/