Skip to contentSkip to conversation

ld segfault at end of 2.6.6 compile

DISCUSSION Geoff Mishkin 3 participants 5 messages Jun 16, 2004 1 message not in the archive

lore
Share & tools
lore

Geoff Mishkin

author
#0 lore raw

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

Both are using gcc 2.95.3. Both are using binutils version 2.14.90.0.8. Both have the same module-init-tools version. Etc., etc., etc.

The only difference is on the nonworking one, the processor type is Pentium M instead of Pentium 4, and I'm using different video and ethernet drivers because the two machines have different video and ethernet cards :P. The nonworking one is a laptop, if that makes a difference. I've got the enhanced SpeedStep option enabled for it.

I found a lot of stuff on Google about this problem, but a lot of it is old and/or just tells you to upgrade to a 2.14 of binutils, which I have. I get this error if I use gcc3 as well.

--Geoff Mishkin <[email protected]>

#1 lore raw
Quoted 7 lines · Geoff Mishkin

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.

Quoted 8 lines

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

author
#2 lore raw

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 <[email protected]>

Quoted 34 lines · Harald Dunkel
Quoted 9 lines · Geoff Mishkin

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

Quoted 11 lines

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

#3 lore raw
Quoted 3 lines · 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.

The bios does very wimpy checking of ram. If it is indeed a RAM problem, you should use a tool like memtest86 in linux (you boot to it, its not a linux tool per se) or prime95(is that the name?) in windows.

Quoted 9 lines

Still having the problem, though.

--Geoff Mishkin <[email protected]>

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

A message that is not in the archive (sent off-list or not yet received): [email protected]

author
#5 lore raw

Yes, it always happens right away, even between reboots. And just for technicality, its ld that segfaults, not gcc. If it makes a difference.

--Geoff Mishkin <[email protected]>

Quoted 19 lines · Denis Vlasenko
Quoted 8 lines · Eric
Quoted 3 lines · 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.

The bios does very wimpy checking of ram. If it is indeed a RAM problem, you should use a tool like memtest86 in linux (you boot to it, its not a linux tool per se) or prime95(is that the name?) in windows.

In my case, it wasn't enough. Neuther memtest86 nor cpuburn was able to trigger problem, only gcc. (I did not try prime95). I tweaked memory timings until gcc stopped segv'ing.

BTW, "bad memory" theory does not hold if fails _every time in the same place_.
--
vda