From owner-freebsd-current Sat Jul 13 13:45: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 2939737B400 for ; Sat, 13 Jul 2002 13:45:43 -0700 (PDT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D9C643E81 for ; Sat, 13 Jul 2002 13:45:43 -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 C01CD2A7D6 for ; Sat, 13 Jul 2002 13:45:42 -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 7FB9A4C241 for ; Sat, 13 Jul 2002 13:45:42 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (Postfix) with ESMTP id C9B113811 for ; Sat, 13 Jul 2002 13:45:41 -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: <20020713042840.52B9B3811@overcee.wemm.org> Date: Sat, 13 Jul 2002 13:45:41 -0700 From: Peter Wemm Message-Id: <20020713204541.C9B113811@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: > 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. I believe I know what the problem is. I'll throw in a short term fix (yes, it only affects SMP boxes) and work on a real solution. 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