From: "Samium Gromoff" <_deepfire@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: strange gcc crashes...
Date: Mon, 13 Aug 2001 15:55:24 +0400 [thread overview]
Message-ID: <E15WGJY-000Ecx-00@f12.port.ru> (raw)
at Aug 11, 01 06:51:15 PM +0000 Mark Hahn wrote:
>> so it seems to me like kernel problem...
>
>why is that? I've never seen a sig11 from production >code
>that wasn't caused by flakey ram. in fact, your >descriptions
>are a perfect example of similar hardware problems.
and some other people told me about cpu overheating...
but 55 minutes long memtest run showed no problems et al
with cpu (P166-nonMMX-oc`ed to 180) staying warm, not by any means hot
on mobo Zida 5DVX.
maybe 55 min is not enough for proper mem testing?
---
cheers,
Samium Gromoff
next reply other threads:[~2001-08-13 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 11:55 Samium Gromoff [this message]
2001-08-13 12:04 ` Rasmus Andersen
2001-08-13 12:56 ` Nicholas Knight
2001-08-13 19:26 ` Josh McKinney
-- strict thread matches above, loose matches on Subject: below --
2001-08-11 14:58 Samium Gromoff
2001-08-11 15:16 ` Ignacio Vazquez-Abrams
2001-08-11 18:38 ` Horst von Brand
2001-08-11 16:42 ` J.H.M. Dassen (Ray)
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=E15WGJY-000Ecx-00@f12.port.ru \
--to=_deepfire@mail.ru \
--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®