From owner-freebsd-acpi@FreeBSD.ORG Mon Oct 10 04:38:43 2011 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 161AC106564A; Mon, 10 Oct 2011 04:38:43 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E29F48FC14; Mon, 10 Oct 2011 04:38:42 +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 p9A4cgZm035545; Mon, 10 Oct 2011 04:38:42 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9A4cgI3035541; Mon, 10 Oct 2011 04:38:42 GMT (envelope-from linimon) Date: Mon, 10 Oct 2011 04:38:42 GMT Message-Id: <201110100438.p9A4cgI3035541@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-acpi@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/160838: [acpi] ACPI Battery Monitor Non-Functional X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2011 04:38:43 -0000 Old Synopsis: ACPI Battery Monitor Non-Functional New Synopsis: [acpi] ACPI Battery Monitor Non-Functional Responsible-Changed-From-To: freebsd-bugs->freebsd-acpi Responsible-Changed-By: linimon Responsible-Changed-When: Mon Oct 10 04:38:02 UTC 2011 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=160838 From owner-freebsd-acpi@FreeBSD.ORG Mon Oct 10 11:07:00 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9AF51065675 for ; Mon, 10 Oct 2011 11:07:00 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 987448FC24 for ; Mon, 10 Oct 2011 11:07:00 +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 p9AB70lf032300 for ; Mon, 10 Oct 2011 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9AB6xNo032298 for freebsd-acpi@FreeBSD.org; Mon, 10 Oct 2011 11:06:59 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 10 Oct 2011 11:06:59 GMT Message-Id: <201110101106.p9AB6xNo032298@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2011 11:07:00 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/160838 acpi [acpi] ACPI Battery Monitor Non-Functional o kern/158689 acpi [acpi] value of sysctl hw.acpi.thermal.polling_rate ne o kern/154955 acpi [acpi] Keyboard or ACPI doesn't work on Lenovo S10-3 o kern/152438 acpi [acpi]: patch to acpi_asus(4) to add extra sysctls for o kern/152098 acpi [acpi] Lenovo T61p does not resume o i386/146715 acpi [acpi] Suspend works, resume not on a HP Probook 4510s o kern/145306 acpi [acpi]: Can't change brightness on HP ProBook 4510s o i386/144045 acpi [acpi] [panic] kernel trap with acpi enabled o i386/143798 acpi [acpi] shutdown problem with SiS K7S5A o kern/143420 acpi [acpi] ACPI issues with Toshiba o kern/142009 acpi [acpi] [panic] Panic in AcpiNsGetAttachedObject o kern/139088 acpi [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error o amd64/138210 acpi [acpi] acer aspire 5536 ACPI problems (S3, brightness, o bin/137053 acpi [hang] FreeBSD 8.0 BETA2Compaq Mini 700 locks on boot o kern/137042 acpi [acpi] hp laptop's lcd not wakes up after suspend to r o i386/136008 acpi [acpi] Dell Vostro 1310 will not shutdown (Requires us o bin/135349 acpi [patch] teach acpidump(8) to disassemble arbitrary mem o kern/132602 acpi [acpi] ACPI Problem with Intel SS4200: System does not o kern/130683 acpi [ACPI] shutdown hangs after syncing disks - ACPI race? o i386/129953 acpi [acpi] ACPI timeout (CDROM) with Shuttle X27D p kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/91594 acpi [acpi] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/ o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 o kern/73823 acpi [request] acpi / power-on by timer support o i386/69750 acpi Boot without ACPI failed on ASUS L5 o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 41 problems total. From owner-freebsd-acpi@FreeBSD.ORG Wed Oct 12 14:36:49 2011 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 8334F1065672; Wed, 12 Oct 2011 14:36:49 +0000 (UTC) (envelope-from remko@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5A88E8FC13; Wed, 12 Oct 2011 14:36:49 +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 p9CEanE0069545; Wed, 12 Oct 2011 14:36:49 GMT (envelope-from remko@freefall.freebsd.org) Received: (from remko@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9CEanfb069541; Wed, 12 Oct 2011 14:36:49 GMT (envelope-from remko) Date: Wed, 12 Oct 2011 14:36:49 GMT Message-Id: <201110121436.p9CEanfb069541@freefall.freebsd.org> To: dieter@lin-k.net, remko@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-acpi@FreeBSD.org From: remko@FreeBSD.org Cc: Subject: Re: bin/115947: [hang] Dell poweredge 860 hangs when stressed and ACPI is enabled X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2011 14:36:49 -0000 Synopsis: [hang] Dell poweredge 860 hangs when stressed and ACPI is enabled State-Changed-From-To: feedback->open State-Changed-By: remko State-Changed-When: Wed Oct 12 14:36:21 UTC 2011 State-Changed-Why: This might be related to ACPI, reopen and assign Responsible-Changed-From-To: freebsd-i386->freebsd-acpi Responsible-Changed-By: remko Responsible-Changed-When: Wed Oct 12 14:36:21 UTC 2011 Responsible-Changed-Why: This might be related to ACPI, reopen and assign http://www.freebsd.org/cgi/query-pr.cgi?pr=115947 From owner-freebsd-acpi@FreeBSD.ORG Fri Oct 14 12:40:31 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F145C1065670; Fri, 14 Oct 2011 12:40:31 +0000 (UTC) (envelope-from gelraen.ua@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9DB658FC13; Fri, 14 Oct 2011 12:40:30 +0000 (UTC) Received: by vcbfo13 with SMTP id fo13so1054069vcb.13 for ; Fri, 14 Oct 2011 05:40:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=NK5tpDkLOrR6MXoMi2hufHXjiH83QJX4E+DECBsC2DE=; b=f/i2IGGxzr9jLgTQNI5Ee5jtYgIUjaZ9IqM973NY/YeDfSwLdj/YsWXxQ6qDmrv77D T5WWTycLToT8bOsKOv/r+Vn6jAXkB0ln+lqtd8AKysvbtIdu/g2hPxnPHLVoHFvdNFWy Ut0jIh7OpI8m4Hj9+8Otv52r8ct4YsNO8bvEw= Received: by 10.52.70.242 with SMTP id p18mr8685187vdu.28.1318594290843; Fri, 14 Oct 2011 05:11:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.185.129 with HTTP; Fri, 14 Oct 2011 05:11:10 -0700 (PDT) From: Maxim Ignatenko Date: Fri, 14 Oct 2011 15:11:10 +0300 Message-ID: To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: freebsd-acpi@freebsd.org Subject: Acquiring ACPI_LOCK(acpi) from kernel module during boot process X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2011 12:40:32 -0000 Hi, I have this code: https://gitorious.org/acpi_call-freebsd/acpi_call-freebsd/blobs/5e6a79869721a2bd8de88b5cfa90c14b429cb5c7/acpi_call.c It works just fine when loaded into kernel manually, but crashes if loaded during boot via loader.conf: http://i.imgur.com/fLPen.png I've added some printf's to acpi_register_ioctl() to track down where it hangs and crashes after about one minute: http://pastebin.com/vvJutWLA What am I missing? Do I need to somehow (how?) specify module initialization order? Or just call acpi_register_ioctl() by some other mean when it would not cause panic? Thanks. From owner-freebsd-acpi@FreeBSD.ORG Fri Oct 14 16:54:24 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7289106564A; Fri, 14 Oct 2011 16:54:24 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5ECD78FC13; Fri, 14 Oct 2011 16:54:24 +0000 (UTC) Received: by vcbfo13 with SMTP id fo13so1422236vcb.13 for ; Fri, 14 Oct 2011 09:54:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2gN4F8qJD0pe7sZZRtfqlwwE/HQmcIbZtX3+PO5trd4=; b=aAepuPJ+v+M1u7T3ZlrmV36c2zZfOoZFp7cIfR6lYZLkCSHFkEQetoDJL8ZmTJ8edn Dvio0eVE3mbhy/qxf1NoRySLg5adcQ4bsOkNgTR7M/YcYyIjuqq9EN3obJQOgIdywB4n WkLljgAZDiFSYppe3Dm8jpD+QQ4nlEYIDxdhM= MIME-Version: 1.0 Received: by 10.182.124.9 with SMTP id me9mr5064838obb.1.1318609701834; Fri, 14 Oct 2011 09:28:21 -0700 (PDT) Received: by 10.182.220.1 with HTTP; Fri, 14 Oct 2011 09:28:21 -0700 (PDT) In-Reply-To: References: Date: Fri, 14 Oct 2011 20:28:21 +0400 Message-ID: From: Sergey Kandaurov To: Maxim Ignatenko Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org, freebsd-acpi@freebsd.org Subject: Re: Acquiring ACPI_LOCK(acpi) from kernel module during boot process X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Oct 2011 16:54:24 -0000 On 14 October 2011 16:11, Maxim Ignatenko wrote: > Hi, > > I have this code: > https://gitorious.org/acpi_call-freebsd/acpi_call-freebsd/blobs/5e6a79869721a2bd8de88b5cfa90c14b429cb5c7/acpi_call.c > It works just fine when loaded into kernel manually, but crashes if > loaded during boot via loader.conf: http://i.imgur.com/fLPen.png > > I've added some printf's to acpi_register_ioctl() to track down where > it hangs and crashes after about one minute: > http://pastebin.com/vvJutWLA > > What am I missing? Do I need to somehow (how?) specify module > initialization order? Or just call acpi_register_ioctl() by some other > mean when it would not cause panic? > Hi. The call of mtx_lock_spin() (as seen from your attached screenshot) on MTX_DEF acpi mutex tells me that you try to use it before it was initialized. This is usually done in acpi_attach() routine which is called with SI_SUB_DRIVERS (? - correct me if I'm wrong) order. Your module is initialized with the earlier SI_SUB_KLD order. That also might depend on whether acpi.ko is statically compiled in, even though you have MODULE_DEPEND(acpi_call, acpi, 1, 1, 1); First I would change the order in DECLARE_MODULE() to a more common SI_SUB_EXEC. -- wbr, pluknet