From owner-freebsd-questions@FreeBSD.ORG Tue Sep 17 09:24:44 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 52BBE145 for ; Tue, 17 Sep 2013 09:24:44 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 161972851 for ; Tue, 17 Sep 2013 09:24:43 +0000 (UTC) Received: from r56.edvax.de (port-92-195-74-65.dynamic.qsc.de [92.195.74.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 5FC522789A; Tue, 17 Sep 2013 11:24:41 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id r8H9OXSF004559; Tue, 17 Sep 2013 11:24:33 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 17 Sep 2013 11:24:33 +0200 From: Polytropon To: Atar Subject: Re: FreeBSD stuck during the boot process. Message-Id: <20130917112433.7f550b1a.freebsd@edvax.de> In-Reply-To: References: Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "freebsd-questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Sep 2013 09:24:44 -0000 On Tue, 17 Sep 2013 12:15:58 +0300, Atar wrote: > When I try to boot FreeBSD from a USB stick, it stuck during the > boot process. But if I boot it in safe mode, it succeeds to boot. > How can I figure out what's wrong with the standard boot process? > I can't even log the boot messages since the computer stuck and > not respond. You could try a verbose boot (equivalent: boot -v) and see _when_ the system stops resonding. It would help to post the error message (last lines of console output) to the list to get a better impression about what's happening. If I remember correctly, "safe mode" refers to the mode with ACPI disabled, right? In this case, it _could_ be an ACPI problem (a really wild guess, as you have provided no information about the system you are trying to boot FreeBSD on). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...