From owner-freebsd-questions@FreeBSD.ORG Sat Oct 11 05:35:00 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C86F034C for ; Sat, 11 Oct 2014 05:35:00 +0000 (UTC) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46BEB89A for ; Sat, 11 Oct 2014 05:34:59 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id s9B5Ym8O031892; Sat, 11 Oct 2014 16:34:49 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sat, 11 Oct 2014 16:34:48 +1100 (EST) From: Ian Smith To: Mayuresh Kathe Subject: Re: freebsd 10 : cold-boot freeze In-Reply-To: Message-ID: <20141011161809.K56328@sola.nimnet.asn.au> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Oct 2014 05:35:00 -0000 In freebsd-questions Digest, Vol 540, Issue 5, Message: 19 On Fri, 10 Oct 2014 07:38:41 +0530 Mayuresh Kathe wrote: > hello, > > my newly purchased hp aio works well with freebsd 10.0, just that after > a cold-boot, it just freezes during the boot-up process at the point > shown in image at the following link. > http://mayuresh.sdf.org/WP_20140926_001.jpg > > this is repeatable. > > i am more than willing to assist the freebsd team overcome this issue by > way of providing as much of diagnostic information as required. > > best, > > ~mayuresh Hi Mayuresh, I suggest posting this issue to freebsd-acpi@freebsd.org with a bit more information about your system (uname -a etc) .. perhaps after checking whether a recent 10.1-BETA CD or memstick boot still has this issue? Sounds like you don't have this problem on a warm boot? If that's so, providing a (link to a) full dmesg after a verbose boot should help, but people there will likely ask you for more specific details. cheers, Ian