From owner-freebsd-acpi@FreeBSD.ORG Sat Sep 4 19:50:04 2010 Return-Path: Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 702131065675 for ; Sat, 4 Sep 2010 19:50:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5F8828FC18 for ; Sat, 4 Sep 2010 19:50:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o84Jo49C095720 for ; Sat, 4 Sep 2010 19:50:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o84Jo4p6095719; Sat, 4 Sep 2010 19:50:04 GMT (envelope-from gnats) Date: Sat, 4 Sep 2010 19:50:04 GMT Message-Id: <201009041950.o84Jo4p6095719@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Andriy Gapon Cc: Subject: Re: kern/147858: [acpi] acpi_hp not working when loaded via loader.conf X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2010 19:50:04 -0000 The following reply was made to PR kern/147858; it has been noted by GNATS. From: Andriy Gapon To: Maciej Suszko Cc: bug-followup@FreeBSD.org, Rui Paulo Subject: Re: kern/147858: [acpi] acpi_hp not working when loaded via loader.conf Date: Sat, 04 Sep 2010 22:49:30 +0300 on 04/09/2010 22:33 Maciej Suszko said the following: > Andriy Gapon wrote: >> >> Could originator and other people having the problem please test the >> attached patch and followup to the PR? >> Thanks! >> >> The patch is only compile-tested by me, because I don't have the >> hardware. So you might experience crashes or other surprising >> behavior. But I hope that you won't. > > Thanks, now it's working again. Device is present and readable, no > crashes or any unexpected behavior... at least for now. Thank you very much for testing! Could you please share verbose dmesg just in case? Thanks! -- Andriy Gapon