From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 15 11:02:06 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8C1C16A4CE for ; Mon, 15 Nov 2004 11:02:06 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 985CF43D2D for ; Mon, 15 Nov 2004 11:02:06 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id iAFB26NK074548 for ; Mon, 15 Nov 2004 11:02:06 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iAFB25hF074543 for freebsd-acpi@freebsd.org; Mon, 15 Nov 2004 11:02:05 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 15 Nov 2004 11:02:05 GMT Message-Id: <200411151102.iAFB25hF074543@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 11:02:06 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/06/07] kern/53008 acpi [PATCH] genwakecode generates errornously o [2003/07/22] i386/54756 acpi ACPI suspend/resume problem on CF-W2 lapt o [2003/08/17] i386/55661 acpi ACPI suspend/resume problem on ARMADA M70 o [2003/08/20] kern/55822 acpi No ACPI power off with SMP kernel o [2003/08/27] kern/56024 acpi ACPI suspend drains battery while in S3 o [2003/09/03] i386/56372 acpi acpi don't work on TYAN tiger100 M/B f [2003/09/10] kern/56659 acpi ACPI trouble on IBM ThinkPad X31 f [2003/12/17] i386/60317 acpi FreeBSD 5.2rc1 doesn't boot with ACPI ena o [2004/03/09] i386/64002 acpi acpi problem o [2004/05/27] i386/67273 acpi [hang] system hangs with acpi and Xfree o [2004/10/12] i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Arma 11 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [2004/01/22] i386/61703 acpi ACPI + Sound + Boot = Reboot o [2004/03/17] kern/64365 acpi ACPI problems f [2004/05/25] i386/67189 acpi ACPI S3 reboot computer on Dell Latitude o [2004/05/28] kern/67309 acpi zzz reboot computer (ACPI S3) f [2004/06/23] i386/68219 acpi ACPI + snd_maestro3 problem o [2004/07/29] i386/69750 acpi Boot without ACPI failed on ASUS L5 6 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 15 17:56:32 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AAEF16A4CE for ; Mon, 15 Nov 2004 17:56:32 +0000 (GMT) Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 259A243D41 for ; Mon, 15 Nov 2004 17:56:32 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222])iAFHuXJC031825; Mon, 15 Nov 2004 12:56:33 -0500 Message-ID: <4198EDCD.8070306@root.org> Date: Mon, 15 Nov 2004 09:56:29 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruno Ducrot References: <41910F00.3070402@voicenet.com> <419113BA.9000806@root.org> <41911D01.1090303@voicenet.com> <4191201A.4080406@root.org> <4191330A.7040707@voicenet.com> <41913F15.9060701@root.org> <419145A7.3000406@voicenet.com> <41914DCC.8000100@root.org> <20041112181038.GK31422@poupinou.org> In-Reply-To: <20041112181038.GK31422@poupinou.org> Content-Type: multipart/mixed; boundary="------------040708000206000906050004" cc: freebsd-acpi@freebsd.org cc: Adam K Kirchhoff Subject: Re: Laptop troubles... X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 17:56:32 -0000 This is a multi-part message in MIME format. --------------040708000206000906050004 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Bruno Ducrot wrote: > On Tue, Nov 09, 2004 at 03:07:56PM -0800, Nate Lawson wrote: > >>That's fine, try cx_lowest=C2. If that works, a workaround is to set >>cx_performance_state=C2 and cx_economy_state=C2 in /etc/rc.conf (or >>something like that, see /etc/defaults/rc.conf for the right variable >>names). Please send me the output of acpidump -t -d > adam.asl >>separately as an attachment. I think I will have enough with that to >>debug why C3 is hanging your system. I'm pretty sure the problem area >>of the commit is in enabling C3 for systems that don't have bus master >>control. >> > > C3 support with a PIIX4 southbridge is buggy as hell and > should be disabled no matter what. Right, thanks for the reminder. I actually have quirk code to do this but it wasn't enabled since I wanted to find an actual test case before turning it on. Adam, please recompile with the attached patch. Also, send me pciconf -l. The patch will disable C3 and you should only get C1/C2 if your system is truly a PIIX4. Thanks, Nate --------------040708000206000906050004 Content-Type: text/plain; name="cpu_quirks.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="cpu_quirks.diff" Index: sys/dev/acpica/acpi_cpu.c =================================================================== RCS file: /home/ncvs/src/sys/dev/acpica/acpi_cpu.c,v retrieving revision 1.45 diff -u -r1.45 acpi_cpu.c --- sys/dev/acpica/acpi_cpu.c 11 Oct 2004 21:15:10 -0000 1.45 +++ sys/dev/acpica/acpi_cpu.c 15 Nov 2004 17:52:15 -0000 @@ -966,6 +966,7 @@ static int acpi_cpu_quirks(struct acpi_cpu_softc *sc) { + device_t acpi_dev; /* * C3 on multiple CPUs requires using the expensive flush cache @@ -974,7 +975,6 @@ if (mp_ncpus > 1) cpu_quirks |= CPU_QUIRK_NO_BM_CTRL; -#ifdef notyet /* Look for various quirks of the PIIX4 part. */ acpi_dev = pci_find_device(PCI_VENDOR_INTEL, PCI_DEVICE_82371AB_3); if (acpi_dev != NULL) { @@ -1011,7 +1011,6 @@ break; } } -#endif return (0); } --------------040708000206000906050004-- From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 15 19:45:31 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10C6416A585 for ; Mon, 15 Nov 2004 19:45:31 +0000 (GMT) Received: from chons.visualtech.com (a.smtp.visualtech.com [208.16.19.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4911E43D39 for ; Mon, 15 Nov 2004 19:45:30 +0000 (GMT) (envelope-from adamk@voicenet.com) Received: from [208.16.19.49] (memory.visualtech.com [208.16.19.49]) by chons.visualtech.com (Postfix) with ESMTP id A994BA1AF; Mon, 15 Nov 2004 14:45:26 -0500 (EST) Message-ID: <41990786.2070604@voicenet.com> Date: Mon, 15 Nov 2004 14:46:14 -0500 From: Adam K Kirchhoff User-Agent: Mozilla Thunderbird 0.9 (X11/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <41910F00.3070402@voicenet.com> <419113BA.9000806@root.org> <41911D01.1090303@voicenet.com> <4191201A.4080406@root.org> <4191330A.7040707@voicenet.com> <41913F15.9060701@root.org> <419145A7.3000406@voicenet.com> <41914DCC.8000100@root.org> <20041112181038.GK31422@poupinou.org> <4198EDCD.8070306@root.org> In-Reply-To: <4198EDCD.8070306@root.org> Content-Type: multipart/mixed; boundary="------------050701000705000901090907" cc: freebsd-acpi@freebsd.org Subject: Re: Laptop troubles... X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 19:45:31 -0000 This is a multi-part message in MIME format. --------------050701000705000901090907 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Nate Lawson wrote: > Bruno Ducrot wrote: > >> On Tue, Nov 09, 2004 at 03:07:56PM -0800, Nate Lawson wrote: >> >>> That's fine, try cx_lowest=C2. If that works, a workaround is to >>> set cx_performance_state=C2 and cx_economy_state=C2 in /etc/rc.conf >>> (or something like that, see /etc/defaults/rc.conf for the right >>> variable names). Please send me the output of acpidump -t -d > >>> adam.asl separately as an attachment. I think I will have enough >>> with that to debug why C3 is hanging your system. I'm pretty sure >>> the problem area of the commit is in enabling C3 for systems that >>> don't have bus master control. >>> >> >> C3 support with a PIIX4 southbridge is buggy as hell and >> should be disabled no matter what. > > > Right, thanks for the reminder. I actually have quirk code to do this > but it wasn't enabled since I wanted to find an actual test case > before turning it on. Adam, please recompile with the attached > patch. Also, send me pciconf -l. The patch will disable C3 and you > should only get C1/C2 if your system is truly a PIIX4. > > Thanks, > Nate With that patch, I still have the option of setting C3. And, if I do, I get the lockups. I'm attaching the output of pciconf -l. Adam --------------050701000705000901090907 Content-Type: text/plain; name="pciconf.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pciconf.txt" agp0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x71908086 rev=0x03 hdr=0x00 pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x71918086 rev=0x03 hdr=0x01 isab0@pci0:7:0: class=0x068000 card=0x00000000 chip=0x71108086 rev=0x02 hdr=0x00 atapci0@pci0:7:1: class=0x010180 card=0x00000000 chip=0x71118086 rev=0x01 hdr=0x00 uhci0@pci0:7:2: class=0x0c0300 card=0x00000000 chip=0x71128086 rev=0x01 hdr=0x00 none0@pci0:7:3: class=0x068000 card=0x00000000 chip=0x71138086 rev=0x03 hdr=0x00 cbb0@pci0:10:0: class=0x060700 card=0x0010103c chip=0xac51104c rev=0x00 hdr=0x02 cbb1@pci0:10:1: class=0x060700 card=0x0010103c chip=0xac51104c rev=0x00 hdr=0x02 none1@pci0:11:0: class=0x020000 card=0x625610b7 chip=0x605510b7 rev=0x10 hdr=0x00 none2@pci0:11:1: class=0x078000 card=0x615810b7 chip=0x100710b7 rev=0x10 hdr=0x00 pcm0@pci0:13:0: class=0x040100 card=0x0010103c chip=0x1998125d rev=0x00 hdr=0x00 none3@pci1:0:0: class=0x030000 card=0x0010103c chip=0x4c4d1002 rev=0x64 hdr=0x00 --------------050701000705000901090907-- From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 15 20:05:49 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA58916A4CE for ; Mon, 15 Nov 2004 20:05:48 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 959BB43D48 for ; Mon, 15 Nov 2004 20:05:48 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAFK5kFp022814 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 15 Nov 2004 12:05:47 -0800 Message-ID: <41990C1A.60802@root.org> Date: Mon, 15 Nov 2004 12:05:46 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adam K Kirchhoff References: <41910F00.3070402@voicenet.com> <419113BA.9000806@root.org> <41911D01.1090303@voicenet.com> <4191201A.4080406@root.org> <4191330A.7040707@voicenet.com> <41913F15.9060701@root.org> <419145A7.3000406@voicenet.com> <41914DCC.8000100@root.org> <20041112181038.GK31422@poupinou.org> <4198EDCD.8070306@root.org> <41990786.2070604@voicenet.com> In-Reply-To: <41990786.2070604@voicenet.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: Laptop troubles... X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 20:05:49 -0000 Adam K Kirchhoff wrote: > Nate Lawson wrote: >> Bruno Ducrot wrote: >>> C3 support with a PIIX4 southbridge is buggy as hell and >>> should be disabled no matter what. >> >> >> Right, thanks for the reminder. I actually have quirk code to do this >> but it wasn't enabled since I wanted to find an actual test case >> before turning it on. Adam, please recompile with the attached >> patch. Also, send me pciconf -l. The patch will disable C3 and you >> should only get C1/C2 if your system is truly a PIIX4. > > With that patch, I still have the option of setting C3. And, if I do, I > get the lockups. I'm attaching the output of pciconf -l. I'll need to figure out what's wrong with the acpi_cpu_quirks() function then. You definitely have the hardware I'm checking for (in particular, the 4M chipset): none0@pci0:7:3: class=0x068000 card=0x00000000 chip=0x71138086 rev=0x03 I think the problem is that acpi_cpu_quirks() is run before PCI has been initialized or that device created. I'll change the patch to run the quirks late in the boot and see if that fixes things. It's not completely easy because it will have to properly clean up states >= C3 after they have probed, but I know what needs to be done. Thanks, -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 15 21:16:39 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10F2416A4CE; Mon, 15 Nov 2004 21:16:39 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E3AF43D39; Mon, 15 Nov 2004 21:16:38 +0000 (GMT) (envelope-from marks@ripe.net) Received: by postman.ripe.net (Postfix, from userid 8) id C7B6D240CE; Mon, 15 Nov 2004 22:16:37 +0100 (CET) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id C53A5240C9; Mon, 15 Nov 2004 22:16:36 +0100 (CET) Received: from ripe.net (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id iAFLGaLE001249; Mon, 15 Nov 2004 22:16:36 +0100 Received: (nullmailer pid 1981 invoked by uid 1001); Mon, 15 Nov 2004 21:16:36 -0000 Date: Mon, 15 Nov 2004 22:16:36 +0100 From: Mark Santcroos To: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Message-ID: <20041115211636.GA1540@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Status: U 0.223372 / -5.9 X-RIPE-Signature: fa78ef1f21f9d026bb08be89b6c62864 Subject: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 21:16:39 -0000 If the following patch doesn't burn down too many systems, it will be committed to HEAD in the near future. http://www.santcroos.net/mark/freebsd/files/acpi_import_20041105.diff.gz Mark -- RIPE NCC - Delft University of Technology - The FreeBSD Project marks@ripe.net - m.a.santcroos@ewi.tudelft.nl - marks@freebsd.org From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 15 22:02:58 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E728616A4CE; Mon, 15 Nov 2004 22:02:58 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F9FB43D31; Mon, 15 Nov 2004 22:02:58 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAFM1v0c023965; Mon, 15 Nov 2004 15:01:58 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 15 Nov 2004 15:02:15 -0700 (MST) Message-Id: <20041115.150215.05160797.imp@bsdimp.com> To: marks@ripe.net From: "M. Warner Losh" In-Reply-To: <20041115211636.GA1540@laptop.6bone.nl> References: <20041115211636.GA1540@laptop.6bone.nl> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 22:02:59 -0000 What are the big features of ACPI since the last import? Warner From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 15 22:05:28 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60B1616A4CE for ; Mon, 15 Nov 2004 22:05:28 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B77643D1F for ; Mon, 15 Nov 2004 22:05:28 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAFM5PFp026272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 15 Nov 2004 14:05:26 -0800 Message-ID: <41992825.7050803@root.org> Date: Mon, 15 Nov 2004 14:05:25 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <20041115211636.GA1540@laptop.6bone.nl> <20041115.150215.05160797.imp@bsdimp.com> In-Reply-To: <20041115.150215.05160797.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@FreeBSD.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 22:05:28 -0000 M. Warner Losh wrote: > What are the big features of ACPI since the last import? Read the CHANGES.txt portion of the diff (first one). Things like ACPI 3.0 asl support, lots of bugfixes to various operators, etc. The reason we haven't done an import since May is that a lot of experimental features went in over the summer and the Linux lists have shown things to be unstable. IMO, it's just starting to stabilize again. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 15 22:05:57 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21DB516A4CE; Mon, 15 Nov 2004 22:05:57 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABCDE43D1F; Mon, 15 Nov 2004 22:05:56 +0000 (GMT) (envelope-from marks@ripe.net) Received: by postman.ripe.net (Postfix, from userid 8) id 183EB241DF; Mon, 15 Nov 2004 23:05:56 +0100 (CET) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 25F2F241DE; Mon, 15 Nov 2004 23:05:54 +0100 (CET) Received: from ripe.net (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id iAFM5sLE014458; Mon, 15 Nov 2004 23:05:54 +0100 Received: (nullmailer pid 2922 invoked by uid 1001); Mon, 15 Nov 2004 22:05:53 -0000 Date: Mon, 15 Nov 2004 23:05:53 +0100 From: Mark Santcroos To: "M. Warner Losh" Message-ID: <20041115220553.GB731@laptop.6bone.nl> References: <20041115211636.GA1540@laptop.6bone.nl> <20041115.150215.05160797.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041115.150215.05160797.imp@bsdimp.com> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Status: N 0.001077 / -5.9 X-RIPE-Signature: 84debc40111f8d37fe7b10eff2b08494 cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 22:05:57 -0000 On Mon, Nov 15, 2004 at 03:02:15PM -0700, M. Warner Losh wrote: > What are the big features of ACPI since the last import? See the diff of CHANGES.txt included in the patchset. Mark -- RIPE NCC - Delft University of Technology - The FreeBSD Project marks@ripe.net - m.a.santcroos@ewi.tudelft.nl - marks@freebsd.org From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 03:45:12 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E16C716A4CE for ; Tue, 16 Nov 2004 03:45:11 +0000 (GMT) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8107E43D45 for ; Tue, 16 Nov 2004 03:45:11 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-185.dsl.snfc21.pacbell.net [64.171.186.185])iAG3j7Fb001913; Mon, 15 Nov 2004 22:45:07 -0500 Message-ID: <419977C4.2010403@root.org> Date: Mon, 15 Nov 2004 19:45:08 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adam K Kirchhoff References: <41910F00.3070402@voicenet.com> <419113BA.9000806@root.org> <41911D01.1090303@voicenet.com> <4191201A.4080406@root.org> <4191330A.7040707@voicenet.com> <41913F15.9060701@root.org> <419145A7.3000406@voicenet.com> <41914DCC.8000100@root.org> <20041112181038.GK31422@poupinou.org> <4198EDCD.8070306@root.org> <41990786.2070604@voicenet.com> In-Reply-To: <41990786.2070604@voicenet.com> Content-Type: multipart/mixed; boundary="------------060106050805090904050203" cc: freebsd-acpi@freebsd.org Subject: Re: Laptop troubles... X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 03:45:12 -0000 This is a multi-part message in MIME format. --------------060106050805090904050203 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Adam K Kirchhoff wrote: > Nate Lawson wrote: >> Right, thanks for the reminder. I actually have quirk code to do this >> but it wasn't enabled since I wanted to find an actual test case >> before turning it on. Adam, please recompile with the attached >> patch. Also, send me pciconf -l. The patch will disable C3 and you >> should only get C1/C2 if your system is truly a PIIX4. >> >> Thanks, >> Nate > > > > With that patch, I still have the option of setting C3. And, if I do, I > get the lockups. I'm attaching the output of pciconf -l. Take 2. This patch defers quirks till later. -Nate --------------060106050805090904050203 Content-Type: text/plain; name="cpu_quirks.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="cpu_quirks.diff" Index: sys/dev/acpica/acpi_cpu.c =================================================================== RCS file: /home/ncvs/src/sys/dev/acpica/acpi_cpu.c,v retrieving revision 1.45 diff -u -r1.45 acpi_cpu.c --- sys/dev/acpica/acpi_cpu.c 11 Oct 2004 21:15:10 -0000 1.45 +++ sys/dev/acpica/acpi_cpu.c 16 Nov 2004 02:30:36 -0000 @@ -299,10 +299,6 @@ SYSCTL_CHILDREN(acpi_sc->acpi_sysctl_tree), OID_AUTO, "cpu", CTLFLAG_RD, 0, ""); - /* If this is the first device probed, check for quirks. */ - if (device_get_unit(dev) == 0) - acpi_cpu_quirks(sc); - /* * Probe for throttling and Cx state support. * If none of these is present, free up unused resources. @@ -674,6 +670,10 @@ /* Get set of CPU devices */ devclass_get_devices(acpi_cpu_devclass, &cpu_devices, &cpu_ndevices); + /* Check for quirks via the first CPU device. */ + sc = device_get_softc(cpu_devices[0]); + acpi_cpu_quirks(sc); + /* * Make sure all the processors' Cx counts match. We should probably * also check the contents of each. However, no known systems have @@ -702,6 +702,10 @@ acpi_cpu_startup_throttling() { + /* If throttling is not usable, don't initialize it. */ + if (cpu_quirks & CPU_QUIRK_NO_THROTTLE) + return; + /* Initialise throttling states */ cpu_throttle_max = CPU_MAX_SPEED; cpu_throttle_state = CPU_MAX_SPEED; @@ -737,13 +741,22 @@ acpi_cpu_startup_cx() { struct acpi_cpu_softc *sc; - struct sbuf sb; + struct sbuf sb; int i; + /* + * Set up the list of Cx states, eliminating C3 states by truncating + * cpu_cx_count if quirks indicate C3 is not usable. + */ sc = device_get_softc(cpu_devices[0]); sbuf_new(&sb, cpu_cx_supported, sizeof(cpu_cx_supported), SBUF_FIXEDLEN); - for (i = 0; i < cpu_cx_count; i++) - sbuf_printf(&sb, "C%d/%d ", i + 1, sc->cpu_cx_states[i].trans_lat); + for (i = 0; i < cpu_cx_count; i++) { + if ((cpu_quirks & CPU_QUIRK_NO_C3) == 0 || + sc->cpu_cx_states[i].type != ACPI_STATE_C3) + sbuf_printf(&sb, "C%d/%d ", i + 1, sc->cpu_cx_states[i].trans_lat); + else + cpu_cx_count = i; + } sbuf_trim(&sb); sbuf_finish(&sb); SYSCTL_ADD_STRING(&acpi_cpu_sysctl_ctx, @@ -966,6 +979,7 @@ static int acpi_cpu_quirks(struct acpi_cpu_softc *sc) { + device_t acpi_dev; /* * C3 on multiple CPUs requires using the expensive flush cache @@ -974,7 +988,6 @@ if (mp_ncpus > 1) cpu_quirks |= CPU_QUIRK_NO_BM_CTRL; -#ifdef notyet /* Look for various quirks of the PIIX4 part. */ acpi_dev = pci_find_device(PCI_VENDOR_INTEL, PCI_DEVICE_82371AB_3); if (acpi_dev != NULL) { @@ -1011,7 +1024,6 @@ break; } } -#endif return (0); } --------------060106050805090904050203-- From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 06:20:46 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC60F16A4CE for ; Tue, 16 Nov 2004 06:20:46 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B0D043D48 for ; Tue, 16 Nov 2004 06:20:46 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAG6Humu029165 for ; Mon, 15 Nov 2004 23:17:57 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 15 Nov 2004 23:18:16 -0700 (MST) Message-Id: <20041115.231816.133541642.imp@bsdimp.com> To: acpi@FreeBSD.org From: "M. Warner Losh" X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Mon_Nov_15_23:18:16_2004_769)--" Content-Transfer-Encoding: 7bit Subject: Minor improvement to acpiconf X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 06:20:46 -0000 ----Next_Part(Mon_Nov_15_23:18:16_2004_769)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit acpiconf -i 0 now prints more information about the battery from the bst: Rate of discharge Present Capacity Current Voltage For example: Battery 0 information Design capacity: 48840 mWh Last full capacity: 47360 mWh Technology: primary (non-rechargeable) Design voltage: 11100 mV Capacity (warn): 0 mWh Capacity (low): 120 mWh Low/warn granularity: 0 mWh Warn/full granularity: 10 mWh Model number: Serial number: Type: LION OEM info: Sony Corp. +State: Present +Rate: 5415 mWh +Cap: 42730 mWh +Volt: 12535 mV Comments? Warner ----Next_Part(Mon_Nov_15_23:18:16_2004_769)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="acpiconf.diff" --- /dell/imp/FreeBSD/src/usr.sbin/acpi/acpiconf/acpiconf.c Wed Aug 18 16:14:43 2004 +++ ./acpiconf.c Mon Nov 15 23:12:50 2004 @@ -45,8 +45,8 @@ static int acpifd; -static int -acpi_init() +static void +acpi_init(void) { acpifd = open(ACPIDEV, O_RDWR); if (acpifd == -1){ @@ -117,6 +117,17 @@ printf("Type:\t\t\t%s\n", battio.bif.type); printf("OEM info:\t\t%s\n", battio.bif.oeminfo); + if (ioctl(acpifd, ACPIIO_CMBAT_GET_BST, &battio) == -1) + err(EX_IOERR, "get battery info (%d) failed", num); + + if (battio.bst.state != ACPI_BATT_STAT_NOT_PRESENT) { + printf("State:\t\t\tPresent\n"); + printf("Rate:\t\t\t%d mWh\n", battio.bst.rate); + printf("Cap:\t\t\t%d mWh\n", battio.bst.cap); + printf("Volt:\t\t\t%d mV\n", battio.bst.volt); + } else { + printf("State:\t\t\tNot Present\n"); + } return (0); } ----Next_Part(Mon_Nov_15_23:18:16_2004_769)---- From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 06:29:46 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A81E016A4CE for ; Tue, 16 Nov 2004 06:29:46 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FD7743D48 for ; Tue, 16 Nov 2004 06:29:46 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAG6RiNd029276 for ; Mon, 15 Nov 2004 23:27:44 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 15 Nov 2004 23:28:04 -0700 (MST) Message-Id: <20041115.232804.118795653.imp@bsdimp.com> To: acpi@freebsd.org From: "M. Warner Losh" In-Reply-To: <20041115.231816.133541642.imp@bsdimp.com> References: <20041115.231816.133541642.imp@bsdimp.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Minor improvement to acpiconf X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 06:29:46 -0000 In message: <20041115.231816.133541642.imp@bsdimp.com> "M. Warner Losh" writes: : @@ -45,8 +45,8 @@ : : static int acpifd; : : -static int : -acpi_init() : +static void : +acpi_init(void) : { : acpifd = open(ACPIDEV, O_RDWR); : if (acpifd == -1){ This isn't part of the change, but rather due to a sync error between p4 tree and my freebsd tree :-). Please ignore it. Warner From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 06:47:02 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3383516A4CE for ; Tue, 16 Nov 2004 06:47:02 +0000 (GMT) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id D894543D1D for ; Tue, 16 Nov 2004 06:47:01 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-185.dsl.snfc21.pacbell.net [64.171.186.185])iAG6l7re003194; Tue, 16 Nov 2004 01:47:08 -0500 Message-ID: <4199A260.3020001@root.org> Date: Mon, 15 Nov 2004 22:46:56 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <20041115.231816.133541642.imp@bsdimp.com> In-Reply-To: <20041115.231816.133541642.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@FreeBSD.org Subject: Re: Minor improvement to acpiconf X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 06:47:02 -0000 M. Warner Losh wrote: > acpiconf -i 0 now prints more information about the battery from the bst: > Rate of discharge > Present Capacity > Current Voltage ------------------------------------------------- > > --- /dell/imp/FreeBSD/src/usr.sbin/acpi/acpiconf/acpiconf.c Wed Aug 18 16:14:43 2004 > +++ ./acpiconf.c Mon Nov 15 23:12:50 2004 > @@ -45,8 +45,8 @@ > > static int acpifd; > > -static int > -acpi_init() > +static void > +acpi_init(void) > { Why the change to void if it still returns 0? > acpifd = open(ACPIDEV, O_RDWR); > if (acpifd == -1){ > @@ -117,6 +117,17 @@ > printf("Type:\t\t\t%s\n", battio.bif.type); > printf("OEM info:\t\t%s\n", battio.bif.oeminfo); > > + if (ioctl(acpifd, ACPIIO_CMBAT_GET_BST, &battio) == -1) > + err(EX_IOERR, "get battery info (%d) failed", num); > + > + if (battio.bst.state != ACPI_BATT_STAT_NOT_PRESENT) { Prefer positive logic. > + printf("State:\t\t\tPresent\n"); > + printf("Rate:\t\t\t%d mWh\n", battio.bst.rate); > + printf("Cap:\t\t\t%d mWh\n", battio.bst.cap); > + printf("Volt:\t\t\t%d mV\n", battio.bst.volt); I agree with these except for a slight misgiving about "cap". That information is already exported via sysctl and if we have to export the same thing different ways, I think the interface is not optimal. In general, I'd like to move away from acpi-specific ioctls. There should be just one way of getting the battery info and it shouldn't refer to the underlying method names (_BST and _BIF) like the current ones do. Mike made a good case for eliminating the dev_t entirely since there is never any IO for acpi, it's all control traffic. Sysctl seems more appropriate for that than creating a device that will never see a read, write, or other access other than ioctl(). But this is a complaint about the current design and the half-ioctl, half-sysctl implementation. You're not making it worse so go ahead and commit. I'm just hoping someone will consider improving the interface in the future. -Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 07:14:47 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D161916A4D0 for ; Tue, 16 Nov 2004 07:14:47 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1813F43D3F for ; Tue, 16 Nov 2004 07:14:47 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAG7ERQe029782; Tue, 16 Nov 2004 00:14:27 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 16 Nov 2004 00:14:46 -0700 (MST) Message-Id: <20041116.001446.66168349.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <4199A260.3020001@root.org> References: <20041115.231816.133541642.imp@bsdimp.com> <4199A260.3020001@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: acpi@FreeBSD.org Subject: Re: Minor improvement to acpiconf X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 07:14:48 -0000 In message: <4199A260.3020001@root.org> Nate Lawson writes: : M. Warner Losh wrote: : > acpiconf -i 0 now prints more information about the battery from the bst: : > Rate of discharge : > Present Capacity : > Current Voltage : ------------------------------------------------- : > : > --- /dell/imp/FreeBSD/src/usr.sbin/acpi/acpiconf/acpiconf.c Wed Aug 18 16:14:43 2004 : > +++ ./acpiconf.c Mon Nov 15 23:12:50 2004 : > @@ -45,8 +45,8 @@ : > : > static int acpifd; : > : > -static int : > -acpi_init() : > +static void : > +acpi_init(void) : > { : : Why the change to void if it still returns 0? See other mail. There's no return there at all... : > acpifd = open(ACPIDEV, O_RDWR); : > if (acpifd == -1){ : > @@ -117,6 +117,17 @@ : > printf("Type:\t\t\t%s\n", battio.bif.type); : > printf("OEM info:\t\t%s\n", battio.bif.oeminfo); : > : > + if (ioctl(acpifd, ACPIIO_CMBAT_GET_BST, &battio) == -1) : > + err(EX_IOERR, "get battery info (%d) failed", num); : > + : > + if (battio.bst.state != ACPI_BATT_STAT_NOT_PRESENT) { : : Prefer positive logic. Most common path first is generally the logic I prefer... : > + printf("State:\t\t\tPresent\n"); : > + printf("Rate:\t\t\t%d mWh\n", battio.bst.rate); : > + printf("Cap:\t\t\t%d mWh\n", battio.bst.cap); : > + printf("Volt:\t\t\t%d mV\n", battio.bst.volt); : : I agree with these except for a slight misgiving about "cap". That : information is already exported via sysctl and if we have to export the : same thing different ways, I think the interface is not optimal. Capacity isnt' exported via a sysctl. 'life' is, but it doesn't export anything more than a percentage. : In general, I'd like to move away from acpi-specific ioctls. There : should be just one way of getting the battery info and it shouldn't : refer to the underlying method names (_BST and _BIF) like the current : ones do. Mike made a good case for eliminating the dev_t entirely since : there is never any IO for acpi, it's all control traffic. Sysctl seems : more appropriate for that than creating a device that will never see a : read, write, or other access other than ioctl(). But this is a : complaint about the current design and the half-ioctl, half-sysctl : implementation. The amount of information exported is certainly parsimonious at best. I was mostly interested in 'Rate' to see if the various things I was doing was having any effect on the amount of power being eaten from the batteries.... I'm not entirely sure I agree with a device needing read/write methods to be legit. Especially after I saw sysctl abused for the devinfo interface, which likely should have been read instead :-)... : You're not making it worse so go ahead and commit. I'm just hoping : someone will consider improving the interface in the future. True.... It should be one or the other... Warner From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 08:21:58 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97F1916A4CE for ; Tue, 16 Nov 2004 08:21:58 +0000 (GMT) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B64843D31 for ; Tue, 16 Nov 2004 08:21:58 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-185.dsl.snfc21.pacbell.net [64.171.186.185])iAG8M5re025478; Tue, 16 Nov 2004 03:22:05 -0500 Message-ID: <4199B8A1.6080205@root.org> Date: Tue, 16 Nov 2004 00:21:53 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <20041115.231816.133541642.imp@bsdimp.com> <4199A260.3020001@root.org> <20041116.001446.66168349.imp@bsdimp.com> In-Reply-To: <20041116.001446.66168349.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@FreeBSD.org Subject: Re: Minor improvement to acpiconf X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 08:21:58 -0000 M. Warner Losh wrote: > In message: <4199A260.3020001@root.org> > Nate Lawson writes: > > : > acpifd = open(ACPIDEV, O_RDWR); > : > if (acpifd == -1){ > : > @@ -117,6 +117,17 @@ > : > printf("Type:\t\t\t%s\n", battio.bif.type); > : > printf("OEM info:\t\t%s\n", battio.bif.oeminfo); > : > > : > + if (ioctl(acpifd, ACPIIO_CMBAT_GET_BST, &battio) == -1) > : > + err(EX_IOERR, "get battery info (%d) failed", num); > : > + > : > + if (battio.bst.state != ACPI_BATT_STAT_NOT_PRESENT) { > : > : Prefer positive logic. > > Most common path first is generally the logic I prefer... I thought there was a PRESENT define but apparently not. > : > + printf("State:\t\t\tPresent\n"); > : > + printf("Rate:\t\t\t%d mWh\n", battio.bst.rate); > : > + printf("Cap:\t\t\t%d mWh\n", battio.bst.cap); > : > + printf("Volt:\t\t\t%d mV\n", battio.bst.volt); > : > : I agree with these except for a slight misgiving about "cap". That > : information is already exported via sysctl and if we have to export the > : same thing different ways, I think the interface is not optimal. > > Capacity isnt' exported via a sysctl. 'life' is, but it doesn't > export anything more than a percentage. Life is derived from cap, but like I said above, I'm ok with it. > : In general, I'd like to move away from acpi-specific ioctls. There > : should be just one way of getting the battery info and it shouldn't > : refer to the underlying method names (_BST and _BIF) like the current > : ones do. Mike made a good case for eliminating the dev_t entirely since > : there is never any IO for acpi, it's all control traffic. Sysctl seems > : more appropriate for that than creating a device that will never see a > : read, write, or other access other than ioctl(). But this is a > : complaint about the current design and the half-ioctl, half-sysctl > : implementation. > > I'm not entirely sure I agree with a device needing read/write methods > to be legit. Especially after I saw sysctl abused for the devinfo > interface, which likely should have been read instead :-)... Looking in /dev, nearly all devices support IO. Only the .ctl or .init/.lock devices are questionable. I think it makes sense for this to be a criterion for using a dev_t. -Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 14:08:48 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5862816A4CE for ; Tue, 16 Nov 2004 14:08:48 +0000 (GMT) Received: from mx2.lsn.net (mx2.lsn.net [66.90.130.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1D0343D31 for ; Tue, 16 Nov 2004 14:08:47 +0000 (GMT) (envelope-from davidb@boothscientific.com) Received: from wdbnb (cs7011314-170.austin.rr.com [70.113.14.170]) by mx2.lsn.net (8.13.0.Beta3/8.12.8) with ESMTP id iAGE8iKP015329 for ; Tue, 16 Nov 2004 08:08:49 -0600 From: David Booth To: freebsd-acpi@freebsd.org Date: Tue, 16 Nov 2004 08:08:33 -0600 User-Agent: KMail/1.7.1 References: <20041115.231816.133541642.imp@bsdimp.com> In-Reply-To: <20041115.231816.133541642.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411160808.34721.davidb@boothscientific.com> X-AntiVirus: checked by Vexira Milter 1.0.6; VAE 6.28.0.12; VDF 6.28.0.75 Subject: Re: Minor improvement to acpiconf X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: davidb@boothscientific.com List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 14:08:48 -0000 On Tuesday 16 November 2004 12:18 am, M. Warner Losh wrote: > acpiconf -i 0 now prints more information about the battery from > the bst: Rate of discharge > Present Capacity > Current Voltage > > For example: > > Battery 0 information > Design capacity: 48840 mWh > Last full capacity: 47360 mWh > Technology: primary (non-rechargeable) > Design voltage: 11100 mV > Capacity (warn): 0 mWh > Capacity (low): 120 mWh > Low/warn granularity: 0 mWh > Warn/full granularity: 10 mWh > Model number: > Serial number: > Type: LION > OEM info: Sony Corp. > +State: Present > +Rate: 5415 mWh > +Cap: 42730 mWh > +Volt: 12535 mV > > Comments? > > Warner It makes more sense to me to display the discharge rate in mW rather than mWh. From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 15:02:42 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EAA016A4CE for ; Tue, 16 Nov 2004 15:02:42 +0000 (GMT) Received: from chons.visualtech.com (a.smtp.visualtech.com [208.16.19.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4AEE43D41 for ; Tue, 16 Nov 2004 15:02:41 +0000 (GMT) (envelope-from adamk@voicenet.com) Received: from [192.168.0.104] (memory.visualtech.com [208.16.19.49]) by chons.visualtech.com (Postfix) with ESMTP id 2E5A4A1AF; Tue, 16 Nov 2004 10:02:41 -0500 (EST) Message-ID: <419A169D.9000905@voicenet.com> Date: Tue, 16 Nov 2004 10:02:53 -0500 From: Adam K Kirchhoff User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041113 X-Accept-Language: en MIME-Version: 1.0 To: Nate Lawson References: <41910F00.3070402@voicenet.com> <419113BA.9000806@root.org> <41911D01.1090303@voicenet.com> <4191201A.4080406@root.org> <4191330A.7040707@voicenet.com> <41913F15.9060701@root.org> <419145A7.3000406@voicenet.com> <41914DCC.8000100@root.org> <20041112181038.GK31422@poupinou.org> <4198EDCD.8070306@root.org> <41990786.2070604@voicenet.com> <419977C4.2010403@root.org> In-Reply-To: <419977C4.2010403@root.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: Laptop troubles... X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 15:02:42 -0000 Nate Lawson wrote: > Adam K Kirchhoff wrote: > >> Nate Lawson wrote: >> >>> Right, thanks for the reminder. I actually have quirk code to do >>> this but it wasn't enabled since I wanted to find an actual test >>> case before turning it on. Adam, please recompile with the attached >>> patch. Also, send me pciconf -l. The patch will disable C3 and you >>> should only get C1/C2 if your system is truly a PIIX4. >>> >>> Thanks, >>> Nate >> >> >> >> >> With that patch, I still have the option of setting C3. And, if I >> do, I get the lockups. I'm attaching the output of pciconf -l. > > > Take 2. This patch defers quirks till later. > > -Nate > > > That works! I am unable to set the option to C3 now. Adam From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 16:28:07 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9B4D16A4CE for ; Tue, 16 Nov 2004 16:28:07 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F54B43D54 for ; Tue, 16 Nov 2004 16:28:07 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 10941 invoked from network); 16 Nov 2004 16:28:07 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 16 Nov 2004 16:28:06 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAGGRue5082873; Tue, 16 Nov 2004 11:28:02 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Tue, 16 Nov 2004 10:36:00 -0500 User-Agent: KMail/1.6.2 References: <20041115.231816.133541642.imp@bsdimp.com> <20041116.001446.66168349.imp@bsdimp.com> <4199B8A1.6080205@root.org> In-Reply-To: <4199B8A1.6080205@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411161036.01226.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org Subject: Re: Minor improvement to acpiconf X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 16:28:08 -0000 On Tuesday 16 November 2004 03:21 am, Nate Lawson wrote: > M. Warner Losh wrote: > > In message: <4199A260.3020001@root.org> > > > > Nate Lawson writes: > > : > acpifd = open(ACPIDEV, O_RDWR); > > : > if (acpifd == -1){ > > : > @@ -117,6 +117,17 @@ > > : > printf("Type:\t\t\t%s\n", battio.bif.type); > > : > printf("OEM info:\t\t%s\n", battio.bif.oeminfo); > > : > > > : > + if (ioctl(acpifd, ACPIIO_CMBAT_GET_BST, &battio) == -1) > > : > + err(EX_IOERR, "get battery info (%d) failed", num); > > : > + > > : > + if (battio.bst.state != ACPI_BATT_STAT_NOT_PRESENT) { > > : > > : Prefer positive logic. > > > > Most common path first is generally the logic I prefer... > > I thought there was a PRESENT define but apparently not. > > > : > + printf("State:\t\t\tPresent\n"); > > : > + printf("Rate:\t\t\t%d mWh\n", battio.bst.rate); > > : > + printf("Cap:\t\t\t%d mWh\n", battio.bst.cap); > > : > + printf("Volt:\t\t\t%d mV\n", battio.bst.volt); > > : > > : I agree with these except for a slight misgiving about "cap". That > > : information is already exported via sysctl and if we have to export the > > : same thing different ways, I think the interface is not optimal. > > > > Capacity isnt' exported via a sysctl. 'life' is, but it doesn't > > export anything more than a percentage. > > Life is derived from cap, but like I said above, I'm ok with it. > > > : In general, I'd like to move away from acpi-specific ioctls. There > > : should be just one way of getting the battery info and it shouldn't > > : refer to the underlying method names (_BST and _BIF) like the current > > : ones do. Mike made a good case for eliminating the dev_t entirely > > : since there is never any IO for acpi, it's all control traffic. Sysctl > > : seems more appropriate for that than creating a device that will never > > : see a read, write, or other access other than ioctl(). But this is a > > : complaint about the current design and the half-ioctl, half-sysctl > > : implementation. > > > > I'm not entirely sure I agree with a device needing read/write methods > > to be legit. Especially after I saw sysctl abused for the devinfo > > interface, which likely should have been read instead :-)... > > Looking in /dev, nearly all devices support IO. Only the .ctl or > .init/.lock devices are questionable. I think it makes sense for this > to be a criterion for using a dev_t. I think it would be handy personally to have /dev/batt0, etc. that both apm and acpi provide that are ways of getting info about the current battery state either via read(2) (which could always return a fixed-size status packet) or some kind of ioctl. I.e. a concept of an abstract battery driver with an interface implemented by both APM and ACPI and possibly other drivers in the future. (PowerMacs don't use ACPI AFAIK for example.) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 16:28:08 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19B2416A4CE for ; Tue, 16 Nov 2004 16:28:08 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id B57CE43D2F for ; Tue, 16 Nov 2004 16:28:07 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 10941 invoked from network); 16 Nov 2004 16:28:07 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 16 Nov 2004 16:28:06 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAGGRue5082873; Tue, 16 Nov 2004 11:28:02 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Tue, 16 Nov 2004 10:36:00 -0500 User-Agent: KMail/1.6.2 References: <20041115.231816.133541642.imp@bsdimp.com> <20041116.001446.66168349.imp@bsdimp.com> <4199B8A1.6080205@root.org> In-Reply-To: <4199B8A1.6080205@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411161036.01226.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org Subject: Re: Minor improvement to acpiconf X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 16:28:08 -0000 On Tuesday 16 November 2004 03:21 am, Nate Lawson wrote: > M. Warner Losh wrote: > > In message: <4199A260.3020001@root.org> > > > > Nate Lawson writes: > > : > acpifd = open(ACPIDEV, O_RDWR); > > : > if (acpifd == -1){ > > : > @@ -117,6 +117,17 @@ > > : > printf("Type:\t\t\t%s\n", battio.bif.type); > > : > printf("OEM info:\t\t%s\n", battio.bif.oeminfo); > > : > > > : > + if (ioctl(acpifd, ACPIIO_CMBAT_GET_BST, &battio) == -1) > > : > + err(EX_IOERR, "get battery info (%d) failed", num); > > : > + > > : > + if (battio.bst.state != ACPI_BATT_STAT_NOT_PRESENT) { > > : > > : Prefer positive logic. > > > > Most common path first is generally the logic I prefer... > > I thought there was a PRESENT define but apparently not. > > > : > + printf("State:\t\t\tPresent\n"); > > : > + printf("Rate:\t\t\t%d mWh\n", battio.bst.rate); > > : > + printf("Cap:\t\t\t%d mWh\n", battio.bst.cap); > > : > + printf("Volt:\t\t\t%d mV\n", battio.bst.volt); > > : > > : I agree with these except for a slight misgiving about "cap". That > > : information is already exported via sysctl and if we have to export the > > : same thing different ways, I think the interface is not optimal. > > > > Capacity isnt' exported via a sysctl. 'life' is, but it doesn't > > export anything more than a percentage. > > Life is derived from cap, but like I said above, I'm ok with it. > > > : In general, I'd like to move away from acpi-specific ioctls. There > > : should be just one way of getting the battery info and it shouldn't > > : refer to the underlying method names (_BST and _BIF) like the current > > : ones do. Mike made a good case for eliminating the dev_t entirely > > : since there is never any IO for acpi, it's all control traffic. Sysctl > > : seems more appropriate for that than creating a device that will never > > : see a read, write, or other access other than ioctl(). But this is a > > : complaint about the current design and the half-ioctl, half-sysctl > > : implementation. > > > > I'm not entirely sure I agree with a device needing read/write methods > > to be legit. Especially after I saw sysctl abused for the devinfo > > interface, which likely should have been read instead :-)... > > Looking in /dev, nearly all devices support IO. Only the .ctl or > .init/.lock devices are questionable. I think it makes sense for this > to be a criterion for using a dev_t. I think it would be handy personally to have /dev/batt0, etc. that both apm and acpi provide that are ways of getting info about the current battery state either via read(2) (which could always return a fixed-size status packet) or some kind of ioctl. I.e. a concept of an abstract battery driver with an interface implemented by both APM and ACPI and possibly other drivers in the future. (PowerMacs don't use ACPI AFAIK for example.) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 16:30:22 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 968D116A4CE; Tue, 16 Nov 2004 16:30:22 +0000 (GMT) Received: from sv02.webonaut.com (kirk.webonaut.com [212.41.243.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id E219843D41; Tue, 16 Nov 2004 16:30:21 +0000 (GMT) (envelope-from klammer@webonaut.com) Received: from localhost (localhost [127.0.0.1]) by sv02.webonaut.com (Postfix) with ESMTP id 623FD76440; Tue, 16 Nov 2004 17:30:19 +0100 (CET) Received: from sv02.webonaut.com ([127.0.0.1]) by localhost (sv02.webonaut.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 46017-08; Tue, 16 Nov 2004 17:29:59 +0100 (CET) Received: from mail.webonaut.com (localhost [127.0.0.1]) by sv02.webonaut.com (Postfix) with SMTP id 82A7776449; Tue, 16 Nov 2004 17:29:59 +0100 (CET) Received: from fw-axxess.ycn.com ([213.147.173.194]) (SquirrelMail authenticated user klammer) by mail.webonaut.com with HTTP; Tue, 16 Nov 2004 17:29:59 +0100 (CET) Message-ID: <3183.213.147.173.194.1100622599.squirrel@mail.webonaut.com> In-Reply-To: <20041115211636.GA1540@laptop.6bone.nl> References: <20041115211636.GA1540@laptop.6bone.nl> Date: Tue, 16 Nov 2004 17:29:59 +0100 (CET) From: "Franz Klammer" To: "Mark Santcroos" User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Virus-Scanned: by amavisd-new at webonaut.com cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 16:30:22 -0000 Mark Santcroos: > If the following patch doesn't burn down too many systems, it will be > committed to HEAD in the near future. > does this patch also work with 5.3 or only with -CURRENT? i yes, i will try it: i miss the thermal zones and hope for a better suspend/resume support - currently is only S1 "working". franz. > http://www.santcroos.net/mark/freebsd/files/acpi_import_20041105.diff.gz > > Mark From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 18:48:30 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC27616A4CE for ; Tue, 16 Nov 2004 18:48:30 +0000 (GMT) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F63D43D2D for ; Tue, 16 Nov 2004 18:48:28 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222])iAGImOFb014618; Tue, 16 Nov 2004 13:48:24 -0500 Message-ID: <419A4B79.30303@root.org> Date: Tue, 16 Nov 2004 10:48:25 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adam K Kirchhoff References: <41910F00.3070402@voicenet.com> <419113BA.9000806@root.org> <41911D01.1090303@voicenet.com> <4191201A.4080406@root.org> <4191330A.7040707@voicenet.com> <41913F15.9060701@root.org> <419145A7.3000406@voicenet.com> <41914DCC.8000100@root.org> <20041112181038.GK31422@poupinou.org> <4198EDCD.8070306@root.org> <41990786.2070604@voicenet.com> <419977C4.2010403@root.org> <419A169D.9000905@voicenet.com> In-Reply-To: <419A169D.9000905@voicenet.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: Laptop troubles... X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 18:48:30 -0000 Adam K Kirchhoff wrote: > Nate Lawson wrote: > >> Adam K Kirchhoff wrote: >> >>> Nate Lawson wrote: >>> >>>> Right, thanks for the reminder. I actually have quirk code to do >>>> this but it wasn't enabled since I wanted to find an actual test >>>> case before turning it on. Adam, please recompile with the attached >>>> patch. Also, send me pciconf -l. The patch will disable C3 and you >>>> should only get C1/C2 if your system is truly a PIIX4. >>>> >>>> Thanks, >>>> Nate >>> >>> >>> With that patch, I still have the option of setting C3. And, if I >>> do, I get the lockups. I'm attaching the output of pciconf -l. >> >> >> >> Take 2. This patch defers quirks till later. >> > That works! I am unable to set the option to C3 now. Ok, committed thanks. You should be able to remove the settings in /etc/rc.conf and your system will use C2 as the lowest power state. -Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 19:07:41 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A205016A4CE for ; Tue, 16 Nov 2004 19:07:41 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49C7C43D54 for ; Tue, 16 Nov 2004 19:07:41 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 27140 invoked from network); 16 Nov 2004 19:07:41 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 16 Nov 2004 19:07:40 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAGJ7XRo083780; Tue, 16 Nov 2004 14:07:37 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Tue, 16 Nov 2004 13:39:13 -0500 User-Agent: KMail/1.6.2 References: <200411111737.00537.jhb@FreeBSD.org> In-Reply-To: <200411111737.00537.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411161339.13818.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org cc: gallatin@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 19:07:41 -0000 On Thursday 11 November 2004 05:37 pm, John Baldwin wrote: > I've done some work on the ACPI PCI link code to make it a bit more like > $PIR in that it is link centric and uses actual new-bus devices for each > device link. One benefit of this is that unused links will be disabled now > which might help with interrupt aliasing problems on machines using APICs. > Also, instead of routing IRQs for links via PCI device numbers using > tunables, they are now routed via the link name ala $PIR. Thus, one uses > 'hw.pci.link.LNKA.irq=X' to route LNKA to IRQ X. Also, when choosing a > virgin interrupt, we no longer try to guess at which IRQs might be used by > ISA devices. Instead, we only use known-good IRQs including IRQs that the > BIOS has already used and the SCI if the link is being routed via ISA IRQs. > The patch is at http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch > Please test and let me know if there are any problems, thanks. I've updated this to the latest current and verified that it compiles ok (since I had at least one report that it didn't patch cleanly and/or compile). I plan to commit this in a couple of days unless I hear some sort of negative feedback. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 19:07:41 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4B2A16A4D3 for ; Tue, 16 Nov 2004 19:07:41 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 495C843D4C for ; Tue, 16 Nov 2004 19:07:41 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 27140 invoked from network); 16 Nov 2004 19:07:41 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 16 Nov 2004 19:07:40 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAGJ7XRo083780; Tue, 16 Nov 2004 14:07:37 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Tue, 16 Nov 2004 13:39:13 -0500 User-Agent: KMail/1.6.2 References: <200411111737.00537.jhb@FreeBSD.org> In-Reply-To: <200411111737.00537.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411161339.13818.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org cc: gallatin@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 19:07:41 -0000 On Thursday 11 November 2004 05:37 pm, John Baldwin wrote: > I've done some work on the ACPI PCI link code to make it a bit more like > $PIR in that it is link centric and uses actual new-bus devices for each > device link. One benefit of this is that unused links will be disabled now > which might help with interrupt aliasing problems on machines using APICs. > Also, instead of routing IRQs for links via PCI device numbers using > tunables, they are now routed via the link name ala $PIR. Thus, one uses > 'hw.pci.link.LNKA.irq=X' to route LNKA to IRQ X. Also, when choosing a > virgin interrupt, we no longer try to guess at which IRQs might be used by > ISA devices. Instead, we only use known-good IRQs including IRQs that the > BIOS has already used and the SCI if the link is being routed via ISA IRQs. > The patch is at http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch > Please test and let me know if there are any problems, thanks. I've updated this to the latest current and verified that it compiles ok (since I had at least one report that it didn't patch cleanly and/or compile). I plan to commit this in a couple of days unless I hear some sort of negative feedback. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 19:08:34 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CACFD16A4CE; Tue, 16 Nov 2004 19:08:34 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 655D743D3F; Tue, 16 Nov 2004 19:08:34 +0000 (GMT) (envelope-from marks@ripe.net) Received: by postman.ripe.net (Postfix, from userid 8) id EA1692528B; Tue, 16 Nov 2004 20:08:04 +0100 (CET) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 74B9F250E4; Tue, 16 Nov 2004 20:08:03 +0100 (CET) Received: from ripe.net (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id iAGJ83LE023390; Tue, 16 Nov 2004 20:08:03 +0100 Received: (nullmailer pid 2028 invoked by uid 1001); Tue, 16 Nov 2004 19:08:03 -0000 Date: Tue, 16 Nov 2004 20:08:03 +0100 From: Mark Santcroos To: Franz Klammer Message-ID: <20041116190803.GC736@laptop.6bone.nl> References: <20041115211636.GA1540@laptop.6bone.nl> <3183.213.147.173.194.1100622599.squirrel@mail.webonaut.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3183.213.147.173.194.1100622599.squirrel@mail.webonaut.com> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00 X-RIPE-Spam-Status: N 0.000207 / -5.9 X-RIPE-Signature: 2408c6b86b2a17b6bb1fac1a44baad5d cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 19:08:34 -0000 On Tue, Nov 16, 2004 at 05:29:59PM +0100, Franz Klammer wrote: > does this patch also work with 5.3 or only with -CURRENT? It probably wouldn't be too hard to get it to work for 5.3 in case of this particular patch. In general I don't know yet what the policy will be regarding 5-STABLE and ACPI. Mark -- RIPE NCC - Delft University of Technology - The FreeBSD Project marks@ripe.net - m.a.santcroos@ewi.tudelft.nl - marks@freebsd.org From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 21:06:13 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E90016A4CE for ; Tue, 16 Nov 2004 21:06:13 +0000 (GMT) Received: from chimie.u-strasbg.fr (chimie.u-strasbg.fr [130.79.34.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78EEC43D4C for ; Tue, 16 Nov 2004 21:06:12 +0000 (GMT) (envelope-from gb@isis.u-strasbg.fr) Received: from localhost (localhost.u-strasbg.fr [127.0.0.1]) by chimie.u-strasbg.fr (Postfix) with ESMTP id 1EFAAFB844; Tue, 16 Nov 2004 22:06:11 +0100 (CET) Received: from chimie.u-strasbg.fr ([127.0.0.1]) by localhost (chimie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20948-08; Tue, 16 Nov 2004 22:06:11 +0100 (CET) Received: from mathilda.u-strasbg.fr (chimie.u-strasbg.fr [130.79.34.77]) by chimie.u-strasbg.fr (Postfix) with ESMTP id CB77FFB842; Tue, 16 Nov 2004 22:06:10 +0100 (CET) Received: by mathilda.u-strasbg.fr (Postfix, from userid 1001) id 59F3B34501; Tue, 16 Nov 2004 22:03:56 +0100 (CET) Date: Tue, 16 Nov 2004 22:03:56 +0100 From: Guy Brand To: freebsd-acpi@freebsd.org Message-ID: <20041116210356.GO614@chimie.u-strasbg.fr> References: <20041115211636.GA1540@laptop.6bone.nl> <3183.213.147.173.194.1100622599.squirrel@mail.webonaut.com> <20041116190803.GC736@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20041116190803.GC736@laptop.6bone.nl> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by ClamAV at chimie.u-strasbg.fr Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 21:06:13 -0000 On 16 November at 20:08, Mark Santcroos wrote: > On Tue, Nov 16, 2004 at 05:29:59PM +0100, Franz Klammer wrote: > > does this patch also work with 5.3 or only with -CURRENT? > > It probably wouldn't be too hard to get it to work for 5.3 in case of > this particular patch. It applies without problem to 5.3-RC2. It breaks ipw module for Intel which was working before applying the patch, but it fixes s3 mode on my Asus s5n which was not working until the patch. Many thanks Mark ! gb From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 21:19:19 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67A8516A4CE; Tue, 16 Nov 2004 21:19:19 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCD4143D31; Tue, 16 Nov 2004 21:19:16 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id iAGLJGt7024542 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Nov 2004 16:19:16 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id iAGLJBQA099341; Tue, 16 Nov 2004 16:19:11 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16794.28367.159895.3565@grasshopper.cs.duke.edu> Date: Tue, 16 Nov 2004 16:19:11 -0500 (EST) To: John Baldwin In-Reply-To: <200411161339.13818.jhb@FreeBSD.org> References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-acpi@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 21:19:19 -0000 "panic: link_add_crs: too many interrupts" Full boot -v output at: http://people.freebsd.org/~gallatin/pcilink.boot This is from a machine with an evil ACPI (but I don't want to mess with it for fear of breaking the machine). Drew From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 21:47:19 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DDD616A4CE for ; Tue, 16 Nov 2004 21:47:19 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF1E043D48 for ; Tue, 16 Nov 2004 21:47:18 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 8144 invoked from network); 16 Nov 2004 21:47:18 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 16 Nov 2004 21:47:18 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAGLlEsb084819; Tue, 16 Nov 2004 16:47:15 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Andrew Gallatin Date: Tue, 16 Nov 2004 16:47:14 -0500 User-Agent: KMail/1.6.2 References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <16794.28367.159895.3565@grasshopper.cs.duke.edu> In-Reply-To: <16794.28367.159895.3565@grasshopper.cs.duke.edu> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200411161647.14543.jhb@FreeBSD.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-acpi@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 21:47:19 -0000 On Tuesday 16 November 2004 04:19 pm, Andrew Gallatin wrote: > "panic: link_add_crs: too many interrupts" > > Full boot -v output at: > http://people.freebsd.org/~gallatin/pcilink.boot > > This is from a machine with an evil ACPI (but I don't want to mess > with it for fear of breaking the machine). Ok, that's weird. Can you hack the link_add_crs() function to print out the number of interrupts before the KASSERT()'s if it is not 1? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 22:38:04 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 695E216A4CE; Tue, 16 Nov 2004 22:38:04 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13D5343D54; Tue, 16 Nov 2004 22:38:04 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id iAGMc3t7005608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Nov 2004 17:38:03 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id iAGMbwH9099404; Tue, 16 Nov 2004 17:37:58 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16794.33094.416989.88341@grasshopper.cs.duke.edu> Date: Tue, 16 Nov 2004 17:37:58 -0500 (EST) To: John Baldwin In-Reply-To: <200411161647.14543.jhb@FreeBSD.org> References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <16794.28367.159895.3565@grasshopper.cs.duke.edu> <200411161647.14543.jhb@FreeBSD.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-acpi@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 22:38:04 -0000 John Baldwin writes: > On Tuesday 16 November 2004 04:19 pm, Andrew Gallatin wrote: > > "panic: link_add_crs: too many interrupts" > > > > Full boot -v output at: > > http://people.freebsd.org/~gallatin/pcilink.boot > > > > This is from a machine with an evil ACPI (but I don't want to mess > > with it for fear of breaking the machine). > > Ok, that's weird. Can you hack the link_add_crs() function to print out the > number of interrupts before the KASSERT()'s if it is not 1? There are 3 interrupts. Eg: pci_link1: on acpi0 3 interrupts panic: link_add_crs: too many interrupts If you want me to extract any acpi info, just say the word (and let me know what the incantation is). I have the asl and the dsdt I extracted ages ago saved in ~gallatin/trinity.tgz on freefall. Drew From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 23:12:41 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9E2616A4CE; Tue, 16 Nov 2004 23:12:41 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5506F43D3F; Tue, 16 Nov 2004 23:12:41 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAGNCZC4005759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Nov 2004 15:12:36 -0800 Message-ID: <419A8962.9080804@root.org> Date: Tue, 16 Nov 2004 15:12:34 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20041115.231816.133541642.imp@bsdimp.com> <20041116.001446.66168349.imp@bsdimp.com> <4199B8A1.6080205@root.org> <200411161036.01226.jhb@FreeBSD.org> In-Reply-To: <200411161036.01226.jhb@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@FreeBSD.org cc: freebsd-acpi@FreeBSD.org Subject: Re: Minor improvement to acpiconf X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 23:12:41 -0000 John Baldwin wrote: > On Tuesday 16 November 2004 03:21 am, Nate Lawson wrote: > >>M. Warner Losh wrote: >> >>>In message: <4199A260.3020001@root.org> >>> Nate Lawson writes: >>>: In general, I'd like to move away from acpi-specific ioctls. There >>>: should be just one way of getting the battery info and it shouldn't >>>: refer to the underlying method names (_BST and _BIF) like the current >>>: ones do. Mike made a good case for eliminating the dev_t entirely >>>: since there is never any IO for acpi, it's all control traffic. Sysctl >>>: seems more appropriate for that than creating a device that will never >>>: see a read, write, or other access other than ioctl(). But this is a >>>: complaint about the current design and the half-ioctl, half-sysctl >>>: implementation. >>> >>>I'm not entirely sure I agree with a device needing read/write methods >>>to be legit. Especially after I saw sysctl abused for the devinfo >>>interface, which likely should have been read instead :-)... >> >>Looking in /dev, nearly all devices support IO. Only the .ctl or >>.init/.lock devices are questionable. I think it makes sense for this >>to be a criterion for using a dev_t. > > I think it would be handy personally to have /dev/batt0, etc. that both apm > and acpi provide that are ways of getting info about the current battery > state either via read(2) (which could always return a fixed-size status > packet) or some kind of ioctl. I.e. a concept of an abstract battery driver > with an interface implemented by both APM and ACPI and possibly other drivers > in the future. (PowerMacs don't use ACPI AFAIK for example.) I don't like this approach of adding more dev_t's. We already have a generic battery driver (see acpi_battery.c) which exports data via sysctl. It's acpi-specific in name only and could be generalized. Device entries in /dev were first created in Unix to handle IO. Later, ioctl() was added to handle the out-of-band configuration cases that just didn't fit read/write/seek. So creating new devices that only allow ioctl() access is the wrong way to go, I think. It never makes sense to write() to a battery. The cpufreq framework (which I'll polish and start posting as soon as I finish the major outstanding problem reports) is a good example of how this could work. It exports a single, unified interface via sysctl for adjusting CPU frequency. It also has a kobj interface for other kernel subsystems to control it. More than one control provider can register with it at once and it provides the union of all drivers' settings. It is not acpi-specific as well. Requests for settings from the kernel override user settings (i.e. for passive cooling). Anyway, while I agree the current interface sucks (amalgam of sysctl, multi-driver ioctls on /dev/acpi, and /dev/apm compatibility), I don't think adding more dev_t's is the right way to go on this. I'd rather see a uniform sysctl interface of hw.thermal.*, hw.battery.*, etc. and a mid-layer that takes registration requests from the various subsystems (apm, acpi, PowerPC Whatever) and presents a unified interface. Wrapping this interface in a user library is even better since it makes it possible to maintain an ABI for third-party apps (all of which currently use /dev/apm as the standard, BTW). My nightmare is that /dev/acpi becomes a new third-party standard, blech. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 23:12:41 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9E2616A4CE; Tue, 16 Nov 2004 23:12:41 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5506F43D3F; Tue, 16 Nov 2004 23:12:41 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAGNCZC4005759 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Nov 2004 15:12:36 -0800 Message-ID: <419A8962.9080804@root.org> Date: Tue, 16 Nov 2004 15:12:34 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20041115.231816.133541642.imp@bsdimp.com> <20041116.001446.66168349.imp@bsdimp.com> <4199B8A1.6080205@root.org> <200411161036.01226.jhb@FreeBSD.org> In-Reply-To: <200411161036.01226.jhb@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@FreeBSD.org cc: freebsd-acpi@FreeBSD.org Subject: Re: Minor improvement to acpiconf X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 23:12:41 -0000 John Baldwin wrote: > On Tuesday 16 November 2004 03:21 am, Nate Lawson wrote: > >>M. Warner Losh wrote: >> >>>In message: <4199A260.3020001@root.org> >>> Nate Lawson writes: >>>: In general, I'd like to move away from acpi-specific ioctls. There >>>: should be just one way of getting the battery info and it shouldn't >>>: refer to the underlying method names (_BST and _BIF) like the current >>>: ones do. Mike made a good case for eliminating the dev_t entirely >>>: since there is never any IO for acpi, it's all control traffic. Sysctl >>>: seems more appropriate for that than creating a device that will never >>>: see a read, write, or other access other than ioctl(). But this is a >>>: complaint about the current design and the half-ioctl, half-sysctl >>>: implementation. >>> >>>I'm not entirely sure I agree with a device needing read/write methods >>>to be legit. Especially after I saw sysctl abused for the devinfo >>>interface, which likely should have been read instead :-)... >> >>Looking in /dev, nearly all devices support IO. Only the .ctl or >>.init/.lock devices are questionable. I think it makes sense for this >>to be a criterion for using a dev_t. > > I think it would be handy personally to have /dev/batt0, etc. that both apm > and acpi provide that are ways of getting info about the current battery > state either via read(2) (which could always return a fixed-size status > packet) or some kind of ioctl. I.e. a concept of an abstract battery driver > with an interface implemented by both APM and ACPI and possibly other drivers > in the future. (PowerMacs don't use ACPI AFAIK for example.) I don't like this approach of adding more dev_t's. We already have a generic battery driver (see acpi_battery.c) which exports data via sysctl. It's acpi-specific in name only and could be generalized. Device entries in /dev were first created in Unix to handle IO. Later, ioctl() was added to handle the out-of-band configuration cases that just didn't fit read/write/seek. So creating new devices that only allow ioctl() access is the wrong way to go, I think. It never makes sense to write() to a battery. The cpufreq framework (which I'll polish and start posting as soon as I finish the major outstanding problem reports) is a good example of how this could work. It exports a single, unified interface via sysctl for adjusting CPU frequency. It also has a kobj interface for other kernel subsystems to control it. More than one control provider can register with it at once and it provides the union of all drivers' settings. It is not acpi-specific as well. Requests for settings from the kernel override user settings (i.e. for passive cooling). Anyway, while I agree the current interface sucks (amalgam of sysctl, multi-driver ioctls on /dev/acpi, and /dev/apm compatibility), I don't think adding more dev_t's is the right way to go on this. I'd rather see a uniform sysctl interface of hw.thermal.*, hw.battery.*, etc. and a mid-layer that takes registration requests from the various subsystems (apm, acpi, PowerPC Whatever) and presents a unified interface. Wrapping this interface in a user library is even better since it makes it possible to maintain an ABI for third-party apps (all of which currently use /dev/apm as the standard, BTW). My nightmare is that /dev/acpi becomes a new third-party standard, blech. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 23:18:05 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E7D616A4CE; Tue, 16 Nov 2004 23:18:05 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0697443D2F; Tue, 16 Nov 2004 23:18:05 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAGNI3C4005998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Nov 2004 15:18:03 -0800 Message-ID: <419A8AA9.3070808@root.org> Date: Tue, 16 Nov 2004 15:18:01 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Santcroos References: <20041115211636.GA1540@laptop.6bone.nl> <3183.213.147.173.194.1100622599.squirrel@mail.webonaut.com> <20041116190803.GC736@laptop.6bone.nl> In-Reply-To: <20041116190803.GC736@laptop.6bone.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: Franz Klammer cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 23:18:05 -0000 Mark Santcroos wrote: > On Tue, Nov 16, 2004 at 05:29:59PM +0100, Franz Klammer wrote: >>does this patch also work with 5.3 or only with -CURRENT? > > It probably wouldn't be too hard to get it to work for 5.3 in case of > this particular patch. > > In general I don't know yet what the policy will be regarding 5-STABLE > and ACPI. My current understanding of how things should work in RELENG_5 is that ACPI-CA imports will be tested in 6-current for a minimum of 1 week. Patches will be posted to freebsd-acpi@ for about 5 days before an import to 6-current. Changes, additions, etc. to acpi in general can be committed to 6-current immediately if not too drastic and MFCd after 2 days to 1 week. I intend for RELENG_5 to never diverge from 6-current unless required by external API changes. If minimal, we'll ifdef around the interface changes with __FreeBSD_version__. Hope that answers the question. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 23:21:30 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B2A316A4CE; Tue, 16 Nov 2004 23:21:30 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6287343D1D; Tue, 16 Nov 2004 23:21:30 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAGNLQC4006089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Nov 2004 15:21:26 -0800 Message-ID: <419A8B75.4060000@root.org> Date: Tue, 16 Nov 2004 15:21:25 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Gallatin References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <16794.28367.159895.3565@grasshopper.cs.duke.edu> <200411161647.14543.jhb@FreeBSD.org> <16794.33094.416989.88341@grasshopper.cs.duke.edu> In-Reply-To: <16794.33094.416989.88341@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org cc: scottl@FreeBSD.org cc: John Baldwin Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 23:21:30 -0000 Andrew Gallatin wrote: > John Baldwin writes: > > On Tuesday 16 November 2004 04:19 pm, Andrew Gallatin wrote: > > > "panic: link_add_crs: too many interrupts" > > > > > > Full boot -v output at: > > > http://people.freebsd.org/~gallatin/pcilink.boot > > > > > > This is from a machine with an evil ACPI (but I don't want to mess > > > with it for fear of breaking the machine). > > > > Ok, that's weird. Can you hack the link_add_crs() function to print out the > > number of interrupts before the KASSERT()'s if it is not 1? > > There are 3 interrupts. Eg: > > pci_link1: on acpi0 > 3 interrupts > panic: link_add_crs: too many interrupts > > If you want me to extract any acpi info, just say the word (and let me > know what the incantation is). I have the asl and the dsdt I > extracted ages ago saved in ~gallatin/trinity.tgz on freefall. You'll need ASL to debug this, acpidump -t -d > trinity.asl It seems very surprising that _CRS would return 3 interrupts. I'm guessing the first is the active one? -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 23:22:31 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D745916A4CE; Tue, 16 Nov 2004 23:22:31 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D55C43D1D; Tue, 16 Nov 2004 23:22:31 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAGNMUC4006099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Nov 2004 15:22:31 -0800 Message-ID: <419A8BB5.9050201@root.org> Date: Tue, 16 Nov 2004 15:22:29 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> In-Reply-To: <200411161339.13818.jhb@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@FreeBSD.org cc: gallatin@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 23:22:32 -0000 John Baldwin wrote: > On Thursday 11 November 2004 05:37 pm, John Baldwin wrote: > >>I've done some work on the ACPI PCI link code to make it a bit more like >>$PIR in that it is link centric and uses actual new-bus devices for each >>device link. One benefit of this is that unused links will be disabled now >>which might help with interrupt aliasing problems on machines using APICs. >>Also, instead of routing IRQs for links via PCI device numbers using >>tunables, they are now routed via the link name ala $PIR. Thus, one uses >>'hw.pci.link.LNKA.irq=X' to route LNKA to IRQ X. Also, when choosing a >>virgin interrupt, we no longer try to guess at which IRQs might be used by >>ISA devices. Instead, we only use known-good IRQs including IRQs that the >>BIOS has already used and the SCI if the link is being routed via ISA IRQs. >>The patch is at http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch >>Please test and let me know if there are any problems, thanks. > > > I've updated this to the latest current and verified that it compiles ok > (since I had at least one report that it didn't patch cleanly and/or > compile). I plan to commit this in a couple of days unless I hear some sort > of negative feedback. I think it's ok to commit, modulo Andrew's panic. I hope it generates enough debugging info so that we can quickly fix things in -current as reports arise. Thanks for working on this, -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 23:27:42 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A48C16A4D0; Tue, 16 Nov 2004 23:27:42 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id B964C43D5D; Tue, 16 Nov 2004 23:27:41 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAGNReC4006217 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Nov 2004 15:27:41 -0800 Message-ID: <419A8CEB.4070305@root.org> Date: Tue, 16 Nov 2004 15:27:39 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> In-Reply-To: <200411161339.13818.jhb@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org cc: gallatin@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 23:27:42 -0000 John Baldwin wrote: > On Thursday 11 November 2004 05:37 pm, John Baldwin wrote: > >>I've done some work on the ACPI PCI link code to make it a bit more like >>$PIR in that it is link centric and uses actual new-bus devices for each >>device link. One benefit of this is that unused links will be disabled now >>which might help with interrupt aliasing problems on machines using APICs. >>Also, instead of routing IRQs for links via PCI device numbers using >>tunables, they are now routed via the link name ala $PIR. Thus, one uses >>'hw.pci.link.LNKA.irq=X' to route LNKA to IRQ X. Also, when choosing a >>virgin interrupt, we no longer try to guess at which IRQs might be used by >>ISA devices. Instead, we only use known-good IRQs including IRQs that the >>BIOS has already used and the SCI if the link is being routed via ISA IRQs. >>The patch is at http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch >>Please test and let me know if there are any problems, thanks. > > > I've updated this to the latest current and verified that it compiles ok > (since I had at least one report that it didn't patch cleanly and/or > compile). I plan to commit this in a couple of days unless I hear some sort > of negative feedback. Oh, please s/style(msmith)/style(9) in some parts you added. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 23:28:23 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A92B816A4CE; Tue, 16 Nov 2004 23:28:23 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 536C343D49; Tue, 16 Nov 2004 23:28:23 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id iAGNSMt7012161 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Nov 2004 18:28:22 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id iAGNSHWF099446; Tue, 16 Nov 2004 18:28:17 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16794.36113.628156.440391@grasshopper.cs.duke.edu> Date: Tue, 16 Nov 2004 18:28:17 -0500 (EST) To: Nate Lawson In-Reply-To: <419A8B75.4060000@root.org> References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <16794.28367.159895.3565@grasshopper.cs.duke.edu> <200411161647.14543.jhb@FreeBSD.org> <16794.33094.416989.88341@grasshopper.cs.duke.edu> <419A8B75.4060000@root.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-acpi@FreeBSD.org cc: scottl@FreeBSD.org cc: John Baldwin Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 23:28:23 -0000 Nate Lawson writes: > > You'll need ASL to debug this, acpidump -t -d > trinity.asl > It seems very surprising that _CRS would return 3 interrupts. I'm > guessing the first is the active one? http://people.freebsd.org/~gallatin/trinity.asl Drew From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 23:38:54 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01ACD16A4CE; Tue, 16 Nov 2004 23:38:54 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8F6643D2F; Tue, 16 Nov 2004 23:38:53 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAGNcqC4006654 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Nov 2004 15:38:52 -0800 Message-ID: <419A8F8B.3050206@root.org> Date: Tue, 16 Nov 2004 15:38:51 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Gallatin References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <16794.28367.159895.3565@grasshopper.cs.duke.edu> <200411161647.14543.jhb@FreeBSD.org> <16794.33094.416989.88341@grasshopper.cs.duke.edu> <419A8B75.4060000@root.org> <16794.36113.628156.440391@grasshopper.cs.duke.edu> In-Reply-To: <16794.36113.628156.440391@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org cc: scottl@FreeBSD.org cc: John Baldwin Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 23:38:54 -0000 Andrew Gallatin wrote: > Nate Lawson writes: > > > > You'll need ASL to debug this, acpidump -t -d > trinity.asl > > It seems very surprising that _CRS would return 3 interrupts. I'm > > guessing the first is the active one? > > http://people.freebsd.org/~gallatin/trinity.asl Name (IRTP, ResourceTemplate () { IRQ (Level, ActiveLow, Shared) {0} }) CreateWordField (IRTP, 0x01, INTP) Name (IRTA, ResourceTemplate () { Interrupt (ResourceConsumer, Level, ActiveLow, Exclusive) { 0x00000000, } }) CreateDWordField (IRTA, 0x05, INTA) Method (GETI, 1, NotSerialized) { If (And (Arg0, 0x0F, Local0)) { Return (Local0) } Else { Return (\MLIB.CNV2 (And (Arg0, 0x0F))) } } Device (LN00) { Method (_CRS, 0, NotSerialized) { Store (GETI (PI00), INTP) Return (IRTP) } Um, what a weird system. This link is used for both APIC and PIC mode but only returns the PIC settings via _CRS (IRTP). To generate the _CRS result, it creates a word field (2 bytes) at the start of IRTP + 2 bytes. It then overwrites this IRQ template with the current setting, retrieved from an IO port specified by PI00. Still, IRTP only has one IRQ template so the KASSERT should be incorrect. It may make sense to hexdump the interrupt object returned. Perhaps the Word field is at the wrong offset or wrong size and so it overwrites the IRQ template with some bogus value. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 16 23:40:50 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0132D16A4DC; Tue, 16 Nov 2004 23:40:47 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC1C043D2F; Tue, 16 Nov 2004 23:40:46 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAGNeiC4006711 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Nov 2004 15:40:45 -0800 Message-ID: <419A8FFB.2080204@root.org> Date: Tue, 16 Nov 2004 15:40:43 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Gallatin References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <16794.28367.159895.3565@grasshopper.cs.duke.edu> <200411161647.14543.jhb@FreeBSD.org> <16794.33094.416989.88341@grasshopper.cs.duke.edu> <419A8B75.4060000@root.org> <16794.36113.628156.440391@grasshopper.cs.duke.edu> In-Reply-To: <16794.36113.628156.440391@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org cc: scottl@FreeBSD.org cc: John Baldwin Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 23:40:50 -0000 Andrew Gallatin wrote: > Nate Lawson writes: > > > > You'll need ASL to debug this, acpidump -t -d > trinity.asl > > It seems very surprising that _CRS would return 3 interrupts. I'm > > guessing the first is the active one? > > http://people.freebsd.org/~gallatin/trinity.asl What kind of system is this??? 8 cpu? -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 06:51:24 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BC5A16A4CE; Wed, 17 Nov 2004 06:51:24 +0000 (GMT) Received: from mwinf0301.wanadoo.fr (smtp3.wanadoo.fr [193.252.22.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94F7943D2F; Wed, 17 Nov 2004 06:51:21 +0000 (GMT) (envelope-from aurelien.nephtali@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0301.wanadoo.fr (SMTP Server) with SMTP id 4C5201C0056B; Wed, 17 Nov 2004 07:51:20 +0100 (CET) Received: from [192.168.2.30] (ca-sqy-1-210.w80-8.abo.wanadoo.fr [80.8.54.210]) by mwinf0301.wanadoo.fr (SMTP Server) with ESMTP id 07C631C00566; Wed, 17 Nov 2004 07:51:19 +0100 (CET) Message-ID: <419AF4E7.5000206@wanadoo.fr> Date: Wed, 17 Nov 2004 07:51:19 +0100 From: Aurelien Nephtali User-Agent: Mozilla Thunderbird 0.9 (X11/20041112) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Santcroos References: <20041115211636.GA1540@laptop.6bone.nl> In-Reply-To: <20041115211636.GA1540@laptop.6bone.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 06:51:24 -0000 Mark Santcroos wrote: > If the following patch doesn't burn down too many systems, it will be > committed to HEAD in the near future. > > http://www.santcroos.net/mark/freebsd/files/acpi_import_20041105.diff.gz > > Mark > Hello, The patch applies fine but it sill doesn't fix two long standing bugs :/ The first one is a resume problem, when I suspend my laptop with 'zzz' it works, but when I resume it the LCD stays black and that's all. I've tested setting reset_video to 0 but it's the same. The secong bug is relatted to battery. Sometimes when I unplug the AC, the system catch it and ma battery % falls to 98% and stays stuck on this value. It means no warning when battery is critical :/ Tell me if you need technical informations. Thanks. -- NEPHTALI 'dak' Aurelien From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 08:10:10 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 922AB16A4CE; Wed, 17 Nov 2004 08:10:10 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AA4943D41; Wed, 17 Nov 2004 08:10:10 +0000 (GMT) (envelope-from marks@ripe.net) Received: by postman.ripe.net (Postfix, from userid 8) id 923DF25542; Wed, 17 Nov 2004 09:10:09 +0100 (CET) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 8229525541; Wed, 17 Nov 2004 09:10:08 +0100 (CET) Received: from ripe.net (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id iAH8A8LE026244; Wed, 17 Nov 2004 09:10:08 +0100 Received: (nullmailer pid 46993 invoked by uid 1001); Wed, 17 Nov 2004 08:10:07 -0000 Date: Wed, 17 Nov 2004 09:10:07 +0100 From: Mark Santcroos To: Aurelien Nephtali Message-ID: <20041117081007.GC95090@laptop.6bone.nl> References: <20041115211636.GA1540@laptop.6bone.nl> <419AF4E7.5000206@wanadoo.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <419AF4E7.5000206@wanadoo.fr> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00 X-RIPE-Spam-Status: N 0.000114 / -5.9 X-RIPE-Signature: 287b25f4cf29664b3d95328be8e6cd27 cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 08:10:10 -0000 On Wed, Nov 17, 2004 at 07:51:19AM +0100, Aurelien Nephtali wrote: > The patch applies fine but it sill doesn't fix two long standing bugs :/ At least there are no regressions, thats good news. > The first one is a resume problem, when I suspend my laptop with 'zzz' > it works, but when I resume it the LCD stays black and that's all. I've > tested setting reset_video to 0 but it's the same. So it is only the display that doesn't come back? Is this in X or at the console? Have you tried jhb's acpi_video patches that have the dpms patches included? (They are in the archive of this list) > The secong bug is relatted to battery. Sometimes when I unplug the AC, > the system catch it and ma battery % falls to 98% and stays stuck on > this value. It means no warning when battery is critical :/ What happens if you plug the AC back after a while? Mark -- RIPE NCC - Delft University of Technology - The FreeBSD Project marks@ripe.net - m.a.santcroos@ewi.tudelft.nl - marks@freebsd.org From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 08:28:52 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B645916A4CE for ; Wed, 17 Nov 2004 08:28:52 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6CEE43D49 for ; Wed, 17 Nov 2004 08:28:51 +0000 (GMT) (envelope-from aurelien.nephtali@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so636817rns for ; Wed, 17 Nov 2004 00:28:51 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=uKHmvyzIk9kV1NOqmRYhv6ODlpS5qIRGU+Tnx3nXLwwqxxOUjesBRKJzAfBbYWGaeus0YHzsR2yc0f80AcFI6ZnbjNywuzVRPDk3tBuVvYPs4mCVS8jGdUpDzuc7H2CmZS7xjnv6oeWSkGF88/MwHUX/dp8QXd01cmsD55sp3Hk= Received: by 10.38.179.4 with SMTP id b4mr165771rnf; Wed, 17 Nov 2004 00:28:51 -0800 (PST) Received: by 10.38.179.71 with HTTP; Wed, 17 Nov 2004 00:28:51 -0800 (PST) Message-ID: <5334c8b041117002821dd5c65@mail.gmail.com> Date: Wed, 17 Nov 2004 09:28:51 +0100 From: Aurelien Nephtali To: freebsd-current@freebsd.org, freebsd-acpi@freebsd.org In-Reply-To: <5334c8b041117002779c899d9@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041115211636.GA1540@laptop.6bone.nl> <20041117081007.GC95090@laptop.6bone.nl> <5334c8b041117002779c899d9@mail.gmail.com> Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Aurelien Nephtali List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 08:28:52 -0000 On Wed, 17 Nov 2004 09:10:07 +0100, Mark Santcroos wrote: > On Wed, Nov 17, 2004 at 07:51:19AM +0100, Aurelien Nephtali wrote: > > The patch applies fine but it sill doesn't fix two long standing bugs :/ > > At least there are no regressions, thats good news. :) > > > The first one is a resume problem, when I suspend my laptop with 'zzz' > > it works, but when I resume it the LCD stays black and that's all. I've > > tested setting reset_video to 0 but it's the same. > > So it is only the display that doesn't come back? Is this in X or at the > console? Have you tried jhb's acpi_video patches that have the dpms patches > included? (They are in the archive of this list) I have not recently tested with X but the tests I've done yesterday was with the console. The laptop seems to come back from suspend mode but the LCD stays black as if the laptop wasn't powered (but the system seems to come back correctly from suspend mode but, of course, I can't be sure of that). I'll search through the list for these patches and test when I'll come back home. > > > The secong bug is relatted to battery. Sometimes when I unplug the AC, > > the system catch it and ma battery % falls to 98% and stays stuck on > > this value. It means no warning when battery is critical :/ > > What happens if you plug the AC back after a while? If I plug the AC back, ACPI code detects it, the correct % went back and the battery is correctly detected as charging . -- Aurelien 'dak' Nephtali From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 09:27:32 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBC4416A4CE; Wed, 17 Nov 2004 09:27:32 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 122BE43D3F; Wed, 17 Nov 2004 09:27:32 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id iAH9RRdn072976; Wed, 17 Nov 2004 10:27:29 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <419B194E.5090800@DeepCore.dk> Date: Wed, 17 Nov 2004 10:26:38 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Santcroos References: <20041115211636.GA1540@laptop.6bone.nl> <419AF4E7.5000206@wanadoo.fr> <20041117081007.GC95090@laptop.6bone.nl> In-Reply-To: <20041117081007.GC95090@laptop.6bone.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 09:27:32 -0000 Mark Santcroos wrote: > On Wed, Nov 17, 2004 at 07:51:19AM +0100, Aurelien Nephtali wrote: >=20 >>The patch applies fine but it sill doesn't fix two long standing bugs := / >=20 > At least there are no regressions, thats good news. >=20 >>The first one is a resume problem, when I suspend my laptop with 'zzz' = >>it works, but when I resume it the LCD stays black and that's all. I've= =20 >>tested setting reset_video to 0 but it's the same. >=20 > So it is only the display that doesn't come back? Is this in X or at th= e=20 > console? Have you tried jhb's acpi_video patches that have the dpms pat= ches > included? (They are in the archive of this list) The problem here has been known since mid august (3 months), I have 3=20 different laptops here that all fails in this manner (ASUS, Acer, IBM),=20 however they lockup solid on resume which might be why ;) >>The secong bug is relatted to battery. Sometimes when I unplug the AC, = >>the system catch it and ma battery % falls to 98% and stays stuck on=20 >>this value. It means no warning when battery is critical :/ >=20 > What happens if you plug the AC back after a while? There are nasties in the bat stuff, I have to comment out various parts=20 of it to get the ASUS to boot at all :( This brings up the question: do we have a maintainer for ACPI and why=20 arent these issues being dealt with ? I for one have reported these=20 issue for ages including as much debug as is possible, but it seems to=20 be silently ignored (and yes 5.3-RELEASE is just as broken)... --=20 -S=F8ren From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 11:04:51 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F7C116A4CE for ; Wed, 17 Nov 2004 11:04:51 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9982A43D48 for ; Wed, 17 Nov 2004 11:04:50 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAHB4nBu006266; Wed, 17 Nov 2004 13:04:49 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 20438-13; Wed, 17 Nov 2004 13:04:49 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAHB4mBF006263 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 13:04:48 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAHB4oMV025090; Wed, 17 Nov 2004 13:04:50 +0200 (EET) (envelope-from ru) Date: Wed, 17 Nov 2004 13:04:50 +0200 From: Ruslan Ermilov To: Mark Santcroos Message-ID: <20041117110450.GC24927@ip.net.ua> References: <20041115211636.GA1540@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="s9fJI615cBHmzTOP" Content-Disposition: inline In-Reply-To: <20041115211636.GA1540@laptop.6bone.nl> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-acpi@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 11:04:51 -0000 --s9fJI615cBHmzTOP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 15, 2004 at 10:16:36PM +0100, Mark Santcroos wrote: > If the following patch doesn't burn down too many systems, it will be > committed to HEAD in the near future. >=20 > http://www.santcroos.net/mark/freebsd/files/acpi_import_20041105.diff.gz >=20 Nothing has improved (I still can't get S3 to work, and I get interrupt storms with and only with ACPI), but at least I do not see any regression. ;) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --s9fJI615cBHmzTOP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBmzBSqRfpzJluFF4RAmQRAJ9M4iChZPIhWU/Wxr05s5065x9KPACfZhu3 C4Gxi4v791wtvzNWW1FjDKY= =7TPc -----END PGP SIGNATURE----- --s9fJI615cBHmzTOP-- From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 13:33:53 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C552016A4CE; Wed, 17 Nov 2004 13:33:53 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DD4C43D46; Wed, 17 Nov 2004 13:33:53 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id iAHDXqt7008008 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 08:33:53 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id iAHDXj97000716; Wed, 17 Nov 2004 08:33:45 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16795.21305.605718.371785@grasshopper.cs.duke.edu> Date: Wed, 17 Nov 2004 08:33:45 -0500 (EST) To: Nate Lawson In-Reply-To: <419A8FFB.2080204@root.org> References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <16794.28367.159895.3565@grasshopper.cs.duke.edu> <200411161647.14543.jhb@FreeBSD.org> <16794.33094.416989.88341@grasshopper.cs.duke.edu> <419A8B75.4060000@root.org> <16794.36113.628156.440391@grasshopper.cs.duke.edu> <419A8FFB.2080204@root.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-acpi@FreeBSD.org cc: scottl@FreeBSD.org cc: John Baldwin Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 13:33:53 -0000 Nate Lawson writes: > Andrew Gallatin wrote: > > Nate Lawson writes: > > > > > > You'll need ASL to debug this, acpidump -t -d > trinity.asl > > > It seems very surprising that _CRS would return 3 interrupts. I'm > > > guessing the first is the active one? > > > > http://people.freebsd.org/~gallatin/trinity.asl > > What kind of system is this??? 8 cpu? No.. Its a single P4, but with a Serverworks GC-SL chipset and 2 PCI-X slots. http://www.tyan.com/products/html/trinitygcsl.html Drew From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 14:18:49 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2287016A4CE for ; Wed, 17 Nov 2004 14:18:49 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id E63EF43D5A for ; Wed, 17 Nov 2004 14:18:48 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6982 invoked from network); 17 Nov 2004 14:18:47 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 17 Nov 2004 14:18:46 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAHEIcJ4090146; Wed, 17 Nov 2004 09:18:43 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Wed, 17 Nov 2004 09:05:34 -0500 User-Agent: KMail/1.6.2 References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <419A8CEB.4070305@root.org> In-Reply-To: <419A8CEB.4070305@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411170905.34296.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: gallatin@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 14:18:49 -0000 On Tuesday 16 November 2004 06:27 pm, Nate Lawson wrote: > John Baldwin wrote: > > On Thursday 11 November 2004 05:37 pm, John Baldwin wrote: > >>I've done some work on the ACPI PCI link code to make it a bit more like > >>$PIR in that it is link centric and uses actual new-bus devices for each > >>device link. One benefit of this is that unused links will be disabled > >> now which might help with interrupt aliasing problems on machines using > >> APICs. Also, instead of routing IRQs for links via PCI device numbers > >> using tunables, they are now routed via the link name ala $PIR. Thus, > >> one uses 'hw.pci.link.LNKA.irq=X' to route LNKA to IRQ X. Also, when > >> choosing a virgin interrupt, we no longer try to guess at which IRQs > >> might be used by ISA devices. Instead, we only use known-good IRQs > >> including IRQs that the BIOS has already used and the SCI if the link is > >> being routed via ISA IRQs. The patch is at > >> http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch Please test and > >> let me know if there are any problems, thanks. > > > > I've updated this to the latest current and verified that it compiles ok > > (since I had at least one report that it didn't patch cleanly and/or > > compile). I plan to commit this in a couple of days unless I hear some > > sort of negative feedback. > > Oh, please s/style(msmith)/style(9) in some parts you added. Heh, I can do that in the new code, sure. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 15:41:50 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C628C16A4CE; Wed, 17 Nov 2004 15:41:50 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8842343D49; Wed, 17 Nov 2004 15:41:48 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAHFfkIm026154; Wed, 17 Nov 2004 17:41:46 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 49244-20; Wed, 17 Nov 2004 17:41:45 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAHFfi6p026151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 17:41:45 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAHFflHU026264; Wed, 17 Nov 2004 17:41:47 +0200 (EET) (envelope-from ru) Date: Wed, 17 Nov 2004 17:41:46 +0200 From: Ruslan Ermilov To: John Baldwin Message-ID: <20041117154146.GD25995@ip.net.ua> References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fXStkuK2IQBfcDe+" Content-Disposition: inline In-Reply-To: <200411161339.13818.jhb@FreeBSD.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: acpi@FreeBSD.org cc: freebsd-acpi@FreeBSD.org cc: gallatin@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 15:41:50 -0000 --fXStkuK2IQBfcDe+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 16, 2004 at 01:39:13PM -0500, John Baldwin wrote: > On Thursday 11 November 2004 05:37 pm, John Baldwin wrote: > > I've done some work on the ACPI PCI link code to make it a bit more like > > $PIR in that it is link centric and uses actual new-bus devices for each > > device link. One benefit of this is that unused links will be disabled= now > > which might help with interrupt aliasing problems on machines using API= Cs.=20 > > Also, instead of routing IRQs for links via PCI device numbers using > > tunables, they are now routed via the link name ala $PIR. Thus, one us= es > > 'hw.pci.link.LNKA.irq=3DX' to route LNKA to IRQ X. Also, when choosing= a > > virgin interrupt, we no longer try to guess at which IRQs might be used= by > > ISA devices. Instead, we only use known-good IRQs including IRQs that = the > > BIOS has already used and the SCI if the link is being routed via ISA I= RQs. > > The patch is at http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch > > Please test and let me know if there are any problems, thanks. >=20 > I've updated this to the latest current and verified that it compiles ok= =20 > (since I had at least one report that it didn't patch cleanly and/or=20 > compile). I plan to commit this in a couple of days unless I hear some s= ort=20 > of negative feedback. >=20 I get a panic on boot with this change. I don't have a serial console attached to this notebook, but if needs be it can be arranged (tomorrow). The panic I get is as follows: panic: Assertion resource->Data.Irq.NumberOfInterrupts =3D=3D 1 failed at .= =2E./acpi_pci_link.c:497 Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --fXStkuK2IQBfcDe+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBm3E6qRfpzJluFF4RApP5AJwJmdpYDabZfhJeXzCeltvBeO0pUACeO617 fNBwwlYSVu7ETQePootAWis= =LxOj -----END PGP SIGNATURE----- --fXStkuK2IQBfcDe+-- From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 15:41:50 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C628C16A4CE; Wed, 17 Nov 2004 15:41:50 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8842343D49; Wed, 17 Nov 2004 15:41:48 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAHFfkIm026154; Wed, 17 Nov 2004 17:41:46 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 49244-20; Wed, 17 Nov 2004 17:41:45 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAHFfi6p026151 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 17:41:45 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAHFflHU026264; Wed, 17 Nov 2004 17:41:47 +0200 (EET) (envelope-from ru) Date: Wed, 17 Nov 2004 17:41:46 +0200 From: Ruslan Ermilov To: John Baldwin Message-ID: <20041117154146.GD25995@ip.net.ua> References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fXStkuK2IQBfcDe+" Content-Disposition: inline In-Reply-To: <200411161339.13818.jhb@FreeBSD.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: acpi@FreeBSD.org cc: freebsd-acpi@FreeBSD.org cc: gallatin@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 15:41:50 -0000 --fXStkuK2IQBfcDe+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 16, 2004 at 01:39:13PM -0500, John Baldwin wrote: > On Thursday 11 November 2004 05:37 pm, John Baldwin wrote: > > I've done some work on the ACPI PCI link code to make it a bit more like > > $PIR in that it is link centric and uses actual new-bus devices for each > > device link. One benefit of this is that unused links will be disabled= now > > which might help with interrupt aliasing problems on machines using API= Cs.=20 > > Also, instead of routing IRQs for links via PCI device numbers using > > tunables, they are now routed via the link name ala $PIR. Thus, one us= es > > 'hw.pci.link.LNKA.irq=3DX' to route LNKA to IRQ X. Also, when choosing= a > > virgin interrupt, we no longer try to guess at which IRQs might be used= by > > ISA devices. Instead, we only use known-good IRQs including IRQs that = the > > BIOS has already used and the SCI if the link is being routed via ISA I= RQs. > > The patch is at http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch > > Please test and let me know if there are any problems, thanks. >=20 > I've updated this to the latest current and verified that it compiles ok= =20 > (since I had at least one report that it didn't patch cleanly and/or=20 > compile). I plan to commit this in a couple of days unless I hear some s= ort=20 > of negative feedback. >=20 I get a panic on boot with this change. I don't have a serial console attached to this notebook, but if needs be it can be arranged (tomorrow). The panic I get is as follows: panic: Assertion resource->Data.Irq.NumberOfInterrupts =3D=3D 1 failed at .= =2E./acpi_pci_link.c:497 Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --fXStkuK2IQBfcDe+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBm3E6qRfpzJluFF4RApP5AJwJmdpYDabZfhJeXzCeltvBeO0pUACeO617 fNBwwlYSVu7ETQePootAWis= =LxOj -----END PGP SIGNATURE----- --fXStkuK2IQBfcDe+-- From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 19:50:21 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A898B16A4CE for ; Wed, 17 Nov 2004 19:50:21 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FA2B43D5C for ; Wed, 17 Nov 2004 19:50:21 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 4303 invoked from network); 17 Nov 2004 19:50:21 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 17 Nov 2004 19:50:20 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAHJoBnu092049; Wed, 17 Nov 2004 14:50:16 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Ruslan Ermilov Date: Wed, 17 Nov 2004 11:24:48 -0500 User-Agent: KMail/1.6.2 References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <20041117154146.GD25995@ip.net.ua> In-Reply-To: <20041117154146.GD25995@ip.net.ua> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411171124.48268.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org cc: freebsd-acpi@FreeBSD.org cc: gallatin@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 19:50:21 -0000 On Wednesday 17 November 2004 10:41 am, Ruslan Ermilov wrote: > On Tue, Nov 16, 2004 at 01:39:13PM -0500, John Baldwin wrote: > > On Thursday 11 November 2004 05:37 pm, John Baldwin wrote: > > > I've done some work on the ACPI PCI link code to make it a bit more > > > like $PIR in that it is link centric and uses actual new-bus devices > > > for each device link. One benefit of this is that unused links will be > > > disabled now which might help with interrupt aliasing problems on > > > machines using APICs. Also, instead of routing IRQs for links via PCI > > > device numbers using tunables, they are now routed via the link name > > > ala $PIR. Thus, one uses 'hw.pci.link.LNKA.irq=X' to route LNKA to IRQ > > > X. Also, when choosing a virgin interrupt, we no longer try to guess > > > at which IRQs might be used by ISA devices. Instead, we only use > > > known-good IRQs including IRQs that the BIOS has already used and the > > > SCI if the link is being routed via ISA IRQs. The patch is at > > > http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch Please test and > > > let me know if there are any problems, thanks. > > > > I've updated this to the latest current and verified that it compiles ok > > (since I had at least one report that it didn't patch cleanly and/or > > compile). I plan to commit this in a couple of days unless I hear some > > sort of negative feedback. > > I get a panic on boot with this change. I don't have a serial > console attached to this notebook, but if needs be it can be > arranged (tomorrow). The panic I get is as follows: > > panic: Assertion resource->Data.Irq.NumberOfInterrupts == 1 failed at > .../acpi_pci_link.c:497 Can you print out what 'NumberOfInterrupts' is before the printf? Drew has a machine that has hit the same panic as well. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 19:50:21 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E004F16A4D0 for ; Wed, 17 Nov 2004 19:50:21 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C60943D66 for ; Wed, 17 Nov 2004 19:50:21 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 4303 invoked from network); 17 Nov 2004 19:50:21 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 17 Nov 2004 19:50:20 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAHJoBnu092049; Wed, 17 Nov 2004 14:50:16 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Ruslan Ermilov Date: Wed, 17 Nov 2004 11:24:48 -0500 User-Agent: KMail/1.6.2 References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <20041117154146.GD25995@ip.net.ua> In-Reply-To: <20041117154146.GD25995@ip.net.ua> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411171124.48268.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org cc: freebsd-acpi@FreeBSD.org cc: gallatin@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 19:50:22 -0000 On Wednesday 17 November 2004 10:41 am, Ruslan Ermilov wrote: > On Tue, Nov 16, 2004 at 01:39:13PM -0500, John Baldwin wrote: > > On Thursday 11 November 2004 05:37 pm, John Baldwin wrote: > > > I've done some work on the ACPI PCI link code to make it a bit more > > > like $PIR in that it is link centric and uses actual new-bus devices > > > for each device link. One benefit of this is that unused links will be > > > disabled now which might help with interrupt aliasing problems on > > > machines using APICs. Also, instead of routing IRQs for links via PCI > > > device numbers using tunables, they are now routed via the link name > > > ala $PIR. Thus, one uses 'hw.pci.link.LNKA.irq=X' to route LNKA to IRQ > > > X. Also, when choosing a virgin interrupt, we no longer try to guess > > > at which IRQs might be used by ISA devices. Instead, we only use > > > known-good IRQs including IRQs that the BIOS has already used and the > > > SCI if the link is being routed via ISA IRQs. The patch is at > > > http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch Please test and > > > let me know if there are any problems, thanks. > > > > I've updated this to the latest current and verified that it compiles ok > > (since I had at least one report that it didn't patch cleanly and/or > > compile). I plan to commit this in a couple of days unless I hear some > > sort of negative feedback. > > I get a panic on boot with this change. I don't have a serial > console attached to this notebook, but if needs be it can be > arranged (tomorrow). The panic I get is as follows: > > panic: Assertion resource->Data.Irq.NumberOfInterrupts == 1 failed at > .../acpi_pci_link.c:497 Can you print out what 'NumberOfInterrupts' is before the printf? Drew has a machine that has hit the same panic as well. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 20:14:36 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F05D816A4D0; Wed, 17 Nov 2004 20:14:36 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75CAE43D1D; Wed, 17 Nov 2004 20:14:36 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222])iAHKELDU032024; Wed, 17 Nov 2004 15:14:22 -0500 Message-ID: <419BB117.4070802@root.org> Date: Wed, 17 Nov 2004 12:14:15 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= References: <20041115211636.GA1540@laptop.6bone.nl> <419AF4E7.5000206@wanadoo.fr> <20041117081007.GC95090@laptop.6bone.nl> <419B194E.5090800@DeepCore.dk> In-Reply-To: <419B194E.5090800@DeepCore.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 20:14:37 -0000 Søren Schmidt wrote: > There are nasties in the bat stuff, I have to comment out various parts > of it to get the ASUS to boot at all :( > > > This brings up the question: do we have a maintainer for ACPI and why > arent these issues being dealt with ? I for one have reported these > issue for ages including as much debug as is possible, but it seems to > be silently ignored (and yes 5.3-RELEASE is just as broken)... > cvs logs will show who is active in each area of acpi. I'm sure that's a rhetorical question though. As for your particular problems, the battery issue may be related to your system not operating according to the locking model. I fixed one thermal problem for brooks@ where his ASL generated notifies every time we read the temperature and the notify handler read the temperature. It may be something similar. Send me the ASL and I'll take a look. The suspend/resume issue has not been isolated but you can start by checking where it gets with a serial console attached (if it gets that far) or by putting some beep code in the resume handler to see if it even gets called (Warner has the patch in his tree, it may make sense to commit it under some option to help with debugging.) I'd love it if more people would help with debugging. I'm sure you can relate to maintaining a subsystem where behavior is widely divergent even among the same model device, OEM bugs are rampant and undocumented, and you don't have access to a system that can repeat the behavior that the submitter is reporting. As donations@ shows, I'm willing to accept problem laptops on loan or for donation. Currently, I own an IBM R32, T23, Sony PCG-F390, and Abit SMP. All work correctly including suspend/resume to RAM for the laptops. -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 20:15:06 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4ABC916A4D0 for ; Wed, 17 Nov 2004 20:15:06 +0000 (GMT) Received: from mail.delit.net (delit.net [194.67.27.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB26743D55 for ; Wed, 17 Nov 2004 20:15:05 +0000 (GMT) (envelope-from smir@delit.net) Received: from [192.168.0.101] (ppp83-237-169-163.pppoe.mtu-net.ru [83.237.169.163]) by mail.delit.net (Postfix) with ESMTP id 9E13934F80 for ; Wed, 17 Nov 2004 23:15:03 +0300 (MSK) Message-ID: <419BB14C.1060301@delit.net> Date: Wed, 17 Nov 2004 23:15:08 +0300 From: Andrey Smirnov User-Agent: Mozilla Thunderbird 0.9 (X11/20041109) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: Why C3 state isn't entered? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 20:15:06 -0000 Hello! I've got Centrino notebook (specifically Asus M3700Np), and it doesn't seem to enter C3 sleep state in any case. Sample output from 'sysctl hw.acpi.cpu' (while working at battery): hw.acpi.cpu.cx_supported: C1/0 C2/1 C3/101 hw.acpi.cpu.cx_lowest: C3 hw.acpi.cpu.cx_usage: 0.00% 100.00% 0.00% So C3 is supported, is allowed but isn't entered according to cx_usage. Why could it be so? My system: bash-2.05b$ uname -a FreeBSD smira.mlab.cs.msu.su 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Wed Oct 13 13:50:01 MSD 2004 root@smira.mlab.cs.msu.su:/usr/src/sys/i386/compile/smira.mobile i386 acpidump -d -t output, bzipped: http://images.delit.net/acpidump.asl.bz2 Thanks, Andrey. From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 20:15:18 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E46C16A4CE; Wed, 17 Nov 2004 20:15:18 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1183643D48; Wed, 17 Nov 2004 20:15:18 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222])iAHKF9DU000726; Wed, 17 Nov 2004 15:15:10 -0500 Message-ID: <419BB147.5030209@root.org> Date: Wed, 17 Nov 2004 12:15:03 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ruslan Ermilov References: <20041115211636.GA1540@laptop.6bone.nl> <20041117110450.GC24927@ip.net.ua> In-Reply-To: <20041117110450.GC24927@ip.net.ua> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 20:15:18 -0000 Ruslan Ermilov wrote: > On Mon, Nov 15, 2004 at 10:16:36PM +0100, Mark Santcroos wrote: > >>If the following patch doesn't burn down too many systems, it will be >>committed to HEAD in the near future. >> >>http://www.santcroos.net/mark/freebsd/files/acpi_import_20041105.diff.gz >> > > Nothing has improved (I still can't get S3 to work, and I get > interrupt storms with and only with ACPI), but at least I do > not see any regression. ;) Have you tested jhb@'s interrupt patch posted a few days ago here? -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 20:17:46 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E85CD16A4CE; Wed, 17 Nov 2004 20:17:46 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B74643D1D; Wed, 17 Nov 2004 20:17:46 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222])iAHKHcDU004633; Wed, 17 Nov 2004 15:17:38 -0500 Message-ID: <419BB1DB.3090002@root.org> Date: Wed, 17 Nov 2004 12:17:31 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <419A8CEB.4070305@root.org> <200411170905.34296.jhb@FreeBSD.org> In-Reply-To: <200411170905.34296.jhb@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org cc: gallatin@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 20:17:47 -0000 John Baldwin wrote: > On Tuesday 16 November 2004 06:27 pm, Nate Lawson wrote: > >>John Baldwin wrote: >> >>>On Thursday 11 November 2004 05:37 pm, John Baldwin wrote: >>> >>>>I've done some work on the ACPI PCI link code to make it a bit more like >>>>$PIR in that it is link centric and uses actual new-bus devices for each >>>>device link. One benefit of this is that unused links will be disabled >>>>now which might help with interrupt aliasing problems on machines using >>>>APICs. Also, instead of routing IRQs for links via PCI device numbers >>>>using tunables, they are now routed via the link name ala $PIR. Thus, >>>>one uses 'hw.pci.link.LNKA.irq=X' to route LNKA to IRQ X. Also, when >>>>choosing a virgin interrupt, we no longer try to guess at which IRQs >>>>might be used by ISA devices. Instead, we only use known-good IRQs >>>>including IRQs that the BIOS has already used and the SCI if the link is >>>>being routed via ISA IRQs. The patch is at >>>>http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch Please test and >>>>let me know if there are any problems, thanks. >>> >>>I've updated this to the latest current and verified that it compiles ok >>>(since I had at least one report that it didn't patch cleanly and/or >>>compile). I plan to commit this in a couple of days unless I hear some >>>sort of negative feedback. >> >>Oh, please s/style(msmith)/style(9) in some parts you added. > > > Heh, I can do that in the new code, sure. I just ask because acpi_pci_link.c was already closer to style(9) and I'd like all new modules to do that as well. Changes to style(msmith) files should conform to the existing file unless they rewrite it so much that it can be brought into compliance easily. -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 20:24:21 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6037F16A4CE for ; Wed, 17 Nov 2004 20:24:21 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69A1643D2D for ; Wed, 17 Nov 2004 20:24:20 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAHKOJC1043036; Wed, 17 Nov 2004 22:24:19 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 77867-05; Wed, 17 Nov 2004 22:24:18 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAHKOHoA043029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 22:24:18 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAHKOKIK027837; Wed, 17 Nov 2004 22:24:20 +0200 (EET) (envelope-from ru) Date: Wed, 17 Nov 2004 22:24:19 +0200 From: Ruslan Ermilov To: Nate Lawson Message-ID: <20041117202419.GH26967@ip.net.ua> References: <20041115211636.GA1540@laptop.6bone.nl> <20041117110450.GC24927@ip.net.ua> <419BB147.5030209@root.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fmEUq8M7S0s+Fl0V" Content-Disposition: inline In-Reply-To: <419BB147.5030209@root.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-acpi@FreeBSD.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 20:24:21 -0000 --fmEUq8M7S0s+Fl0V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 17, 2004 at 12:15:03PM -0800, Nate Lawson wrote: > Ruslan Ermilov wrote: > >On Mon, Nov 15, 2004 at 10:16:36PM +0100, Mark Santcroos wrote: > > > >>If the following patch doesn't burn down too many systems, it will be > >>committed to HEAD in the near future. > >> > >>http://www.santcroos.net/mark/freebsd/files/acpi_import_20041105.diff.gz > >> > > > >Nothing has improved (I still can't get S3 to work, and I get > >interrupt storms with and only with ACPI), but at least I do > >not see any regression. ;) >=20 > Have you tested jhb@'s interrupt patch posted a few days ago here? >=20 Yes, it causes a panic on boot (I reported this in a reply to John's email). Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --fmEUq8M7S0s+Fl0V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBm7NzqRfpzJluFF4RAv8TAKCMq1+yBen+d99JJbLKesWj7C0d4gCfc3zS LZQsUdty8sb1lRO08blFw5g= =gdAe -----END PGP SIGNATURE----- --fmEUq8M7S0s+Fl0V-- From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 20:27:53 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD89B16A4CE for ; Wed, 17 Nov 2004 20:27:53 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9073F43D41 for ; Wed, 17 Nov 2004 20:27:53 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222])iAHKRgDU019767; Wed, 17 Nov 2004 15:27:43 -0500 Message-ID: <419BB438.3040906@root.org> Date: Wed, 17 Nov 2004 12:27:36 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrey Smirnov References: <419BB14C.1060301@delit.net> In-Reply-To: <419BB14C.1060301@delit.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: Why C3 state isn't entered? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 20:27:54 -0000 Andrey Smirnov wrote: > Hello! > > I've got Centrino notebook (specifically Asus M3700Np), and it doesn't > seem to enter C3 sleep state in any case. > Sample output from 'sysctl hw.acpi.cpu' (while working at battery): > > hw.acpi.cpu.cx_supported: C1/0 C2/1 C3/101 > hw.acpi.cpu.cx_lowest: C3 > hw.acpi.cpu.cx_usage: 0.00% 100.00% 0.00% > > So C3 is supported, is allowed but isn't entered according to cx_usage. > Why could it be so? > > My system: > bash-2.05b$ uname -a > FreeBSD smira.mlab.cs.msu.su 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Wed Oct > 13 13:50:01 MSD 2004 > root@smira.mlab.cs.msu.su:/usr/src/sys/i386/compile/smira.mobile i386 > > acpidump -d -t output, bzipped: > http://images.delit.net/acpidump.asl.bz2 This is a FAQ, perhaps we can add it to the handbook entry or man page: C3 can't be entered while bus masters are active. Typical bus mastering devices include USB and sound. Since USB constantly polls when loaded, disabling USB support or stopping sound playback should allow C3 to be used. A better fix would be to power down the USB host controller when idle. -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 20:59:54 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4972216A4CE; Wed, 17 Nov 2004 20:59:54 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5067B43D2D; Wed, 17 Nov 2004 20:59:53 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAHKxq6W044852; Wed, 17 Nov 2004 22:59:52 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 80233-02; Wed, 17 Nov 2004 22:59:51 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAHKxpjn044849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 22:59:51 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAHKxr1F073277; Wed, 17 Nov 2004 22:59:53 +0200 (EET) (envelope-from ru) Date: Wed, 17 Nov 2004 22:59:53 +0200 From: Ruslan Ermilov To: John Baldwin Message-ID: <20041117205952.GB68320@ip.net.ua> References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <20041117154146.GD25995@ip.net.ua> <200411171124.48268.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XF85m9dhOBO43t/C" Content-Disposition: inline In-Reply-To: <200411171124.48268.jhb@FreeBSD.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: acpi@freebsd.org cc: freebsd-acpi@freebsd.org cc: gallatin@freebsd.org cc: scottl@freebsd.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 20:59:54 -0000 --XF85m9dhOBO43t/C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 17, 2004 at 11:24:48AM -0500, John Baldwin wrote: > On Wednesday 17 November 2004 10:41 am, Ruslan Ermilov wrote: > > I get a panic on boot with this change. I don't have a serial > > console attached to this notebook, but if needs be it can be > > arranged (tomorrow). The panic I get is as follows: > > > > panic: Assertion resource->Data.Irq.NumberOfInterrupts =3D=3D 1 failed = at > > .../acpi_pci_link.c:497 >=20 > Can you print out what 'NumberOfInterrupts' is before the printf? Drew h= as a=20 > machine that has hit the same panic as well. >=20 It's zero. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --XF85m9dhOBO43t/C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBm7vIqRfpzJluFF4RAlVQAJ9Ozwr7vV2qo5Mbzh6Pxhuf+E4zKQCfaDJk W3x6TSkNcqRnvgtbhkL0JyA= =TP96 -----END PGP SIGNATURE----- --XF85m9dhOBO43t/C-- From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 20:59:54 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4972216A4CE; Wed, 17 Nov 2004 20:59:54 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5067B43D2D; Wed, 17 Nov 2004 20:59:53 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAHKxq6W044852; Wed, 17 Nov 2004 22:59:52 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 80233-02; Wed, 17 Nov 2004 22:59:51 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAHKxpjn044849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 22:59:51 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAHKxr1F073277; Wed, 17 Nov 2004 22:59:53 +0200 (EET) (envelope-from ru) Date: Wed, 17 Nov 2004 22:59:53 +0200 From: Ruslan Ermilov To: John Baldwin Message-ID: <20041117205952.GB68320@ip.net.ua> References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <20041117154146.GD25995@ip.net.ua> <200411171124.48268.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XF85m9dhOBO43t/C" Content-Disposition: inline In-Reply-To: <200411171124.48268.jhb@FreeBSD.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: acpi@freebsd.org cc: freebsd-acpi@freebsd.org cc: gallatin@freebsd.org cc: scottl@freebsd.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 20:59:54 -0000 --XF85m9dhOBO43t/C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 17, 2004 at 11:24:48AM -0500, John Baldwin wrote: > On Wednesday 17 November 2004 10:41 am, Ruslan Ermilov wrote: > > I get a panic on boot with this change. I don't have a serial > > console attached to this notebook, but if needs be it can be > > arranged (tomorrow). The panic I get is as follows: > > > > panic: Assertion resource->Data.Irq.NumberOfInterrupts =3D=3D 1 failed = at > > .../acpi_pci_link.c:497 >=20 > Can you print out what 'NumberOfInterrupts' is before the printf? Drew h= as a=20 > machine that has hit the same panic as well. >=20 It's zero. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --XF85m9dhOBO43t/C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBm7vIqRfpzJluFF4RAlVQAJ9Ozwr7vV2qo5Mbzh6Pxhuf+E4zKQCfaDJk W3x6TSkNcqRnvgtbhkL0JyA= =TP96 -----END PGP SIGNATURE----- --XF85m9dhOBO43t/C-- From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 21:18:56 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02F9B16A4CE; Wed, 17 Nov 2004 21:18:56 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE16D43D5E; Wed, 17 Nov 2004 21:18:55 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAHLIsC4010307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Nov 2004 13:18:54 -0800 Message-ID: <419BC030.5080803@root.org> Date: Wed, 17 Nov 2004 13:18:40 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ruslan Ermilov References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <20041117154146.GD25995@ip.net.ua> <200411171124.48268.jhb@FreeBSD.org> <20041117205952.GB68320@ip.net.ua> In-Reply-To: <20041117205952.GB68320@ip.net.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@freebsd.org cc: freebsd-acpi@freebsd.org cc: gallatin@freebsd.org cc: scottl@freebsd.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 21:18:56 -0000 Ruslan Ermilov wrote: > On Wed, Nov 17, 2004 at 11:24:48AM -0500, John Baldwin wrote: > >>On Wednesday 17 November 2004 10:41 am, Ruslan Ermilov wrote: >> >>>I get a panic on boot with this change. I don't have a serial >>>console attached to this notebook, but if needs be it can be >>>arranged (tomorrow). The panic I get is as follows: >>> >>>panic: Assertion resource->Data.Irq.NumberOfInterrupts == 1 failed at >>>.../acpi_pci_link.c:497 >> >>Can you print out what 'NumberOfInterrupts' is before the printf? Drew has a >>machine that has hit the same panic as well. >> > > It's zero. Is line 497 in _CRS? It's ok to return 0 interrupts from _CRS if the link was disabled. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 21:18:56 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02F9B16A4CE; Wed, 17 Nov 2004 21:18:56 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE16D43D5E; Wed, 17 Nov 2004 21:18:55 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAHLIsC4010307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Nov 2004 13:18:54 -0800 Message-ID: <419BC030.5080803@root.org> Date: Wed, 17 Nov 2004 13:18:40 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ruslan Ermilov References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <20041117154146.GD25995@ip.net.ua> <200411171124.48268.jhb@FreeBSD.org> <20041117205952.GB68320@ip.net.ua> In-Reply-To: <20041117205952.GB68320@ip.net.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@freebsd.org cc: freebsd-acpi@freebsd.org cc: gallatin@freebsd.org cc: scottl@freebsd.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 21:18:56 -0000 Ruslan Ermilov wrote: > On Wed, Nov 17, 2004 at 11:24:48AM -0500, John Baldwin wrote: > >>On Wednesday 17 November 2004 10:41 am, Ruslan Ermilov wrote: >> >>>I get a panic on boot with this change. I don't have a serial >>>console attached to this notebook, but if needs be it can be >>>arranged (tomorrow). The panic I get is as follows: >>> >>>panic: Assertion resource->Data.Irq.NumberOfInterrupts == 1 failed at >>>.../acpi_pci_link.c:497 >> >>Can you print out what 'NumberOfInterrupts' is before the printf? Drew has a >>machine that has hit the same panic as well. >> > > It's zero. Is line 497 in _CRS? It's ok to return 0 interrupts from _CRS if the link was disabled. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 21:19:45 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0A9A16A4D0; Wed, 17 Nov 2004 21:19:44 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9873243D58; Wed, 17 Nov 2004 21:19:44 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP id IBA74465; Wed, 17 Nov 2004 13:19:44 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id E583E5D0A; Wed, 17 Nov 2004 13:19:43 -0800 (PST) To: Nate Lawson In-reply-to: Your message of "Wed, 17 Nov 2004 12:14:15 PST." <419BB117.4070802@root.org> Date: Wed, 17 Nov 2004 13:19:43 -0800 From: "Kevin Oberman" Message-Id: <20041117211943.E583E5D0A@ptavv.es.net> cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org cc: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 21:19:45 -0000 > Date: Wed, 17 Nov 2004 12:14:15 -0800 > From: Nate Lawson > Sender: owner-freebsd-acpi@freebsd.org > > Søren Schmidt wrote: > > There are nasties in the bat stuff, I have to comment out various parts > > of it to get the ASUS to boot at all :( > > > > > > This brings up the question: do we have a maintainer for ACPI and why > > arent these issues being dealt with ? I for one have reported these > > issue for ages including as much debug as is possible, but it seems to > > be silently ignored (and yes 5.3-RELEASE is just as broken)... > > > > cvs logs will show who is active in each area of acpi. I'm sure that's > a rhetorical question though. > > As for your particular problems, the battery issue may be related to > your system not operating according to the locking model. I fixed one > thermal problem for brooks@ where his ASL generated notifies every time > we read the temperature and the notify handler read the temperature. It > may be something similar. Send me the ASL and I'll take a look. The > suspend/resume issue has not been isolated but you can start by checking > where it gets with a serial console attached (if it gets that far) or by > putting some beep code in the resume handler to see if it even gets > called (Warner has the patch in his tree, it may make sense to commit it > under some option to help with debugging.) > > I'd love it if more people would help with debugging. I'm sure you can > relate to maintaining a subsystem where behavior is widely divergent > even among the same model device, OEM bugs are rampant and undocumented, > and you don't have access to a system that can repeat the behavior that > the submitter is reporting. > > As donations@ shows, I'm willing to accept problem laptops on loan or > for donation. Currently, I own an IBM R32, T23, Sony PCG-F390, and Abit > SMP. All work correctly including suspend/resume to RAM for the laptops. Nate, Does the sound work properly on the R32 and T23 after S3 resume? I suspect the problem with my system is limited to very few models, maybe just the T30 and R40. It only shows up in that sound plays too fast (at the raw device rate rather then the programmed rate). I do suspect that this is a PCI power issue and not an ACPI issue, but I'd like to know if it shows up on more models. It is most obvious when playing a stream as the buffers keep emptying and the sound stops after a short time. Music is clearly too fast and high pitched, but at 10% overspeed, some may not notice. (Does Dr. Dre sound much different 10% faster?) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 21:22:52 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76E4E16A4CE for ; Wed, 17 Nov 2004 21:22:52 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FBEE43D45 for ; Wed, 17 Nov 2004 21:22:52 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAHLMkC4010446 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Nov 2004 13:22:48 -0800 Message-ID: <419BC119.4040209@root.org> Date: Wed, 17 Nov 2004 13:22:33 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrey Smirnov References: <419BB14C.1060301@delit.net> <419BB438.3040906@root.org> <419BBFAA.3000605@delit.net> In-Reply-To: <419BBFAA.3000605@delit.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@FreeBSD.org Subject: Re: Why C3 state isn't entered? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 21:22:52 -0000 Andrey Smirnov wrote: > Nate Lawson wrote: >> This is a FAQ, perhaps we can add it to the handbook entry or man page: >> >> C3 can't be entered while bus masters are active. Typical bus >> mastering devices include USB and sound. Since USB constantly polls >> when loaded, disabling USB support or stopping sound playback should >> allow C3 to be used. A better fix would be to power down the USB host >> controller when idle. >> >> -Nate >> > Thanks for the quick answer, so if I use USB mouse I won't be able to > use C3 state? Is there a way to disable USB polling, if I know I won't > connect new devices, or it is required for normal USB operation? > As I understand it, C3 would give me much more power savings, so it will > extend battery life? (If the effect is less than 10%, it isn't very > important to me). If you have the USB driver (usb.ko) loaded or compiled into the kernel, you can't use C3. The way to disable it is to implement support for idling ports in uhci, ehci, and ohci. C3 doesn't make a huge difference (2-5%?) compared to C2 although it does help. I did some profiling of this a while back and found that the top three power saving features are dimming the display (by far the most), changing CPU frequency (similar but definitely less), and C2/C3 (better than C1 but not nearly as much savings as the first two). -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 21:26:21 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F25616A4CE; Wed, 17 Nov 2004 21:26:21 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1336243D55; Wed, 17 Nov 2004 21:26:21 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAHLQ1C4010485 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Nov 2004 13:26:02 -0800 Message-ID: <419BC1DC.7080603@root.org> Date: Wed, 17 Nov 2004 13:25:48 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Oberman References: <20041117211943.E583E5D0A@ptavv.es.net> In-Reply-To: <20041117211943.E583E5D0A@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org cc: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 21:26:21 -0000 Kevin Oberman wrote: >>Date: Wed, 17 Nov 2004 12:14:15 -0800 >>From: Nate Lawson >>I'd love it if more people would help with debugging. I'm sure you can >>relate to maintaining a subsystem where behavior is widely divergent >>even among the same model device, OEM bugs are rampant and undocumented, >>and you don't have access to a system that can repeat the behavior that >>the submitter is reporting. >> >>As donations@ shows, I'm willing to accept problem laptops on loan or >>for donation. Currently, I own an IBM R32, T23, Sony PCG-F390, and Abit >>SMP. All work correctly including suspend/resume to RAM for the laptops. > > Does the sound work properly on the R32 and T23 after S3 resume? I > suspect the problem with my system is limited to very few models, maybe > just the T30 and R40. It only shows up in that sound plays too fast (at > the raw device rate rather then the programmed rate). > > I do suspect that this is a PCI power issue and not an ACPI issue, but > I'd like to know if it shows up on more models. It is most obvious when > playing a stream as the buffers keep emptying and the sound stops after > a short time. Music is clearly too fast and high pitched, but at 10% > overspeed, some may not notice. (Does Dr. Dre sound much different 10% > faster?) I've tested sound thoroughly on my ICH3M system (T23) and it works exactly the same before and after suspend. I had a problem about a year ago where it would hang and stop delivering interrupts a short time after playing music after resume but that was fixed by Warner's pci power commit. I haven't tested the R32 sound after resume but will check it. It's probably similar to your R40 so it may exhibit the same problem. It's my wife's so I have to be able to grab it from her and reboot to FreeBSD to test. :) -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 22:48:26 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E75B116A4CE for ; Wed, 17 Nov 2004 22:48:26 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A77643D2D for ; Wed, 17 Nov 2004 22:48:26 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 24308 invoked from network); 17 Nov 2004 22:48:26 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 17 Nov 2004 22:48:25 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAHMmLfr093124; Wed, 17 Nov 2004 17:48:22 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Wed, 17 Nov 2004 15:19:18 -0500 User-Agent: KMail/1.6.2 References: <200411111737.00537.jhb@FreeBSD.org> <200411170905.34296.jhb@FreeBSD.org> <419BB1DB.3090002@root.org> In-Reply-To: <419BB1DB.3090002@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411171519.18473.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: gallatin@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 22:48:27 -0000 On Wednesday 17 November 2004 03:17 pm, Nate Lawson wrote: > John Baldwin wrote: > > On Tuesday 16 November 2004 06:27 pm, Nate Lawson wrote: > >>John Baldwin wrote: > >>>On Thursday 11 November 2004 05:37 pm, John Baldwin wrote: > >>>>I've done some work on the ACPI PCI link code to make it a bit more > >>>> like $PIR in that it is link centric and uses actual new-bus devices > >>>> for each device link. One benefit of this is that unused links will > >>>> be disabled now which might help with interrupt aliasing problems on > >>>> machines using APICs. Also, instead of routing IRQs for links via PCI > >>>> device numbers using tunables, they are now routed via the link name > >>>> ala $PIR. Thus, one uses 'hw.pci.link.LNKA.irq=X' to route LNKA to > >>>> IRQ X. Also, when choosing a virgin interrupt, we no longer try to > >>>> guess at which IRQs might be used by ISA devices. Instead, we only > >>>> use known-good IRQs including IRQs that the BIOS has already used and > >>>> the SCI if the link is being routed via ISA IRQs. The patch is at > >>>>http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch Please test and > >>>>let me know if there are any problems, thanks. > >>> > >>>I've updated this to the latest current and verified that it compiles ok > >>>(since I had at least one report that it didn't patch cleanly and/or > >>>compile). I plan to commit this in a couple of days unless I hear some > >>>sort of negative feedback. > >> > >>Oh, please s/style(msmith)/style(9) in some parts you added. > > > > Heh, I can do that in the new code, sure. > > I just ask because acpi_pci_link.c was already closer to style(9) and > I'd like all new modules to do that as well. Changes to style(msmith) > files should conform to the existing file unless they rewrite it so much > that it can be brought into compliance easily. I checked and acpi_pci_link.c with my changes is style(9), but the existing files are the other style, so I think it is good as is. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 22:48:40 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BB0E16A4D2 for ; Wed, 17 Nov 2004 22:48:40 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09EA843D54 for ; Wed, 17 Nov 2004 22:48:39 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 20274 invoked from network); 17 Nov 2004 22:48:38 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 17 Nov 2004 22:48:38 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAHMmLfw093124; Wed, 17 Nov 2004 17:48:34 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Nate Lawson Date: Wed, 17 Nov 2004 17:44:53 -0500 User-Agent: KMail/1.6.2 References: <200411111737.00537.jhb@FreeBSD.org> <20041117205952.GB68320@ip.net.ua> <419BC030.5080803@root.org> In-Reply-To: <419BC030.5080803@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411171744.53665.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org cc: scottl@FreeBSD.org cc: freebsd-acpi@FreeBSD.org cc: gallatin@FreeBSD.org cc: Ruslan Ermilov Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 22:48:40 -0000 On Wednesday 17 November 2004 04:18 pm, Nate Lawson wrote: > Ruslan Ermilov wrote: > > On Wed, Nov 17, 2004 at 11:24:48AM -0500, John Baldwin wrote: > >>On Wednesday 17 November 2004 10:41 am, Ruslan Ermilov wrote: > >>>I get a panic on boot with this change. I don't have a serial > >>>console attached to this notebook, but if needs be it can be > >>>arranged (tomorrow). The panic I get is as follows: > >>> > >>>panic: Assertion resource->Data.Irq.NumberOfInterrupts == 1 failed at > >>>.../acpi_pci_link.c:497 > >> > >>Can you print out what 'NumberOfInterrupts' is before the printf? Drew > >> has a machine that has hit the same panic as well. > > > > It's zero. > > Is line 497 in _CRS? It's ok to return 0 interrupts from _CRS if the > link was disabled. Erm, unless I've got a logic bug I don't run the KASSERT() for zero interrupts. Oh darn, I left a bogus KASSERT() in in the function that does the actual routing. The assertion's on lines 497 and 511 can be dropped. I'll update the patch in a second. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Wed Nov 17 22:48:40 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C5AE16A4D3 for ; Wed, 17 Nov 2004 22:48:40 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09BB243D49 for ; Wed, 17 Nov 2004 22:48:39 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 20274 invoked from network); 17 Nov 2004 22:48:38 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 17 Nov 2004 22:48:38 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAHMmLfw093124; Wed, 17 Nov 2004 17:48:34 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Nate Lawson Date: Wed, 17 Nov 2004 17:44:53 -0500 User-Agent: KMail/1.6.2 References: <200411111737.00537.jhb@FreeBSD.org> <20041117205952.GB68320@ip.net.ua> <419BC030.5080803@root.org> In-Reply-To: <419BC030.5080803@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411171744.53665.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org cc: scottl@FreeBSD.org cc: freebsd-acpi@FreeBSD.org cc: gallatin@FreeBSD.org cc: Ruslan Ermilov Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 22:48:40 -0000 On Wednesday 17 November 2004 04:18 pm, Nate Lawson wrote: > Ruslan Ermilov wrote: > > On Wed, Nov 17, 2004 at 11:24:48AM -0500, John Baldwin wrote: > >>On Wednesday 17 November 2004 10:41 am, Ruslan Ermilov wrote: > >>>I get a panic on boot with this change. I don't have a serial > >>>console attached to this notebook, but if needs be it can be > >>>arranged (tomorrow). The panic I get is as follows: > >>> > >>>panic: Assertion resource->Data.Irq.NumberOfInterrupts == 1 failed at > >>>.../acpi_pci_link.c:497 > >> > >>Can you print out what 'NumberOfInterrupts' is before the printf? Drew > >> has a machine that has hit the same panic as well. > > > > It's zero. > > Is line 497 in _CRS? It's ok to return 0 interrupts from _CRS if the > link was disabled. Erm, unless I've got a logic bug I don't run the KASSERT() for zero interrupts. Oh darn, I left a bogus KASSERT() in in the function that does the actual routing. The assertion's on lines 497 and 511 can be dropped. I'll update the patch in a second. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 00:19:48 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A14B416A4CE; Thu, 18 Nov 2004 00:19:48 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC19643D46; Thu, 18 Nov 2004 00:19:47 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAI0Jk3q055268; Thu, 18 Nov 2004 02:19:46 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 91466-15; Thu, 18 Nov 2004 02:19:45 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAI0Jj9N055265 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Nov 2004 02:19:45 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAI0JlDH057905; Thu, 18 Nov 2004 02:19:47 +0200 (EET) (envelope-from ru) Date: Thu, 18 Nov 2004 02:19:47 +0200 From: Ruslan Ermilov To: John Baldwin Message-ID: <20041118001947.GA53060@ip.net.ua> References: <200411111737.00537.jhb@FreeBSD.org> <20041117205952.GB68320@ip.net.ua> <419BC030.5080803@root.org> <200411171744.53665.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/9DWx/yDrRhgMJTb" Content-Disposition: inline In-Reply-To: <200411171744.53665.jhb@FreeBSD.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: acpi@FreeBSD.org cc: gallatin@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 00:19:48 -0000 --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 17, 2004 at 05:44:53PM -0500, John Baldwin wrote: [...] > Erm, unless I've got a logic bug I don't run the KASSERT() for zero=20 > interrupts. Oh darn, I left a bogus KASSERT() in in the function that do= es=20 > the actual routing. The assertion's on lines 497 and 511 can be dropped.= =20 > I'll update the patch in a second. >=20 With an updated patch, I no longer get panic on boot, and there are no more interrupt storms, but the latter is probably at the cost of old bug re-introduced. My dc(4) PCCard doesn't get a correct IRQ, "dc0: watchdog timeout". Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBm+qjqRfpzJluFF4RAid+AJ4naT2hr2TsZEaSR3APAaZK6mfc9gCggtVL z/6b4OPVplHm/dDGcS4kDPg= =yPji -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb-- From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 00:36:11 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EC6816A4CE for ; Thu, 18 Nov 2004 00:36:11 +0000 (GMT) Received: from onyx.hysteria.sk (onyx.hysteria.sk [195.168.3.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43AD343D31 for ; Thu, 18 Nov 2004 00:36:10 +0000 (GMT) (envelope-from rejden@hysteria.sk) Received: (qmail 10569 invoked by uid 1607); 18 Nov 2004 00:36:01 -0000 Date: Thu, 18 Nov 2004 01:36:01 +0100 From: rejden To: freebsd-acpi@freebsd.org Message-ID: <20041118003601.GA8873@hysteria.sk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i Subject: acpi cpu throttling X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 00:36:11 -0000 Hi, is there any way how to change CPU frequency with ACPI ? i saw something similar under linux, googling whole night and nothin... i'm running generic 5.3release kernel jan ----- daemon# sysctl -a |grep cpu kern.threads.virtual_cpu: 1 kern.ccpu: 1948 kern.smp.maxcpus: 1 kern.smp.cpus: 1 hw.ncpu: 1 hw.acpi.cpu.throttle_max: 8 hw.acpi.cpu.throttle_state: 8 hw.acpi.cpu.cx_supported: C1/1 C2/2 C3/185 hw.acpi.cpu.cx_lowest: C3 hw.acpi.cpu.cx_usage: 0.08% 99.91% 0.00% machdep.cpu_idle_hlt: 1 dev.cpu.0.%desc: ACPI CPU (3 Cx states) dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 daemon# dmesg -a |grep cpu cpu0: on acpi0 acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% hw.acpi.cpu.cx_lowest: hw.acpi.cpu.throttle_state: From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 00:36:50 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 244CA16A4CE; Thu, 18 Nov 2004 00:36:50 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id B91F843D31; Thu, 18 Nov 2004 00:36:49 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAI0Y91v059494; Wed, 17 Nov 2004 17:34:10 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Wed, 17 Nov 2004 17:34:09 -0700 (MST) Message-Id: <20041117.173409.104092741.imp@harmony.village.org> To: oberman@es.net From: Warner Losh In-Reply-To: <20041117211943.E583E5D0A@ptavv.es.net> References: <419BB117.4070802@root.org> <20041117211943.E583E5D0A@ptavv.es.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: sos@DeepCore.dk Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 00:36:50 -0000 > I do suspect that this is a PCI power issue and not an ACPI issue, but > I'd like to know if it shows up on more models. It is most obvious when > playing a stream as the buffers keep emptying and the sound stops after > a short time. Music is clearly too fast and high pitched, but at 10% > overspeed, some may not notice. (Does Dr. Dre sound much different 10% > faster?) I've flipped the sense of the PCI power sysctl in current. Once that's sanner, we should investigate setting the power states on resume. Not sure what to do about suspend, since I think that acpi has different notions of what D level to put a device in for different S levels and it would likely have to take care of that after giving the device a chance to save state. Warner From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 01:24:17 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED94316A4CE; Thu, 18 Nov 2004 01:24:17 +0000 (GMT) Received: from wonkity.com (wonkity.com [65.173.111.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F7A843D2D; Thu, 18 Nov 2004 01:24:17 +0000 (GMT) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.13.1/8.13.1) with ESMTP id iAI1O623015432; Wed, 17 Nov 2004 18:24:06 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.13.1/8.13.1/Submit) with ESMTP id iAI1O6rv015429; Wed, 17 Nov 2004 18:24:06 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 17 Nov 2004 18:24:06 -0700 (MST) From: Warren Block To: Nate Lawson In-Reply-To: <419BB117.4070802@root.org> Message-ID: <20041117181754.W12541@wonkity.com> References: <20041115211636.GA1540@laptop.6bone.nl> <419AF4E7.5000206@wanadoo.fr><419B194E.5090800@DeepCore.dk> <419BB117.4070802@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (wonkity.com [127.0.0.1]); Wed, 17 Nov 2004 18:24:06 -0700 (MST) cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org cc: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 01:24:18 -0000 On Wed, 17 Nov 2004, Nate Lawson wrote: > I'd love it if more people would help with debugging. I'm sure you can > relate to maintaining a subsystem where behavior is widely divergent even > among the same model device, OEM bugs are rampant and undocumented, and you > don't have access to a system that can repeat the behavior that the submitter > is reporting. Is there a test suite or procedure for what to test to verify ACPI function? Put something like that on the FLCL web site, and you may have more help than you want. 8-) http://gerda.univie.ac.at/freebsd-laptops/ -Warren Block * Rapid City, South Dakota USA From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 01:54:13 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 458E716A4CE; Thu, 18 Nov 2004 01:54:13 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0965743D4C; Thu, 18 Nov 2004 01:54:13 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAI1rvC4018177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Nov 2004 17:53:58 -0800 Message-ID: <419C00A7.7030300@root.org> Date: Wed, 17 Nov 2004 17:53:43 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Warner Losh References: <419BB117.4070802@root.org> <20041117211943.E583E5D0A@ptavv.es.net> <20041117.173409.104092741.imp@harmony.village.org> In-Reply-To: <20041117.173409.104092741.imp@harmony.village.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: sos@DeepCore.dk Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 01:54:13 -0000 Warner Losh wrote: >>I do suspect that this is a PCI power issue and not an ACPI issue, but >>I'd like to know if it shows up on more models. It is most obvious when >>playing a stream as the buffers keep emptying and the sound stops after >>a short time. Music is clearly too fast and high pitched, but at 10% >>overspeed, some may not notice. (Does Dr. Dre sound much different 10% >>faster?) > > I've flipped the sense of the PCI power sysctl in current. Once > that's sanner, we should investigate setting the power states on > resume. Not sure what to do about suspend, since I think that acpi > has different notions of what D level to put a device in for different > S levels and it would likely have to take care of that after giving > the device a chance to save state. > > Warner I have a patch in my tree to do this. I'll post it once it's well-tested. At the moment, setting UART to D3 appears to hang the system and I'm not sure why. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 03:27:43 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E88C16A4CE; Thu, 18 Nov 2004 03:27:43 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id A087843D31; Thu, 18 Nov 2004 03:27:42 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAI3PMsx060941; Wed, 17 Nov 2004 20:25:22 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Wed, 17 Nov 2004 20:25:21 -0700 (MST) Message-Id: <20041117.202521.74694027.imp@harmony.village.org> To: nate@root.org From: Warner Losh In-Reply-To: <419C00A7.7030300@root.org> References: <20041117211943.E583E5D0A@ptavv.es.net> <20041117.173409.104092741.imp@harmony.village.org> <419C00A7.7030300@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: imp@rover.village.org cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: sos@DeepCore.dk Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 03:27:43 -0000 From: Nate Lawson Subject: Re: [PATCH] Please test: new ACPI release (20041105) import Date: Wed, 17 Nov 2004 17:53:43 -0800 > Warner Losh wrote: > >>I do suspect that this is a PCI power issue and not an ACPI issue, but > >>I'd like to know if it shows up on more models. It is most obvious when > >>playing a stream as the buffers keep emptying and the sound stops after > >>a short time. Music is clearly too fast and high pitched, but at 10% > >>overspeed, some may not notice. (Does Dr. Dre sound much different 10% > >>faster?) > > > > I've flipped the sense of the PCI power sysctl in current. Once > > that's sanner, we should investigate setting the power states on > > resume. Not sure what to do about suspend, since I think that acpi > > has different notions of what D level to put a device in for different > > S levels and it would likely have to take care of that after giving > > the device a chance to save state. > > > > Warner > > I have a patch in my tree to do this. I'll post it once it's > well-tested. At the moment, setting UART to D3 appears to hang the > system and I'm not sure why. What do you mean 'UART'? I'm confused... Warner From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 03:44:20 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B51D716A4CE; Thu, 18 Nov 2004 03:44:20 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B06A43D31; Thu, 18 Nov 2004 03:44:20 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-185.dsl.snfc21.pacbell.net [64.171.186.185])iAI3i2DU010770; Wed, 17 Nov 2004 22:44:03 -0500 Message-ID: <419C1A7A.6050000@root.org> Date: Wed, 17 Nov 2004 19:43:54 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Warner Losh References: <20041117211943.E583E5D0A@ptavv.es.net> <20041117.173409.104092741.imp@harmony.village.org> <419C00A7.7030300@root.org> <20041117.202521.74694027.imp@harmony.village.org> In-Reply-To: <20041117.202521.74694027.imp@harmony.village.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: imp@rover.village.org cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: sos@DeepCore.dk Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 03:44:20 -0000 Warner Losh wrote: > From: Nate Lawson > Subject: Re: [PATCH] Please test: new ACPI release (20041105) import > Date: Wed, 17 Nov 2004 17:53:43 -0800 > > >>Warner Losh wrote: >> >>>>I do suspect that this is a PCI power issue and not an ACPI issue, but >>>>I'd like to know if it shows up on more models. It is most obvious when >>>>playing a stream as the buffers keep emptying and the sound stops after >>>>a short time. Music is clearly too fast and high pitched, but at 10% >>>>overspeed, some may not notice. (Does Dr. Dre sound much different 10% >>>>faster?) >>> >>>I've flipped the sense of the PCI power sysctl in current. Once >>>that's sanner, we should investigate setting the power states on >>>resume. Not sure what to do about suspend, since I think that acpi >>>has different notions of what D level to put a device in for different >>>S levels and it would likely have to take care of that after giving >>>the device a chance to save state. >>> >>>Warner >> >>I have a patch in my tree to do this. I'll post it once it's >>well-tested. At the moment, setting UART to D3 appears to hang the >>system and I'm not sure why. > > > What do you mean 'UART'? I'm confused... My serial port. It's named UART in the AML, that's all. Setting it to D3 hangs the system. -Nate From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 03:48:38 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0677416A4CE; Thu, 18 Nov 2004 03:48:38 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 542DD43D2D; Thu, 18 Nov 2004 03:48:36 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAI3m494061144; Wed, 17 Nov 2004 20:48:04 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Wed, 17 Nov 2004 20:48:04 -0700 (MST) Message-Id: <20041117.204804.71148446.imp@harmony.village.org> To: nate@root.org From: Warner Losh In-Reply-To: <419C1A7A.6050000@root.org> References: <419C00A7.7030300@root.org> <20041117.202521.74694027.imp@harmony.village.org> <419C1A7A.6050000@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: imp@rover.village.org cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: sos@DeepCore.dk Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 03:48:38 -0000 > My serial port. It's named UART in the AML, that's all. Setting it to > D3 hangs the system. Is it a PCI device too? If not, then maybe you need to disable interrupts in the UART before setting the power state. Chances are its interrupt cause register is returning 0xff, which hangs sio, since it never breaks out of the loop when this happens. Warner From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 06:01:54 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAF0816A4CE; Thu, 18 Nov 2004 06:01:54 +0000 (GMT) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9350D43D2D; Thu, 18 Nov 2004 06:01:54 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-185.dsl.snfc21.pacbell.net [64.171.186.185])iAI61rdl019655; Thu, 18 Nov 2004 01:01:53 -0500 Message-ID: <419C3AC2.5010505@root.org> Date: Wed, 17 Nov 2004 22:01:38 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Warner Losh References: <419C00A7.7030300@root.org> <20041117.202521.74694027.imp@harmony.village.org> <419C1A7A.6050000@root.org> <20041117.204804.71148446.imp@harmony.village.org> In-Reply-To: <20041117.204804.71148446.imp@harmony.village.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 06:01:55 -0000 Warner Losh wrote: >>My serial port. It's named UART in the AML, that's all. Setting it to >>D3 hangs the system. > > Is it a PCI device too? If not, then maybe you need to disable > interrupts in the UART before setting the power state. Chances are > its interrupt cause register is returning 0xff, which hangs sio, since > it never breaks out of the loop when this happens. It is not, it's a legacy device: sio0 pnpinfo _HID=PNP0501 _UID=0 at handle=\_SB_.PCI0.LPC_.UART The power methods for it are: Method (_PS0, 0, NotSerialized) { Store (0x03, LDN) Store (0x01, LDA) Store (0x01, SSBY) } Method (_PS3, 0, NotSerialized) { Store (0x03, LDN) Store (0x00, LDA) Store (0x00, SSBY) } The regions accessed by these Store ops are as follows, and all appear to be mapped to the ICH: OperationRegion (IMGA, SystemIO, 0x15E0, 0x10) OperationRegion (NCFG, SystemIO, 0x2E, 0x02) Is there a standard for how to do power transitions for non-PCI devices? I thought you just call the acpi methods if present. -Nate From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 08:46:29 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A342416A4CE; Thu, 18 Nov 2004 08:46:29 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C16D143D1F; Thu, 18 Nov 2004 08:46:28 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAI8kRN5083124; Thu, 18 Nov 2004 10:46:27 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 19342-17; Thu, 18 Nov 2004 10:46:25 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAI8kPH1083116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Nov 2004 10:46:25 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAI8kSlU072064; Thu, 18 Nov 2004 10:46:28 +0200 (EET) (envelope-from ru) Date: Thu, 18 Nov 2004 10:46:27 +0200 From: Ruslan Ermilov To: John Baldwin Message-ID: <20041118084627.GA72018@ip.net.ua> References: <200411111737.00537.jhb@FreeBSD.org> <20041117205952.GB68320@ip.net.ua> <419BC030.5080803@root.org> <200411171744.53665.jhb@FreeBSD.org> <20041118001947.GA53060@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+HP7ph2BbKc20aGI" Content-Disposition: inline In-Reply-To: <20041118001947.GA53060@ip.net.ua> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: acpi@FreeBSD.org cc: gallatin@FreeBSD.org cc: scottl@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 08:46:29 -0000 --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 18, 2004 at 02:19:47AM +0200, Ruslan Ermilov wrote: > On Wed, Nov 17, 2004 at 05:44:53PM -0500, John Baldwin wrote: > [...] > > Erm, unless I've got a logic bug I don't run the KASSERT() for zero=20 > > interrupts. Oh darn, I left a bogus KASSERT() in in the function that = does=20 > > the actual routing. The assertion's on lines 497 and 511 can be droppe= d. =20 > > I'll update the patch in a second. > >=20 > With an updated patch, I no longer get panic on boot, and there > are no more interrupt storms, but the latter is probably at the > cost of old bug re-introduced. My dc(4) PCCard doesn't get a > correct IRQ, "dc0: watchdog timeout". >=20 I've put a verbose boot output here, as requested: http://people.freebsd.org/~ru/dmesg.boot Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --+HP7ph2BbKc20aGI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBnGFjqRfpzJluFF4RAseoAJ4ma4QRmBsvhHVxfHrLAzf0eMvvFACfZh8A MFS2m/ipT/6+onmm7ZOd0vw= =pAqj -----END PGP SIGNATURE----- --+HP7ph2BbKc20aGI-- From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 08:52:05 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F185E16A4CE for ; Thu, 18 Nov 2004 08:52:05 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D4D243D2F for ; Thu, 18 Nov 2004 08:52:05 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAI8q4Bm083446; Thu, 18 Nov 2004 10:52:04 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 20443-03; Thu, 18 Nov 2004 10:52:03 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAI8q34Q083443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Nov 2004 10:52:03 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAI8q5Nc072163; Thu, 18 Nov 2004 10:52:05 +0200 (EET) (envelope-from ru) Date: Thu, 18 Nov 2004 10:52:05 +0200 From: Ruslan Ermilov To: rejden Message-ID: <20041118085205.GC72018@ip.net.ua> References: <20041118003601.GA8873@hysteria.sk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MnLPg7ZWsaic7Fhd" Content-Disposition: inline In-Reply-To: <20041118003601.GA8873@hysteria.sk> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-acpi@freebsd.org Subject: Re: acpi cpu throttling X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 08:52:06 -0000 --MnLPg7ZWsaic7Fhd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 18, 2004 at 01:36:01AM +0100, rejden wrote: > Hi, > is there any way how to change CPU frequency with ACPI ? > i saw something similar under linux, googling whole night and nothin... > i'm running generic 5.3release kernel >=20 > jan >=20 > ----- >=20 > daemon# sysctl -a |grep cpu > kern.threads.virtual_cpu: 1 > kern.ccpu: 1948 > kern.smp.maxcpus: 1 > kern.smp.cpus: 1 > hw.ncpu: 1 > hw.acpi.cpu.throttle_max: 8 > hw.acpi.cpu.throttle_state: 8 > hw.acpi.cpu.cx_supported: C1/1 C2/2 C3/185 > hw.acpi.cpu.cx_lowest: C3 > hw.acpi.cpu.cx_usage: 0.08% 99.91% 0.00% > machdep.cpu_idle_hlt: 1 > dev.cpu.0.%desc: ACPI CPU (3 Cx states) > dev.cpu.0.%driver: cpu > dev.cpu.0.%location: handle=3D\_PR_.CPU0 > dev.cpu.0.%pnpinfo: _HID=3Dnone _UID=3D0 > dev.cpu.0.%parent: acpi0 >=20 > daemon# dmesg -a |grep cpu > cpu0: on acpi0 > acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% > hw.acpi.cpu.cx_lowest:=20 > hw.acpi.cpu.throttle_state:=20 >=20 Yes, go read acpi(4) manpage when it talks about SYSCTLS. You want hw.acpi.cpu.throttle_state. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --MnLPg7ZWsaic7Fhd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBnGK1qRfpzJluFF4RAoLTAKCTeCP9nkWvcFTigulG1ZcLR59cYACffSam BQGXo1Qw5IsrXEfFXtb0Cdo= =pAyg -----END PGP SIGNATURE----- --MnLPg7ZWsaic7Fhd-- From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 09:53:29 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F249A16A4CE for ; Thu, 18 Nov 2004 09:53:29 +0000 (GMT) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 878AC43D2F for ; Thu, 18 Nov 2004 09:53:29 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1CUiyB-0003nh-00; Thu, 18 Nov 2004 10:52:51 +0100 Date: Thu, 18 Nov 2004 10:52:51 +0100 To: Nate Lawson Message-ID: <20041118095251.GZ31422@poupinou.org> References: <419BB14C.1060301@delit.net> <419BB438.3040906@root.org> <419BBFAA.3000605@delit.net> <419BC119.4040209@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <419BC119.4040209@root.org> User-Agent: Mutt/1.5.5.1+cvs20040105i From: Bruno Ducrot cc: acpi@FreeBSD.org Subject: Re: Why C3 state isn't entered? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 09:53:30 -0000 On Wed, Nov 17, 2004 at 01:22:33PM -0800, Nate Lawson wrote: > If you have the USB driver (usb.ko) loaded or compiled into the kernel, > you can't use C3. The way to disable it is to implement support for > idling ports in uhci, ehci, and ohci. C3 doesn't make a huge difference > (2-5%?) compared to C2 although it does help. I did some profiling of > this a while back and found that the top three power saving features are > dimming the display (by far the most), changing CPU frequency (similar > but definitely less), and C2/C3 (better than C1 but not nearly as much > savings as the first two). > Spin down disks is maybe more important than CPU frequency scaling also. -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 16:15:48 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFB8A16A4CE; Thu, 18 Nov 2004 16:15:48 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40C9043D58; Thu, 18 Nov 2004 16:15:48 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAIGD6cb070490; Thu, 18 Nov 2004 09:13:06 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 18 Nov 2004 09:13:32 -0700 (MST) Message-Id: <20041118.091332.71089191.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <419C3AC2.5010505@root.org> References: <419C1A7A.6050000@root.org> <20041117.204804.71148446.imp@harmony.village.org> <419C3AC2.5010505@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 16:15:49 -0000 In message: <419C3AC2.5010505@root.org> Nate Lawson writes: : Warner Losh wrote: : >>My serial port. It's named UART in the AML, that's all. Setting it to : >>D3 hangs the system. : > : > Is it a PCI device too? If not, then maybe you need to disable : > interrupts in the UART before setting the power state. Chances are : > its interrupt cause register is returning 0xff, which hangs sio, since : > it never breaks out of the loop when this happens. : : It is not, it's a legacy device: : sio0 pnpinfo _HID=PNP0501 _UID=0 at handle=\_SB_.PCI0.LPC_.UART : : The power methods for it are: : Method (_PS0, 0, NotSerialized) : { : Store (0x03, LDN) : Store (0x01, LDA) : Store (0x01, SSBY) : } : : Method (_PS3, 0, NotSerialized) : { : Store (0x03, LDN) : Store (0x00, LDA) : Store (0x00, SSBY) : } : : The regions accessed by these Store ops are as follows, and all appear : to be mapped to the ICH: : OperationRegion (IMGA, SystemIO, 0x15E0, 0x10) : OperationRegion (NCFG, SystemIO, 0x2E, 0x02) : : Is there a standard for how to do power transitions for non-PCI devices? : I thought you just call the acpi methods if present. There might be some driver stuff that will need to be done on top of the calling these things. I don't know what the behavior of the device is, but many pci devices read 0xffffffff when in d3 mode. Warner From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 17:39:10 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08E7016A4CE for ; Thu, 18 Nov 2004 17:39:10 +0000 (GMT) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id B434543D41 for ; Thu, 18 Nov 2004 17:39:09 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222])iAIHd8dl027055; Thu, 18 Nov 2004 12:39:09 -0500 Message-ID: <419CDE22.8040402@root.org> Date: Thu, 18 Nov 2004 09:38:42 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: rejden References: <20041118003601.GA8873@hysteria.sk> In-Reply-To: <20041118003601.GA8873@hysteria.sk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: acpi cpu throttling X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 17:39:10 -0000 rejden wrote: > Hi, > is there any way how to change CPU frequency with ACPI ? > i saw something similar under linux, googling whole night and nothin... > i'm running generic 5.3release kernel > > jan > > ----- > > daemon# sysctl -a |grep cpu > kern.threads.virtual_cpu: 1 > kern.ccpu: 1948 > kern.smp.maxcpus: 1 > kern.smp.cpus: 1 > hw.ncpu: 1 > hw.acpi.cpu.throttle_max: 8 > hw.acpi.cpu.throttle_state: 8 > hw.acpi.cpu.cx_supported: C1/1 C2/2 C3/185 > hw.acpi.cpu.cx_lowest: C3 > hw.acpi.cpu.cx_usage: 0.08% 99.91% 0.00% > machdep.cpu_idle_hlt: 1 > dev.cpu.0.%desc: ACPI CPU (3 Cx states) > dev.cpu.0.%driver: cpu > dev.cpu.0.%location: handle=\_PR_.CPU0 > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > dev.cpu.0.%parent: acpi0 > > daemon# dmesg -a |grep cpu > cpu0: on acpi0 > acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% > hw.acpi.cpu.cx_lowest: > hw.acpi.cpu.throttle_state: You can set it directly with sysctl hw.acpi.cpu.throttle_state. However, you will probably find using /etc/rc.conf more useful. There, you can set the online and offline Cx and throttling levels. See /etc/defaults/rc.conf for info. -Nate From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 18 17:44:37 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C95B816A4CE for ; Thu, 18 Nov 2004 17:44:37 +0000 (GMT) Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2005343D1F for ; Thu, 18 Nov 2004 17:44:37 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222])iAIHicJC024152; Thu, 18 Nov 2004 12:44:39 -0500 Message-ID: <419CDF6A.9090507@root.org> Date: Thu, 18 Nov 2004 09:44:10 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruno Ducrot References: <419BB14C.1060301@delit.net> <419BB438.3040906@root.org> <419BBFAA.3000605@delit.net> <419BC119.4040209@root.org> <20041118095251.GZ31422@poupinou.org> In-Reply-To: <20041118095251.GZ31422@poupinou.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@FreeBSD.org Subject: Re: Why C3 state isn't entered? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 17:44:37 -0000 Bruno Ducrot wrote: > On Wed, Nov 17, 2004 at 01:22:33PM -0800, Nate Lawson wrote: > >>If you have the USB driver (usb.ko) loaded or compiled into the kernel, >>you can't use C3. The way to disable it is to implement support for >>idling ports in uhci, ehci, and ohci. C3 doesn't make a huge difference >>(2-5%?) compared to C2 although it does help. I did some profiling of >>this a while back and found that the top three power saving features are >>dimming the display (by far the most), changing CPU frequency (similar >>but definitely less), and C2/C3 (better than C1 but not nearly as much >>savings as the first two). >> > > Spin down disks is maybe more important than CPU frequency scaling also. At least on my laptop, that didn't make much difference. But we have old behavior for many things like the syncer that is not power-aware so spinning down disks may not be as helpful. BTW, interested in implementing S4-OS for FreeBSD? :) -Nate From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 19 11:29:07 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E7E516A4CE for ; Fri, 19 Nov 2004 11:29:07 +0000 (GMT) Received: from daedalus.desk.pl (daedalus.desk.pl [62.233.238.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id A579B43D62 for ; Fri, 19 Nov 2004 11:29:06 +0000 (GMT) (envelope-from creep@daedalus.desk.pl) Received: from localhost (localhost [127.0.0.1]) by daedalus.desk.pl (Postfix) with ESMTP id A9FCC366E31 for ; Fri, 19 Nov 2004 12:20:22 +0100 (CET) Received: from daedalus.desk.pl ([127.0.0.1]) by localhost (daedalus [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19417-10 for ; Fri, 19 Nov 2004 12:20:20 +0100 (CET) Received: by daedalus.desk.pl (Postfix, from userid 1023) id C0BE9366E2E; Fri, 19 Nov 2004 12:20:20 +0100 (CET) Date: Fri, 19 Nov 2004 12:20:20 +0100 From: Marcin To: freebsd-acpi@freebsd.org Message-ID: <20041119112020.GA12853@daedalus.desk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Antivirus: Skaner Antywirusowy DESK.pl Subject: FBSD5.3 Compaq AP400 cannot warm-reboot (as in kern/27834) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 11:29:07 -0000 Hello FreeBSD users! I have posted this problem to freebsd-questions, but then figured it was not actually the best place to send it. I'm experiencing the same problem described in http://www.freebsd.org/cgi/query-pr.cgi?pr=27834 but the fix included doesn't actually fix the problem. The system is FreeBSD 5.3 with GENERIC kernel on dual Compaq AP400 (Professional workstation) (dmesg/mptables below). When i reboot the system shutdowns properly (prints Rebooting...) but then just hangs with no activity (screen blank, disk diodes dead,etc). I have to push power button two times to reboot it, which is impossible with remote administration. This is the case with acpi.ko not loaded or with acpi.ko loaded but APIC disabled with hints.acpi.0.disabled. When i want to load acpi.ko wit APIC enabled i get a panic at system boottime with following message: "ACPI disabled by blacklist. Contact your BIOS vendor." (from sys/dev/acpica/acpi.c acpi_Startup returning AE_ERROR) called by: MADT: ACPI Startup failed with ACPI disabled by blacklist. Contact your BIOS vendor. Try disabling either ACPI or apic support. panic("Using MADT but ACPI doesn't work"); (from sys/i386/acpica/madt.c madt_setup_io()) (i'm writing these from memory, i didn't have serial console to catch the exact message. If it's needed, i'll provide the exact hand written version) I thought that there is nothing i could do except installing linux back [there was a linux system there before, the person using it said he had no problem with rebooting] but when the ACPI panic happes (the one listed above) and the user is prompted to press any key [or wait 15 secs] system prints Rebooting... and really restarts the machine the way i want! I searched for 'Rebooting' code in the kernel. found sys/kern/kern_shutdown.c shutdown_reset which calls cpu_reset(), then, checked what shutdown(1)/reboot(1) do and found they call the same function... so what happens in cpu_reset() what is different at panic and normal shutdown is still a mystery to me, but may be a hint for someone knowing the subject. Hints? Ideas? Pointers? -- Best regards, m. DMESG: [with apic disabled, unfortunately i can't catch messages on panic] Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (399.06-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183fbff real memory = 335544320 (320 MB) avail memory = 318705664 (303 MB) ACPI disabled by blacklist. Contact your BIOS vendor. npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 $PIR: No matching entry for 0.11.INTA agp0: mem 0x54000000-0x57ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 sym0: <875> port 0x5000-0x50ff mem 0x50a00000-0x50a00fff,0x50b00000-0x50b000ff irq 11 at device 11.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym0: [GIANT-LOCKED] fxp0: port 0x5400-0x541f mem 0x50800000-0x508fffff,0x50c00000-0x50c00fff irq 11 at device 12.0 on pci0 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:08:c7:5c:cc:38 pci0: at device 15.0 (no driver attached) isab0: at device 20.0 on pci0 isa0: on isab0 atapci0: port 0x5440-0x544f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 20.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0x5420-0x543f irq 11 at device 20.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 20.3 (no driver attached) cpu0 on motherboard orm0: at iomem 0xec000-0xeffff,0xc8000-0xcbfff,0xc0000-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounter "TSC" frequency 399062929 Hz quality 800 Timecounters tick every 10.000 msec acd0: CDROM at ata0-master PIO4 Waiting 15 seconds for SCSI devices to settle da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 4067MB (8330543 512 byte sectors: 255H 63S/T 518C) Mounting root from ufs:/dev/da0s1a MPTables [with blank lines truncated] =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f6420 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0xfd mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f6430 signature: 'PCMP' base table length: 396 version: 1.4 checksum: 0x75 OEM ID: 'COMPAQ ' Product ID: 'Workstation ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 40 local APIC address: 0xfee00000 extended table length: 0 extended table checksum: 0 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 1 0x10 BSP, usable 6 5 2 0x183fbff 0 0x10 AP, usable 6 5 2 0x183fbff -- Bus: Bus ID Type 0 PCI 1 PCI 9 ISA -- I/O APICs: APIC ID Version State Address 8 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# INT active-lo level 0 12:A 8 20 INT active-lo level 0 11:A 8 21 INT active-lo level 0 1:A 8 22 INT active-lo level 0 1:B 8 23 INT active-lo level 0 16:A 8 16 INT active-lo level 0 16:B 8 17 INT active-lo level 0 16:C 8 18 INT active-lo level 0 16:D 8 19 INT active-lo level 0 15:A 8 18 INT active-lo level 0 15:B 8 19 INT active-lo level 0 15:C 8 16 INT active-lo level 0 15:D 8 17 INT active-lo level 0 14:A 8 19 INT active-lo level 0 14:B 8 16 INT active-lo level 0 14:C 8 17 INT active-lo level 0 14:D 8 18 INT active-lo level 0 13:A 8 17 INT active-lo level 0 13:B 8 18 INT active-lo level 0 13:C 8 19 INT active-lo level 0 13:D 8 16 INT conforms conforms 9 0 8 2 INT conforms conforms 9 1 8 1 INT conforms conforms 9 3 8 3 INT conforms conforms 9 4 8 4 INT conforms conforms 9 5 8 5 INT conforms conforms 9 6 8 6 INT conforms conforms 9 7 8 7 INT conforms conforms 9 8 8 8 INT conforms conforms 9 9 8 9 INT conforms conforms 9 10 8 10 INT conforms conforms 9 12 8 12 INT conforms conforms 9 13 8 13 INT conforms conforms 9 14 8 14 INT conforms conforms 9 15 8 15 =============================================================================== From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 19 14:16:56 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2485416A4CE for ; Fri, 19 Nov 2004 14:16:56 +0000 (GMT) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id D67E843D5C for ; Fri, 19 Nov 2004 14:16:55 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1CV9Yl-0004tF-00; Fri, 19 Nov 2004 15:16:23 +0100 Date: Fri, 19 Nov 2004 15:16:23 +0100 To: Nate Lawson Message-ID: <20041119141623.GF31422@poupinou.org> References: <419BB14C.1060301@delit.net> <419BB438.3040906@root.org> <419BBFAA.3000605@delit.net> <419BC119.4040209@root.org> <20041118095251.GZ31422@poupinou.org> <419CDF6A.9090507@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <419CDF6A.9090507@root.org> User-Agent: Mutt/1.5.5.1+cvs20040105i From: Bruno Ducrot cc: acpi@FreeBSD.org Subject: Re: Why C3 state isn't entered? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 14:16:56 -0000 On Thu, Nov 18, 2004 at 09:44:10AM -0800, Nate Lawson wrote: > Bruno Ducrot wrote: > >On Wed, Nov 17, 2004 at 01:22:33PM -0800, Nate Lawson wrote: > > > >>If you have the USB driver (usb.ko) loaded or compiled into the kernel, > >>you can't use C3. The way to disable it is to implement support for > >>idling ports in uhci, ehci, and ohci. C3 doesn't make a huge difference > >>(2-5%?) compared to C2 although it does help. I did some profiling of > >>this a while back and found that the top three power saving features are > >>dimming the display (by far the most), changing CPU frequency (similar > >>but definitely less), and C2/C3 (better than C1 but not nearly as much > >>savings as the first two). > >> > > > >Spin down disks is maybe more important than CPU frequency scaling also. > > At least on my laptop, that didn't make much difference. But we have > old behavior for many things like the syncer that is not power-aware so > spinning down disks may not be as helpful. Well, it was more a general note. Under FreeBSD, I guess you can save something like 6 or 7% of battery remaining times if a more power aware developpement is done for DD. I don't expect much more. Under Linux, there is a need to do much more tweaks to achive a 20-30% remaining time (via the laptop-mode) due to agressive disk access in general. > BTW, interested in implementing S4-OS for FreeBSD? :) I can't promise anything yet. Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 19 21:53:42 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17ECD16A4CE for ; Fri, 19 Nov 2004 21:53:42 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id A15E243D1D for ; Fri, 19 Nov 2004 21:53:41 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 19393 invoked from network); 19 Nov 2004 21:53:41 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 19 Nov 2004 21:53:41 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAJLrVcT007881; Fri, 19 Nov 2004 16:53:36 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Fri, 19 Nov 2004 15:59:46 -0500 User-Agent: KMail/1.6.2 References: <200411111737.00537.jhb@FreeBSD.org> <20041118001947.GA53060@ip.net.ua> <20041118084627.GA72018@ip.net.ua> In-Reply-To: <20041118084627.GA72018@ip.net.ua> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411191559.46209.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org cc: scottl@FreeBSD.org cc: gallatin@FreeBSD.org cc: Ruslan Ermilov Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 21:53:42 -0000 On Thursday 18 November 2004 03:46 am, Ruslan Ermilov wrote: > On Thu, Nov 18, 2004 at 02:19:47AM +0200, Ruslan Ermilov wrote: > > On Wed, Nov 17, 2004 at 05:44:53PM -0500, John Baldwin wrote: > > [...] > > > > > Erm, unless I've got a logic bug I don't run the KASSERT() for zero > > > interrupts. Oh darn, I left a bogus KASSERT() in in the function that > > > does the actual routing. The assertion's on lines 497 and 511 can be > > > dropped. I'll update the patch in a second. > > > > With an updated patch, I no longer get panic on boot, and there > > are no more interrupt storms, but the latter is probably at the > > cost of old bug re-introduced. My dc(4) PCCard doesn't get a > > correct IRQ, "dc0: watchdog timeout". > > I've put a verbose boot output here, as requested: > > http://people.freebsd.org/~ru/dmesg.boot Looks like it hung everything off of IRQ 9 since the BIOS didn't preset any device IRQs. What was the behavior prior to this patch? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 19 21:53:43 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C0A416A4CE for ; Fri, 19 Nov 2004 21:53:43 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id A208843D45 for ; Fri, 19 Nov 2004 21:53:41 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 19393 invoked from network); 19 Nov 2004 21:53:41 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 19 Nov 2004 21:53:41 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAJLrVcT007881; Fri, 19 Nov 2004 16:53:36 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Fri, 19 Nov 2004 15:59:46 -0500 User-Agent: KMail/1.6.2 References: <200411111737.00537.jhb@FreeBSD.org> <20041118001947.GA53060@ip.net.ua> <20041118084627.GA72018@ip.net.ua> In-Reply-To: <20041118084627.GA72018@ip.net.ua> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411191559.46209.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org cc: scottl@FreeBSD.org cc: gallatin@FreeBSD.org cc: Ruslan Ermilov Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 21:53:43 -0000 On Thursday 18 November 2004 03:46 am, Ruslan Ermilov wrote: > On Thu, Nov 18, 2004 at 02:19:47AM +0200, Ruslan Ermilov wrote: > > On Wed, Nov 17, 2004 at 05:44:53PM -0500, John Baldwin wrote: > > [...] > > > > > Erm, unless I've got a logic bug I don't run the KASSERT() for zero > > > interrupts. Oh darn, I left a bogus KASSERT() in in the function that > > > does the actual routing. The assertion's on lines 497 and 511 can be > > > dropped. I'll update the patch in a second. > > > > With an updated patch, I no longer get panic on boot, and there > > are no more interrupt storms, but the latter is probably at the > > cost of old bug re-introduced. My dc(4) PCCard doesn't get a > > correct IRQ, "dc0: watchdog timeout". > > I've put a verbose boot output here, as requested: > > http://people.freebsd.org/~ru/dmesg.boot Looks like it hung everything off of IRQ 9 since the BIOS didn't preset any device IRQs. What was the behavior prior to this patch? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 19 22:58:50 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4203A16A4CE; Fri, 19 Nov 2004 22:58:50 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 649FF43D1F; Fri, 19 Nov 2004 22:58:49 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAJMwmok023552; Sat, 20 Nov 2004 00:58:48 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 94433-16; Sat, 20 Nov 2004 00:58:47 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAJMwlaY023549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 20 Nov 2004 00:58:47 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAJMwoJT052274; Sat, 20 Nov 2004 00:58:50 +0200 (EET) (envelope-from ru) Date: Sat, 20 Nov 2004 00:58:50 +0200 From: Ruslan Ermilov To: John Baldwin Message-ID: <20041119225850.GA49744@ip.net.ua> References: <200411111737.00537.jhb@FreeBSD.org> <20041118001947.GA53060@ip.net.ua> <20041118084627.GA72018@ip.net.ua> <200411191559.46209.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline In-Reply-To: <200411191559.46209.jhb@FreeBSD.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: acpi@FreeBSD.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 22:58:50 -0000 --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 19, 2004 at 03:59:46PM -0500, John Baldwin wrote: > On Thursday 18 November 2004 03:46 am, Ruslan Ermilov wrote: > > On Thu, Nov 18, 2004 at 02:19:47AM +0200, Ruslan Ermilov wrote: > > > On Wed, Nov 17, 2004 at 05:44:53PM -0500, John Baldwin wrote: > > > [...] > > > > > > > Erm, unless I've got a logic bug I don't run the KASSERT() for zero > > > > interrupts. Oh darn, I left a bogus KASSERT() in in the function t= hat > > > > does the actual routing. The assertion's on lines 497 and 511 can = be > > > > dropped. I'll update the patch in a second. > > > > > > With an updated patch, I no longer get panic on boot, and there > > > are no more interrupt storms, but the latter is probably at the > > > cost of old bug re-introduced. My dc(4) PCCard doesn't get a > > > correct IRQ, "dc0: watchdog timeout". > > > > I've put a verbose boot output here, as requested: > > > > http://people.freebsd.org/~ru/dmesg.boot >=20 > Looks like it hung everything off of IRQ 9 since the BIOS didn't preset a= ny=20 > device IRQs. What was the behavior prior to this patch? >=20 http://people.freebsd.org/~ru/dmesg.boot2 The system is dead slow due to interrupt storm in IRQ 10, but at least dc(4) works. # vmstat -i interrupt total rate irq0: clk 353566 993 irq1: atkbd0 1134 3 irq6: fdc0 22 0 irq8: rtc 45394 127 irq9: acpi0 648 1 irq10: cbb1 dc0 28202293 79219 irq11: cbb0 csa0 689545 1936 irq12: psm0 1161 3 irq13: npx0 1 0 irq14: ata0 1939 5 irq15: ata1 52 0 Total 29295755 82291 Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBnnqpqRfpzJluFF4RAlkoAJ0TqPg+Fb7JjJcJr4H3vN4gWRrr8QCghXdS p0IRcXg7ZMwJfRJfo/fa0aA= =HnT7 -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- From owner-freebsd-acpi@FreeBSD.ORG Sat Nov 20 00:40:45 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C296D16A4CE for ; Sat, 20 Nov 2004 00:40:45 +0000 (GMT) Received: from alfred.skaarup.org (alfred.skaarup.org [195.234.155.140]) by mx1.FreeBSD.org (Postfix) with SMTP id E01D343D46 for ; Sat, 20 Nov 2004 00:40:44 +0000 (GMT) (envelope-from mfbsd@skaarup.org) Received: (qmail 88706 invoked by uid 98); 20 Nov 2004 00:40:43 -0000 Received: from mfbsd@skaarup.org by alfred.skaarup.org by uid 82 with qmail-scanner-1.20 (uvscan: v4.3.20/v4323. Clear:RC:1(127.0.0.1):. Processed in 0.0189 secs); 20 Nov 2004 00:40:43 -0000 X-Qmail-Scanner-Mail-From: mfbsd@skaarup.org via alfred.skaarup.org X-Qmail-Scanner: 1.20 (Clear:RC:1(127.0.0.1):. Processed in 0.0189 secs) Received: from localhost (HELO alfred.skaarup.org) (127.0.0.1) by localhost with SMTP; 20 Nov 2004 00:40:43 -0000 Received: (qmail 88698 invoked by uid 1039); 20 Nov 2004 00:40:43 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Nov 2004 00:40:43 -0000 Date: Sat, 20 Nov 2004 01:40:43 +0100 (CET) From: Rasmus Skaarup To: freebsd-acpi@freebsd.org Message-ID: <20041120013919.V87997@alfred.skaarup.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Problems with an IBM Thankpad X40 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2004 00:40:45 -0000 Hello, I recently purchased a IBM Thinkpad X40, and installed FreeBSD 5.3-R without any problems. After that I upgraded to 5.3-STABLE as of 16th of November. My problem is that the system freezes whenever I press a button (volume up, volume down, mute) or when I connect or disconnect the power. If I disable ACPI the system freezes by itself, one minut after it comes up. I tried to add: hw.acpi.osname="Windows 2001" to /boot/loader.conf - but no luck. I also tried the new acpi stuff from Mark Santcroos (acpi_import_20041105.diff) but still no difference. The firmware is the latest from IBM (1.43) as of 10th of October. "acpidump -d -t" can be found here: http://skaarup.org/ibmx40.asl "dmesg" can be found here: http://skaarup.org/ibmx40.dmesg Any help or input is greatly appreciated. Best regards, Rasmus Skaarup From owner-freebsd-acpi@FreeBSD.ORG Sat Nov 20 07:52:17 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB65D16A4CE; Sat, 20 Nov 2004 07:52:17 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1310A43D2F; Sat, 20 Nov 2004 07:52:17 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.115] (adsl-64-171-186-185.dsl.snfc21.pacbell.net [64.171.186.185])iAK7q6DU020394; Sat, 20 Nov 2004 02:52:07 -0500 Message-ID: <419EF7AD.8050007@root.org> Date: Fri, 19 Nov 2004 23:52:13 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: acpi@FreeBSD.org Content-Type: multipart/mixed; boundary="------------000406040402060700060908" Subject: PATCH: power down acpi and pci devices in suspend/resume X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2004 07:52:17 -0000 This is a multi-part message in MIME format. --------------000406040402060700060908 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit The attached patch implements setting power states for ACPI (i.e. ISA) and PCI devices in the suspend/resume path. This may help with some problems; it's quite likely it may introduce problems. That's why I'd like it tested. If you have a system that suspends/resumes ok or that fails, please try it. The likely failure case is a hang in suspend or resume or a device that doesn't work afterwords. It's pretty heavy-handed, only avoiding changing power for serial ports since those are known to cause a hang (which can possibly be fixed by making sio/uart more aware of power states.) I suspect devices like PCI bridges may have problems with power changes. If you have problems, please let me know the info it prints before the hang so I can figure out what the problem device is. -Nate Here is some info from a successful suspend/resume with the patch: acpi_button0: sleep button pressed acpi: _SxD is D3 acpi: _SxD is D2 acpi: _SxD is D2 acpi: _SxD is D2 acpi: _SxD is D2 acpi: _SxD is D3 acpi: _SxD is D3 acpi: _SxD is D3 acpi: _SxD is D3 acpi: _SxD is D3 cbb0: bad Vcc request. ctrl=0xffffff88, status=0xffffffff cbb_power: 0V cbb1: bad Vcc request. ctrl=0xffffff88, status=0xffffffff cbb_power: 0V acpi attempting to switch \\_SB_.PCI0.LPC_.EC__ into D3 (if supported) acpi attempting to switch \\_SB_.MEM_ into D3 (if supported) acpi attempting to switch \\_SB_.PCI0.LPC_.SIO_ into D3 (if supported) acpi attempting to switch \\_PR_.CPU_ into D3 (if supported) acpi attempting to switch \\_TZ_.THM0 into D3 (if supported) acpi attempting to switch \\_SB_.LID_ into D3 (if supported) acpi attempting to switch \\_SB_.SLPB into D3 (if supported) acpi: _SxD is D2 acpi attempting to switch \\_SB_.PCI0 into D2 (if supported) acpi0: failed to set ACPI power state D2 on \\_SB_.PCI0: AE_BAD_PARAMETER acpi attempting to switch \\_SB_.PCI0.LPC_.PIC_ into D3 (if supported) acpi attempting to switch \\_SB_.PCI0.LPC_.TIMR into D3 (if supported) acpi attempting to switch \\_SB_.PCI0.LPC_.DMAC into D3 (if supported) acpi attempting to switch \\_SB_.PCI0.LPC_.FPU_ into D3 (if supported) acpi attempting to switch \\_SB_.PCI0.LPC_.RTC_ into D3 (if supported) acpi attempting to switch \\_SB_.PCI0.LPC_.KBD_ into D3 (if supported) acpi attempting to switch \\_SB_.PCI0.LPC_.MOU_ into D3 (if supported) acpi attempting to switch \\_SB_.PCI0.LPC_.LPT_ into D3 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.LPT_ into D3 acpi attempting to switch \\_SB_.PCI0.LPC_.EC__.BAT0 into D3 (if supported) acpi attempting to switch \\_SB_.PCI0.LPC_.EC__.AC__ into D3 (if supported) [----asleep----] acpi_ec0: info: new max delay is 80 us acpi_ec0: info: new max delay is 90 us acpi attempting to switch \\_SB_.PCI0.LPC_.EC__ into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.EC__ into D0 acpi attempting to switch \\_SB_.MEM_ into D0 (if supported) acpi succeeded putting \\_SB_.MEM_ into D0 acpi attempting to switch \\_SB_.PCI0.LPC_.SIO_ into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.SIO_ into D0 acpi attempting to switch \\_PR_.CPU_ into D0 (if supported) acpi succeeded putting \\_PR_.CPU_ into D0 acpi attempting to switch \\_TZ_.THM0 into D0 (if supported) acpi succeeded putting \\_TZ_.THM0 into D0 acpi attempting to switch \\_SB_.LID_ into D0 (if supported) acpi succeeded putting \\_SB_.LID_ into D0 acpi attempting to switch \\_SB_.SLPB into D0 (if supported) acpi succeeded putting \\_SB_.SLPB into D0 acpi attempting to switch \\_SB_.PCI0 into D0 (if supported) acpi succeeded putting \\_SB_.PCI0 into D0 acpi attempting to switch \\_SB_.PCI0.LPC_.PIC_ into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.PIC_ into D0 acpi attempting to switch \\_SB_.PCI0.LPC_.TIMR into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.TIMR into D0 acpi attempting to switch \\_SB_.PCI0.LPC_.DMAC into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.DMAC into D0 acpi attempting to switch \\_SB_.PCI0.LPC_.FPU_ into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.FPU_ into D0 acpi attempting to switch \\_SB_.PCI0.LPC_.RTC_ into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.RTC_ into D0 acpi attempting to switch \\_SB_.PCI0.LPC_.KBD_ into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.KBD_ into D0 acpi attempting to switch \\_SB_.PCI0.LPC_.MOU_ into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.MOU_ into D0 acpi attempting to switch \\_SB_.PCI0.LPC_.UART into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.UART into D0 acpi attempting to switch \\_SB_.PCI0.LPC_.LPT_ into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.LPT_ into D0 acpi attempting to switch \\_SB_.PCI0.LPC_.FIR_ into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.FIR_ into D0 acpi attempting to switch \\_SB_.PCI0.LPC_.EC__.BAT0 into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.EC__.BAT0 into D0 acpi attempting to switch \\_SB_.PCI0.LPC_.EC__.AC__ into D0 (if supported) acpi succeeded putting \\_SB_.PCI0.LPC_.EC__.AC__ into D0 ata1-slave: FAILURE - ATAPI_IDENTIFY timed out ata1-slave: FAILURE - ATAPI_IDENTIFY timed out acpi_cmbat0: battery initialization start acpi_cmbat0: battery initialization done, tried 1 times --------------000406040402060700060908 Content-Type: text/plain; name="acpi_pwr.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="acpi_pwr.diff" Index: sys/dev/acpica/acpi.c =================================================================== RCS file: /home/ncvs/src/sys/dev/acpica/acpi.c,v retrieving revision 1.193 diff -u -r1.193 acpi.c --- sys/dev/acpica/acpi.c 13 Oct 2004 07:29:29 -0000 1.193 +++ sys/dev/acpica/acpi.c 20 Nov 2004 03:13:45 -0000 @@ -59,6 +59,10 @@ #include #include +#include "pci_if.h" +#include +#include + MALLOC_DEFINE(M_ACPIDEV, "acpidev", "ACPI devices"); /* Hooks for the ACPI CA debugging infrastructure */ @@ -87,10 +91,13 @@ static void acpi_identify(driver_t *driver, device_t parent); static int acpi_probe(device_t dev); static int acpi_attach(device_t dev); +static int acpi_suspend(device_t dev); +static int acpi_resume(device_t dev); static int acpi_shutdown(device_t dev); static device_t acpi_add_child(device_t bus, int order, const char *name, int unit); static int acpi_print_child(device_t bus, device_t child); +static void acpi_probe_nomatch(device_t bus, device_t child); static int acpi_read_ivar(device_t dev, device_t child, int index, uintptr_t *result); static int acpi_write_ivar(device_t dev, device_t child, int index, @@ -110,10 +117,14 @@ static ACPI_STATUS acpi_device_eval_obj(device_t bus, device_t dev, ACPI_STRING pathname, ACPI_OBJECT_LIST *parameters, ACPI_BUFFER *ret); +static int acpi_device_pwr_for_sleep(device_t bus, device_t dev, + int *dstate); static ACPI_STATUS acpi_device_scan_cb(ACPI_HANDLE h, UINT32 level, void *context, void **retval); static ACPI_STATUS acpi_device_scan_children(device_t bus, device_t dev, int max_depth, acpi_scan_cb_t user_fn, void *arg); +static int acpi_set_powerstate_method(device_t bus, device_t child, + int state); static int acpi_isa_pnp_probe(device_t bus, device_t child, struct isa_pnp_id *ids); static void acpi_probe_children(device_t bus); @@ -145,12 +156,13 @@ DEVMETHOD(device_attach, acpi_attach), DEVMETHOD(device_shutdown, acpi_shutdown), DEVMETHOD(device_detach, bus_generic_detach), - DEVMETHOD(device_suspend, bus_generic_suspend), - DEVMETHOD(device_resume, bus_generic_resume), + DEVMETHOD(device_suspend, acpi_suspend), + DEVMETHOD(device_resume, acpi_resume), /* Bus interface */ DEVMETHOD(bus_add_child, acpi_add_child), DEVMETHOD(bus_print_child, acpi_print_child), + DEVMETHOD(bus_probe_nomatch, acpi_probe_nomatch), DEVMETHOD(bus_read_ivar, acpi_read_ivar), DEVMETHOD(bus_write_ivar, acpi_write_ivar), DEVMETHOD(bus_get_resource_list, acpi_get_rlist), @@ -169,8 +181,12 @@ /* ACPI bus */ DEVMETHOD(acpi_id_probe, acpi_device_id_probe), DEVMETHOD(acpi_evaluate_object, acpi_device_eval_obj), + DEVMETHOD(acpi_pwr_for_sleep, acpi_device_pwr_for_sleep), DEVMETHOD(acpi_scan_children, acpi_device_scan_children), + /* PCI emulation */ + DEVMETHOD(pci_set_powerstate, acpi_set_powerstate_method), + /* ISA emulation */ DEVMETHOD(isa_pnp_probe, acpi_isa_pnp_probe), @@ -570,6 +586,82 @@ } static int +acpi_suspend(device_t dev) +{ + struct acpi_softc *sc; + ACPI_HANDLE handle; + char sxd[8]; + device_t *devlist; + int error, i, numdevs, pstate; + + /* First give child devices a chance to suspend. */ + error = bus_generic_suspend(dev); + if (error) + return (error); + + /* + * Now set them into the appropriate power state, usually D3. If the + * device has an _SxD method for the next sleep state, use that power + * state instead. + */ + sc = device_get_softc(dev); + device_get_children(dev, &devlist, &numdevs); + for (i = 0; i < numdevs; i++) { + if (!device_is_attached(devlist[i])) + continue; + pstate = PCI_POWERSTATE_D3; + handle = acpi_get_handle(devlist[i]); + + /* + * XXX If we find these devices, don't try to power them down. + * The serial and IRDA ports on my T23 hang the system when + * set to D3 and it appears that such legacy devices may + * need special handling in their drivers. + */ + if (handle == NULL || acpi_MatchHid(handle, "PNP0500") || + acpi_MatchHid(handle, "PNP0501") || + acpi_MatchHid(handle, "PNP0502") || + acpi_MatchHid(handle, "PNP0510") || + acpi_MatchHid(handle, "PNP0511")) + continue; + + /* Override next state with the value from _SxD, if present. */ + snprintf(sxd, sizeof(sxd), "_S%dD", sc->acpi_sstate); + if (acpi_GetInteger(handle, sxd, &pstate) == 0) + printf("acpi: _SxD is D%d\n", pstate); + if (pstate < PCI_POWERSTATE_D0 || pstate > PCI_POWERSTATE_D3) + pstate = PCI_POWERSTATE_D3; + + pci_set_powerstate(devlist[i], pstate); + } + free(devlist, M_TEMP); + error = 0; + + return (error); +} + +static int +acpi_resume(device_t dev) +{ + ACPI_HANDLE handle; + int i, numdevs; + device_t *devlist; + + device_get_children(dev, &devlist, &numdevs); + for (i = 0; i < numdevs; i++) { + /* XXX */ + handle = acpi_get_handle(devlist[i]); + if (handle) + AcpiEvaluateObject(handle, "_S0D", NULL, NULL); + if (device_is_attached(devlist[i])) + pci_set_powerstate(devlist[i], PCI_POWERSTATE_D0); + } + free(devlist, M_TEMP); + + return (bus_generic_resume(dev)); +} + +static int acpi_shutdown(device_t dev) { @@ -624,6 +716,23 @@ return (retval); } +static void +acpi_probe_nomatch(device_t bus, device_t child) +{ + + /* + * If this device is an ACPI child but no one claimed it, attempt + * to power it off. We'll power it back up when a driver is added. + * + * XXX Disabled for now since many necessary devices (like fdc and + * ATA) don't claim the devices we created for them but still expect + * them to be powered up. + */ +#if 0 + pci_set_powerstate(child, PCI_POWERSTATE_D3); +#endif +} + /* Location hint for devctl(8) */ static int acpi_child_location_str_method(device_t cbdev, device_t child, char *buf, @@ -1064,6 +1173,36 @@ return (AcpiEvaluateObject(h, pathname, parameters, ret)); } +static int +acpi_device_pwr_for_sleep(device_t bus, device_t dev, int *dstate) +{ + struct acpi_softc *sc; + ACPI_HANDLE handle; + char sxd[8]; + + sc = device_get_softc(bus); + handle = acpi_get_handle(dev); + + /* + * XXX If we find these devices, don't try to power them down. + * The serial and IRDA ports on my T23 hang the system when + * set to D3 and it appears that such legacy devices may + * need special handling in their drivers. + */ + if (handle == NULL || acpi_MatchHid(handle, "PNP0500") || + acpi_MatchHid(handle, "PNP0501") || + acpi_MatchHid(handle, "PNP0502") || + acpi_MatchHid(handle, "PNP0510") || + acpi_MatchHid(handle, "PNP0511")) + return (ENXIO); + + /* Override next state with the value from _SxD, if present. */ + snprintf(sxd, sizeof(sxd), "_S%dD", sc->acpi_sstate); + if (acpi_GetInteger(handle, sxd, dstate) == 0) + printf("acpi: _SxD is D%d\n", *dstate); + return (0); +} + /* Callback arg for our implementation of walking the namespace. */ struct acpi_device_scan_ctx { acpi_scan_cb_t user_fn; @@ -1138,6 +1277,50 @@ acpi_device_scan_cb, &ctx, NULL)); } +/* + * Even though ACPI devices are not PCI, we use the PCI approach for setting + * device power states since it's close enough to ACPI. + */ +static int +acpi_set_powerstate_method(device_t bus, device_t child, int state) +{ + ACPI_HANDLE h; + ACPI_STATUS status; + int acpi_state, error; + + error = 0; + switch (state) { + case PCI_POWERSTATE_D0: + acpi_state = ACPI_STATE_D0; + break; + case PCI_POWERSTATE_D1: + acpi_state = ACPI_STATE_D1; + break; + case PCI_POWERSTATE_D2: + acpi_state = ACPI_STATE_D2; + break; + case PCI_POWERSTATE_D3: + acpi_state = ACPI_STATE_D3; + break; + default: + return (EINVAL); + } + + h = acpi_get_handle(child); + if (h == NULL) + return (0); + printf("acpi attempting to switch %s into D%d (if supported)\n", + acpi_name(h), state); + status = acpi_pwr_switch_consumer(h, acpi_state); + if (ACPI_SUCCESS(status)) + printf("acpi succeeded putting %s into D%d\n", acpi_name(h), state); + if (ACPI_FAILURE(status) && status != AE_NOT_FOUND) + device_printf(bus, "failed to set ACPI power state D%d on %s: %s\n", + acpi_state, acpi_name(h), AcpiFormatException(status)); + + return (error); +} + static int acpi_isa_pnp_probe(device_t bus, device_t child, struct isa_pnp_id *ids) { Index: sys/dev/acpica/acpi_if.m =================================================================== RCS file: /home/ncvs/src/sys/dev/acpica/acpi_if.m,v retrieving revision 1.2 diff -u -r1.2 acpi_if.m --- sys/dev/acpica/acpi_if.m 15 Jul 2004 16:29:08 -0000 1.2 +++ sys/dev/acpica/acpi_if.m 20 Nov 2004 03:12:35 -0000 @@ -109,6 +109,26 @@ }; # +# Get the highest power state (D0-D3) that is usable for a device when +# suspending/resuming. If a bus calls this when suspending a device, it +# must also call it when resuming. +# +# device_t bus: parent bus for the device +# +# device_t dev: check this device's appropriate power state +# +# int *dstate: if successful, contains the highest valid sleep state +# +# Returns: 0 on success, ESRCH if device has no special state, or +# some other error value. +# +METHOD int pwr_for_sleep { + device_t bus; + device_t dev; + int *dstate; +}; + +# # Rescan a subtree and optionally reattach devices to handles. Users # specify a callback that is called for each ACPI_HANDLE of type Device # that is a child of "dev". Index: sys/dev/pci/pci.c =================================================================== RCS file: /home/ncvs/src/sys/dev/pci/pci.c,v retrieving revision 1.268 diff -u -r1.268 pci.c --- sys/dev/pci/pci.c 10 Nov 2004 00:41:39 -0000 1.268 +++ sys/dev/pci/pci.c 20 Nov 2004 03:01:10 -0000 @@ -60,6 +60,10 @@ #include "pcib_if.h" #include "pci_if.h" +#include +#include +#include "acpi_if.h" + static uint32_t pci_mapbase(unsigned mapreg); static int pci_maptype(unsigned mapreg); static int pci_mapsize(unsigned testval); @@ -1016,22 +1020,29 @@ int pci_suspend(device_t dev) { - int numdevs; - device_t *devlist; - device_t child; + int dstate, i, numdevs; + device_t acpi_dev, child, *devlist; struct pci_devinfo *dinfo; - int i; /* - * Save the pci configuration space for each child. We don't need - * to do this, unless the BIOS suspend code powers down the bus and - * the devices on the bus. + * Save the PCI configuration space for each child and set the + * device in the appropriate power state for this sleep state. */ + acpi_dev = devclass_get_device(devclass_find("acpi"), 0); device_get_children(dev, &devlist, &numdevs); for (i = 0; i < numdevs; i++) { child = devlist[i]; dinfo = (struct pci_devinfo *) device_get_ivars(child); pci_cfg_save(child, dinfo, 0); + + /* + * Always set the device to D3. If ACPI suggests a different + * power state, use it instead. + */ + dstate = PCI_POWERSTATE_D3; + if (acpi_dev != NULL) + ACPI_PWR_FOR_SLEEP(acpi_dev, child, &dstate); + pci_set_powerstate(child, dstate); } free(devlist, M_TEMP); return (bus_generic_suspend(dev)); @@ -1040,18 +1051,23 @@ int pci_resume(device_t dev) { - int numdevs; - device_t *devlist; - device_t child; + int i, numdevs; + device_t acpi_dev, child, *devlist; struct pci_devinfo *dinfo; - int i; /* - * Restore the pci configuration space for each child. + * Set each child to D0 and restore its PCI configuration space. */ + acpi_dev = devclass_get_device(devclass_find("acpi"), 0); device_get_children(dev, &devlist, &numdevs); for (i = 0; i < numdevs; i++) { + /* Notify ACPI we're going to D0 but ignore the result. */ child = devlist[i]; + if (acpi_dev != NULL) + ACPI_PWR_FOR_SLEEP(acpi_dev, child, NULL); + pci_set_powerstate(child, PCI_POWERSTATE_D0); + + /* Now the device is powered up, restore its config space. */ dinfo = (struct pci_devinfo *) device_get_ivars(child); pci_cfg_restore(child, dinfo); } --------------000406040402060700060908-- From owner-freebsd-acpi@FreeBSD.ORG Sat Nov 20 16:05:59 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F98116A4CE for ; Sat, 20 Nov 2004 16:05:59 +0000 (GMT) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 289D943D1F for ; Sat, 20 Nov 2004 16:05:58 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from nadesico.ninth-nine.com (nadesico.ninth-nine.com [219.127.74.122]) by sakura.ninth-nine.com (8.13.1/8.13.1/NinthNine) with SMTP id iAKG5uNN056229; Sun, 21 Nov 2004 01:05:57 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Sun, 21 Nov 2004 01:05:56 +0900 (JST) Message-Id: <200411201605.iAKG5uNN056229@sakura.ninth-nine.com> From: Norikatsu Shigemura To: Nate Lawson In-Reply-To: <419EF7AD.8050007@root.org> References: <419EF7AD.8050007@root.org> X-Mailer: Sylpheed version 0.9.99-gtk2-20041024 (GTK+ 2.4.13; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart=_Sun__21_Nov_2004_01_05_56_+0900_v5guTKDo1sRoJtav" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.11 (sakura.ninth-nine.com [219.127.74.121]); Sun, 21 Nov 2004 01:05:57 +0900 (JST) cc: acpi@FreeBSD.org Subject: Re: PATCH: power down acpi and pci devices in suspend/resume X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2004 16:05:59 -0000 This is a multi-part message in MIME format. --Multipart=_Sun__21_Nov_2004_01_05_56_+0900_v5guTKDo1sRoJtav Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 19 Nov 2004 23:52:13 -0800 Nate Lawson wrote: > If you have problems, please let me know the info it prints before the > hang so I can figure out what the problem device is. Wow!! Almost works for me, without X11. With X11, on resume, machine is hanging up. I attached acpidump -t -d to this mail. Please see also. # acpiconf -s 3 on conssole at 00:18:27 switch to X(ttyp4) manually and hang up at 00:19:29 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Nov 21 00:18:27 pelsia acpi: suspend at 20041121 00:18:27 Nov 21 00:18:30 pelsia kernel: acpi: _SxD is D2 Nov 21 00:18:30 pelsia kernel: pci2: Failed to set ACPI power state D2 on \_SB_.PCI0.PCIB.OHC0: AE_BAD_PARAMETER Nov 21 00:18:30 pelsia kernel: acpi: _SxD is D2 Nov 21 00:18:30 pelsia kernel: pci2: Failed to set ACPI power state D2 on \_SB_.PCI0.PCIB.OHC1: AE_BAD_PARAMETER Nov 21 00:18:30 pelsia kernel: acpi: _SxD is D2 Nov 21 00:18:30 pelsia kernel: pci2: Failed to set ACPI power state D2 on \_SB_.PCI0.PCIB.EHC1: AE_BAD_PARAMETER Nov 21 00:18:30 pelsia kernel: cbb0: bad Vcc request. ctrl=0xffffff88, status=0xffffffff Nov 21 00:18:30 pelsia kernel: cbb_power: 0V Nov 21 00:18:30 pelsia kernel: cbb1: bad Vcc request. ctrl=0xffffff88, status=0xffffffff Nov 21 00:18:30 pelsia kernel: cbb_power: 0V Nov 21 00:18:30 pelsia kernel: fwohci0: fwohci_pci_suspend Nov 21 00:18:30 pelsia kernel: usb2: reset timeout Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.FIGD into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.MBRD into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_PR_.CPU0 into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_TZ_.THRM into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.BAT0 into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.ADP1 into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PWRB into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.LID_ into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi: _SxD is D2 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0 into D2 (if supported) Nov 21 00:18:45 pelsia kernel: acpi0: failed to set ACPI power state D2 on \_SB_.PCI0: AE_BAD_PARAMETER Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.PS2M into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.TIMR into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.IPIC into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.RTC_ into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.MATH into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.DMAC into D3 (if supported) Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.FIGD into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_SB_.PCI0.FIGD into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.MBRD into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_SB_.PCI0.LPCB.MBRD into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_PR_.CPU0 into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_PR_.CPU0 into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_TZ_.THRM into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_TZ_.THRM into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.BAT0 into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_SB_.BAT0 into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.ADP1 into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_SB_.ADP1 into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PWRB into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_SB_.PWRB into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.LID_ into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_SB_.LID_ into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0 into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_SB_.PCI0 into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.PS2M into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_SB_.PCI0.LPCB.PS2M into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.TIMR into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_SB_.PCI0.LPCB.TIMR into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.IPIC into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_SB_.PCI0.LPCB.IPIC into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.RTC_ into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_SB_.PCI0.LPCB.RTC_ into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.MATH into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_SB_.PCI0.LPCB.MATH into D0 Nov 21 00:18:45 pelsia kernel: acpi attempting to switch \_SB_.PCI0.LPCB.DMAC into D0 (if supported) Nov 21 00:18:45 pelsia kernel: acpi succeeded putting \_SB_.PCI0.LPCB.DMAC into D0 Nov 21 00:18:45 pelsia kernel: fwohci0: Phy 1394a available S400, 2 ports. Nov 21 00:18:45 pelsia kernel: fwohci0: Link S400, max_rec 2048 bytes. Nov 21 00:18:45 pelsia kernel: fwohci0: Initiate bus reset Nov 21 00:18:45 pelsia kernel: usb2: config timeout Nov 21 00:18:45 pelsia kernel: wakeup from sleeping state (slept 00:00:15) Nov 21 00:18:45 pelsia kernel: ichsmb0: irq 0x02 during -1 Nov 21 00:18:45 pelsia kernel: fwohci0: BUS reset Nov 21 00:18:45 pelsia kernel: fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode Nov 21 00:18:45 pelsia kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) Nov 21 00:18:45 pelsia kernel: firewire0: bus manager 0 (me) Nov 21 00:18:45 pelsia kernel: fwohci0: unrecoverable error Nov 21 00:18:46 pelsia acpi: resumed at 20041121 00:18:46 Nov 21 00:19:29 pelsia kernel: pid 2836 (Xorg), uid 0: exited on signal 6 (core dumped) --Multipart=_Sun__21_Nov_2004_01_05_56_+0900_v5guTKDo1sRoJtav Content-Type: application/octet-stream; name="acpidump-t-d.txt.bz2" Content-Disposition: attachment; filename="acpidump-t-d.txt.bz2" Content-Transfer-Encoding: base64 QlpoOTFBWSZTWegNrR4AUjx/gHx0RERUd//yv+//9L/v//pgO176+aHtqKpIUAVevEOnqtCipw08 9RNvEvPcbVTAHve48SHrPu57ym+URne7ndujM6cjZ5devKPVAOTUoANq9Te5nLWdG20XW0nXcdZ4 2+MZ7jvler1oLn0d565d72vbQqGz6eve2BG026ZkeuL6+uvsG9vK5pIEonsMAANsJUkAKEppCAMS A0EARkamIo8KbRqPU00PUaGIyAMQIEQI0m1NMp5TampMn6p6g9QNHpAD1AAACJp/qlCJigaD1GgA AAAAAAAAAJPVKRJqJmojU9E/VNGhkDymTJoMg0Gh6gBoAwRJIRoCaMETEwKbRNBoaBGjAp5MU9Mk yaaCIkgUaRpkmqeMp6j0k3pR7Uaaj1AADRoADQDYHDX6aEiwkWJFgsWorAFPCrBAWSMASJCFxURx YggnYSQDviB2cR68D9/E+w2XduQclu2Hf6dh6M//EQdhATUzbKa22apWmm1r8fvX5BMo2M38zc02 1+f3z3343qvVcfdXzr5EkCPNg7YgGRDY05DLZBhgWXASjTyeRzXZebeN1tv0r3Q29q5pEXvc2eXa ou6u6MTu7YK6urliGdy3a4RV3N10HGKdqreGm1BbFqKfXvr4/HTZr6yvme60WtFtyNkCkEEkQEgE gkEiiAW9qYAQQosikgMO9dNR0QvrtMDKp3MiLRrctUy1CElEktJJTEcTCQJMTBcaYj12c7VylNd0 l3K7do7qXLa7ba+9qNjVtFk1Fa9yRg2jSS1k1jH1/Dv0K9KhM1WRlqQIMO++DDRqFbAYxfXKSEF9 U31933635rbYNbJ9XXfXq664GQ5JhBSkSUK6yhTHlHQ6mDStts9Z12u4buuODpElXcZJ1N2TzzXT Us2lSzztW6kpBgkyJkJBiscgVUrVbIJgSDRy3DKYBkkyxSQpGXCBkGUqNRDty6c7zTzdvPHgiTYy 50dzuZhazXjzy7d1uVcupFVr6tsmtrGmVGgtjBr3m1t9JrdSzLbfdluVZslqWAkhIdaJUcIQlKdw Y4mZgZVevst8tqKMSaglovsuslRrtSzXs2azWlYlS30tuq6YpJLJbGojd1zWPS4RETl2XXdrzu8O rbt63SMqWa3mm1GM15purLtVzRbLiXStFUC7uoqZVPN3EXnlV15tV9iS2lS2Zt9c2vgGNTNjaNb5 6tdo18W+Os0rZKlebTXKpZPo7l1ddXdVAlCYrkZCEWZHINBJbIjQWq+giwW16FDVX9L49+avXVRE E3pbRSrvA0QzVlaRgED6wPlY5nhcZwktPYMUFqxuyYIshmGAAJVGYAaoCqKfx3BRQAMQaKqQBRoI sCI9Z5+f3/2yBgGt/X8lWs+Smvi4auX4rdHdbf1ccmcz5jACwA7E+XxUT5wf5p23f725AA+iI6IA GZf2h/SAtjhHCiwWKCMB+scn+UdjmHOFQ4YEQiwDmM3wP/eSp0SBeOeth6f1VF/LvIXsQOSGtXiP aEh1A62avBMAzd6utCWyN/6gTMM3M1lWQ7UoTRCh4G9AkPBMIkOXtn9uoWlTdTflJGar490r49+e VyO3LU6JtfOb8Xo7Y3VNjWf667uCZSJkyMZxBN4wtMIhCTaU9vvuTvYnYY94cPMCCSJAIREqDA8U MpBIpIJYoN02AFoY9cismhLg2VTN7vmlzfL6OBKbJ+lpNC4iBgtI7heN2SMiQtg4wXlneGbkCJpV N1dMpBsgURJScbG2tRpP0oqMwNySSnfDMkt7HV8S/FnqAL33cvGMXjz08vsa8i61e4DvwdalriBq CkiqEllWRjCykKBUDRAZrNgc25QNtzFNjaQYsPTSkkkkUh1HkSu29pCb3bbRWULxaFkJJQ0duTNo TYaISwp81AOtgAAAOvfvvnXerPfr38d8qXvdo7JpWvB1Rya6oZxAokkJNXJQMAqFttttttttttts c8DvANGtR2hMknS3E1Cmsyzp3NZANnaVMcIQhDzd1wA+Ld/s162vu81aL56u32jwZqvRIDrLj+lh Hem50EoGxvaJWqrampbUNtmq8u262VlZ9HG0bGxsmqlEVp+jW9f27Va/Zggih8MAFHyRIIMRSL4Z /93KXDACMQBz0HwxUtEA1QQqCr2b6BG0V/HCkALEENwbCECkQCwRBugB8wfQNAChpgNQL2Cr2QBS iKLynxGUHCACwhGKODBR9n2+vfcPiBQge9H15p6u7wefN7phPbPetXlJMKqYQPb3nx6pPP69GGbZ h/QZPvaIUQVqeeuqIqIJvDkd00wdzYO4trul94RDv9VxTy+3zeLf7fW9jZ5WbF+hmRJx/e72/X38 0RxDcDxb3XQW/fvvvCJezk+++6nZC4aWDq0px8ExGUGSSugwSdvxW+dTQEe7gXt1szj8i2pdgViy A33QjU3/dLdhTW9txoZsEhMJi6JKIUuXILg8+g5eJGAC+Ba5RhY5Ce7wkxZhmjiZwBmLOJ9x3+0E AUKFwIgWfYuJCv5fd7D6zuzbHN15+WmDpbruIMCuFn5/pYavbqbw2XR8DYg8eSSSHd0lAjxB1Mdi xMyQv1OcseqJhemRGPDo+yPA42SjWPZGPd2fbbjQNEhNtQj05PxCQzSYEEeeVEkYXBSFfPu3dRJw ga6SxijV+AOHOB3/qevUeVFwgtlbZ/OJemrZtwUJRZk1Ip/L7Pd9vrvh3jzfT8Xz8et+ru/DwAAA AAAAAAAAAAAAAAAAAeuqQmHys7lFc0gwLW449vXx9r4AxjGOEwxYQqRDiEBydiDAs8NKHchxYMHf FuDgNRqBDhL2xi+n9X6f0QAAAPs+5r30vv7eefsO+vv6+XlrEYkfp6SCOUqeIPNR61QMIaijr2us M2yGnYOExTdCH0RoPFpFa+ihABM3XBzsXNu9hXdq6CORZW/bTbGKVoWdQHcHwYBgUR0+E+nry9e7 juAtwdEa1rWta1a1rWtazX0Dszhu2nHKt+Ny0MA0MmR4x9uawmYUm8S4fu4vao+yusXO9g+V+LZW 2f0N8OmaHqhcaIcAByAOhNzaxM87iHsl7bFJl3l1r1zkIaJ6UtPq8Nk4xAL7LsKW0C1g1L9rYYSe LgNxg7YTDehu1hiPvkqUUiQ2cptvo7zQZ2DTkDy0Hg+0CLcsu8CTZscjM23GG5/JDEBhbiJXfECV RuMkfp64c8+DqGd2YmJMpYkdpPm0AHrGQGlK8wgURuk8tsee+TVANgkhJhISQmHK5DPXG2DzckCY zPBLkw+qcQhJMwClAAfmu4Gd0sO/0JbT0zVQ7+TPwfl8XxjFs4mXInpXwty4d1tZ0CcC+uHD5QPc C0vSOWZBJRqeELXJ6fgSRRvsJnO+aMYGychBC7DwXK8yMZ7lmpuKm/KBs73v/MPMV75za2tB1Dw4 8I4V3B5wRuz5w4Z4VrzyaEnAFlzFmi87D36yB37NpXuHCo35d21xO3OwjQV8gUIf2tulItXKII3t 8L7bV9FlaZbavq80mGArXpOOTVZ312xvra+b557OIWtPoSNwlc9fIG/w7+AqThFnsNhdDmiPNuTd hx5z4DQ4IXrLvmlbm0ejE0Qk8z01riAORGNQ4jIE5xu412zYde6uKzirSH9APdkBzDs5NRuzdmGz pRzxptGRhWW9oj+zevLby3D4Bzgc4HZ+3tt5+L9b58zM9fqZFJGRSQTtbr1ZgEiSBNSsw9ikkLnK xXiOo6PqcC0q9vMPIvLIJ9MkkkoJ38Y4Ew4GXpJJJJJnAcF5SZwvHZ62mtxjDoIKiFDCQ0hrJ5gp Fg8QGSeU7wh5/duThnp6LYhUgh7BjeHFGhDIzlIME2bXJ7C4mM7aCZyoJsQlFx2Tj4oID3+EIy7l CH+AZ6fuVIeLfV64xivb3nmQi2rNkNIbPZpQropP7XQt7O223t138L7Of57DO01nau7zXp/WBiuX W2uOw2D7jv8k8zl3fPG/dVUzNVVU1azOzMz1VX5Woug10ir/B3dmaMYxnrtxnvrv3d8C3xK6Xbqa aXl/zQWe1IW24+HpZGxg+c3uDvUGHsSSSEMd6AzLGBwaMtts4weUs+nOX77mu6pJXP+fLfppjZfm THATAYXc5jwlTh4uJ9ulmOfrBejpA3Lt5W7JYiVnubCsZWxT3q/R3etYu7v6Nxg+1+f8V3lnMxG0 ORhp1XW2DdKcP4ohOaOO2vTPVz0DvdbBJkDWxWCxXFWKSkpKSIiEJLNUVFavFH6IWCW7XTq6unV1 lZUKFChQkO3p8vKhz2stsaaOFYDsOfLAJi/f5eaSSSSQ6TxwxYeQw7fTnEW3BjWEOUvqtrnLNWF9 vuqx2b3mJ3uga1TVAWiSmEKYKEVXHNSAHPGrUBeB1aq35t/Lv232y3wYbrnvhvUOUyanf4RyTWsM X3gBqt84F8pbLZKNdk9ueQSMGYvyyjjvGOAxa447jlvSNbEZYTa23qHT2u3fU2m/PeL3i6zkMDNF LWunnY8UdwogJmADHS0iNt2hEO0OM4x2rna2kMWdwXhhjFPedOLXh9wMANdbFG2ruRFiLEZJkvwT u6iCam1lPYuYTOxTja+jTT1RCoV6sL7hjhJSSSaDSFtMuAuGemBE3FR3Vw8NuvbOQEd0lsiKDM/N izcndJUi6dJBJM7jh+DPJL/H85TwYANNbneGES9J3dJCSWSdJNvTgAoe/p5+1vn48+D1u4QYADQD 6fTzw87jzuAAEPt7j8H65IsgLotYZ663a8NdbqrGe7bFqqqDRJMkkkkgAQBgAADD6dwwV8Nx+Xdx +x3Afb3d53kAAAAFBQD47gP3vw+fft+revPhLBvA6NSXxu7u7Z3hdziDQDyl6RboHwsh2IDLk+F5 ZZj163PZpK7TvnryPwYC6yPt0goM6IkAIEG0rEiGS5+ngQkJLtKQUDAWOyMu7angl5Zy/pevTEeq iqqSyo2CP74AEA5Az7W9lhdywuKjEcE1fSu0zeHZ28+ownSGvrs831+UQshu2EC22El4Ky7KLxuz CPirkJ4qvuP1G3E57/ZOn5fK8eHaS2zH2TPWlvjqJimQ2pgnTdsmKRMEvTsm6ZwLwDYBQBuW8Ig7 g8ARsOUjybvUuhCwswGzu2scWIHa9+DoWQugw6xUdb0QJwpFIe+m7maWTN3jvcesZeGFtNmt92vT zmOf3je9sfn5bb/H73O+QL/MkD1AA/E8CD4/lE8XuJAJB8aHUwsAL30yTFKpGISCp40frR2DyX68 KDGscbt86Omjn66gw5Oj6OABoP4/bfzBq+3Bvy4PqgHLb9/qDSIrnno01EbPHb0bmAf6Mw1Y7H6g GdL0z1cd3HSY2gbrn5ctfX9u5HRdvDfgo5DvbRiXp2IK8GIChw6QKIZBQzJOGACJB/9IAQr4t8sf UYuHwOvfHXBs+/G8jxBCpUmTJky5kTdymkK/29AvmI9Lnzu3lZtsysOi6/XJ3V8fbfzDrvafFKA/ OyhSqEugANJAB+cKbNlenn/BD+yGX6soAB9v583Lz2vT99LszCFag03jgftNb/siF5+DrI+zbFva TjGU84xBvZBohgstzhYJK78ZQAjkw56oP2IFdIsLICrhtJAgk2lpdXtMjmsiH5PATMZsMIN8JJXW AfrAed/lKxNcWgEEBdEBwBRMGRgILIUhp38Pex8mN2zWVYhFE83tYRcxIxgSdJ9aYXQGJHPowdA9 0NW8OOUc2e8y7uk4cCwARwoRZhEQJvO3JhIGV9EFs/5yOgl+AE4gkGIhhvb9mwly27Xt1/J/dg/S EHu5yvkNLOMkzNwdzs05JKAMdqYdMBrbuO015HTpxnXnLIxzaiW5xZWWW0uyyys3bdCuKsZmZrKg ARedAJTGZRACFcXTZIeEWpJC9iuwzQ7YZiSdbaMIbSkXWbRCvipBRCRE0xFZTIRFOOYs6rVrWkTE bs3CXeuLuk7NDNiIiEksWiI7MyVMzBmSO3rzwAA7uPy+/n3+P7vXtfO+fnruAPfcfN3AHz688P6l 3fffF8Xr0B58eeBJJJJNoO83DuklXOYiv0wNK/hXAYiTnPHm59oygcV0ufX2fHG4ziRMY8FtUu5j gzONziP4AKbIHuSQD34oyHG9DhCSSSSSSVZ8j5uCfKw0SLuONnmi6t+nm1N+E31wcVVLgADwXTES gJmsCjRIIExiO29EgOEADgIJUgGQF1wYlfXUKqdRDu8/wTDXG4OKvzfhoOF7rgAUpUmXwgk47c+H o35yNCMAiIB09rWEGFlmZmZgDwFFIVTMze2DtPW1rXkIG32d3HXWxzzSRA795KhrVXjaFQXc36xW 2geWqDCAvgHUFoBIRLSh1QLkKSJGGcYWvWg06gUJATaISHshkNiVZDx+P7fVVeS0Woq3199qgyEI nn5eeIiBs+VsngcDqJoM0lkXzM2LLN+S6q5Wita++bXMm666xU423IXrRejSY2lRIZAokrKJPLMQ yIhxz1MF0R24MwlhRWJBId8lAKHfVV7EA46l2JIrIQOe9yzPMYawvc0axkAN+JVONBbvziaiO29M Ib0WqmtXUQ0EQQ8SKNePfgZCEEYsnfQa6tCQxqBzDDVoQhGaogGomOkCJZCchtiYkj7qSJYRdDmg NKFi6O6b4FOkP5ST18+HstuGWtVVaYfv5z1h+H2inQvpIJAYyIkUkGLFjGLAgpINxcNwpZT7YBD+ 9AO4ARIDCCR/Qx5qNnDSVtWZcETFJwWy7MjMhjbQhGNBa0LKeldK3jVUavW0yVNKWoSwCKkIsCJI xgGgM0uAAulzFWSJniJ5682vSTZpKZqU2pWi20ber1rreNZkzZdaDSYaCMIQYDIEhgYXfVSLFLbG r16vPNslNLLabUaPfrvMmaSGd6uvT0MaPm99eLGkk28nNoNXTstoIiLbTLSzRpJqWNShRpte67lt U9dXMzFvcuw219N3URs6fy86dDzXjSYqaU3q+PK80q9yirV2TS0vXVypSZRtJVJjakqm3lm3WZaK UpXO0lJblW7U2jZ3a3aUaxJTKys151yUa1SmmJYm2UtpqTXw6srXverFqSi8MP2Oj8tXwGKb3f5w O3PkQuOfLYcIieE+gz8P28Gxy+1p7ofX3JQtSzuNpMTNZg+/RWdZQZY+jxpGqvwLg9PgnenLApJV w3YFYwF74si5D491fCD8UnoMN3PnYBBhGIQPh9OBfvnnuv3cHw9Hk8Ht1z2xgW5I3LbZZAZs3vJS fTrhE8uJ+eEwTaCJhSUADeGRADaaNB3IovIAewiBzN2fQaMhJ5wgwkwN3GDOQ1IXx2jDYGFkTpCB h9JWjMW3ZxDKs+vcxIXIgqLVW+P5/NelkhIQkNM7YfNcf3GxUCBUcHFp05+f+LWyvp4W/CiJE8mc IID9x2O1u6hyURp/+ASieKKjxts+0nQWBp0ayetFsIkv3hvpJ+RdCYkJDQ0KJGECP0I7qhCy8g4+ nxNL13Ymz1YWU80CQe7f5eOu9Dy81BkIeML4tjxoAPRG3HqksAHqy0c0EwhYzU23bYN3KS0kcGYI OnHTodDggcdumPvNlfdst+PB+zB7LdX3Rbl8PjB+EHtziSuTuv0R0NO2yKZi4568VHrlwu5efIOj TjyQOyQECEGEiSAfjWBYoqfjp9/5tJu9/s4utIkDeNMn2fHSbTR8QtJEoxKCdrreoiSKabvvh6Mc 1uuSIaPPTfBugdCgSOaY1x9wngxcganYznTVgdkkm6dbvCO/x8pR8l4Kdo2cY7fDurgWRjCG6Q5v SRFzxVnuwGxV+u8NcIiBfFgfL0j1Ywk7O5ynCO6DXX1Z0B+Rgh0i3ucZmgCOaDOO8shh17o8d+um WvLh13znOc5znOc5znPYbGBNEQIcRWta1rWta1rlWs5znOc5znOc5z1ZqVA8kFrJm2Ao7NksMLDx G7/539AOdkNrm9lsjpgdMQDThxLZYECKS1FRyR6iNt1Vgdu0LtE1woIAdpHp9kilvdsbkePPpti1 EKKqqojxbNqbI7UYjZk7s4gSRdY8F0v2ECXy6X5uPIHbtdOohbTm6uwG9G+PTvxuDIQ00U9EyQPx PCpZoNgDmZ7KUhIIt4DRvo7u7u7vj3ja29XduqLbHXc4HMUjR+KLJPKxHdA7Vale9lj80BZ1v33W 9dbmL03WkTCJyI/TVjoq6OHNRfdePFCEg2oOY38QZ1zIO2qgkHbdTbfENgX8LzO3omqCEIKKZk6X InZMPxUrFIQkkhFht2mFj4pfFIFmJWkpJyD6l5sDB81qQ6clGzY5s02WKLMbInShEFks0MQGEGWb jukg3UKEhO7CYYZklEwWhiXW2++vb9PPPXs8fDtp26UpSlKUpSlKUpSlKiTKta1rWta1rWta0pSl KUpSlKUpSlGdDVZpSjyAK7hskxGbjuqfDbkkxFChrmvh6q27Gd2XjeWWm813KLxz3YoXf08Lz5+r WZmdwbyQHuKSEojClFpWoRVx3xnN+kAGULdCSGStxSDkhwVc9M5nagw9RPdizC9ZYSQJ1bD3TUDt t4TjQbQO3btbVVVVX3CbzPrxMkAqDoquaAfpx0WIVCk1HWQDBRQTTE0HLx3ezHhjf+nH/LJjL+Hk 7/n7f3wb7UgmVgzOX3EoRGX8v98f+7VAU04v5py0fA/qVyGPx0P+T9QIPrft8Lgby5Zw3OHSalYJ kF10F733L4/AxD77zbSygRpEDOzEyit7LY6VL7/2JIHuryGDhMEPBXulGAO5wgQcHcQQNF6/8EQ0 7sLD8m/oFfs4xon2Jiu5GT0m+Ru/IzKOoOCe9ZM2cbgyuskiB9uHjzpgnOhSUc42y6td1Hd9QRnv 0lON2b9P6Z+ptXxE/lXH6X3qvC5xc1u/493d3Xl5q+kr1lgAA29O8dnj/g8ys1TNW0SVRqSpkI+P ceLDN3s/k5ry9N8pqwY873sQWkn77b4kEWmX+WQzZbs44hDMgQAGQgK+hrnuz9pmPT19vtAAAAAA AAABlnq9VhQAAAAAAAAAUz2y5sR4owi2fDRVVjPwwvpHQzKIj8VBkmaAvMPf09Qlrds2/L5bfy6c teXHrzpSlKUpSlKUpSlNwbZuY6EAFppDTTS3TTTTTTTSlKUpSlKUpSlKU7j3QkGmwIQteK1idu/i De27lcFSwatH+J1iVbMD2hoOqLLIg6/dMmS4Mh/kT1o/LelhPXhYS9QPDt5eHbcW9+t2/VkVXlQ9 ExOYxL+c4mRvHu4j7fMe9bnPLfAnPOfjx4W6ceQ2MzMkbADnRvEReoxjY0apm0zURGbiRtTHCrTj xt5qvpAAAAAAAAACr3qgAAAAAAAAQhCEIad6d+E7smTAcgmWBOc9Yt2qMYwheF3Qwg/PdaIGgwoX j5jkJL8uD4+rv9VsstC2yWzy66oqHcHIdtyHkh0PgH3O+eMkkJsux8iQ45NCIJlw+sJOftMTMFpR mBm63g5pSbvYEDR9Z9L8+kgau3kPkmvJkPwKPCjnHdzJUR1c/XVVVVVVnMHzONcSz5vNo/1p5sw4 oV6OgU4Ek7A3pHz+77kArgGMciYkghUIAaBvHTs01xoIBQVRJVIxrm3cpKPgrtnl92af3TePaTRV s2Z0vf9fxcuXMOXLl/T6sBuiR5xx76rl27ZM96ry2HH8es/Lr5lNJcbLSVsLoePi7dPmUmMQ8X2h 9SeXcW75TIHE0YMOcZgbhYAvvC/4ZeEvTTEciXHed07LkxDL9ZMmCwMh6UpK7KPcHeMwF8Bngag7 bDy6g00FjMYjmGV5do3C6tIe4FUZe1dJrw/UDDvLtCGUISJMxiK+Qt0PUfZLJv2DkGZgeskIBvmc 6MpQeJQHwAukQ95Oue1QyIqPDapl9vxJ94Ab+7/KdhI2wjYBYEjbRvVMhG4hA7vh3/Tw2r5lhI18 3dequXSNrc775QY+sxUiw++0LvhbIjhM6UaEdgSJQJGP2pgQgEgTJd7s6JRRRDU+K/PXxfNdX08/ c1+QTL5wsCW3+NTdgZjMhrC5bA/tvUnJYNy6skOkOIdgq5jbgDSBzbucD6GEsfmzB9m4xey/e7uJ xPEhCDu8YyfaM33a7PMEs9hAQt/x38d82Y+YkLcOjp0GhV7+5dSOsX4U+GJgevaiLR1KJ3ebjw/B wR9fo3ivRgO2ytMzpzkMQ2vJmpl+ZgB7UCNs64ffJttvbjxdlwaHYMzENlO2XGBgn4sByvOUCfxh wVEClovqsTyDDSQ1vhtLE/wgYIEBI/gkxwnA+fu0Bw6RRbahWh8Pl6JJbznPX+zlz9vw+76tmvXd SlKUpSlKUpSlKbwVa1rWta1rWta1nOc5znOc5znOdDcbGPUNvmtUFpa4zJmGEkG92B+guO8BEb9J JBHSVDMzM0kDjxzqbd/Wr+EO8s1qw1YF6mrY7EnKw415x8xn6pt9Gr5jAzdqHjW72I3+GWpa/gaN M0up3dyBxr9F+2G37dMmTSbGZcAMc1JJIfIDz9z84B/CoR5n/xROJqRDinr5ueeLaqtKLrcDxD1v AaA9xAftJ2nlaX37mBP4gOEfUnJsBunPegeLB5+ft8I+/n8+Pu44qBbbbjjjjZdhdddddddheL0Y D9wISBAgh6tXp4F56vl8eCAZB6wH0OJ5H4ef5Bwv/M5fSUiqmq+7BwPBYakhwfZ6gpaFsJQSpXbt 3dVvbdPjGoDKVfcBcQM4wMuLozeHC6835cqasoOBbwK4v0zbh7yofCAe0ILIUQKgZi0NUKIADCCk IdJ9ihxzED5oEXWmqAESAMQgvA02OYnOlEnu5QE8Dw8QDuAHkDQeIagBAgNNAnSjiJoIvSRCgoN3 SDoJP0Vdpm1BRK06NM0bTbYrSQC2bfuYmmG0sNqQpuaob75Jhc3+czbY4mjU2zWxTKEwgNhckkmw ahIs1lR0MMl22NsTc23wlZSRI3fCzLuYVGbzAzbDjdPGoPn7fstv5/MND8F9QfMdgL2bZt1957e3 t8qfLsCEIWWWWhZZZZZZYeaLj17dha5Q2+ftjJJIQsJbW2LFreixPdzvkm7wh0kcxEvQ5yOYvFuR FsyMQIy/A8j6TJFsLRrjp76dnugHAhSgBjsREzM2mbTMySQiroDqL2SrNwqEF7+O8vA2BzHKfCvx C3D73cmdA9kuJACQkBiEWIpJVC0aEWRaab/BisWvn+BAzg+YH3Oy3H4yjuuvDtu9DRxkodI6qLm4 odAxB3O/kHeCG7xJufAcbqQhJJJYnEZrRrH4v2lGE5ouc6MBomMWPy9fa4uRnjQzYliFsT6hNKh8 YB8b778/s9ikkqkGohVJ6UkUn69QdEG7U1DFq1GRMiSunA2uRxta2tANrRwIhNcqGvSbELr8o+08 z6PgQiMt98sRxawCRyBp+yu/00H3fGUtkkknYwTP5FkKGyj3gNdHsFfTw7/OTels9B4eScPrEhfI g59+shrQBhi+YNpk1AiEAwLQLFJLCjEIbiNoQLJda68KQvvKjIB4qJvQdgLIxAQyFzIHyGJWQkDL fZw6NGpVR3EFD5GCePhyuVHyHxDBV4HmEpAMq8aL273dh0ImSyDZkxfUtc9P9RHFrWN7I4O44Djp VMHGE+o91NBfopkySQtkkP95vkPQHt949YJRY7A3mvebeTyZIk44tYx5RYPcmgWfLWARYhDC1QGZ uncRcfXRgWT+u7bcJ0BpRgGHkADImAPU6+wySfGhkMwPGpJLh8wcdNRuE2LfQQPs6+aeEPQ7EDil LSlpS0paUvXXddd19N+v32Ij9qcjnIiIkJCTzOBv04Rkk7t/vFdn46787xidDF0h0FNoaSWAf47C PhBhnslwTaYw7HunhiGzVF4q7hDTfrHNpMKxwRKiEjNgVpRLVtJUFNjhSjXcoZ9y9ShCALu04ySA AAHr1ttvPD8tfk/P+H7/ra/D1+zeLUQAdusfGvzb6K7Nyz47cq+fedMoHTTCFIbb8oFzAIQDEOW5 OrswSwxIa5AhFgwSQCK8tk6UIJl0wNKMFkgfQnQWyaMWTRlMREDkTIjAdSM2iMtqJ3+e+5vaItqz Zcy83q0Rbr3nsdm4BNwWta1sFOPHpMpoAJ6f5iPf5HfVEkrYd36OVQ8DuANgiJwkTDhHSBpDkMMc StQoOQgB9ZjlmYW4XJpimiGQGhK4PV1qy3RvKaAJbSDQ93Ih+8A+f4vtC1VVJJJzqnSO72B4J2h1 Hld2p5CGcc40C4Agj52gjQNLe8ADd94B3IZgaogT5+iQPRqlLKUpDlgGQ10ijiP3ebIHfgDnlx5F olgcou7TipDubRuEoh9T9Q6O2GC2e2hs1nsq0X+rguZM/n3YO2+sUHFHmRtlPI2X2K4p5g0hT0Sp kfHps25UIwI9lM+a7u/5iQ0GuPSnI3fLzsAhpNOUdqnwLcdiMJGSBBhBCECRGKNSjGxKVLaCQAIB FSSAR+IlQPADd/X5sMNH44aKT9Ufft9LGgBxTfVCc12zbMkkIMIarbjWGXCZzcyhodHwNallAjwk LvCQkDczXFZGEZKwhqWuaBzNEU2gFNaIkCKaoroD8jsWOQDo6hCSLAejg7nuQ9oSIl1y22012VQ8 I9dpCQykUg4YMxDXa4nt88nGJtTTCOEwC+UNCQRIP0x0bfGXapESQE9Ad/PRo5/N0JFxC6Hcnlp9 A5P3YgNew4Me/B4ZWk7hMIZwh4ZloiYZ3hEYEzJX6wyGv1DLXbgOSY3eMjJZDfJEfVRPAfIDsGB7 fHAwMzAwMz2e0AWYwPjqcxuNjYckkuJtjvPPd0vSRlpXJnQkJChILnQzZiSEJ0DkOXLNTl5kw5vH qA6hH5OUiu+PpbIXlqLr1OXPEmP68vLJsNkIYbFYZtDefkYZCe1pYBxL7iTf6tPwh2As/CjIEiQW BJBIAQQ9CB36YHZcxqiNUVaWKKCikz8243KEO3zvnYEyGQQP25yjm5PVp0LAiRgeUdQIQXPWoUxG BkkCQEzJ8aW0tu90bQH7hIgHw+j0fg0Xzn3XVuv81c3bf8/9cgLeDkpBqIS30lhQtxKHsmT+tZTn zWeSJmjPPVDEE2kV6+utUQb0UZ4QUJ6SnCFwQQ7pm/lY/kq8DUNgDgAbBQP9fKlyh9goG1FPp/+R F/ZEE0/x/sQF+h7wQHr7zSJ/dAvADU7TiJrRGyCB/kTIo0DcoePcfX+X4cuwT0ClG5NwLl/DtyiC fsIvSKehgsAQ5UOdu4A1xiLgoFD4w7EAFfiuu5wH9BImJihnoVZ5F+6VUIjRIRYkkCAVBpUDubEy hgZSBSiQspLUchGBkC2xMIVAkkSgEIwlQNNawxdXFmEQhEUTQigemdkNJFQKwQxLKRAtijrcih6Y io4Cr6ilC7igmP/cDoRGCP+F1QI0hSsCDBiOaRhrGS1X6780236ivc89bmqkIULozEynJDAylIwt RpaVSKRIQlsi0Sy2OZWZB2itUyASylO2XKwaoEkkE9qUAogNiyCGw/8IvPR3IEKIaAJ5kRUbpRW9 Q/45lDMREblE8P0OwA7VDFyIiH2a7x+lFVx29TpEBcqBQodBGtAZ0utoqsfrFuRDNyIGdQQs2FN5 kBPAU9aI8iIYrwBOO9ENSakQ4OhWRJ5UBs4qFCXCfg6BHJ3CAvH9BAw39G5R4b1HgohuTWXqpnE4 CAt6qDegaVFoQ2g7CI94g/HBkEFJGHZ+3l1nR7Fhulik5BLV6U7MyqbusHRkyKpBblAN6qhPIUDA 5CwjeiFyKXL4HKvBA4gHsHvsC/At14gLgA6BAWhOoVezX9Sghfk7QXIo3g5vlOoBvW7xE7VDMJbL pEegEoQOhhf6lXtNghkU+tU2IGnf6BNBnUMXOCnK3iAvMi+EFA54sCzEBejyiBSoJkRTiiNlBDpX gKSnMlrCYIgv3cu5BN66TMuXlLlzim0qjMCAwEkFK5fOJZEYa0wRSABFauWpK02FkMZNtJpskm0B PQoQR+K/aoj6EzQnKIbIOC5iy3dxYT8LhFwyOVDMIHyAgb+CIJaqBegQF2gCtyh7J4KaxEJ6+FA4 L1bwbvAQGhAAv6hT5VDWCg5FEJqQLPMl4PBcLIhwEdF6I6lmvaiLc7u8jAIc1oRCBCBAIlBqieCf ETMEfoUQ9mCA2CgHeRFJFUIcgCvWgQHoQNOXk0gkUcyqhYQF7eaB3Z2FQYIG6J2r3ABFGimvgomP Klvcuwl2ChepigHQgmLeZFHwVTzichkEMphgohfByE/gUwUsJ7FucQYeRAkFD3ngEMtdTiHRdBlA qhgkjrRtiXTaJROwAbo6RDcF4E2VAPBQMyI4IGdSgUIoEBSsmgUshGAQQ0mtcRAW4TFRmSCOtcpq UPmuB0CAB4JffiKg5RP+Ii4J7qh6Es+peRe6/DWoh5lUHxMVNhiX6N6jpRKQMkUWmCFyBzx+ayjB AVQ5lCdxgClBmTEAhzqMphpEp2oaxTWKmVEF/x+ip94AfeKp9yAD9ygAfeAD96C/mvAPzgCyAmIh iA4origCYoCGILiJiZTN/YxHEHFQxFH94LmFPt+7+hx/L+uAtrciGkA/hwy1ciGwM2hwm1yTDC7y XWFNELowwkJt6n8fmnkeSh5CcohqizYo67y9vRLk//F3JFOFCQ6A2tHg --Multipart=_Sun__21_Nov_2004_01_05_56_+0900_v5guTKDo1sRoJtav-- From owner-freebsd-acpi@FreeBSD.ORG Sat Nov 20 18:40:06 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 553E416A4CF for ; Sat, 20 Nov 2004 18:40:06 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id E073F43D5C for ; Sat, 20 Nov 2004 18:40:05 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iAKIe5xS053307 for ; Sat, 20 Nov 2004 10:40:05 -0800 (PST) (envelope-from marcel@xcllnt.net) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <97861236-3B23-11D9-AF96-000D93C47836@xcllnt.net> Content-Type: text/plain; charset=US-ASCII; format=flowed To: acpi@FreeBSD.org From: Marcel Moolenaar Date: Sat, 20 Nov 2004 10:40:03 -0800 X-Mailer: Apple Mail (2.619) Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2004 18:40:06 -0000 Mark et al, I tested the bits on ia64 and there are no problems that I can see. FYI, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-acpi@FreeBSD.ORG Sat Nov 20 20:33:15 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EDF216A4CE for ; Sat, 20 Nov 2004 20:33:15 +0000 (GMT) Received: from alfred.skaarup.org (alfred.skaarup.org [195.234.155.140]) by mx1.FreeBSD.org (Postfix) with SMTP id 6369243D5D for ; Sat, 20 Nov 2004 20:33:14 +0000 (GMT) (envelope-from mfbsd@skaarup.org) Received: (qmail 65425 invoked by uid 98); 20 Nov 2004 20:33:12 -0000 Received: from mfbsd@skaarup.org by alfred.skaarup.org by uid 82 with qmail-scanner-1.20 (uvscan: v4.3.20/v4323. Clear:RC:1(127.0.0.1):. Processed in 0.136268 secs); 20 Nov 2004 20:33:12 -0000 X-Qmail-Scanner-Mail-From: mfbsd@skaarup.org via alfred.skaarup.org X-Qmail-Scanner: 1.20 (Clear:RC:1(127.0.0.1):. Processed in 0.136268 secs) Received: from localhost (HELO alfred.skaarup.org) (127.0.0.1) by localhost with SMTP; 20 Nov 2004 20:33:12 -0000 Received: (qmail 65417 invoked by uid 1039); 20 Nov 2004 20:33:12 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Nov 2004 20:33:12 -0000 Date: Sat, 20 Nov 2004 21:33:12 +0100 (CET) From: Rasmus Skaarup To: freebsd-acpi@freebsd.org In-Reply-To: <20041120135830.GA933@tongi.org> Message-ID: <20041120212514.E64859@alfred.skaarup.org> References: <20041120013919.V87997@alfred.skaarup.org> <20041120135830.GA933@tongi.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: FIXED: Re: Problems with an IBM Thinkpad X40 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2004 20:33:15 -0000 > On Sat, Nov 20, 2004 at 01:40:43AM +0100, Rasmus Skaarup wrote: >> My problem is that the system freezes whenever I press a button (volume >> up, volume down, mute) or when I connect or disconnect the power. > > I'm not sure if this is the notorious FreeBSD-on-IBM-TP > problem. Give it a try, I hope it helps. > > http://lists.freebsd.org/pipermail/freebsd-current/2004-January/019435.html > http://lists.freebsd.org/pipermail/freebsd-mobile/2004-May/004002.html > http://lists.freebsd.org/pipermail/freebsd-mobile/2004-May/004003.html > > Briefly speaking, turn off secondary IDE. Yes! That fixed it. Everything works now. Thanks! For the record: I downloaded the "Configuration utility for DOS - ThinkPad General" from: http://www-3.ibm.com/pc/support/site.wss/document.do?Indocid=MIGR-4ZFPEG Ran the exe file on a Windows machine, burned the "%WINROOT%\DRIVERS\WIN\UTILITY" folder (which the exe file just created) on a cd. Booted my X40 on a MS-DOS 7.10 bootable CD. Inserted the cd I just prepared, and ran the ps2.exe utility as follows: D:\UTILITY> PS2.EXE IDE2 Disable And rebooted. Best regards, Rasmus Skaarup