From owner-freebsd-current Fri Jul 12 21:28:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72E0337B400 for ; Fri, 12 Jul 2002 21:28:41 -0700 (PDT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2866E43E31 for ; Fri, 12 Jul 2002 21:28:41 -0700 (PDT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id B41AC2A7F2 for ; Fri, 12 Jul 2002 21:28:40 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 679634C28B for ; Fri, 12 Jul 2002 21:28:40 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (Postfix) with ESMTP id 52B9B3811 for ; Fri, 12 Jul 2002 21:28:40 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: current@freebsd.org Subject: Re: HEADS UP, beware of pmap changes. In-Reply-To: <20020712092941.B03793811@overcee.wemm.org> Date: Fri, 12 Jul 2002 21:28:40 -0700 From: Peter Wemm Message-Id: <20020713042840.52B9B3811@overcee.wemm.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Wemm wrote: > This is mostly a FYI because I do not expect major problems this time. > I have been extensively testing it in a handful of configurations. As murphy would dictate, something fishy is going on. In the last 12 hours or so (I had a long sleep), I've started getting apparent memory corruption - although it only seems visible to userland. The usual symptom is that gas gets blocks of memory clobbered with 0xd0d0d0d0 (yes, the same fill pattern used in phkmalloc). This is highly suspicious. I'll keep everybody informed once I've narrowed down when it started breaking. My test machines had one last cvs update/merge conflicts/compile/reboot before commit. I hope I didn't fat-finger merging the conflicts or something silly right before commit. I have only seen it happen occasionally on one SMP box, the others appear OK. I have not seen problems show up on UP at all. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message