From: Ulf Carlsson <ulfc@thepuffingroup.com>
To: "William J. Earl" <wje@fir.engr.sgi.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Memory corruption
Date: Wed, 30 Jun 1999 04:47:02 +0200 [thread overview]
Message-ID: <19990630044702.A6969@thepuffingroup.com> (raw)
In-Reply-To: <199906300101.SAA09334@fir.engr.sgi.com>; from William J. Earl on Tue, Jun 29, 1999 at 06:01:47PM -0700
> > The compiler may stop working sometimes on certain files, giving bogus
> > error messages which I don't understand (the compiler is probably not the
> > only application affected). Running this program I just wrote forces the
> > corrupted caches to be flushed or something and ``fixes'' the problems:
> ...
>
> This problem sounds like a cache flushing problem. Do you also get
> SIGILL, SIGBUS, and SIGSEGV failures? One possibility is that the
> icache is not being flushed on a page fault, when a page is read in from
> disk, and the icache still has old data in it. This could lead to a
> cache line of bogus instructions being executed.
Sometimes when this happens I think I only get a SIGSEGV or a SIGBUS, otherwise
I get internal compiler errors. It's hard to say since these problems are very
hard to reproduce, and I forget what happens from time to time. I have
unfortunately not written down the results. It sounds like this may be the
cause of the type of file corruption I have when only a little part of the file
is damaged (sounds like the problem covers both icache and dcache). That type
of file corruption goes away after reboot. I haven't had a chance to try this
with my discard-disk-cache program since this happens very seldom..
> What model of CPU do you have in your machine?
I have a 133 MHz R4600 with 512kb board cache, 16kb dcache and 16kb icache.
Regards,
Ulf
next prev parent reply other threads:[~1999-06-30 2:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-22 1:39 Memory corruption Ulf Carlsson
1999-06-30 1:01 ` William J. Earl
1999-06-30 2:47 ` Ulf Carlsson [this message]
1999-06-30 22:01 ` William J. Earl
1999-07-01 0:23 ` Ralf Baechle
1999-07-01 0:53 ` William J. Earl
1999-07-01 11:25 ` Harald Koerfgen
1999-07-02 22:41 ` Ralf Baechle
1999-07-06 13:05 ` Ralf Baechle
1999-07-07 21:08 ` Harald Koerfgen
1999-07-08 1:51 ` Warner Losh
1999-07-08 3:12 ` William J. Earl
[not found] ` <37846EE7.EADD9E32@niisi.msk.ru>
1999-07-08 17:56 ` William J. Earl
1999-07-08 10:39 ` Ralf Baechle
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=19990630044702.A6969@thepuffingroup.com \
--to=ulfc@thepuffingroup.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=wje@fir.engr.sgi.com \
/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