My laptop has been doing weird stuff lately. I built it a while ago from Gentoo 2006.0 Stage 3, and every now and again it would turn off while compiling something (usually if I had to upgrade glibc). I was just trying to update mythtv and it crashed so I decided to level it and start from scratch. I installed Gentoo 2006.1 Stage 3 and it's doing the same thing. I went down to Stage 2 and I'm still having a problem. I've done memtest in the past with clean results, but I'm stuck because I don't know what the error is. While building a few minutes ago I forgot to turn on swap space and it ran out of memory before crashing (turning off). Is there anything I can do aside from piping the output to a file to capture what the problem might be (tried it, not much help)? Has anybody had similar problems with gcc / glibc? Thanks in advance Eric
On Saturday 23 December 2006 19:08, Eric Martin wrote:
Is there anything I can do aside from piping the output to a file to capture what the problem might be (tried it, not much help)?
it depends on the error if gcc is randomly ICEing, then it can commonly be caused by: - not enough physical ram - flaky hardware - flaky ram - cpu overheating the exact error message would point in the direction -mike
From: Mike Frysinger <vapier@gentoo.org>
if gcc is randomly ICEing,
What's that then? ICE seems to be an acronym, but for what? The jargon file (Hacker's Dictionary) tells me what I already knew, that ICE means Intrusion Counter-measure Electronics in some fiction I read long ago, but this doesn't seem to have anything to do with your usage. Further search reveals some kind of graphic hardware or company called ICE, but the PCI graphic card is in a different thread. So what is ICE? This could be your chance to get your entry in the jargon file, and if it becomes the next big catch-phrase you might even bargain to exchange the IP for some free advice. -- Keith
On Sunday 24 December 2006 19:32, Keith Wright wrote:
From: Mike Frysinger <vapier@gentoo.org>
if gcc is randomly ICEing,
What's that then? ICE seems to be an acronym
it's a gcc term: Internal Compiler Error
This could be your chance to get your entry in the jargon file, and if it becomes the next big catch-phrase you might even bargain to exchange the IP for some free advice.
the thing run by esr ? yeah i could care less :p -mike
From: Mike Frysinger <vapier@gentoo.org>
On Sunday 24 December 2006 19:32, Keith Wright wrote:
From: Mike Frysinger <vapier@gentoo.org>
if gcc is randomly ICEing,
What's that then? ICE seems to be an acronym
it's a gcc term: Internal Compiler Error
Thank you, though this is a bit disapointing. I was hoping it meant Inexplicable Computer Error, or something else more general purpose.
This could be your chance to get your entry in the jargon file, and if it becomes the next big catch-phrase you might even bargain to exchange the IP for some free advice.
the thing run by esr ? yeah i could care less :p
I'm guessing you couldn't care very much less without going negative. I was about to object that the jargon file is older than ESR, but that's not strictly true. In any case, he does run it, by the "You touch it, you own it" Hacker rule of IP. (Which is very different from the Lawyer's rule. They never have to Fix the Damned Thing.) Just for that, no free advice for you. -- Keith
Eric Martin wrote:
My laptop has been doing weird stuff lately. I built it a while ago from Gentoo 2006.0 Stage 3, and every now and again it would turn off while compiling something (usually if I had to upgrade glibc). I was just trying to update mythtv and it crashed so I decided to level it and start from scratch. I installed Gentoo 2006.1 Stage 3 and it's doing the same thing. I went down to Stage 2 and I'm still having a problem. I've done memtest in the past with clean results, but I'm stuck because I don't know what the error is. While building a few minutes ago I forgot to turn on swap space and it ran out of memory before crashing (turning off).
Is there anything I can do aside from piping the output to a file to capture what the problem might be (tried it, not much help)? Has anybody had similar problems with gcc / glibc?
Thanks in advance Eric
My laptop will turn it self off if the temperature gets above 70C. Most laptops have some kind of temperature shut off function.. I would monitor your temperature with lmsensors, or mbmon (acpi temp zone). For me to control my Gentoo laptop temperature while compiling big packages, I have to have cpu frequency scaling running. If i run my 2.8ghz P4 laptop at 50% speed 1.4Ghz I don't have any temperature problems. I usually use the "powersave" or "ondemand" shedulers. Also you could try keeping a big enough space blow your laptop for air.. Assuming the temperature is the problem. -- -- Karl Hiramoto http://karl.hiramoto.org/ US VOIP: (1) 603.966.4448 Spain Casa (34) 951.273.347 Spain Mobil (34) 617.463.826 Yahoo_IM = karl_hiramoto GTalk= karl.hiramoto [at] gmail [d0t] com -- The most exciting phrase to hear in science, the one that heralds new discoveries, is not "Eureka!" (I found it!) but "That's funny ..." -- Isaac Asimov
participants (4)
-
Eric Martin -
Karl Hiramoto -
Keith Wright -
Mike Frysinger