From owner-freebsd-mobile@FreeBSD.ORG Wed Jul 21 15:10:04 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 13BAD16A4CE; Wed, 21 Jul 2004 15:10:04 +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 i6LFA3Tg096694; Wed, 21 Jul 2004 11:10:03 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i6LFA2C7096693; Wed, 21 Jul 2004 11:10:02 -0400 (EDT) (envelope-from green) Date: Wed, 21 Jul 2004 11:10:01 -0400 From: Brian Fundakowski Feldman To: Maxim Maximov Message-ID: <20040721151001.GH1009@green.homeunix.org> References: <40FE0DF3.4030008@anobject.com> <40FE1576.10206@elischer.org> <20040721102420.GE1009@green.homeunix.org> <40FE5118.3040900@mcsi.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FE5118.3040900@mcsi.pp.ru> User-Agent: Mutt/1.5.6i cc: Jake Hamby cc: Julian Elischer cc: freebsd-current@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: Using -current on a Fujitsu Lifebook N5010 (no Atheros 802.11, no Ethernet, + hard freezes) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 15:10:04 -0000 On Wed, Jul 21, 2004 at 03:18:48PM +0400, Maxim Maximov wrote: > Brian Fundakowski Feldman wrote: > > >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. > > What are you guys all smoking? 64BTT stands for "64 bit time_t" > http://www.freebsd.org/cgi/cvsweb.cgi/src/UPDATING.64BTT Haha; never believe everything you read I suppose. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\