From owner-freebsd-current@FreeBSD.ORG Mon Oct 30 23:50:42 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 287CA16A494 for ; Mon, 30 Oct 2006 23:50:42 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 008DB43D99 for ; Mon, 30 Oct 2006 23:50:04 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 12232 invoked by uid 399); 30 Oct 2006 23:50:04 -0000 Received: from localhost (HELO ?192.168.0.7?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 30 Oct 2006 23:50:04 -0000 Message-ID: <45468FA5.1040901@FreeBSD.org> Date: Mon, 30 Oct 2006 15:49:57 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Nicolas Blais References: <200610211403.43055.nb_root@videotron.ca> <200610281406.04246.nb_root@videotron.ca> <200610281751.46929.joao@matik.com.br> <200610281700.09301.nb_root@videotron.ca> In-Reply-To: <200610281700.09301.nb_root@videotron.ca> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, JoaoBR Subject: Re: Asus A8V hangs during pci probe on fresh-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Oct 2006 23:50:42 -0000 Nicolas Blais wrote: > I've been running this machine overclocked for about a year and a half, with > multiple pci cards and it has been running -CURRENT fine so far. > > Considering that, and also that I'm not the only one with the problem and that > it happened with the update to pci.c, I'm pretty confident this is not an > overclocking issue, but thanks anyway. That's nice, but the only way to determine that for sure is to try it without overclocking. That will at least help narrow down the problem. It's also worth noting that over time overclocking can have unexpected side effects on the hardware that won't disappear when the clock is reset. (I speak from experience here.) Doug -- This .signature sanitized for your protection