[olug] wine problem (fwd)

[Andrew Embury]

There is a Signal 11 FAQ at http://www.bitwizard.nl/sig11/

Its almost always related to hardware and usually only crops up when
compiling large programs like the kernel or X11

_Drew

On Fri, 14 Sep 2001 alassek at techie.com wrote:

> Well, I'm not running a stock kernel, it's a 2.4.3 kernel compiled by me. And I have 256megs of RAM in it, it's not even hitting swap. I'll run memtest but i don't understand why bad ram would only manifest itself while building wine...
>
> -----Original Message-----
> From: Eric Johnson <eric_j at novia.net>
> Date: Wed, 12 Sep 2001 09:43:04 -0500 (CDT)
> To:  <olug at bstc.net>
> Subject: Re: [olug] wine problem (fwd)
>
>
> > Hi,
> >
> > 	I remembered a friend had run across this message before and asked
> > him about it. Here's his response:
> >
> > -- Eric Johnson
> > -- eric_j at novia.net
> >
> >
> > Eric,
> >
> > 	Yes.  The this is the symtom I had.  The stock RedHat 6.2 kernel  that
> > came on the disk 2.2.14 (sub revision 5 I think??) caused this problem.
> >   My research at the time made the hardware flaw sound like it is the
> > more common cause.
> >
> > 	I found VMware was the program that alerted me to the bug.  I believe it
> > has something to do with when you start to swap a lot.  The bug is in
> > the kernel.
> >
> > 	The alternative problem which the other reply suggests is described in
> > more detail here:
> >
> > http://www.bitwizard.nl/sig11/
> >
> > If this is the problem it is a hardware flaw.
> >
> > The hardware problem could possibly be detected using this:
> >
> > http://reality.sgi.com/cbrady/memtest86
> >
> > I have never actually had this find a memory flaw, but then I don't
> > think I have ever had flawed memory.  It will take a day or two to run
> > on the full checking mode, but it is the best I have seen.  You can run
> > it quicker but it is less pedantic in the checking.
> >
> > 		Hope this helps,
> > 				Kirby
> >
> >
> >
> >
> >
> >
> > Eric Johnson wrote:
> > > Didn't you have this problem compiling our software? It was a compiler or
> > > kernel bug, wasn't it?
> > >
> > > -- Eric Johnson
> > > -- eric_j at novia.net
> > >
> > > It is not through the benevolence of the butcher, the brewer or the baker
> > > that we expect our dinner, but from their regard to their own interests.
> > >
> > > Adam Smith
> > >
> > >
> > > ---------- Forwarded message ----------
> > > Date: 11 Sep 2001 21:56:10 -0500
> > > From: Phil Brutsche <phil at giedi.obix.com>
> > > Reply-To: olug at bstc.net
> > > To: olug <olug at bstc.net>
> > > Subject: Re: [olug] wine problem
> > >
> > > On Tue, 2001-09-11 at 19:41, Adam Lassek wrote:
> > >
> > >>perhaps someone here knows how to fix this. When I try to compile Wine I get
> > >>this error:
> > >>
> > >>gcc: Internal compiler error: program cc1 got fatal signal 11
> > >>
> > >>any idea what's wrong?
> > >>
> > >
> > > First guess: hardware.  Memory, specifically.
> > >
> > > If you can, swap in some memory from another computer and try it again.
> > >
> > > If you don't have another computer, replace the memory outright.  A
> > > 256MB stick is $35.  A 128 MB stick is near $20; 64MB is even cheaper.
> > >
> > > They don't make SDRAM smaller than 64MB, unfortunately.
> > >
> > > This is all Crucial (aka Micron) and Kingston memory, BTW.  The generic,
> > > no-name stuff is even cheaper.
> > >
> > >
> >
> >
> >
> > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> >
> > For help contact olug-help at bstc.net - run by ezmlm
> > to unsubscribe, send mail to olug-unsubscribe at bstc.net
> > or `mail olug-unsubscribe at bstc.net < /dev/null`
> > (c)2001 OLUG http://www.olug.org
> >
> > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> >
> >
>
> --
>
>
> "God is dead." -- Nietzsche
> "Nietzsche is dead." -- God
>
>
> _______________________________________________
> FREE Personalized E-mail at Mail.com
> http://www.mail.com/?sr=signup
>
> Talk More, Pay Less with Net2Phone Direct(R), up to 1500 minutes free!
> http://www.net2phone.com/cgi-bin/link.cgi?143
>
>
>
> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
>
> For help contact olug-help at bstc.net - run by ezmlm
> to unsubscribe, send mail to olug-unsubscribe at bstc.net
> or `mail olug-unsubscribe at bstc.net < /dev/null`
> (c)2001 OLUG http://www.olug.org
>
> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
>
>


-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_

For help contact olug-help at bstc.net - run by ezmlm
to unsubscribe, send mail to olug-unsubscribe at bstc.net
or `mail olug-unsubscribe at bstc.net < /dev/null`
(c)2001 OLUG http://www.olug.org

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_