From: Florian Lohoff <flo@rfc822.org>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: atomic.h changes fixed bug Was: CVS Update@oss.sgi.com: linux
Date: Sun, 29 Oct 2000 17:47:32 +0100 [thread overview]
Message-ID: <20001029174732.D2663@paradigm.rfc822.org> (raw)
In-Reply-To: <20001029172517.C2663@paradigm.rfc822.org>; from flo@rfc822.org on Sun, Oct 29, 2000 at 05:25:17PM +0100
On Sun, Oct 29, 2000 at 05:25:17PM +0100, Florian Lohoff wrote:
> On Thu, Oct 26, 2000 at 04:59:17PM -0700, Ralf Baechle wrote:
> > CVSROOT: /home/pub/cvs
> > Module name: linux
> > Changes by: ralf@oss.sgi.com 00/10/26 16:59:17
> >
> > Modified files:
> > include/asm-mips: atomic.h
> > include/asm-mips64: atomic.h
> >
> > Log message:
> > Add memory clobbers to the atomic_*_return functions. I hope this
> > fixes the file corruption / `D' state processes people observe.
>
> This at least fixes the file corruption stuff i have been seeing
> (Never The Same Checksum aka NTSC)
I was to quick ... It seems to be partially fixed ...
flo@remake:~$ md5sum xfree86_4.0.1.orig.tar.gz
e91fa9fbda045965f12a49def8cafb3a xfree86_4.0.1.orig.tar.gz
flo@remake:~$ md5sum xfree86_4.0.1.orig.tar.gz
06f1bb64a75cf475dfbbde5bb28d8420 xfree86_4.0.1.orig.tar.gz
flo@remake:~$ md5sum xfree86_4.0.1.orig.tar.gz
ade38e19b446a6432f9424994840a699 xfree86_4.0.1.orig.tar.gz
flo@remake:~$ md5sum xfree86_4.0.1.orig.tar.gz
8495ab01d5bd2047311e38d0a7612882 xfree86_4.0.1.orig.tar.gz
flo@remake:~$ pwd
/home2/flo
flo@remake:~$ md5sum /home/flo/xfree86_4.0.1.orig.tar.gz
590767187e145407bcda582facf5afc0 /home/flo/xfree86_4.0.1.orig.tar.gz
flo@remake:~$ md5sum /home/flo/xfree86_4.0.1.orig.tar.gz
590767187e145407bcda582facf5afc0 /home/flo/xfree86_4.0.1.orig.tar.gz
flo@remake:~$ md5sum /home/flo/xfree86_4.0.1.orig.tar.gz
590767187e145407bcda582facf5afc0 /home/flo/xfree86_4.0.1.orig.tar.gz
flo@remake:~$ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sda1 762860 634544 89564 88% /
/dev/sdb1 2079044 50668 1922764 3% /home2
So it seems there is still some problem in some i/o stuff concerning
the different disk ...
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
next prev parent reply other threads:[~2000-10-29 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001026235921Z553785-493+346@oss.sgi.com>
2000-10-29 16:25 ` atomic.h changes fixed bug Was: CVS Update@oss.sgi.com: linux Florian Lohoff
2000-10-29 16:47 ` Florian Lohoff [this message]
2000-10-30 1:17 ` Ralf Baechle
2000-10-30 6:35 ` Klaus Naumann
2000-10-30 21:14 ` Ralf Baechle
2000-10-30 10:39 ` Florian Lohoff
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=20001029174732.D2663@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.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