From: PVotruba@Chemoprojekt.cz
To: nakai@neo.shinko.co.jp, Sven.Riedel@tu-clausthal.de
Cc: linux-kernel@vger.kernel.org
Subject: RE: 2.4.14 Oops during boot (KT133A Problem?)
Date: Wed, 28 Nov 2001 11:50:32 +0100 [thread overview]
Message-ID: <35E64A70B5ACD511BCB0000000004CA10BD4FA@NT_CHEMO> (raw)
the memory check in bios is designed mostly for testing if (detected
memory chips == present memory chips).
Safe comprehensive checking can be done by memtest86, and virtualy
unsafe testing can be cyclic kernel compilation (if you notice strange
compile errors at same kernel config but at different moments, you can
suspect that your hardware is rotten).
To: Sven
are you sure that ALL your memory chips are bad? how about memory
latency and other bios settings, overclocking, etc.? try to setup your box
to run at slowest memory configuration as possible. It's hard to believe
that all of your chips are gone.
Regards
Petr
----- previous message follows:
> Congratulations!
>
> Sven.Riedel@tu-clausthal.de wrote:
> > Well, the problem got solved (although not in a way I'd consider
> > satisfactory). After my machine started random segfaulting the day
> > before yesterday, I memcheck86'ed it again (the last check is a mere two
> > months ago), and lo - all three RAM chips were broken. Unfortunately, I
> > discovered this, after this broken RAM caused my /usr partition to go
> > fubar, resulting in me spending yesterday with a nice little reinstall.
> > After the reinstall, 2.4.14 booted fine off the harddisk. No more
> > oopses.
>
> During this holidays, I guessed, and I thought it because of
> harddisk or PCI chip erro. Memory error! Was it found when booting
> matherboard by BIOS? I think motherboard always check memories when
> booting.
>
> --
> -=-=-=-= SHINKO ELECTRIC INDUSTRIES CO., LTD. =-=-=-=-
> =-=-=-=- Core Technology Research & Laboratory, -=-=-=-=
> -=-=-=-= Infomation Technology Research Dept. =-=-=-=-
> =-=-=-=- Name:Hisakazu Nakai TEL:026-283-2866 -=-=-=-=
> -=-=-=-= Mail:nakai@neo.shinko.co.jp FAX:026-283-2820 =-=-=-=-
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-11-28 10:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 10:50 PVotruba [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-22 15:47 Sven.Riedel
2001-11-15 1:11 Sven.Riedel
2001-11-15 2:40 ` nakai
2001-11-15 3:28 ` Sven.Riedel
2001-11-15 8:03 ` nakai
2001-11-15 10:22 ` Sven.Riedel
2001-11-15 23:59 ` nakai
[not found] ` <20011116202230.A890@moog.heim1.tu-clausthal.de>
2001-11-19 23:31 ` nakai
2001-11-19 16:11 ` bill davidsen
2001-11-19 22:48 ` Sven.Riedel
2001-11-24 17:54 ` Sven.Riedel
2001-11-26 0:40 ` nakai
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=35E64A70B5ACD511BCB0000000004CA10BD4FA@NT_CHEMO \
--to=pvotruba@chemoprojekt.cz \
--cc=Sven.Riedel@tu-clausthal.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nakai@neo.shinko.co.jp \
/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
all inboxes | Powered by JetHome®