From owner-freebsd-smp Tue Aug 20 14:37:26 2002 Delivered-To: freebsd-smp@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id D9DA537B400; Tue, 20 Aug 2002 14:37:23 -0700 (PDT) Date: Tue, 20 Aug 2002 14:37:23 -0700 From: David O'Brien To: smp@freebsd.org Subject: (FWD) -current data corruption Message-ID: <20020820143723.A85243@hub.freebsd.org> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Operating-System: FreeBSD 4.6-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This seems to only happen on SMP machines. Any insight? ----- Forwarded message from Alfred Perlstein ----- Subject: -current data corruption Date: Mon, 19 Aug 2002 21:32:58 -0700 If anyone is interested both David O'Brien and I are experiencing what looks like data corruption under -current. On a dual SMP AMD 1.9ghz box I'm seeing the vim port somehow corrupt patched files. I really don't have the time or energy to backtrack -current to figure out when or why this started happening. At first I thought it had to deal with pipes, but afaik the vim port doesn't patch files, it just does this: /usr/bin/patch -d /vol/share/ports/editors/vim/work/vim61/ --forward --quiet -E -p0 < $i for each patchfile in the port. Please CC me, as I'm not subscribed to this list. -- -Alfred Perlstein [alfred@freebsd.org] [#bsdcode/efnet/irc.prison.net] ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message