From owner-freebsd-stable@FreeBSD.ORG Thu Sep 11 02:16:06 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D52B116A4BF for ; Thu, 11 Sep 2003 02:16:06 -0700 (PDT) Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAA9B43F3F for ; Thu, 11 Sep 2003 02:16:05 -0700 (PDT) (envelope-from Jan.Grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Thu, 11 Sep 2003 10:15:58 +0100 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 19xNWh-0007VE-00; Thu, 11 Sep 2003 10:14:07 +0100 Date: Thu, 11 Sep 2003 10:14:07 +0100 (BST) From: Jan Grant X-X-Sender: cmjg@mail.ilrt.bris.ac.uk To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Jan Grant Subject: Memory corruption with recent kernels? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2003 09:16:06 -0000 I've had problems with post-August kernels. Under load, builds are dying. I see lots of these: Sep 10 17:56:17 tribble /kernel: pid 60715 (make), uid 0: exited on signal 4 (core dumped) Sep 10 17:56:21 tribble /kernel: pid 61489 (make), uid 0: exited on signal 11 (core dumped) Sep 10 17:56:29 tribble /kernel: pid 63495 (sh), uid 0: exited on signal 4 (core dumped) Sep 10 17:56:29 tribble /kernel: pid 63461 (make), uid 0: exited on signal 4 (core dumped) ... for example, this was during a run of portsdb -fUu. Now, this surely looks like flaky memory to me. Unfortunately, I can only reproduce this problem with recent kernels (messages above are from a Sept-10 update); however, I _can_ reliably trigger these problems. Rolling back to a Jul 29 kernel means these issues no longer show up. I've had memtest slog away on this machine for 48 hours (not 100% proof, of course, but some indication that it might be a software flaw). Kernel's a GENERIC one running on a P4 with 512MB of memory. Obviously this might just really be a dodgy bit or two that happen to fall into the wrong spot under new kernels. I'll swap out the memory and see if the problem re-occurs; I'm reporting here at the same time in case anyone else is seeing this. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ YKYBPTMRogueW... you try to move diagonally in vi.