From owner-freebsd-questions@FreeBSD.ORG Thu Apr 10 02:52:23 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B4E737B401; Thu, 10 Apr 2003 02:52:23 -0700 (PDT) Received: from mx1.lphp.org (APastourelles-107-1-8-148.abo.wanadoo.fr [217.128.252.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id A081A43F85; Thu, 10 Apr 2003 02:52:21 -0700 (PDT) (envelope-from ajacoutot@lphp.org) Received: from CPQ19567200651 (lyon-1-a7-62-147-17-108.dial.proxad.net [62.147.17.108]) by mx1.lphp.org (8.12.8p1/8.12.8) with SMTP id h3A9pPwA020834; Thu, 10 Apr 2003 11:52:15 +0200 (CEST) (envelope-from ajacoutot@lphp.org) Message-ID: <002301c2ff46$c6fa9620$6c11933e@CPQ19567200651> From: "Antoine Jacoutot" To: "Willie Viljoen" , References: <200304092142.26122.will@unfoldings.net> Date: Thu, 10 Apr 2003 10:56:21 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 cc: freebsd-hardware@freebsd.org Subject: Re: XFree86 4.3.0, mysterious crash X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 09:52:23 -0000 > I've been experiencing mysterious crashes with XFree86 4.3.0 on FreeBSD > 4.8-STABLE. The problem started occuring as soon as I installed 4.3.0 (with > a portupgrade, all components have been upgraded) > The system seems to simply hang completely, it responds to nothing but a > hardware reset. I have tried with both my ATI Radeon 7500 and my SiS 6326 > AGP, same thing. Other than that, everything works as before. > Anyone out there had a similar problem? Well, actually I do, but I never took the time to investigate more. I though it was because I was using the binary closed drivers from NVidia... but obviously, it's not... I won't have the time to investigate since I won't be home for 2 weeks, but if anyone finds more stuffs about this problem, please post here. Antoine