Re: [gentoo-user] gcc seg faults very often
No, the memory is wasted. :( 2005/8/24, Raphael Melo de Oliveira Bastos Sales <[EMAIL PROTECTED]>: > I'll test the memory chip on another computer and see if it works... > > 2005/8/23, Volker Armin Hemmann <[EMAIL PROTECTED]>: > > On Wednesday 24 August 2005 02:16, Raphael Melo de Oliveira Bastos Sales > > wrote: > > > Yes, I found a kernel patch that does that. It allocates all the bad > > > memory sectors in kernel space permanetely, so they can't be used. > > > But, I found it too late. The memory is so bad now that it doesn't > > > even tries to boot. It just stops after detecting all IDE devices. > > > Gonna have to buy new memory boards... > > > > > > > when your ram becomes worse in some few days, there is a great chance, that > > not the ram, but the PSU is the culprit. > > > > When a PSU is becoming weak, it is not able to hold the voltages at > > sufficient > > levels - lockups and ram-errors are then common problems. > > -- > > gentoo-user@gentoo.org mailing list > > > > > -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
I'll test the memory chip on another computer and see if it works... 2005/8/23, Volker Armin Hemmann <[EMAIL PROTECTED]>: > On Wednesday 24 August 2005 02:16, Raphael Melo de Oliveira Bastos Sales > wrote: > > Yes, I found a kernel patch that does that. It allocates all the bad > > memory sectors in kernel space permanetely, so they can't be used. > > But, I found it too late. The memory is so bad now that it doesn't > > even tries to boot. It just stops after detecting all IDE devices. > > Gonna have to buy new memory boards... > > > > when your ram becomes worse in some few days, there is a great chance, that > not the ram, but the PSU is the culprit. > > When a PSU is becoming weak, it is not able to hold the voltages at sufficient > levels - lockups and ram-errors are then common problems. > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
On Wednesday 24 August 2005 02:16, Raphael Melo de Oliveira Bastos Sales wrote: > Yes, I found a kernel patch that does that. It allocates all the bad > memory sectors in kernel space permanetely, so they can't be used. > But, I found it too late. The memory is so bad now that it doesn't > even tries to boot. It just stops after detecting all IDE devices. > Gonna have to buy new memory boards... > when your ram becomes worse in some few days, there is a great chance, that not the ram, but the PSU is the culprit. When a PSU is becoming weak, it is not able to hold the voltages at sufficient levels - lockups and ram-errors are then common problems. -- gentoo-user@gentoo.org mailing list
Re: Re: [gentoo-user] gcc seg faults very often
Yes, I found a kernel patch that does that. It allocates all the bad memory sectors in kernel space permanetely, so they can't be used. But, I found it too late. The memory is so bad now that it doesn't even tries to boot. It just stops after detecting all IDE devices. Gonna have to buy new memory boards... if anyone ever need it: http://rick.vanrein.org/linux/badram/ 2005/8/23, Michael Kintzios <[EMAIL PROTECTED]>: > > From:: Eugene Rosenzweig <[EMAIL PROTECTED]> > > To: gentoo-user@lists.gentoo.org > > Subject: Re: [gentoo-user] gcc seg faults very often > > Date: Wed, 24 Aug 2005 01:03:01 +1000 > > > Raphael Melo de Oliveira Bastos Sales wrote: > > > > >After running memtest, several errors have occurred. Does that mean I > > >have to buy new memory? > > > > > >2005/8/22, Volker Armin Hemmann <[EMAIL PROTECTED] al.de>: > > > > > > > > >>On Monday 22 August 2005 21:29, Raphael Melo de Oliveira Bastos Sales > > >>wrote: > > >> > > >> > > >>>Hi Richard, > > >>> > > >>>First of all, thanks for replying. I'll test the swap partition > > >>>with the command you sent. But how do I test the memory? Is there any > > >>>way to do it? I think I configured CMOS to do a memory check during > > >>>start up. > > >>> > > >>> > > >>> > > >>please install memtest86 or memtest86+ and let it run for some others. > > >> > > >>gcc segfaults are a very good sign of memory problems - and please the > > >>bios-'check' is not a 'check' - never was! > > >> > > >>The bios counts the available memory - this is not a check but accounting. > > >>-- > > >>gentoo-user@gentoo.org mailing list > > >> > > >> > > You can check memory settings in the BIOS, most BIOSes nowadays have > > options to change memory timings so you can set more relaxed ones and > > see if the errors disappear. Also you can try good oldfashioned > > re-seating of the memory modules, take them out and insert them again. > > > > Eugene. > > I remember an application which would identify the bad memory cells and > isolate them so that your machine could happily carry on using the rest of > the memory - unfortunately just like yours my memory is not what it used to > be . . . ;-) > > I've googled but can't find it. > -- > Regards, > Mick > > Lycos email has now 300 Megabytes of free storage... Get it now at > mail.lycos.co.uk > -- gentoo-user@gentoo.org mailing list
Re: Re: [gentoo-user] gcc seg faults very often
> From:: Eugene Rosenzweig <[EMAIL PROTECTED]> > To: gentoo-user@lists.gentoo.org > Subject: Re: [gentoo-user] gcc seg faults very often > Date: Wed, 24 Aug 2005 01:03:01 +1000 > Raphael Melo de Oliveira Bastos Sales wrote: > > >After running memtest, several errors have occurred. Does that mean I > >have to buy new memory? > > > >2005/8/22, Volker Armin Hemmann <[EMAIL PROTECTED] al.de>: > > > > > >>On Monday 22 August 2005 21:29, Raphael Melo de Oliveira Bastos Sales wrote: > >> > >> > >>>Hi Richard, > >>> > >>>First of all, thanks for replying. I'll test the swap partition > >>>with the command you sent. But how do I test the memory? Is there any > >>>way to do it? I think I configured CMOS to do a memory check during > >>>start up. > >>> > >>> > >>> > >>please install memtest86 or memtest86+ and let it run for some others. > >> > >>gcc segfaults are a very good sign of memory problems - and please the > >>bios-'check' is not a 'check' - never was! > >> > >>The bios counts the available memory - this is not a check but accounting. > >>-- > >>gentoo-user@gentoo.org mailing list > >> > >> > You can check memory settings in the BIOS, most BIOSes nowadays have > options to change memory timings so you can set more relaxed ones and > see if the errors disappear. Also you can try good oldfashioned > re-seating of the memory modules, take them out and insert them again. > > Eugene. I remember an application which would identify the bad memory cells and isolate them so that your machine could happily carry on using the rest of the memory - unfortunately just like yours my memory is not what it used to be . . . ;-) I've googled but can't find it. -- Regards, Mick Lycos email has now 300 Megabytes of free storage... Get it now at mail.lycos.co.uk
Re: [gentoo-user] gcc seg faults very often
On Tuesday 23 August 2005 17:03, Eugene Rosenzweig wrote: > > You can check memory settings in the BIOS, most BIOSes nowadays have > options to change memory timings so you can set more relaxed ones and > see if the errors disappear. Also you can try good oldfashioned > re-seating of the memory modules, take them out and insert them again. > and if the errors stay with new ram, try a new PSU ;) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
Raphael Melo de Oliveira Bastos Sales wrote: After running memtest, several errors have occurred. Does that mean I have to buy new memory? 2005/8/22, Volker Armin Hemmann <[EMAIL PROTECTED]>: On Monday 22 August 2005 21:29, Raphael Melo de Oliveira Bastos Sales wrote: Hi Richard, First of all, thanks for replying. I'll test the swap partition with the command you sent. But how do I test the memory? Is there any way to do it? I think I configured CMOS to do a memory check during start up. please install memtest86 or memtest86+ and let it run for some others. gcc segfaults are a very good sign of memory problems - and please the bios-'check' is not a 'check' - never was! The bios counts the available memory - this is not a check but accounting. -- gentoo-user@gentoo.org mailing list You can check memory settings in the BIOS, most BIOSes nowadays have options to change memory timings so you can set more relaxed ones and see if the errors disappear. Also you can try good oldfashioned re-seating of the memory modules, take them out and insert them again. Eugene. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
After running memtest, several errors have occurred. Does that mean I have to buy new memory? 2005/8/22, Volker Armin Hemmann <[EMAIL PROTECTED]>: > On Monday 22 August 2005 21:29, Raphael Melo de Oliveira Bastos Sales wrote: > > Hi Richard, > > > > First of all, thanks for replying. I'll test the swap partition > > with the command you sent. But how do I test the memory? Is there any > > way to do it? I think I configured CMOS to do a memory check during > > start up. > > > > please install memtest86 or memtest86+ and let it run for some others. > > gcc segfaults are a very good sign of memory problems - and please the > bios-'check' is not a 'check' - never was! > > The bios counts the available memory - this is not a check but accounting. > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
I faced lockups problems during high mem/cpu/io conditions on another computer. Turned out to be the power source that was inadequate (is that how it is spelled?). Most motherboard simply reboot the system when close to overheating conditions. And they normally beep a lot before that happens. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
On 2005-08-22 10:57:47 -0400 (Mon, Aug), R'twick Niceorgaw wrote: > > I also had the same gcc segfault problem recently. After some observation, > I found out whenever cpu temperature goes beyond 50 C I was getting > segfaults. Took out the heat sink and cpu, cleaned them put some arctic > silver between cpu and heat sink and put a fan in front of the box and did > a emerge -Uv world without any problem even though temperature reached > 65. I believe, its the arctic silver that I put between cpu and heat sink > fixed my problem. I am in the middle of troubleshooting similiar (lockups, not segfaults) situation. Maybe it will be of some use to somebody. During some emerges my machine was getting locked up when cpu temperature got above 55 C (AMD Athlon 2GB), but I decided (yeah - decided ;-) that CPU is not the problem - 55 C is pretty low for CPU I think. As a workaround I have limited the RAM amount available (I have 512 MB physical) to 256 MB by kernel parameter mem=256M. No RAM errors were detected by memtest, but limiting available RAM works - no lockups. The 'sensors' utility (part of lm_sensors package) shows that one (out of two) temperature sensor is a bit too hot: it has now (no emerge in progress) 61 C and warning threshold is on 48 C. I assume that it is not CPU that gets too hot but that small, nice north bridge on my mobo. May it be that the solution is to get some bigger heat sink and more powerful fan not only for CPU. HTH -- No virus found in this outgoing message. Checked by "grep -i virus $MESSAGE" -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
Thanks to both R'twick and Volker. I'll try them out, tonight, after I take my girlfriend for pizza ;) 2005/8/22, R'twick Niceorgaw <[EMAIL PROTECTED]>: > On Mon, August 22, 2005 4:28 pm, Raphael Melo de Oliveira Bastos Sales said: > > Any good tools for checking temperature and other system stats? > > > > I use gkrellm2. Make sure you have the acpi (thermal, fan etc) modules > built and loaded for your kernel. > > -R'twick > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
On Mon, August 22, 2005 4:28 pm, Raphael Melo de Oliveira Bastos Sales said: > Any good tools for checking temperature and other system stats? > I use gkrellm2. Make sure you have the acpi (thermal, fan etc) modules built and loaded for your kernel. -R'twick -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
On Monday 22 August 2005 22:28, Raphael Melo de Oliveira Bastos Sales wrote: > Any good tools for checking temperature and other system stats? > lms_sensors + gkrellm, ksensors ... -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
I didn't know that. Good to learn. I'll use the memtest from the live cd, since I can install it without the compiler working well... 2005/8/22, Volker Armin Hemmann <[EMAIL PROTECTED]>: > On Monday 22 August 2005 21:29, Raphael Melo de Oliveira Bastos Sales wrote: > > Hi Richard, > > > > First of all, thanks for replying. I'll test the swap partition > > with the command you sent. But how do I test the memory? Is there any > > way to do it? I think I configured CMOS to do a memory check during > > start up. > > > > please install memtest86 or memtest86+ and let it run for some others. > > gcc segfaults are a very good sign of memory problems - and please the > bios-'check' is not a 'check' - never was! > > The bios counts the available memory - this is not a check but accounting. > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
Any good tools for checking temperature and other system stats? 2005/8/22, R'twick Niceorgaw <[EMAIL PROTECTED]>: > Hi Raphael, > > On Mon, August 22, 2005 3:29 pm, Raphael Melo de Oliveira Bastos Sales said: > > But how do I test the memory? > > memtest86 will do it. > > > >> > I'm using gcc-3.3.5.20050130-r1 and I keep getting segmentation > fault every now and then. > > I also had the same gcc segfault problem recently. After some observation, > I found out whenever cpu temperature goes beyond 50 C I was getting > segfaults. Took out the heat sink and cpu, cleaned them put some arctic > silver between cpu and heat sink and put a fan in front of the box and did > a emerge -Uv world without any problem even though temperature reached > 65. I believe, its the arctic silver that I put between cpu and heat sink > fixed my problem. > > HTH > R'twick > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
Hi Raphael, On Mon, August 22, 2005 3:29 pm, Raphael Melo de Oliveira Bastos Sales said: > But how do I test the memory? memtest86 will do it. >> > I'm using gcc-3.3.5.20050130-r1 and I keep getting segmentation fault every now and then. I also had the same gcc segfault problem recently. After some observation, I found out whenever cpu temperature goes beyond 50 C I was getting segfaults. Took out the heat sink and cpu, cleaned them put some arctic silver between cpu and heat sink and put a fan in front of the box and did a emerge -Uv world without any problem even though temperature reached 65. I believe, its the arctic silver that I put between cpu and heat sink fixed my problem. HTH R'twick -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
On Monday 22 August 2005 21:29, Raphael Melo de Oliveira Bastos Sales wrote: > Hi Richard, > > First of all, thanks for replying. I'll test the swap partition > with the command you sent. But how do I test the memory? Is there any > way to do it? I think I configured CMOS to do a memory check during > start up. > please install memtest86 or memtest86+ and let it run for some others. gcc segfaults are a very good sign of memory problems - and please the bios-'check' is not a 'check' - never was! The bios counts the available memory - this is not a check but accounting. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
Hi Richard, First of all, thanks for replying. I'll test the swap partition with the command you sent. But how do I test the memory? Is there any way to do it? I think I configured CMOS to do a memory check during start up. Also, I'm using -march=i686 -O2 -fomit-frame-pointer, since I don't know if a higher value is compatible with my AMD Sempron. 2005/8/22, Richard Fish <[EMAIL PROTECTED]>: > Raphael Melo de Oliveira Bastos Sales wrote: > > >Hi there, > > > > I'm using gcc-3.3.5.20050130-r1 and I keep getting segmentation > >fault every now and then. Since it doesn't work, I can't compile an > >earlier, more stable version. I hope it isn't a hardware failure, > >because the warranty on my new computer just ended. It is probably not > >an memory error, because I'm not using -pipe. I checked the filesystem > >and no corruption was found. > > > > > > Don't be so sure. -pipe doesn't add that much additional memory > overhead, in fact, only a few pages used as an IO buffer between the > processes. The process of compiling itself is very tough on memory, > reading and writing to various locations in rapid succession. > > I would say memory is the most likely problem, but it could be > overheating or power supply problems also. > > > Anybody had this type of error too? If so, how did you handle it? > >Are there any tools to check the hard drive's surface for flaws? > > > > > > Bad disk blocks are almost certainly not the issue, as you would end up > with IO errors during the compilation, not segfaults. Well, I guess if > your swap had bad blocks, you might get a segfault... > > Anyway, "dd if=/dev/hda of=/dev/null bs=4k" will test readability of > your entire disk. It doesn't test the validity of your data though... > > -Richard > > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] gcc seg faults very often
Raphael Melo de Oliveira Bastos Sales wrote: Hi there, I'm using gcc-3.3.5.20050130-r1 and I keep getting segmentation fault every now and then. Since it doesn't work, I can't compile an earlier, more stable version. I hope it isn't a hardware failure, because the warranty on my new computer just ended. It is probably not an memory error, because I'm not using -pipe. I checked the filesystem and no corruption was found. Don't be so sure. -pipe doesn't add that much additional memory overhead, in fact, only a few pages used as an IO buffer between the processes. The process of compiling itself is very tough on memory, reading and writing to various locations in rapid succession. I would say memory is the most likely problem, but it could be overheating or power supply problems also. Anybody had this type of error too? If so, how did you handle it? Are there any tools to check the hard drive's surface for flaws? Bad disk blocks are almost certainly not the issue, as you would end up with IO errors during the compilation, not segfaults. Well, I guess if your swap had bad blocks, you might get a segfault... Anyway, "dd if=/dev/hda of=/dev/null bs=4k" will test readability of your entire disk. It doesn't test the validity of your data though... -Richard -- gentoo-user@gentoo.org mailing list
