From: nakai <nakai@neo.shinko.co.jp>
To: Sven.Riedel@tu-clausthal.de, kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.14 Oops during boot (KT133A Problem?)
Date: Mon, 26 Nov 2001 09:40:31 +0900 [thread overview]
Message-ID: <3C018F7F.FBEDCAAE@neo.shinko.co.jp> (raw)
In-Reply-To: <20011115021142.A12923@moog.heim1.tu-clausthal.de> <20011124185408.A13437@moog.heim1.tu-clausthal.de>
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 =-=-=-=-
next prev parent reply other threads:[~2001-11-26 0:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2001-11-22 15:47 Sven.Riedel
2001-11-28 10:50 PVotruba
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=3C018F7F.FBEDCAAE@neo.shinko.co.jp \
--to=nakai@neo.shinko.co.jp \
--cc=Sven.Riedel@tu-clausthal.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®