mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Random compiler errors
Date: Sat, 16 Oct 2010 19:04:16 -0700	[thread overview]
Message-ID: <20101016190416.bdbfc69f.rdunlap@xenotime.net> (raw)
In-Reply-To: <20101016174854.4b8eec07@s6510>

On Sat, 16 Oct 2010 17:48:54 -0700 Stephen Hemminger wrote:

> Not sure why this is happening, but lately when building kernels
> I am getting non-reproducible cases of gcc failure. There are no
> messages in system log. Cosmic rays? Bad memory?

I haven't had these personally, but from reading lkml over the past
N years, these are usually due to memory or disk/storage problems.


>   CC      arch/x86/kernel/xsave.o
>   CC      arch/x86/kernel/ptrace.o
> arch/x86/kernel/ptrace.c:1416: internal compiler error: Bus error
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <file:///usr/share/doc/gcc-4.4/README.Bugs> for instructions.
> make[2]: *** [arch/x86/kernel/ptrace.o] Error 1
> make[1]: *** [arch/x86/kernel] Error 2
> make: *** [arch/x86] Error 2
> 
> $ make
>   CHK     include/linux/version.h
>   CHK     include/generated/utsrelease.h
>   CALL    scripts/checksyscalls.sh
>   CHK     include/generated/compile.h
>   CC      arch/x86/kernel/ptrace.o
>   CC      arch/x86/kernel/tls.o
>   CC      arch/x86/kernel/step.o
>   CC      arch/x86/kernel/tboot.o
> --


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-10-17  2:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-17  0:48 Stephen Hemminger
2010-10-17  2:04 ` Randy Dunlap [this message]
2010-10-17 15:58   ` Stephen Hemminger

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=20101016190416.bdbfc69f.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    /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

all inboxes | Powered by JetHome®