From owner-freebsd-mobile@FreeBSD.ORG Wed Jul 21 12:25:45 2004 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1902216A4CE; Wed, 21 Jul 2004 12:25:45 +0000 (GMT) Received: from zombie.ezone.ru (zombie.ezone.ru [195.128.162.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id B992543D3F; Wed, 21 Jul 2004 12:25:41 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from [172.16.4.26] (ultra.domain [172.16.4.26] (may be forged)) by zombie.ezone.ru (8.12.11/8.12.11) with ESMTP id i6LBImvK063531; Wed, 21 Jul 2004 15:18:49 +0400 (MSD) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <40FE5118.3040900@mcsi.pp.ru> Date: Wed, 21 Jul 2004 15:18:48 +0400 From: Maxim Maximov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: Brian Fundakowski Feldman References: <40FE0DF3.4030008@anobject.com> <40FE1576.10206@elischer.org> <20040721102420.GE1009@green.homeunix.org> In-Reply-To: <20040721102420.GE1009@green.homeunix.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 12:25:45 -0000 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 -- Maxim Maximov