public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Random compiler errors
@ 2010-10-17  0:48 Stephen Hemminger
  2010-10-17  2:04 ` Randy Dunlap
  0 siblings, 1 reply; 3+ messages in thread
From: Stephen Hemminger @ 2010-10-17  0:48 UTC (permalink / raw)
  To: linux-kernel

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?

  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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Random compiler errors
  2010-10-17  0:48 Random compiler errors Stephen Hemminger
@ 2010-10-17  2:04 ` Randy Dunlap
  2010-10-17 15:58   ` Stephen Hemminger
  0 siblings, 1 reply; 3+ messages in thread
From: Randy Dunlap @ 2010-10-17  2:04 UTC (permalink / raw)
  To: Stephen Hemminger; +Cc: linux-kernel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Random compiler errors
  2010-10-17  2:04 ` Randy Dunlap
@ 2010-10-17 15:58   ` Stephen Hemminger
  0 siblings, 0 replies; 3+ messages in thread
From: Stephen Hemminger @ 2010-10-17 15:58 UTC (permalink / raw)
  To: Randy Dunlap; +Cc: linux-kernel

On Sat, 16 Oct 2010 19:04:16 -0700
Randy Dunlap <rdunlap@xenotime.net> wrote:

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

That was what I thought, but memtest comes up clean and the
storage is SSD. My suspicion is something like EDAC or some DMA
bug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-10-17 15:58 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-17  0:48 Random compiler errors Stephen Hemminger
2010-10-17  2:04 ` Randy Dunlap
2010-10-17 15:58   ` Stephen Hemminger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox