[gentoo-user] GCC Failing

[gentoo-user] GCC Failing

[Vlad Dogaru]

Hello,

what I initially thought was a problem with kdelibs is turning into
something even more strange. Emerge failed for every package I tried
to install with the message: "Internal compiler error: Segmentation
Fault". I have tried re-emerging gcc from two local mirrors, but got a
bunch of hash failures and corrupted archives. I am now trying
distfiles.gentoo.org, but this will take quite long. Any ideas as to
what might have happened? Could this be connected to X running
alarmingly slow?

Thanks,
Vlad

-- 
How's my English? How about my Netiquette?
Do mail me if something is wrong with my behaviour. Thank you.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] GCC Failing

[Naga]

On Monday 22 January 2007 12:48, Vlad Dogaru wrote:
> Hello,
>
> what I initially thought was a problem with kdelibs is turning into
> something even more strange. Emerge failed for every package I tried
> to install with the message: "Internal compiler error: Segmentation
> Fault". I have tried re-emerging gcc from two local mirrors, but got a
> bunch of hash failures and corrupted archives. I am now trying
> distfiles.gentoo.org, but this will take quite long. Any ideas as to
> what might have happened? Could this be connected to X running
> alarmingly slow?

Faulty memory? Got something like this once and then it was a memory module 
that was broken. Try and check it with memcheck86 (think I got the name 
right :))

-- 
Naga
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] GCC Failing

[Mick]

[-- Attachment #1: Type: text/plain, Size: 495 bytes --]

On Monday 22 January 2007 11:48, Vlad Dogaru wrote:
> Hello,
>
> what I initially thought was a problem with kdelibs is turning into
> something even more strange. Emerge failed for every package I tried
> to install with the message: "Internal compiler error: Segmentation
> Fault".

Segmentation errors indicate low mem.

> Could this be connected to X running 
> alarmingly slow?

Yep.  If you stop/zap xdm and try again from the console, does it segfault?
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] GCC Failing

[Dale]

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

Mick wrote:
> On Monday 22 January 2007 11:48, Vlad Dogaru wrote:
>   
>> Hello,
>>
>> what I initially thought was a problem with kdelibs is turning into
>> something even more strange. Emerge failed for every package I tried
>> to install with the message: "Internal compiler error: Segmentation
>> Fault".
>>     
>
> Segmentation errors indicate low mem.
>
>   
>> Could this be connected to X running 
>> alarmingly slow?
>>     
>
> Yep.  If you stop/zap xdm and try again from the console, does it segfault?
>   

I have got those when I had the wrong driver for my drive controller. 
You may want to check that if this is a new install or you have changed
your kernel recently.  I tested mine by doing back to back hdparm -Tt
tests.  It fails when you do the test 4 or 5 times in a row.

Hope that helps.

Dale

:-)  :-)  :-)

-- 
www.myspace.com/dalek1967


[-- Attachment #2: Type: text/html, Size: 1526 bytes --]

Re: [gentoo-user] GCC Failing

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

On Monday 22 January 2007 12:25, Naga wrote:
> On Monday 22 January 2007 12:48, Vlad Dogaru wrote:
> > Hello,
> >
> > what I initially thought was a problem with kdelibs is turning into
> > something even more strange. Emerge failed for every package I tried
> > to install with the message: "Internal compiler error: Segmentation
> > Fault". I have tried re-emerging gcc from two local mirrors, but got a
> > bunch of hash failures and corrupted archives. I am now trying
> > distfiles.gentoo.org, but this will take quite long. Any ideas as to
> > what might have happened? Could this be connected to X running
> > alarmingly slow?
>
> Faulty memory? Got something like this once and then it was a memory module
> that was broken. Try and check it with memcheck86 (think I got the name
> right :))

If memtest86+ doesn't show anything, then try a more arduous memory test like 
so:

http://people.redhat.com/dledford/memtest.html

PS. Before you start spending time on memory tests I'd first try it on the 
console with no X gui running at all and see what gives.
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] GCC Failing

[Vlad Dogaru]

On 1/22/07, Naga <nagatoro@gmail.com> wrote:
> On Monday 22 January 2007 12:48, Vlad Dogaru wrote:
> > Hello,
> >
> > what I initially thought was a problem with kdelibs is turning into
> > something even more strange. Emerge failed for every package I tried
> > to install with the message: "Internal compiler error: Segmentation
> > Fault". I have tried re-emerging gcc from two local mirrors, but got a
> > bunch of hash failures and corrupted archives. I am now trying
> > distfiles.gentoo.org, but this will take quite long. Any ideas as to
> > what might have happened? Could this be connected to X running
> > alarmingly slow?
>
> Faulty memory? Got something like this once and then it was a memory module
> that was broken. Try and check it with memcheck86 (think I got the name
> right :))

I used memtest and it showed a bunch of errors on my ancient 128 MiB
chip. So I removed it, but even with the (presumably good -- only let
memtest run for about 3 minutes) 256 MiB I have the same problems. I
don't run anything heavily graphical, so RAM rarely got up to 50%
usage back with 384 MiB. Hence, I should be fine (I long gave up
hoping to play games on my machine); but I have the same problems,
with programs taking long to start and strange happenings caused by
gcc. Any other ideas?

Vlad

PS: Unless I got it wrong, it's memtest86 and it proved very valuable.
By the way, does it ever stop? After two hours and 13 thousand errors
I got fed up and removed the chip.

-- 
How's my English? How about my Netiquette?
Do mail me if something is wrong with my behaviour. Thank you.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] GCC Failing

[Vlad Dogaru]

On 1/22/07, Mick <michaelkintzios@gmail.com> wrote:
> On Monday 22 January 2007 12:25, Naga wrote:
> > On Monday 22 January 2007 12:48, Vlad Dogaru wrote:
> > > Hello,
> > >
> > > what I initially thought was a problem with kdelibs is turning into
> > > something even more strange. Emerge failed for every package I tried
> > > to install with the message: "Internal compiler error: Segmentation
> > > Fault". I have tried re-emerging gcc from two local mirrors, but got a
> > > bunch of hash failures and corrupted archives. I am now trying
> > > distfiles.gentoo.org, but this will take quite long. Any ideas as to
> > > what might have happened? Could this be connected to X running
> > > alarmingly slow?
> >
> > Faulty memory? Got something like this once and then it was a memory module
> > that was broken. Try and check it with memcheck86 (think I got the name
> > right :))
>
> If memtest86+ doesn't show anything, then try a more arduous memory test like
> so:
>
> http://people.redhat.com/dledford/memtest.html

Memtest worked fine (or at least I guess it did), but I'll keep your
suggestion in mind if this night's memtest yields nothing.
>
> PS. Before you start spending time on memory tests I'd first try it on the
> console with no X gui running at all and see what gives.

I already tried running no X and it still failed. I am starting to
wonder if there is some other problem, too.

Thanks,
Vlad

-- 
How's my English? How about my Netiquette?
Do mail me if something is wrong with my behaviour. Thank you.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] GCC Failing

[Naga]

On Monday 22 January 2007 18:33, Vlad Dogaru wrote:
[...]
> PS: Unless I got it wrong, it's memtest86 and it proved very valuable.
> By the way, does it ever stop? After two hours and 13 thousand errors
> I got fed up and removed the chip.

Not sure :( It was some time since I used it but if I remember correctly it 
was self instructing so it should be stated somewhere.

> --
> How's my English? How about my Netiquette?
Btw. a signature separator should be "-- " as in dash dash space.

-- 
Naga
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] GCC Failing

[Randy Barlow]

On Mon, 2007-01-22 at 19:33 +0200, Vlad Dogaru wrote:
> (presumably good -- only let
> memtest run for about 3 minutes)

You should probably test it much longer than 3 minutes before you can be
confident that the 256 MB chip doesn't have issues...

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] GCC Failing

[David Relson]

On Mon, 22 Jan 2007 19:33:11 +0200
Vlad Dogaru wrote:

...[snip]...

> PS: Unless I got it wrong, it's memtest86 and it proved very valuable.
> By the way, does it ever stop? After two hours and 13 thousand errors
> I got fed up and removed the chip.

Nope.  It'll run forever, assuming you're patient enough :->
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] GCC Failing

[Pierre-Yves Rofes]

On Mon, January 22, 2007 8:49 pm, Randy Barlow wrote:
> On Mon, 2007-01-22 at 19:33 +0200, Vlad Dogaru wrote:
>> (presumably good -- only let
>> memtest run for about 3 minutes)
>
> You should probably test it much longer than 3 minutes before you can be
> confident that the 256 MB chip doesn't have issues...
>

Indeed, 1 hour is the bare minimum for a memtest, and ideally
you should let it run for about 7-8 hours (during one night for exemple)...

-- 
Pierre-Yves Rofes


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] GCC Failing

[Vlad Dogaru]

On 1/23/07, Pierre-Yves Rofes <gentoo@rofes.fr> wrote:
>
> On Mon, January 22, 2007 8:49 pm, Randy Barlow wrote:
> > On Mon, 2007-01-22 at 19:33 +0200, Vlad Dogaru wrote:
> >> (presumably good -- only let
> >> memtest run for about 3 minutes)
> >
> > You should probably test it much longer than 3 minutes before you can be
> > confident that the 256 MB chip doesn't have issues...
> >
>
> Indeed, 1 hour is the bare minimum for a memtest, and ideally
> you should let it run for about 7-8 hours (during one night for exemple)...

Well, I tested it all last night and still came up with no failures. I
have tried booting into Windows (yuck) and it works reasonably well so
I am guessing a problem with my Gentoo installation. I wanted to do a
complete reinstall of everything (mostly due to swapping my hard
drives), so I can live with the situation for the time being.

Thanks to everyone who helped-- I probably would have ended up with a
specialist just for this faulty memory.

Cheers,
Vlad

-- 
How's my English? How about my Netiquette?
Do mail me if something is wrong with my behaviour. Thank you.
-- 
gentoo-user@gentoo.org mailing list