Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Nov 1997 17:40:48 -0800 (PST)
From:      Simon Shapiro <shimon@simon-shapiro.org>
To:        Mike Smith <mike@smith.net.au>
Cc:        freebsd-current@FreeBSD.ORG, Nate Williams <nate@mt.sri.com>
Subject:   Re: Compiler Bug???
Message-ID:  <XFMail.971125174048.shimon@Simon-Shapiro.ORG>
In-Reply-To: <199711252331.KAA00560@word.smith.net.au>

next in thread | previous in thread | raw e-mail | index | archive | help

On 25-Nov-97 Mike Smith wrote:
 
...

> Not exactly.  I quote:
> 
> ] Scenario 1:
> ]
> ] Xfmail of 17-Nov-97 with xforms 0.88:  Compiles fine, then produces
> ] dozens of ``Bad Attribute'' and `Bad Coordinates''.  These come
> from
> ] libX11.  Tearing my hair out did not help, so I boot UP (was on
> SMP).
> ] The problem is... GONE!
> ]
> ] Recompile on UP, reboot SMP...   Problem is...  Yup, GONE!
> 
> This is actually:
> 
>  - code built while running SMP fails while running SMP.
>  - code built while running SMP works UP.
>  - code built while running UP works everywere.
> 
> Either of our interpretations could be right.  More data, Simon?

OK, if you insist :-)

It appears as if the SMP kernel I am running (from 10-Nov-97) has
(wild guess!) some sort of a leak in the VM:

*  Innocent copiles crash with cc1 exiting on SEGFAULT.
*  Code copiled will crash in a strange way.
*  Fsck, upon reboot) will destroy (or try to) a file system because
   ALL the inodes need to be 208, not what they really are.

These problems go away if I boot a uniprocessor kernel.
The only constant is:

  If it was compiled under UP and run under UP it is good and stable.

All other iterations and combinations have been observed.

I have not upgraded to kernels past the 10th, as the SMP kernel boots
fine, but instead of starting /etc/rcit just sits there in the default
halt loop.

I have received help on this but th ONLY thnig that really works is to
start with the GENERIC kernel and move things around, deleting chaff,
one step at a time, until a new config file is born.

The new config file is materially identical to the old, but ordered a
bit differently.  Dunno why any of this makes any sense.  But it does 

Simon

BTW, different motherboard models react differently to these scenarios.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.971125174048.shimon>