From owner-freebsd-acpi@FreeBSD.ORG Mon May 23 08:32:12 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 EFA23106566C for ; Mon, 23 May 2011 08:32:12 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 401BE8FC1C for ; Mon, 23 May 2011 08:32:11 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA06842; Mon, 23 May 2011 11:12:47 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QOQFr-0003Mj-NK; Mon, 23 May 2011 11:12:47 +0300 Message-ID: <4DDA16FF.8080802@FreeBSD.org> Date: Mon, 23 May 2011 11:12:47 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: John Baldwin , freebsd-acpi@FreeBSD.org X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=X-VIET-VPS Content-Transfer-Encoding: 7bit Cc: Subject: acpi resources problem potentially because of new pcib code 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, 23 May 2011 08:32:13 -0000 John, it seems that possibly your recent changes for PCI bridges could have broken something for my old 440BX/PIIX4/PIII type test machine. Looks like now some I/O resources get assigned to a PCI bridge instead of ACPI. Some highlights follow: ... acpi_timer0: couldn't allocate resource (port 0x4008) ... pcib0: port 0xcf8-0xcff,0x4000-0x4041,0x5000-0x500f on acpi0 ... device_attach: acpi_throttle0 attach returned 6 More data here: http://people.freebsd.org/~avg/ms6163/ I see that _CRS of the Host-PCI bridge indeed claims that 0x4000 range, so I realize that this is a BIOS bug, but I think that perhaps we could have some quirk there to leave this range to ACPI. -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Mon May 23 11:06:54 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 061C91065672 for ; Mon, 23 May 2011 11:06:54 +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 EA1228FC16 for ; Mon, 23 May 2011 11:06:53 +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 p4NB6r8V051594 for ; Mon, 23 May 2011 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4NB6rLr051592 for freebsd-acpi@FreeBSD.org; Mon, 23 May 2011 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 May 2011 11:06:53 GMT Message-Id: <201105231106.p4NB6rLr051592@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, 23 May 2011 11:06:54 -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/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/142263 acpi [acpi] ACPI regression on Asus K8N7-E deluxe motherboa o kern/142009 acpi [acpi] [panic] Panic in AcpiNsGetAttachedObject o amd64/140751 acpi [acpi] BIOS resource allocation and FreeBSD ACPI in TO 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 Mon May 23 13:35:58 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 AD2F71065670; Mon, 23 May 2011 13:35:58 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id C1D378FC14; Mon, 23 May 2011 13:35:57 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA12627; Mon, 23 May 2011 16:35:56 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4DDA62BB.1080808@FreeBSD.org> Date: Mon, 23 May 2011 16:35:55 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110504 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: John Baldwin , freebsd-acpi@FreeBSD.org References: <4DDA16FF.8080802@FreeBSD.org> In-Reply-To: <4DDA16FF.8080802@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: Re: acpi resources problem potentially because of new pcib code 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, 23 May 2011 13:35:58 -0000 on 23/05/2011 11:12 Andriy Gapon said the following: > > John, > > it seems that possibly your recent changes for PCI bridges could have broken > something for my old 440BX/PIIX4/PIII type test machine. > Looks like now some I/O resources get assigned to a PCI bridge instead of ACPI. > > Some highlights follow: > ... > acpi_timer0: couldn't allocate resource (port 0x4008) > ... > pcib0: port 0xcf8-0xcff,0x4000-0x4041,0x5000-0x500f on acpi0 > ... > device_attach: acpi_throttle0 attach returned 6 > > More data here: > http://people.freebsd.org/~avg/ms6163/ > > I see that _CRS of the Host-PCI bridge indeed claims that 0x4000 range, so I > realize that this is a BIOS bug, but I think that perhaps we could have some > quirk there to leave this range to ACPI. I fixed this for myself by creating a custom dsdt override where I moved the following resource from _CRS of Device PCI0 (PNP0A03) to that of Device SYSR (PNP0C02): IO (Decode16, 0x4000, // Range Minimum 0x4000, // Range Maximum 0x01, // Alignment 0x42, // Length ) Maybe this could help other people with similarly broken BIOSes. I hope that not too many systems with that hardware survived to these days, because it seems that almost all of them shared a lot of common bugs in their BIOS (and good luck getting any fixes for those systems from their vendors now). -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Tue May 24 12:02:03 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 EBECF1065675; Tue, 24 May 2011 12:02:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id C5C6D8FC0A; Tue, 24 May 2011 12:02:03 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 7CDC246B37; Tue, 24 May 2011 08:02:03 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1AF928A050; Tue, 24 May 2011 08:02:03 -0400 (EDT) From: John Baldwin To: Andriy Gapon Date: Tue, 24 May 2011 08:02:02 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: <4DDA16FF.8080802@FreeBSD.org> In-Reply-To: <4DDA16FF.8080802@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201105240802.02616.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 24 May 2011 08:02:03 -0400 (EDT) Cc: freebsd-acpi@freebsd.org Subject: Re: acpi resources problem potentially because of new pcib code 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: Tue, 24 May 2011 12:02:04 -0000 On Monday, May 23, 2011 4:12:47 am Andriy Gapon wrote: > > John, > > it seems that possibly your recent changes for PCI bridges could have broken > something for my old 440BX/PIIX4/PIII type test machine. > Looks like now some I/O resources get assigned to a PCI bridge instead of ACPI. Actually, this is due to some older changes in 9 to make ACPI reserve all assigned resources via resource_list_reserve(). > Some highlights follow: > ... > acpi_timer0: couldn't allocate resource (port 0x4008) > ... > pcib0: port 0xcf8-0xcff,0x4000-0x4041,0x5000-0x500f on acpi0 > ... > device_attach: acpi_throttle0 attach returned 6 > > More data here: > http://people.freebsd.org/~avg/ms6163/ > > I see that _CRS of the Host-PCI bridge indeed claims that 0x4000 range, so I > realize that this is a BIOS bug, but I think that perhaps we could have some > quirk there to leave this range to ACPI. Well, it would be hard to know how to quirk this generically. acpi timer devices do not use a fixed address range. One thing I have run into is that we make our lives more difficulty by violating the ACPI namespace in our new-bus tree. Specifically, I think we should have an ACPI-aware ISA driver and that any ACPI-enumerated devices that are below the PCI-ISA bridge should be devices on that ISA bus, not on acpi0 directly. The resource producer ranges set up in Host-PCI bridge devices all assume that ACPI-enumerated ISA devices are behind the Host-PCI bridge rather than at the same level. People did not like this the last time I suggested it, but we may need to do it regardless. I might look at doing that in 10. For your BIOS I'd be tempted to just blacklist it. I suppose we could add a quirk to ignore all 'consumed' devices on Host-PCI bridges that are not for the '0xcf8-0xcff' range as an alternative perhaps. -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Tue May 24 16:00:32 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 D1A04106566B for ; Tue, 24 May 2011 16:00:32 +0000 (UTC) (envelope-from falknisius@gmx.de) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id AF9DE8FC0C for ; Tue, 24 May 2011 16:00:32 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QOtdi-0001rf-O5 for freebsd-acpi@freebsd.org; Tue, 24 May 2011 08:35:22 -0700 Date: Tue, 24 May 2011 08:35:22 -0700 (PDT) From: falk To: freebsd-acpi@freebsd.org Message-ID: <1306251322715-4422456.post@n5.nabble.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Problem with FreeBSD graceful shutdown 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: Tue, 24 May 2011 16:00:32 -0000 You can add at /etc/devd a configuration file like power.conf with the following content: notify 10 { match "system" "ACPI"; match "subsystem" "Button"; match "notify" "0x00"; notify "/etc/rc.halt"; }; It works fine for kvm with libvirt or qemu direct. Falk -- View this message in context: http://freebsd.1045724.n5.nabble.com/Problem-with-FreeBSD-graceful-shutdown-tp4227264p4422456.html Sent from the freebsd-acpi mailing list archive at Nabble.com. From owner-freebsd-acpi@FreeBSD.ORG Tue May 24 16:01:20 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 AC304106564A for ; Tue, 24 May 2011 16:01:20 +0000 (UTC) (envelope-from falknisius@gmx.de) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 8A2BC8FC17 for ; Tue, 24 May 2011 16:01:20 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QOtjM-0002VO-N5 for freebsd-acpi@freebsd.org; Tue, 24 May 2011 08:41:12 -0700 Date: Tue, 24 May 2011 08:41:12 -0700 (PDT) From: falk To: freebsd-acpi@freebsd.org Message-ID: <1306251672702-4422479.post@n5.nabble.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Problem with FreeBSD graceful shutdown 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: Tue, 24 May 2011 16:01:20 -0000 You can add i file at /etc/devd with the configuration for the power button. Perhaps you name the file power.conf The Content should be notify 10 { match "system" "ACPI"; match "subsystem" "Button"; match "notify" "0x00"; notify "/etc/rc.halt"; }; It tolds the devd, if there is a message from ACPI, and from the Buttons (0 means the power button, 1 means the sleep button) than call the halt script to shutdown the system. You can use a other script with more cleaning up before the shutdown -p would be invoked. It works for me with libvirt and qemu Monitor both Falk -- View this message in context: http://freebsd.1045724.n5.nabble.com/Problem-with-FreeBSD-graceful-shutdown-tp4227264p4422479.html Sent from the freebsd-acpi mailing list archive at Nabble.com. From owner-freebsd-acpi@FreeBSD.ORG Wed May 25 18:37:25 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 AD2AD106566C for ; Wed, 25 May 2011 18:37:25 +0000 (UTC) (envelope-from menkovich@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 6614C8FC16 for ; Wed, 25 May 2011 18:37:25 +0000 (UTC) Received: by qyk35 with SMTP id 35so2626489qyk.13 for ; Wed, 25 May 2011 11:37:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=oPyrlKWZfvNo4QA1Yopa82FUKe3pFHvvR5bSb+uaVZs=; b=Cyk1+w8znD02ok4xxz8EqBVumrPN9HqUW8NK+RLE+6k2e++WEF4YNvJ4+lr4ET+f58 R6QYrC7KwSL14YkKf28piYtE3f+2er69NXmy+K6LAktHfdFr/9dAobGYHK9vHEvgwXrZ SoMXym3eiTUHhaRnphANyWpSL7Lobf/haQhFo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=or63vgtVZOF9W2tgwdYltDc+QBr5UH6LU5PWJ731R7nu3TdlUSOYMIfzVtBcQWZIMm vsqAwgPfnOyCASxPPL1GlpvYjciZZVpoTbkxxzxPSKe6QQG7MWOCGWeNnKT6xukGM5aK WmpZa5wE/dcFTpnZqjANK2p1CKufU3cBt0vnA= Received: by 10.229.43.142 with SMTP id w14mr4219817qce.27.1306347120132; Wed, 25 May 2011 11:12:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.33.202 with HTTP; Wed, 25 May 2011 11:11:20 -0700 (PDT) In-Reply-To: <1306251672702-4422479.post@n5.nabble.com> References: <1306251672702-4422479.post@n5.nabble.com> From: Nikita A Menkovich Date: Wed, 25 May 2011 22:11:20 +0400 Message-ID: To: falk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-acpi@freebsd.org Subject: Re: Problem with FreeBSD graceful shutdown 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, 25 May 2011 18:37:25 -0000 Seems this was bug in 0.8* branch of libvirt in later versions everything works fine. By the way - thanks for the answer. :) On 24 May 2011 19:41, falk wrote: > You can add i file at /etc/devd with the configuration for the power butt= on. > Perhaps you name the file power.conf > The Content should be > > notify 10 { > =C2=A0 =C2=A0 =C2=A0 =C2=A0match "system" =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0"ACPI"; > =C2=A0 =C2=A0 =C2=A0 =C2=A0match "subsystem" =C2=A0 =C2=A0 =C2=A0 "Button= "; > =C2=A0 =C2=A0 =C2=A0 =C2=A0match "notify" =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0"0x00"; > =C2=A0 =C2=A0 =C2=A0 =C2=A0notify "/etc/rc.halt"; > }; > > It tolds the devd, if there is a message from ACPI, and from the Buttons = (0 > means the power button, 1 means the sleep button) than call the halt scri= pt > to shutdown the system. You can use a other script with more cleaning up > before the shutdown -p would be invoked. > > It works for me with libvirt and qemu Monitor both > > Falk > > > -- > View this message in context: http://freebsd.1045724.n5.nabble.com/Proble= m-with-FreeBSD-graceful-shutdown-tp4227264p4422479.html > Sent from the freebsd-acpi mailing list archive at Nabble.com. > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" > --=20 Nikita A Menkovich http://libc6.org/ JID: menkovich@gmail.com Tel: +7 (921) 423-96-48 From owner-freebsd-acpi@FreeBSD.ORG Thu May 26 19:43:52 2011 Return-Path: Delivered-To: acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C3A2106564A for ; Thu, 26 May 2011 19:43:52 +0000 (UTC) (envelope-from nate@root.org) Received: from mail.rootlabs.com (rootlabs.com [208.72.84.106]) by mx1.freebsd.org (Postfix) with ESMTP id EFBE18FC18 for ; Thu, 26 May 2011 19:43:51 +0000 (UTC) Received: (Postfix invoked from local network); Thu, 26 May 2011 12:25:20 -0700 (PDT) Message-ID: <4DDEA91F.8080008@root.org> Date: Thu, 26 May 2011 12:25:19 -0700 From: Nate Lawson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: acpi@freebsd.org X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: paper on reverse-engineering drivers 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: Thu, 26 May 2011 19:43:52 -0000 This might be a useful source for making ACPI compatible with Windows. http://dslab.epfl.ch/pubs/revnic I had thought of a project like this before. My idea was to take QEMU and map PCI config space and allow direct access to the bare hardware for only one device. The developer would install Windows in this QEMU image on a system with the target device, identify it by its PCI id, and then run Windows normally. The VM would log the driver's accesses to config space as well as use CoW semantics for DMA accesses to memory and IO ports. Now that Intel/AMD support hardware virtualization and DMA isolation, it would be better to do this with a modified Xen hypervisor. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Thu May 26 20:23:36 2011 Return-Path: Delivered-To: acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 97C24106566B for ; Thu, 26 May 2011 20:23:36 +0000 (UTC) (envelope-from nate@root.org) Received: from mail.rootlabs.com (rootlabs.com [208.72.84.106]) by mx1.freebsd.org (Postfix) with ESMTP id 750138FC1A for ; Thu, 26 May 2011 20:23:36 +0000 (UTC) Received: (Postfix invoked from local network); Thu, 26 May 2011 13:23:35 -0700 (PDT) Message-ID: <4DDEB6C7.6070409@root.org> Date: Thu, 26 May 2011 13:23:35 -0700 From: Nate Lawson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Andriy Gapon References: <4DDEA91F.8080008@root.org> <4DDEB5CC.4050500@FreeBSD.org> In-Reply-To: <4DDEB5CC.4050500@FreeBSD.org> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: acpi@FreeBSD.org Subject: Re: paper on reverse-engineering drivers 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: Thu, 26 May 2011 20:23:36 -0000 On 5/26/2011 1:19 PM, Andriy Gapon wrote: > on 26/05/2011 22:25 Nate Lawson said the following: >> This might be a useful source for making ACPI compatible with Windows. >> >> http://dslab.epfl.ch/pubs/revnic >> >> I had thought of a project like this before. My idea was to take QEMU >> and map PCI config space and allow direct access to the bare hardware >> for only one device. The developer would install Windows in this QEMU >> image on a system with the target device, identify it by its PCI id, and >> then run Windows normally. The VM would log the driver's accesses to >> config space as well as use CoW semantics for DMA accesses to memory and >> IO ports. > > Something like this? > http://www.serialice.com/News/News.html > >> Now that Intel/AMD support hardware virtualization and DMA isolation, it >> would be better to do this with a modified Xen hypervisor. Yes, that is a nice project but requires flashing firmware. With hardware virtualization you can trap all IO accesses and do this in software. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Thu May 26 20:33:37 2011 Return-Path: Delivered-To: acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16B51106566C for ; Thu, 26 May 2011 20:33:37 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 679AB8FC17 for ; Thu, 26 May 2011 20:33:35 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id XAA25864; Thu, 26 May 2011 23:19:25 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1QPh1h-0000iD-29; Thu, 26 May 2011 23:19:25 +0300 Message-ID: <4DDEB5CC.4050500@FreeBSD.org> Date: Thu, 26 May 2011 23:19:24 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110503 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: Nate Lawson References: <4DDEA91F.8080008@root.org> In-Reply-To: <4DDEA91F.8080008@root.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: acpi@FreeBSD.org Subject: Re: paper on reverse-engineering drivers 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: Thu, 26 May 2011 20:33:37 -0000 on 26/05/2011 22:25 Nate Lawson said the following: > This might be a useful source for making ACPI compatible with Windows. > > http://dslab.epfl.ch/pubs/revnic > > I had thought of a project like this before. My idea was to take QEMU > and map PCI config space and allow direct access to the bare hardware > for only one device. The developer would install Windows in this QEMU > image on a system with the target device, identify it by its PCI id, and > then run Windows normally. The VM would log the driver's accesses to > config space as well as use CoW semantics for DMA accesses to memory and > IO ports. Something like this? http://www.serialice.com/News/News.html > Now that Intel/AMD support hardware virtualization and DMA isolation, it > would be better to do this with a modified Xen hypervisor. -- Andriy Gapon