From owner-freebsd-current@FreeBSD.ORG Mon Oct 17 03:50:56 2005 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 6567F16A41F for ; Mon, 17 Oct 2005 03:50:56 +0000 (GMT) (envelope-from pegas@pegas.no-ip.org) Received: from pegas.no-ip.org (user-0c9h55m.cable.mindspring.com [24.152.148.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2022843D46 for ; Mon, 17 Oct 2005 03:50:55 +0000 (GMT) (envelope-from pegas@pegas.no-ip.org) Received: from [10.7.0.127] (simensis.wolfa [10.7.0.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pegas.no-ip.org (Postfix) with ESMTP id CD42560FC; Sun, 16 Oct 2005 20:40:54 -0700 (PDT) Message-ID: <43531F94.6000106@pegas.no-ip.org> Date: Sun, 16 Oct 2005 20:50:44 -0700 From: Evgeny Piven User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Kirkwood References: <20051016120035.028E816A41F@hub.freebsd.org> <4352CA35.2050403@pegas.no-ip.org> <4352E7DF.6010104@paradise.net.nz> In-Reply-To: <4352E7DF.6010104@paradise.net.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 17 Oct 2005 12:23:42 +0000 Cc: freebsd-current@freebsd.org Subject: Re: Reboot hang in 6.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pegas@pegas.no-ip.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2005 03:50:56 -0000 Mark Kirkwood wrote: > Evgeny Piven wrote: > >> When trying to reboot my newly updated 6.0-RC1 machine (updated from >> 5.4-RELEASE), my machine hangs during the reboot. >> This issue has apparently come up before, but never really had a clean >> fix (correct me if I'm wrong). >> From what I've read, the quick fix for this would be turning on USB >> support in BIOS, though this didn't help in my case. >> Basically the hang happens right after the "Uptime: " message is >> displayed and then the machine just sits there and does nothing. From >> what I've read, this might have something to do with ACPI support. > > Looks like you have run into a new variant of the issue :-) > The previous stuff seems to have been tied to USB and (in my case) SMP. > Does disabling (or enabling) ACPI make any difference? > In any case, it might be worth setting 'hw.pci.enable_io_modes=0' in > /boot/loader.conf and seeing if it makes any difference. All I can say for now is that hw.pci.enable_io_modes=0 did not help. Best regards, Evgeny Piven