From: Raphael Melo de Oliveira Bastos Sales <raphael.melo21@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: Re: [gentoo-user] gcc seg faults very often
Date: Tue, 23 Aug 2005 21:16:23 -0300 [thread overview]
Message-ID: <8f7a9d58050823171615d86985@mail.gmail.com> (raw)
In-Reply-To: <54093671718268@lycos-europe.com>
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 <michaelkintzios@lycos.co.uk>:
> > From:: Eugene Rosenzweig <eugene259@internode.on.net>
> > 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 <volker.armin.hemmann@tu-claustha 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
next prev parent reply other threads:[~2005-08-24 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 21:24 Re: [gentoo-user] gcc seg faults very often Michael Kintzios
2005-08-24 0:16 ` Raphael Melo de Oliveira Bastos Sales [this message]
2005-08-24 2:53 ` Volker Armin Hemmann
2005-08-24 13:04 ` Raphael Melo de Oliveira Bastos Sales
2005-08-24 16:18 ` Raphael Melo de Oliveira Bastos Sales
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f7a9d58050823171615d86985@mail.gmail.com \
--to=raphael.melo21@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox