From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 10:24:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 874FB16A4CE; Wed, 21 Jul 2004 10:24:24 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i6LAONsP094971; Wed, 21 Jul 2004 06:24:23 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i6LAOKVw094970; Wed, 21 Jul 2004 06:24:20 -0400 (EDT) (envelope-from green) Date: Wed, 21 Jul 2004 06:24:20 -0400 From: Brian Fundakowski Feldman To: Julian Elischer Message-ID: <20040721102420.GE1009@green.homeunix.org> References: <40FE0DF3.4030008@anobject.com> <40FE1576.10206@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FE1576.10206@elischer.org> User-Agent: Mutt/1.5.6i cc: Jake Hamby cc: freebsd-mobile@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Using -current on a Fujitsu Lifebook N5010 (no Atheros 802.11, no Ethernet, + hard freezes) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 10:24:25 -0000 On Wed, Jul 21, 2004 at 12:04:22AM -0700, Julian Elischer wrote: > Jake Hamby wrote: > > 3) Random freezes > > > > > After an average of 30-40 minutes of heavy usage, I get random system > > freezes. I am typically running XFree86 and downloading something > > or reading web pages at the time it happens. More disturbingly, I am > > occasionally seeing files get renamed, for example > > /usr/src/UPDATING.64BIT became /usr/src/UPDATING.64BTT. This happens > > with or without WITNESS, with INVARIANTS enabled, with or without > > ACPI, and with or without SMP. I am using SCHED_ULE and no > > PREEMPTION. > > you are not alone.. I think you just chose a bad moment to > jump into -current > :-/ Who else is getting random memory corruption? I've only ever seen it in my life with bad RAM/bad cooling, but this could be bad anything, including something spamming random addresses with DMA. The characters 'I' and 'T' are far enough apart such that I wouldn't expect a simple memory error which usually seems to appear as a single bit flip. I don't think this is normal at all. Try burning memtest86 to a floppy or CD to ascertain a a bit more about your hardware, first. If it's a piece of hardware randomly DMAing around, taht's certainly pretty terrible. It would be awesome if someone had a utility to map all of the memory in a running system out into a format showing who allocated it, and what it's doing (contigmalloc, malloc, zone, user, free, cached memory information). I would think if you knew the memory getting corrupted and what was reasonably close to it, you could make some guesses as to what's doing it. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\