From owner-freebsd-current Sun Dec 8 16:11: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 3BB0637B401 for ; Sun, 8 Dec 2002 16:11:45 -0800 (PST) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id C050643EA9 for ; Sun, 8 Dec 2002 16:11:44 -0800 (PST) (envelope-from wa1ter@hotmail.com) Received: from hotmail.com wa1ter@smtp-send.myrealbox.com [67.114.255.162] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.21 $ on Novell NetWare via secured & encrypted transport (TLS); Sun, 08 Dec 2002 17:11:44 -0700 Message-ID: <3DF3D9E3.8070009@hotmail.com> Date: Sun, 08 Dec 2002 15:46:43 -0800 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021127 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: Sound familiar? 5.0-RC hangs on dual athlon References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 Jacques A. Vidrine wrote: > Hello All, > > I finally managed to put some time aside to redo my main > development/desktop machine to run FreeBSD 5.0. (I've been running > 5.x on my laptop for some months.) I had to retreat back to 4.7 > because I could not get through some simple tasks without the system > hanging. The system is a dual Athlon box with 1 GB RAM. The dmesg > output is below. > > At first the system hung while I was building GNOME 2.0 and restoring > some files from tape. It wasn't _completely_ hung: I could switch > VTYs, and enter new commands (though it might take tens of seconds to > echo my typing... I seem to remember something similar from a few months ago that affected machines with lots of RAM because of something to do with high order address bits. I thought it got fixed, but I can't really recall. Was it an Athlon problem, or a gcc problem, or both? Hmpf, can't remember! Anyone else think this might be the same thing? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message