Re: Processes dying with signal 11

2009-06-19 Thread Glen Barber
On Fri, Jun 19, 2009 at 12:55 PM, Bruce Cranbr...@cran.org.uk wrote:
 I've been trying to run a buildworld using the clangbsd branch on my
 G4 iBook, but without success. I'm currently running a fairly
 up-to-date HEAD:

 FreeBSD mac.draftnet 8.0-CURRENT #0: Tue Jun 16 22:07:11 BST 2009
 bru...@mac.draftnet:/usr/obj/usr/src/sys/IBOOK powerpc

 The problem I see is that after a few hours of running buildworld, when
 it starts building clang itself, 'as' crashes with a signal 11.

 I'm wondering if this is the normal case of bad memory/HDD/CPU or
 something else because it also causes several other processes to crash,
 notably dhclient and sendmail, but I've also seen tcsh crash too.  I
 created a test program which allocated 500MB memory to force the system
 into swap (my iBook only has 512MB).  After a few minutes dhclient
 crashed but the test program kept running.  Is this what normally
 happens when hardware's going bad?


Unfortunately, yes.

Does the build fail in the same place everytime?  Usually hardware
failure will cause randomly placed SIGSEGV errors.


-- 
Glen Barber
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Processes dying with signal 11

2009-06-19 Thread Wojciech Puchar

up-to-date HEAD:

FreeBSD mac.draftnet 8.0-CURRENT #0: Tue Jun 16 22:07:11 BST 2009
bru...@mac.draftnet:/usr/obj/usr/src/sys/IBOOK powerpc

The problem I see is that after a few hours of running buildworld, when
it starts building clang itself, 'as' crashes with a signal 11.


always at the same point or in random places?

if first - it's probably not hardware problem.



I'm wondering if this is the normal case of bad memory/HDD/CPU or
something else because it also causes several other processes to crash,
notably dhclient and sendmail, but I've also seen tcsh crash too.  I
created a test program which allocated 500MB memory to force the system
into swap (my iBook only has 512MB).  After a few minutes dhclient
crashed but the test program kept running.  Is this what normally
happens when hardware's going bad?


isn't it going out of swap?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Processes dying with signal 11

2009-06-19 Thread Bruce Cran
On Fri, 19 Jun 2009 21:04:26 +0200 (CEST)
Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote:

  up-to-date HEAD:
 
  FreeBSD mac.draftnet 8.0-CURRENT #0: Tue Jun 16 22:07:11 BST 2009
  bru...@mac.draftnet:/usr/obj/usr/src/sys/IBOOK powerpc
 
  The problem I see is that after a few hours of running buildworld,
  when it starts building clang itself, 'as' crashes with a signal 11.
 
 always at the same point or in random places?
 
 if first - it's probably not hardware problem.

It's at a random location, but it always happens after the build has
been running for a few hours and when it's ended up swapping some
processes out of main memory.  I've read
http://www.freebsd.org/doc/en/books/faq/troubleshoot.html#SIGNAL11 and
wondered if the collatoral is a normal symptom too.

  I'm wondering if this is the normal case of bad memory/HDD/CPU or
  something else because it also causes several other processes to
  crash, notably dhclient and sendmail, but I've also seen tcsh crash
  too.  I created a test program which allocated 500MB memory to
  force the system into swap (my iBook only has 512MB).  After a few
  minutes dhclient crashed but the test program kept running.  Is
  this what normally happens when hardware's going bad?
 
 isn't it going out of swap?

No, it's definitely not running out of swap, since I have 4.5GB
available! For example using the test program I allocate 500MB
memory; 95MB swap gets used but after a few minutes I get:

pid 470 (dhclient), uid 0: exited on signal 11 (core dumped)
pid 1002 (sendmail), uid 0: exited on signal 11
pid 1054 (sendmail), uid 0: exited on signal 11
pid 1104 (sendmail), uid 0: exited on signal 11
pid 1156 (sendmail), uid 0: exited on signal 11
pid 1207 (sendmail), uid 0: exited on signal 11

but my test program keeps running:

1227 v1 R+ 2:06.23 /usr/obj/home/brucec/test

-- 
Bruce
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Processes dying with signal 11

2009-06-19 Thread Glen Barber
On Fri, Jun 19, 2009 at 3:14 PM, Bruce Cranbr...@cran.org.uk wrote:

 It's at a random location, but it always happens after the build has
 been running for a few hours and when it's ended up swapping some
 processes out of main memory.  I've read
 http://www.freebsd.org/doc/en/books/faq/troubleshoot.html#SIGNAL11 and
 wondered if the collatoral is a normal symptom too.


I would suspect hardware.  Most probably RAM than anything else
initially.  Can you run memtest86+?

-- 
Glen Barber
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Processes dying with signal 11

2009-06-19 Thread Glen Barber
On Fri, Jun 19, 2009 at 3:21 PM, Glen Barberglen.j.bar...@gmail.com wrote:
 I would suspect hardware.  Most probably RAM than anything else
 initially.  Can you run memtest86+?


Also, for what it's worth, I had this similar scenario a few years
ago.  After numerous hardware replacements (RAM, motherboard, etc,
etc) it turned out to the the CPU that was the problem.

It was bad enough that I couldn't even do a 'portsnap fetch' because
the checksum would be incorrectly calculated.


-- 
Glen Barber
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Processes dying with signal 11

2009-06-19 Thread Bruce Cran
On Fri, 19 Jun 2009 15:35:09 -0400
Glen Barber glen.j.bar...@gmail.com wrote:

 On Fri, Jun 19, 2009 at 3:21 PM, Glen Barberglen.j.bar...@gmail.com
 wrote:
  I would suspect hardware.  Most probably RAM than anything else
  initially.  Can you run memtest86+?
 
 
 Also, for what it's worth, I had this similar scenario a few years
 ago.  After numerous hardware replacements (RAM, motherboard, etc,
 etc) it turned out to the the CPU that was the problem.
 
 It was bad enough that I couldn't even do a 'portsnap fetch' because
 the checksum would be incorrectly calculated.
 
 

Unfortunately memtest86+ runs on x86 hardware and this is a
PowerPC iBook.  Being Apple hardware there's not much swapping of
hardware I can do - I'll run a few more tests but I guess it's probably
time to chuck it away.

-- 
Bruce
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Processes dying with signal 11

2009-06-19 Thread Wojciech Puchar

The problem I see is that after a few hours of running buildworld,
when it starts building clang itself, 'as' crashes with a signal 11.


always at the same point or in random places?

if first - it's probably not hardware problem.


It's at a random location, but it always happens after the build has
been running for a few hours and when it's ended up swapping some
processes out of main memory.  I've read


so it is hardware problem.

As it start crashing when swap is used, it may be not memory but chipset 
problem - works fine until disk I/O is used.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Processes dying with signal 11

2009-06-19 Thread Wojciech Puchar


I would suspect hardware.  Most probably RAM than anything else
initially.  Can you run memtest86+?

on Mac?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Processes dying with signal 11

2009-06-19 Thread Glen Barber
On Fri, Jun 19, 2009 at 4:21 PM, Bruce Cranbr...@cran.org.uk wrote:

 Unfortunately memtest86+ runs on x86 hardware and this is a
 PowerPC iBook.

Yeah... I apparently had already forgotten it was a PPC machine.  Ooops. :)

-- 
Glen Barber
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Processes dying with signal 11

2009-06-19 Thread Peter Giessel
On Friday, June 19, 2009, at 12:21PM, Bruce Cran br...@cran.org.uk wrote:
Unfortunately memtest86+ runs on x86 hardware and this is a
PowerPC iBook.  Being Apple hardware there's not much swapping of
hardware I can do - I'll run a few more tests but I guess it's probably
time to chuck it away.

Try running Memtest OS X:
http://www.memtestosx.org/joomla/index.php

You could also try Apple Hardware Test (available on the original
system disk - hold down Option on boot) to test all of the 'book's
hardware.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org