public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Geoff Mishkin <gmishkin@acs.bu.edu>
To: linux-kernel@vger.kernel.org
Cc: Harald Dunkel <harald.dunkel@t-online.de>
Subject: Re: ld segfault at end of 2.6.6 compile
Date: Wed, 16 Jun 2004 06:41:35 -0400	[thread overview]
Message-ID: <1087382494.8675.32.camel@amsa> (raw)
In-Reply-To: <40CFE50D.10308@t-online.de>

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@bu.edu>


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


  reply	other threads:[~2004-06-16 10:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16  2:24 ld segfault at end of 2.6.6 compile Geoff Mishkin
2004-06-16  6:13 ` Harald Dunkel
2004-06-16 10:41   ` Geoff Mishkin [this message]
2004-06-16 12:01     ` Eric
     [not found]       ` <200406161935.55740.vda@port.imtp.ilyichevsk.odessa.ua>
2004-06-16 23:24         ` Geoff Mishkin
  -- strict thread matches above, loose matches on Subject: below --
2004-06-16 11:23 Geoff Mishkin
2004-06-16 11:49 ` Harald Dunkel
2004-06-16 12:43 Geoff Mishkin
2004-06-17  4:16 Geoff Mishkin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1087382494.8675.32.camel@amsa \
    --to=gmishkin@acs.bu.edu \
    --cc=gmishkin@bu.edu \
    --cc=harald.dunkel@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox