From owner-freebsd-current Mon Dec 16 14:27: 9 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 35B2537B404; Mon, 16 Dec 2002 14:27:08 -0800 (PST) Received: from smtp0.libero.it (smtp0.libero.it [193.70.192.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FBD843E4A; Mon, 16 Dec 2002 14:27:07 -0800 (PST) (envelope-from flag@libero.it) Received: from newluxor.skynet.org (151.29.206.39) by smtp0.libero.it (6.7.015) id 3DE22A340097F252; Mon, 16 Dec 2002 23:27:05 +0100 Received: by newluxor.skynet.org (Postfix, from userid 1001) id 8C8DF33; Mon, 16 Dec 2002 23:25:05 +0100 (CET) Date: Mon, 16 Dec 2002 23:25:05 +0100 From: Paolo Pisati To: Marc Fonvieille Cc: FreeBSD_Current Subject: Re: 5.0-RC1: X server crash Message-ID: <20021216222505.GA1668@newluxor.skynet.org> References: <20021216035427F.hanche@math.ntnu.no> <20021216090855.GA558@nosferatu.blackend.org> <20021216180700.GA855@newluxor.skynet.org> <20021216205509.GE558@nosferatu.blackend.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021216205509.GE558@nosferatu.blackend.org> User-Agent: Mutt/1.4i X-Useless-Header: Look ma, it's a # sign! X-Operating-System: FreeBSD newluxor.skynet.org 5.0-RC FreeBSD 5.0-RC 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 On Mon, Dec 16, 2002 at 09:55:09PM +0100, Marc Fonvieille wrote: > > We talked about a problem between X and -CURRENT, we had no problem > with -STABLE. A problem that MAYBE is still present even in CURRENT, don't you think? As i said, i don't have my laptop right now, so i couldn't test CURRENT on it ( but i'll do it ASAP ), and i was looking for someone else with the same problem... > Btw I don't see how memtest can report memory corruption, I thought it > was to test "hardware" problem. hardware problem? VERY strange, cause IF i load the agp module i got errors from memtest, system freeze&crash, then if i disable the agp module, memtest reports 0 errors (even after hours&hours of test), no crash&freeze, etcetc As you can it doesn't look like an hardware problem, i think it's a FreeBSD-related problem, probably toggled by the agp && drm stuff more when i'll get my laptop back... -- Paolo Italian FreeBSD User Group: http://www.gufi.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message