From owner-freebsd-acpi@FreeBSD.ORG Fri Aug 29 19:48:27 2008 Return-Path: Delivered-To: acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F758106566C for ; Fri, 29 Aug 2008 19:48:27 +0000 (UTC) (envelope-from robert.moore@intel.com) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by mx1.freebsd.org (Postfix) with ESMTP id 0C15E8FC1A for ; Fri, 29 Aug 2008 19:48:26 +0000 (UTC) (envelope-from robert.moore@intel.com) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 29 Aug 2008 12:46:33 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.32,293,1217833200"; d="scan'208";a="374854855" Received: from azsmsx602.amr.corp.intel.com ([10.2.121.201]) by fmsmga002.fm.intel.com with ESMTP; 29 Aug 2008 12:45:46 -0700 Received: from orsmsx505.amr.corp.intel.com (10.22.226.208) by azsmsx602.amr.corp.intel.com (10.2.121.201) with Microsoft SMTP Server (TLS) id 8.1.240.5; Fri, 29 Aug 2008 12:48:25 -0700 Received: from orsmsx503.amr.corp.intel.com ([10.22.226.47]) by orsmsx505.amr.corp.intel.com ([10.22.226.208]) with mapi; Fri, 29 Aug 2008 12:48:25 -0700 From: "Moore, Robert" To: "Moore, Robert" Date: Fri, 29 Aug 2008 12:48:23 -0700 Thread-Topic: ACPICA version 20080829 released Thread-Index: AckKEDIerYuJ+tiKSXqD+DzqkhdTlQ== Message-ID: <4911F71203A09E4D9981D27F9D83085824AB98@orsmsx503.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailman-Approved-At: Sun, 31 Aug 2008 13:28:39 +0000 Cc: Subject: ACPICA version 20080829 released X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Aug 2008 19:48:27 -0000 29 August 2008. Summary of changes for version 20080829: 1) ACPI CA Core Subsystem: Completed a major cleanup of the internal ACPI_OPERAND_OBJECT of type Refer= ence. Changes include the elimination of cheating on the Object field for t= he DdbHandle subtype, addition of a reference class field to differentiate = the various reference types (instead of an AML opcode), and the cleanup of = debug output for this object. Lin Ming, Bob Moore. BZ 723 Reduce an error to a warning for an incorrect method argument count. Previo= usly aborted with an error if too few arguments were passed to a control me= thod via the external ACPICA interface. Now issue a warning instead and con= tinue. Handles the case where the method inadvertently declares too many ar= guments, but does not actually use the extra ones. Applies mainly to the pr= edefined methods. Lin Ming. Linux BZ 11032. Disallow the evaluation of named object types with no intrinsic value. Retu= rn AE_TYPE for objects that have no value and therefore evaluation is undef= ined: Device, Event, Mutex, Region, Thermal, and Scope. Previously, evaluat= ion of these types were allowed, but an exception would be generated at som= e point during the evaluation. Now, the error is generated up front. Fixed a possible memory leak in the AcpiNsGetExternalPathname function (nsn= ames.c). Fixes a leak in the error exit path. Removed the obsolete debug levels ACPI_DB_WARN and ACPI_DB_ERROR. These deb= ug levels were made obsolete by the ACPI_WARNING, ACPI_ERROR, and ACPI_EXCE= PTION interfaces. Also added ACPI_DB_EVENTS to correspond with the existing= ACPI_LV_EVENTS. Removed obsolete and/or unused exception codes from the acexcep.h header. T= here is the possibility that certain device drivers may be affected if they= use any of these exceptions. The ACPICA documentation has been added to the public git source tree, unde= r acpica/documents. Included are the ACPICA programmer reference, the iASL = compiler reference, and the changes.txt release logfile. Example Code and Data Size: These are the sizes for the OS-independent acpi= ca.lib produced by the Microsoft Visual C++ 6.0 32-bit compiler. The debug = version of the code includes the debug output trace mechanism and has a muc= h larger code and data size. Previous Release: Non-Debug Version: 79.7K Code, 16.4K Data, 96.1K Total Debug Version: 153.9K Code, 48.4K Data, 202.3K Total Current Release: Non-Debug Version: 79.7K Code, 16.4K Data, 96.1K Total Debug Version: 153.7K Code, 48.2K Data, 201.9K Total 2) iASL Compiler/Disassembler and Tools: Allow multiple argument counts for the predefined _SCP method. ACPI 3.0 def= ines _SCP with 3 arguments. Previous versions defined it with only 1 argume= nt. iASL now allows both definitions. iASL/disassembler: avoid infinite loop on bad ACPI tables. Check for zero-l= ength subtables when disassembling ACPI tables. Also fixed a couple of erro= rs where a full 16-bit table type field was not extracted from the input pr= operly. acpisrc: Improve comment counting mechanism for generating source code stat= istics. Count first and last lines of multi-line comments as whitespace, no= t comment lines. Handle Linux legal header in addition to standard acpica h= eader. From owner-freebsd-acpi@FreeBSD.ORG Sun Aug 31 15:08:05 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D7C1106566B for ; Sun, 31 Aug 2008 15:08:05 +0000 (UTC) (envelope-from niktychina@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id 391B18FC12 for ; Sun, 31 Aug 2008 15:08:04 +0000 (UTC) (envelope-from niktychina@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so849406yxb.13 for ; Sun, 31 Aug 2008 08:08:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=5BbhQqZlL4gJzEiBy+Wb+pbAWsN0K+miSV58eapY6r0=; b=tZqAj89BtS00k3Uou76r/gSQ9j4mx7TXA3kOKg7viAsyDGc96xyw2bK83lKkkpN2af d1pN/C3C3YWPjTiS8MFNxlu7pn5ephJNxo7iEnS8hBl6kmHBm3RyX50xP7gEQ5iXEuoR XRwFQVmpVVNJs+XGjZQYRDO+UCItXzGjGl1qg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=kjhrr5nR2uOV2Rx5AbmWd1AkQRJ20hYJTkuwham9UY1fhF67fwSdDSE2fpIvaiQk0+ EA2YDiWHV/E/Mm4coWz+VCCuKYDL+yha7k69MrUS1L4RpSVfQUovpgWOYOPBakHdbA05 8ZrUc8bltOUZvoW8TAESWQFEfntDy1Ojo7Bn4= Received: by 10.150.220.19 with SMTP id s19mr7150518ybg.182.1220193311635; Sun, 31 Aug 2008 07:35:11 -0700 (PDT) Received: by 10.151.109.18 with HTTP; Sun, 31 Aug 2008 07:35:11 -0700 (PDT) Message-ID: Date: Sun, 31 Aug 2008 18:35:11 +0400 From: "=?KOI8-R?B?7snLz8zByiD02d7JzsE=?=" To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ACPI problems on ACER Aspire 5520 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Aug 2008 15:08:05 -0000 Hi all, I have acer aspire 5520 laptop with FreeBSD installed. There is permanent error in dmesg... acpi_ec0: EcRead: failed waiting to get data ACPI Exception (evregion-0529): AE_NO_HARDWARE_RESPONSE, Returned by Handler for [EmbeddedControl] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\\_TZ_.THRM._TMP] (Node 0xc5a5fb80), AE_NO_HARDWARE_RESPONSE ...and FreeBSD can't tell me battery remaining time, capacity etc: # acpiconf -i batt Design capacity: 4800 mAh Last full capacity: 4123 mAh Technology: secondary (rechargeable) Design voltage: 14800 mV Capacity (warn): 240 mAh Capacity (low): 144 mAh Low/warn granularity: 264 mAh Warn/full granularity: 3780 mAh Model number: Primary Serial number: Type: Lion OEM info: ACER State: high Remaining capacity: 100% Remaining time: unknown Present rate: 0 mA Voltage: 16499 mV How can i fix it? Thanks in advance, Nikolay From owner-freebsd-acpi@FreeBSD.ORG Sun Aug 31 16:45:58 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4642E106566B; Sun, 31 Aug 2008 16:45:58 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [220.233.188.227]) by mx1.freebsd.org (Postfix) with ESMTP id A3EBD8FC2D; Sun, 31 Aug 2008 16:45:56 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id m7VGji9D005813; Mon, 1 Sep 2008 02:45:45 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 1 Sep 2008 02:45:44 +1000 (EST) From: Ian Smith To: freebsd_user@guice.ath.cx Message-ID: <20080901020747.A1667@sola.nimnet.asn.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-acpi@freebsd.org, Wes Morgan , freebsd-mobile@freebsd.org Subject: Re: TECRA A9-S9017 -- Idles too hot -- Hardware Support (fwd) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Aug 2008 16:45:58 -0000 Ok, I think we've finally obtained enough info to pin this issue down. I'm going to just forward your message to freebsd-acpi@ because your symptoms (two cpu frequencies only 1 unit apart (one bogus), powerd therefore not shifting to a real lower frequency, so running flat out all the time) came up there several times this year on some machines. While I can't recall the details, nor have access to my own archives currently, I'm pretty sure there was a patch - not sure if it covers or can be applied to 6.3 though. You could browse the -acpi archives for this, but hopefully someone will show mercy and provide a pointer or two, if not directly help out? As Wes since mentioned, 61C isn't hot at all (at that frequency anyway) but still it'd be better to get the mangled cpu freqs sorted out so that powerd can do its thing properly. [FWIW, I'm the OP in this ongoing conversation on -mobile below .. sorry I didn't pay a bit more attention back when this was a 'hot issue' ..] cheers, Ian ---------- Forwarded message ---------- Date: Sat, 30 Aug 2008 17:07:36 -0400 From: freebsd_user@guice.ath.cx To: freebsd-mobile@freebsd.org Cc: Ian Smith Subject: Re: TECRA A9-S9017 -- Idles too hot -- Hardware Support On Thu, Jan 01, 1970 at 12:00:00AM +0000, email@WORKSTATION.guice.ath.cx wrote: FROM THE LAST MESSAGE ... > > > > > However we need some empirical data about what it's doing. Showing your > > > > /var/run/dmesg.boot and 'sysctl hw.acpi' output would be a good start. > > > > > > > Initially we didn't provide that data until someone asked for it to be sure that is > > > in fact what was needed or if the was some other incorrect setting. > > > > > > /var/run/dmesg.boot ... > > > > I'm trimming this down to the likely relevant ACPI stuff .. > > > > > Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. > > > FreeBSD 6.3-RELEASE-p3 #1: Mon Aug 4 23:37:02 EDT 2008 > > > root@WORKSTATION.ath.cx:/usr/obj/usr/src/sys/WORKSTATION > > > ACPI APIC Table: > > > Timecounter "i8254" frequency 1193182 Hz quality 0 > > > CPU: Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz (2194.52-MHz 686-class CPU) > > > Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 > > > Features=0xbfebfbff > > > Features2=0xe3bd > > > AMD Features=0x20100000 > > > AMD Features2=0x1 > > > Cores per package: 2 > > > real memory = 2113142784 (2015 MB) > > > avail memory = 2058563584 (1963 MB) > > > ioapic0: Changing APIC ID to 1 > > > ioapic0 irqs 0-23 on motherboard > > [..] > > > acpi0: on motherboard > > > acpi0: Power Button (fixed) > > > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > > > acpi_timer0: <24-bit timer at 3.579545MHz> port 0xd808-0xd80b on acpi0 > > > acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 > > > Timecounter "HPET" frequency 14318180 Hz quality 900 > > > cpu0: on acpi0 > > [..] > > > acpi_lid0: on acpi0 > > > battery0: on acpi0 > > > acpi_button0: on acpi0 > > > acpi_acad0: on acpi0 > > > acpi_tz0: on acpi0 > > [..] > > > > No cpufreq driver/s. cpufreq removed from your custom kernel? So no > > CPU frequency control. So, powerd is rendered powerless .. > > > 'powerd' is now operational: idle time > 90%, decreasing clock speed from 2201 MHz to 2200 MHz^M idle time > 90%, decreasing clock speed from 2201 MHz to 2200 MHz^M idle time > 90%, decreasing clock speed from 2201 MHz to 2200 MHz^M idle time > 90%, decreasing clock speed from 2201 MHz to 2200 MHz^M idle time > 90%, decreasing clock speed from 2201 MHz to 2200 MHz^M ^Ctotal joules used: 41737.500^M > > Try booting with the GENERIC kernel, you should see one or two of the > > supported drivers listed in cpufreq(4) loaded in dmesg.boot. Then see > > if powerd isn't doing the right thing (w/ powerd -v as discussed below) > > > This has always been the /GENERIC kernel copied to a custome name. This was a 6.0-RELEASE UPGRADED TO -p3. Apparently cpufreq wasn't considered as a default entry in the /GENERIC. > > > > > sysctl hw.acpi ... > > > > > > hw.acpi.supported_sleep_state: S3 S4 S5 > > > hw.acpi.power_button_state: S5 > > > hw.acpi.sleep_button_state: S3 > > > hw.acpi.lid_switch_state: NONE > > > hw.acpi.standby_state: S1 > > > hw.acpi.suspend_state: S3 > > > hw.acpi.sleep_delay: 1 > > > hw.acpi.s4bios: 0 > > > hw.acpi.verbose: 0 > > > hw.acpi.disable_on_reboot: 0 > > > hw.acpi.handle_reboot: 0 > > > hw.acpi.reset_video: 0 > > > hw.acpi.cpu.cx_lowest: C1 > > > hw.acpi.battery.life: 100 > > > hw.acpi.battery.time: -1 > > > hw.acpi.battery.state: 0 > > > hw.acpi.battery.units: 1 > > > hw.acpi.battery.info_expire: 5 > > > hw.acpi.acline: 1 > > > hw.acpi.thermal.min_runtime: 0 > > > hw.acpi.thermal.polling_rate: 10 > > > hw.acpi.thermal.user_override: 0 > > > hw.acpi.thermal.tz0.temperature: 63.0C > > > hw.acpi.thermal.tz0.active: -1 > > > hw.acpi.thermal.tz0.passive_cooling: 0 > > > hw.acpi.thermal.tz0.thermal_flags: 0 > > > hw.acpi.thermal.tz0._PSV: -1 > > > hw.acpi.thermal.tz0._HOT: -1 > > > hw.acpi.thermal.tz0._CRT: 102.0C > > > hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 > > > > No passive cooling. See acpi_thermal(4) .. you may want to set some > > overrides .. but it might all just work with the GENERIC kernel anyway. > Attempting to: --> sysctl hw.acpi.thermal.user_override hw.acpi.thermal.user_override: 0 Attempting to: --> sysctl hw.acpi.thermal.user_override=1 hw.acpi.thermal.user_override: 0 -> 1 Attempting to: --> sysctl hw.acpi.thermal.tz0.passive_cooling hw.acpi.thermal.tz0.passive_cooling: 0 Attempting to: --> sysctl hw.acpi.thermal.tz0.passive_cooling=1 hw.acpi.thermal.tz0.passive_cooling: 0 sysctl: hw.acpi.thermal.tz0.passive_cooling: Operation not supported by device NOTE: While we are able to change the threshold for: hw.acpi.thermal.tz0._PSV: -1, we don't see the need to do so because the above passive_cooling is not enabled. Well, so much for passive_cooling. :=\ > > Also, have you set anything in BIOS regarding power usage, speedstep or > > any other settings that might get reflected into your boot ACPI setup? Initially we left the BIOS power settings the way the OEM set them (Vista). We are able to choose from one of Dynamic, High or low not much else to play with in the way of power settings (ACPI) with the exception of LCD and/or letting the OS control devices. Unable to directly set CPU steppings/freq settings within this BIOS. > > And, are you loading acpi_toshiba(4)? Not sure if it would help with > > this, but may at least provide some useful info in its sysctls .. > > > This is an issue revisited; take a deep breath. Better yet, here's the short version, in the kernel 'device acpi_toshiba' does not work for us on this machine unless we neglected to make an accompanying needed acpi entry. Aa we understand it, we were to only add 'device acpi_toshiba' to load the neccessary acpi toshiba extras. Using 'acpi_toshiba_load="YES"' in the /boot/loader.conf -and- using 'kldload acpi_toshiba' from the cli works like a charm but has no positive affect on the current discussion (heat). > > > > Secondly, in its own window or vty, as root, run /etc/rc.d/powerd stop > > > > (if it's running) then run 'powerd -v' which runs in foreground and says > > > > exactly what it's doing re shifting CPU frequency under various loads. idle time > 90%, decreasing clock speed from 2201 MHz to 2200 MHz^M idle time > 90%, decreasing clock speed from 2201 MHz to 2200 MHz^M idle time > 90%, decreasing clock speed from 2201 MHz to 2200 MHz^M ^Ctotal joules used: 41737.500 > > > > > > > > It's also useful to watch the temperature(s) directly over the time, see > > > > acpi_thermal(4) and try logging those sysctls periodically in a script. The following data is the result of the concerns I have; running too hot. These figures are the lowest temperatures this machine idles while FreeBSD is installed and running. The temperatures shown herein only rise with use but never go lower than what we're showing here when the laptop returns to idle. Attempting to: --> sysctl hw.acpi.thermal.tz0. hw.acpi.thermal.tz0.temperature: 61.0C hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.passive_cooling: 0 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: -1 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 102.0C hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 > > > > Firstly, yes that comment isn't too helpful .. power_profile only acts > > > > (so far) when you apply or remove AC power, using the following values > > > > from /etc/defaults/rc.conf unless you've set them otherwise: > > > > > > > > performance_cx_lowest="HIGH" # Online CPU idle state > > > > performance_cpu_freq="HIGH" # Online CPU frequency > > > > economy_cx_lowest="HIGH" # Offline CPU idle state > > > > economy_cpu_freq="HIGH" # Offline CPU frequency Our /etc/defaults/rc.conf performance_cx_lowest="HIGH" # Online CPU idle state performance_cpu_freq="NONE" # Online CPU frequency economy_cx_lowest="HIGH" # Offline CPU idle state economy_cpu_freq="NONE" # Offline CPU frequency > > > > If you have a look at /etc/rc.d/power_profile you'll see that these are > > > > applied to sysctl hw.acpi.cpu.cx_lowest (from hw.acpi.cpu.cx_supported) > > > > and dev.cpu.0.freq (from dev.cpu.0.freq_levels). You can set the above > > > > variables to HIGH, LOW, a specific value, or NONE. Attempting to: --> sysctl hw.acpi.cpu.cx_supported sysctl: unknown oid 'hw.acpi.cpu.cx_supported' Attempting to: --> sysctl hw.acpi.cpu hw.acpi.cpu.cx_lowest: C1 Above, where is "hw.acpi.cpu.cx_supported"? Did FreeBSD 'not' probe something? Attempting to: --> sysctl dev.cpu.0.freq_levels dev.cpu.0.freq_levels: 2201/35000 2200/35000 1925/30625 1650/26250 1600/23000 1400/20125 1200/16000 1050/14000 900/12000 800/14300 700/12512 600/10725 500/8937 400/7150 300/5362 200/3575 100/1787 Following is grepped from /var/run/dmesg.boot: CPU: Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz (2194.54-MHz 686-class CPU) cpu0: on acpi0 est0: on cpu0 p4tcc0: on cpu0 > > > > Specify "NONE" to have power_profile make no changes. "C3" or at least > > > > "C2" can be useful CX values, in some machines helping with temperature. > > > > powerd will soon override the dev.cpu.0.freq setting anyway, so it's not > > > > a problem - again, watch powerd -v output - and I guess you'll rarely > > > > run on battery (you've got a nice 2-3 hour UPS, though :) > Our /etc/rc.conf performance_cx_lowest="C4" # Online CPU idle state #performance_cpu_freq="HIGH" # Online CPU frequency economy_cx_lowest="C5" # Offline CPU idle state #economy_cpu_freq="HIGH" # Offline CPU frequency This machine can afford to go to C4 and C5 unless needed otherwise. I'll try anything to lowwer this machines temp. > > > This is another issue in addition to the heat. As you say, this battery > > > should last any where from 2-3 hours, however as it is now; > > > out-of-the-box so to speak, this machine will only stay powered up > > > approximately 1-hour on using the oem battery. > > > > That's because it runs at (presumably) its maximum frequency all of the > > time; you're lucky to get an hour at that rate, and yes it'll run hot :) > > > > 'sysctl dev.cpu.0.freq hw.acpi.thermal.tz0.temperature' now and again. These numbers have not changed (lowwer) prior to or during this thread. Attempting to: --> sysctl dev.cpu.0.freq dev.cpu.0.freq: 2201 <-- has gone down to 2200; no lowwer. Attempting to: --> sysctl hw.acpi.thermal.tz0.temperature hw.acpi.thermal.tz0.temperature: 61.0C > > > > This machine has never run this hot, prior to running 'powerd'-- or run > > > > > this warm, while idling with 'powerd' in comparison to running under windows > > > > > --not trying to start and OS confilict here, trying to learn, understand > > > > > and control this beast of a machine if possible. > > > > > > > > Of course, and it's likely doable, though you might need to run 7-STABLE > > > > for the latest dual-core ACPI handling. Let's see how we go with some > > > > real information, before suggesting taking this to freebsd-acpi@. I > > > > don't see where you've mentioned what version of FreeBSD it's running? > > > > > > I believe I did so at the outset of this thread. In any case dmesg has > > > now provided that information. > > > > ok, 6.3-R-p3. Frankly I've no idea whether your dual-core Toshiba is or > > is not subject to any of the dual-core issues solved or being actively > > worked on in freebsd-acpi and being applied mostly or at least firstly > > back into 7-STABLE. I'd suggest browsing the -acpi archives for the > > last few months, it's not that big .. that is, if using the GENERIC > > kernel and running powerd doesn't improve matters sufficiently. > > > > cheers, Ian From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 1 11:06:51 2008 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3215A106575E for ; Mon, 1 Sep 2008 11:06:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2241F8FC15 for ; Mon, 1 Sep 2008 11:06:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m81B6pB7068341 for ; Mon, 1 Sep 2008 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m81B6oZN068337 for freebsd-acpi@FreeBSD.org; Mon, 1 Sep 2008 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 1 Sep 2008 11:06:50 GMT Message-Id: <200809011106.m81B6oZN068337@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2008 11:06:51 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o kern/118973 acpi [acpi]: Kernel panic with acpi boot o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/120953 acpi [acpi]: FreeBSD 6.3 Release: acpi_tz0: _TMP value is f kern/121454 acpi [pst] Promise SuperTrak SX6000 does not load during bo 19 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- f kern/67309 acpi zzz reboot computer (ACPI S3) o i386/69750 acpi Boot without ACPI failed on ASUS L5 s kern/73823 acpi [request] acpi / power-on by timer support o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 o kern/89411 acpi [acpi] acpiconf bug s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108581 acpi [sysctl] sysctl: hw.acpi.cpu.cx_lowest: Invalid argume o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/114165 acpi [acpi] Dell C810 - ACPI problem o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot o kern/124223 acpi [acpi] [patch] acpi_battery.c -- Notify user-defined c o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/124744 acpi [acpi] [patch] incorrect _BST result validation for To 23 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 1 13:28:26 2008 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A9DF1065681 for ; Mon, 1 Sep 2008 13:28:26 +0000 (UTC) (envelope-from lists@peter.de.com) Received: from nemesis.charlie.mouhaha.de (nemesis.charlie.mouhaha.de [78.47.10.193]) by mx1.freebsd.org (Postfix) with ESMTP id D29658FC13 for ; Mon, 1 Sep 2008 13:28:25 +0000 (UTC) (envelope-from lists@peter.de.com) Received: from localhost (nemesis.charlie.mouhaha.de [78.47.10.193]) by nemesis.charlie.mouhaha.de (Postfix) with ESMTP id 3C64E1705A for ; Mon, 1 Sep 2008 14:12:26 +0100 (BST) X-Virus-Scanned: amavisd-new at mouhaha.de Received: from nemesis.charlie.mouhaha.de ([78.47.10.193]) by localhost (nemesis.charlie.mouhaha.de [78.47.10.193]) (amavisd-new, port 10024) with ESMTP id oksZxNf02Ehz for ; Mon, 1 Sep 2008 14:12:18 +0100 (BST) Received: from nemesis.charlie.mouhaha.de (nemesis.charlie.mouhaha.de [78.47.10.193]) by nemesis.charlie.mouhaha.de (Postfix) with SMTP id 7342017043 for ; Mon, 1 Sep 2008 14:12:18 +0100 (BST) Received: from dilbert.office.centralnic.com (office.centralnic.net [82.68.174.118]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by nemesis.charlie.mouhaha.de (Postfix) with ESMTPSA id AAC7C1703F for ; Mon, 1 Sep 2008 14:12:17 +0100 (BST) Date: Mon, 1 Sep 2008 14:12:16 +0100 From: Oliver Peter To: freebsd-acpi@FreeBSD.org Message-ID: <20080901141216.72601dfb@dilbert.office.centralnic.com> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.10.4; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: kernel: interrupt storm detected on "irq22:"; throttling interrupt source [7.0-RELEASE] X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lists@peter.de.com List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2008 13:28:26 -0000 Hi, For about 6 weeks I'm suffering an interrupt storm on my production machine which is running 7.0-RELEASE-p3/amd64. The kernel is flooding my syslog with the following messages[1]. A full dmesg can be found here[2]. As discribed in "Using and Debugging FreeBSD ACPI" I already tried to disable apic during boot time but that's a bad idea because it seems that the SATA2 onboard controller has to have apic loaded - please correct me if I'm wrong. /boot/loader.conf: hint.apic.0.disabled="1" Doesn't work for me. Btw. I think it's worth it to have a little note in that part of the documentation which says something about possible failures during the boot time. Thanks for any suggestions. Bye O. ========================== [1] /var/log/messages ========================== ... Jul 23 09:29:19 charlie kernel: interrupt storm detected on "irq22:"; throttling interrupt source Jul 23 09:29:50 charlie last message repeated 31 times Jul 23 09:31:51 charlie last message repeated 120 times Jul 23 09:41:52 charlie last message repeated 597 times Jul 23 09:51:52 charlie last message repeated 597 times Jul 23 10:01:53 charlie last message repeated 597 times Jul 23 10:11:52 charlie last message repeated 596 times Jul 23 10:21:53 charlie last message repeated 597 times Jul 23 10:31:52 charlie last message repeated 596 times Jul 23 10:41:53 charlie last message repeated 597 times Jul 23 10:51:53 charlie last message repeated 596 times Jul 23 11:01:53 charlie last message repeated 597 times Jul 23 11:11:53 charlie last message repeated 596 times ... Aug 14 14:00:01 charlie kernel: interrupt storm detected on "irq22:"; throttling interrupt source Aug 14 14:00:32 charlie last message repeated 31 times Aug 14 14:02:33 charlie last message repeated 120 times Aug 14 14:12:34 charlie last message repeated 597 times Aug 14 14:22:35 charlie last message repeated 598 times Aug 14 14:32:36 charlie last message repeated 597 times Aug 14 14:42:37 charlie last message repeated 597 times Aug 14 14:52:38 charlie last message repeated 598 times Aug 14 15:02:39 charlie last message repeated 597 times Aug 14 15:12:40 charlie last message repeated 597 times Aug 14 15:22:41 charlie last message repeated 598 times ... ========================== [2] dmesg ========================== Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE-p1 #4: Thu Jun 19 18:03:38 BST 2008 root@charlie.mouhaha.de:/usr/obj/usr/src/sys/CHARLIE Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ (2899.98-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x60fb2 Stepping = 2 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x11f Cores per package: 2 usable memory = 2099699712 (2002 MB) avail memory = 2024751104 (1930 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Jun 19 2008 18:02:12) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7df00000 (3) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_throttle0: CLK_VAL field overlaps THT_EN bit device_attach: acpi_throttle0 attach returned 6 powernow0: on cpu0 cpu1: on acpi0 powernow1: on cpu1 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xc000-0xc0ff mem 0xfc000000-0xfdffffff,0xfe9f0000-0xfe9fffff,0xfe800000-0xfe8fffff irq 18 at device 5.0 on pci1 pci1: at device 5.2 (no driver attached) pcib2: at device 7.0 on pci0 pci2: on pcib2 re0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeafffff irq 19 at device 0.0 on pci2 re0: Using 2 MSI messages miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1d:92:b6:ce:92 re0: [FILTER] re0: [FILTER] atapci0: port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfe7ff800-0xfe7ffbff irq 22 at device 18.0 on pci0 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ohci0: mem 0xfe7fe000-0xfe7fefff irq 16 at device 19.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0xfe7fd000-0xfe7fdfff irq 17 at device 19.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ohci2: mem 0xfe7fc000-0xfe7fcfff irq 18 at device 19.2 on pci0 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: on ohci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ohci3: mem 0xfe7fb000-0xfe7fbfff irq 17 at device 19.3 on pci0 ohci3: [GIANT-LOCKED] ohci3: [ITHREAD] usb3: OHCI version 1.0, legacy support usb3: SMM does not respond, resetting usb3: on ohci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ohci4: mem 0xfe7fa000-0xfe7fafff irq 18 at device 19.4 on pci0 ohci4: [GIANT-LOCKED] ohci4: [ITHREAD] usb4: OHCI version 1.0, legacy support usb4: SMM does not respond, resetting usb4: on ohci4 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered ehci0: mem 0xfe7ff000-0xfe7ff0ff irq 19 at device 19.5 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb5: EHCI version 1.0 usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4 usb5: on ehci0 usb5: USB revision 2.0 uhub5: on usb5 uhub5: 10 ports with 10 removable, self powered pci0: at device 20.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] isab0: at device 20.3 on pci0 isa0: on isab0 pcib3: at device 20.4 on pci0 pci3: on pcib3 acpi_button0: on acpi0 sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] orm0: at iomem 0xcd800-0xce7ff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 WARNING: ZFS is considered to be an experimental feature in FreeBSD. Timecounters tick every 1.000 msec hptrr: no controller detected. ZFS filesystem version 6 ZFS storage pool version 6 ad4: 476940MB at ata2-master UDMA33 ad6: 476940MB at ata3-master UDMA33 SMP: AP CPU #1 Launched! Trying to mount root from zfs:tank re0: link state changed to UP cryptosoft0: on motherboard -- Oliver PETER, email: oliver@peter.de.com, ICQ# 113969174 "I like to con people. And I like to insult people. If you combine con & insult, you get consult!" -- Dogbert From owner-freebsd-acpi@FreeBSD.ORG Mon Sep 1 21:13:45 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14FAE1065684 for ; Mon, 1 Sep 2008 21:13:45 +0000 (UTC) (envelope-from miguel@anjos.strangled.net) Received: from mailrly06.isp.novis.pt (mailrly06.isp.novis.pt [195.23.133.216]) by mx1.freebsd.org (Postfix) with ESMTP id 6B46A8FC17 for ; Mon, 1 Sep 2008 21:13:44 +0000 (UTC) (envelope-from miguel@anjos.strangled.net) Received: (qmail 16831 invoked from network); 1 Sep 2008 21:13:42 -0000 Received: from unknown (HELO mailfrt11.isp.novis.pt) ([195.23.133.227]) (envelope-sender ) by mailrly06.isp.novis.pt with compressed SMTP; 1 Sep 2008 21:13:42 -0000 Received: (qmail 12950 invoked from network); 1 Sep 2008 21:13:41 -0000 Received: from unknown (HELO satan.anjos.strangled.net) ([89.180.147.175]) (envelope-sender ) by mailfrt11.isp.novis.pt with SMTP; 1 Sep 2008 21:13:41 -0000 Received: from satan.anjos.strangled.net (localhost [127.0.0.1]) by satan.anjos.strangled.net (8.14.2/8.14.2) with ESMTP id m81LDMue024105; Mon, 1 Sep 2008 22:13:23 +0100 (WEST) (envelope-from miguel@satan.anjos.strangled.net) Received: (from miguel@localhost) by satan.anjos.strangled.net (8.14.2/8.14.2/Submit) id m81LDK1R024104; Mon, 1 Sep 2008 22:13:20 +0100 (WEST) (envelope-from miguel) Date: Mon, 1 Sep 2008 22:13:20 +0100 (WEST) From: Miguel Lopes Santos Ramos Message-Id: <200809012113.m81LDK1R024104@satan.anjos.strangled.net> To: takawata@init-main.com In-Reply-To: <200808301838.m7UIc4hE018292@sana.init-main.com> Cc: freebsd-acpi@freebsd.org Subject: Re: Suspend/Resume on AMD64 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2008 21:13:45 -0000 This is pretty scary... There's much more to be done than I thought. Well, I'm editing code without paying attention to consequences. It can't hurt anyone until it runs... I'm starting with the easyest part: adding the extra registers (r8-r15, cool!, I wish I had these back in my days of assembly programming). I am also taking a look at amd64/amd64/mpboot.S, which contains protected mode and 64-bit mode initialization, needed for wakeup. It is too early to need help. I'm still learning about AMD64 and refreshing my memory of control registers. I will contact you again in a week or so, if it's ok. Miguel > From takawata@init-main.com Sat Aug 30 20:10:23 2008 > > In message <200808301751.m7UHprcc023311@satan.anjos.strangled.net>, Miguel Lope > s Santos Ramos wrote: > > > >Hi, > > > >I'm running amd64 on my laptop since early 2005. > >Had a bunch of problems, ehci, radeon, etc, but most were fixed by someone sin > >ce then. > >One thing I still miss though is ACPI suspend/resume. > >Browsing through dev/acpica I found out that this feature set is simply disabl > >ed outside i386 > >(several #ifndef __i386__) and figured that maybe that's just because no one a > >ppeared to test it. > > The code is in i386/acpica/acpi_wakeup.c, i386/acpica/acpi_wakecode.S > > > >Well, I hereby volunteer to test this. > >I have already removed the ifndefs and achieved a machine hang when tried to s > >uspend. > > > >I have some experience with 80386 initialization (almost obsolete), > >I am a capable programmer (able to keep the indentation of an existing source > >file), > >and may be able to develop some new code if someone points me to the right > >documents at Intel or AMD. > >I am partially available on weekends. > > > >Will someone involved with suspend/resume on i386 help me on this? > > You called me? :-) > > >Would it be necessary to move to -CURRENT? > >Where should I start? > > Copy the code to amd64/acpica/ then try to run as it is. > In amd64, you have to preserve many registers than i386, so > the code should be more ABI aware. > http://2008.asiabsdcon.org/papers/P9A-paper.pdf > > To debug lowest part of resume code, you may want to use > BEEP debug. > > I wrote incomplete SMP suspend/resume code 3 months ago. > http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004879.html > > Indeed, I reserve 10GB partition to my primary laptop > to develop amd64 suspend/resume.But I don't even install it yet. > So if you implement it, I'm willing to test it :-P. From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 2 06:32:06 2008 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDCA31065674 for ; Tue, 2 Sep 2008 06:32:06 +0000 (UTC) (envelope-from d.vashistha@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by mx1.freebsd.org (Postfix) with ESMTP id 4CADA8FC12 for ; Tue, 2 Sep 2008 06:32:06 +0000 (UTC) (envelope-from d.vashistha@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1430618fgb.35 for ; Mon, 01 Sep 2008 23:32:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=uEmAUlHuuZrAuBE1Q34+rUncbM62zF9AOx5N/q+z/TU=; b=eE+YNZfFtW1s2vLPhzejat04t95nmktrjJj0fQGagvYEEiys/Tf4oi8ODGqT7bFxfe xVRX22hsIpdzLUcgPG+9R3AAZZv6mbFvIymPAksg9m1m8MMKN4d9DnM33P/EPY0LOC6k hocyJRdfyP3jaOWzliMr4xK9mW80ug0CdOvIg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=CctqvGE0tIXYqyjZlvvas5Qu8RLUXnqLpuuruk0FVz/3UCVvdRS/2M4rjJnuTHMUVz yoctgR7EFz3xmof40o4du92HF53pOFlPkTeP96J48XSMFKOzRU5OXA3kJ6P4MagYaXuG XB67mCHh9c5aOpYu0rImiQsNMKVKY2xrZz6Bo= Received: by 10.86.52.6 with SMTP id z6mr5265555fgz.18.1220335739686; Mon, 01 Sep 2008 23:08:59 -0700 (PDT) Received: by 10.86.73.17 with HTTP; Mon, 1 Sep 2008 23:08:59 -0700 (PDT) Message-ID: <5b3db66a0809012308t18faa687lc00257523e8e1c22@mail.gmail.com> Date: Tue, 2 Sep 2008 11:38:59 +0530 From: "Deepak Vashistha" To: freebsd-acpi@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Power management in freebsd X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2008 06:32:06 -0000 Dear sir, I am using freebsd 7.0 and i want to enable powermanagement but for this configuration what setting i have to do please help me i have intel server board for PIII processor and bios is acpi/apm enabled. With Regards Deepak Vashistha From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 2 16:57:33 2008 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37FE21065673 for ; Tue, 2 Sep 2008 16:57:33 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal1.es.net (postal2.es.net [198.128.3.206]) by mx1.freebsd.org (Postfix) with ESMTP id 1EAD88FC1C for ; Tue, 2 Sep 2008 16:57:33 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IZW73850; Tue, 02 Sep 2008 09:46:50 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 344634500F; Tue, 2 Sep 2008 09:46:50 -0700 (PDT) To: "Deepak Vashistha" In-Reply-To: Your message of "Tue, 02 Sep 2008 11:38:59 +0530." <5b3db66a0809012308t18faa687lc00257523e8e1c22@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1220374010_11268P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Tue, 02 Sep 2008 09:46:50 -0700 From: "Kevin Oberman" Message-Id: <20080902164650.344634500F@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ;; X-Sender: X-To_Name: Deepak Vashistha X-To_Domain: gmail.com X-To: "Deepak Vashistha" X-To_Email: d.vashistha@gmail.com X-To_Alias: d.vashistha Cc: freebsd-acpi@FreeBSD.org Subject: Re: Power management in freebsd X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2008 16:57:33 -0000 --==_Exmh_1220374010_11268P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Tue, 2 Sep 2008 11:38:59 +0530 > From: "Deepak Vashistha" > Sender: owner-freebsd-acpi@freebsd.org > > Dear sir, > I am using freebsd 7.0 and i want to enable powermanagement but for this > configuration what setting i have to do please help me i have intel server > board for PIII processor and bios is acpi/apm enabled. PIII has very limited power management and the ACPI implementations are often incomplete or simply broken. I would suggest using APM and not ACPI. (Note that APM and ACPI are mutually exclusive. You can't really run both at the same time although the APM emulation in FreeBSD makes it look a lot like both are running.) -- 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 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1220374010_11268P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFIvW36kn3rs5h7N1ERAiq+AJ9oWA0sJnEUGiEa7+doncrkw/LJEACfTQ7E IF+Url41vvxHX6SmCp6Qbns= =fMKB -----END PGP SIGNATURE----- --==_Exmh_1220374010_11268P-- From owner-freebsd-acpi@FreeBSD.ORG Tue Sep 2 22:21:53 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D34EC106564A for ; Tue, 2 Sep 2008 22:21:53 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by mx1.freebsd.org (Postfix) with ESMTP id A382F8FC15 for ; Tue, 2 Sep 2008 22:21:53 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so2490790wfg.7 for ; Tue, 02 Sep 2008 15:21:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :sender:to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=WHjjH4qb2krEImkA4Vh2kCHUFL4OibM2/kFAr+zNPoQ=; b=jimTXH8vhGOQNvPtrhZ4GhrQVQlrE5s2ayK+Mv4Ylqymqfv62+vqg5cJKzSU+IlIEq T8rSsgzaYO7j5ur5cK3KNkCkHj2P4JC3q+yJX2dmGw4yELLo7BFJLKGZH/rIb/DnTUlL 5umXlV5CwpEKhPglL+TCG73LyXKb3V8hP/dNI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references:x-google-sender-auth; b=WVpu+N3fBuoioxHS9lFAv9xKc63faTDEs2vWR3QaKp0yb1DJJIcRNT51b3n5hpWirK QCPOZR6nchvimUunT4Jptn3k3+l3MQ+/3wpfR5goB0pT0Qu6IgBQ9jIuFIhlmUF/xL0k /yJaRzlXJdDi8p6MVzViZ5kThMxiSzSKuljr0= Received: by 10.142.231.7 with SMTP id d7mr2729348wfh.246.1220392781934; Tue, 02 Sep 2008 14:59:41 -0700 (PDT) Received: by 10.142.141.5 with HTTP; Tue, 2 Sep 2008 14:59:41 -0700 (PDT) Message-ID: <539c60b90809021459g65d9a1b7j40ae129c5ff9d562@mail.gmail.com> Date: Tue, 2 Sep 2008 14:59:41 -0700 From: "Steve Franks" Sender: bahamasfranks@gmail.com To: "Miguel Lopes Santos Ramos" In-Reply-To: <200809012113.m81LDK1R024104@satan.anjos.strangled.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200808301838.m7UIc4hE018292@sana.init-main.com> <200809012113.m81LDK1R024104@satan.anjos.strangled.net> X-Google-Sender-Auth: 29a7fc4823028496 Cc: freebsd-acpi@freebsd.org Subject: Re: Suspend/Resume on AMD64 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: stevefranks@ieee.org List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2008 22:21:53 -0000 If you're looking for more volunteers, I've been highly disappointed for sometime in the lack of support for amd64, especially for suspend. I'm a reasonable C programmer as well, and I've got about 5 boxes deployed to test on. The one thing I don't have is oodles of time for learning new stuff, I'm afraid (little feet around the house these days...) It's somewhat suprising that our "sever-grade" os sticks with the lowest-common denominator for everything - don't we want terabytes of ram? I had enough icky experiences with linux a while back to make me stick with freebsd, so let's flush out the feature set, a bit. Steve On Mon, Sep 1, 2008 at 2:13 PM, Miguel Lopes Santos Ramos wrote: > > This is pretty scary... > There's much more to be done than I thought. > > Well, I'm editing code without paying attention to consequences. > It can't hurt anyone until it runs... > > I'm starting with the easyest part: adding the extra registers (r8-r15, cool!, I > wish I had these back in my days of assembly programming). > > I am also taking a look at amd64/amd64/mpboot.S, which contains protected mode > and 64-bit mode initialization, needed for wakeup. > > It is too early to need help. > I'm still learning about AMD64 and refreshing my memory of control registers. > > I will contact you again in a week or so, if it's ok. > > Miguel > >> From takawata@init-main.com Sat Aug 30 20:10:23 2008 >> >> In message <200808301751.m7UHprcc023311@satan.anjos.strangled.net>, Miguel Lope >> s Santos Ramos wrote: >> > >> >Hi, >> > >> >I'm running amd64 on my laptop since early 2005. >> >Had a bunch of problems, ehci, radeon, etc, but most were fixed by someone sin >> >ce then. >> >One thing I still miss though is ACPI suspend/resume. >> >Browsing through dev/acpica I found out that this feature set is simply disabl >> >ed outside i386 >> >(several #ifndef __i386__) and figured that maybe that's just because no one a >> >ppeared to test it. >> >> The code is in i386/acpica/acpi_wakeup.c, i386/acpica/acpi_wakecode.S >> >> >> >Well, I hereby volunteer to test this. >> >I have already removed the ifndefs and achieved a machine hang when tried to s >> >uspend. >> > >> >I have some experience with 80386 initialization (almost obsolete), >> >I am a capable programmer (able to keep the indentation of an existing source >> >file), >> >and may be able to develop some new code if someone points me to the right >> >documents at Intel or AMD. >> >I am partially available on weekends. >> > >> >Will someone involved with suspend/resume on i386 help me on this? >> >> You called me? :-) >> >> >Would it be necessary to move to -CURRENT? >> >Where should I start? >> >> Copy the code to amd64/acpica/ then try to run as it is. >> In amd64, you have to preserve many registers than i386, so >> the code should be more ABI aware. >> http://2008.asiabsdcon.org/papers/P9A-paper.pdf >> >> To debug lowest part of resume code, you may want to use >> BEEP debug. >> >> I wrote incomplete SMP suspend/resume code 3 months ago. >> http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004879.html >> >> Indeed, I reserve 10GB partition to my primary laptop >> to develop amd64 suspend/resume.But I don't even install it yet. >> So if you implement it, I'm willing to test it :-P. > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" > From owner-freebsd-acpi@FreeBSD.ORG Wed Sep 3 18:32:50 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9CE01065BDA for ; Wed, 3 Sep 2008 18:32:50 +0000 (UTC) (envelope-from niktychina@gmail.com) Received: from mail-gx0-f17.google.com (mail-gx0-f17.google.com [209.85.217.17]) by mx1.freebsd.org (Postfix) with ESMTP id 702E68FC17 for ; Wed, 3 Sep 2008 18:32:50 +0000 (UTC) (envelope-from niktychina@gmail.com) Received: by gxk10 with SMTP id 10so6086689gxk.19 for ; Wed, 03 Sep 2008 11:32:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=K9LSlMeT1um809LMMNYDZboBxNo+XI4L12Lz//YFxoQ=; b=ZhY/RiVvc+WRvQtv9fcBsukUSHYT/WXqWGzHthceGnzFXBFDZfSS1iXCrI4OGsxNzr 7fJiB01BMW+mnkYp408UV4RBnCpg98iibpXkeLvVLtA9DBJd9HDijajlB6Z+WEWghDlz asx2yh/UbJ90intxCg7sqpH+l1RCC3l/xqtSY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=qW9zj1q9Vy4npaEHVHjfd0Lqo3TPMS4sQJHBJ4Pc3e7MH67n8saQQjGWJYJH5kbtbH oy6NfFj1iQhUvQwmZSTph4Ghz50AmcZpB8UhL2EgIvqGgcgYpVMIxHmnwhFQLFCXu6+a wv1vj2N/9I446Y8xAa0JWdu4aMOgq7WsbDzYY= Received: by 10.150.150.3 with SMTP id x3mr12859135ybd.147.1220466769293; Wed, 03 Sep 2008 11:32:49 -0700 (PDT) Received: by 10.151.109.18 with HTTP; Wed, 3 Sep 2008 11:32:49 -0700 (PDT) Message-ID: Date: Wed, 3 Sep 2008 22:32:49 +0400 From: "=?KOI8-R?B?7snLz8zByiD02d7JzsE=?=" To: freebsd-acpi@freebsd.org In-Reply-To: MIME-Version: 1.0 References: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ACER Aspire 5520's fixed .asl X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2008 18:32:50 -0000 Hi all, i fixed .asl of my acer laptop yesterday (by analogy with 5720's from http://acpi.sf.net), so there aren't any errors and warnings now. You can find it here: http://slil.ru/26113392 Today: # iasl asp5520g-ok-3.asl Intel ACPI Component Architecture ASL Optimizing Compiler version 20070320 [Feb 24 2008] Copyright (C) 2000 - 2007 Intel Corporation Supports ACPI Specification Revision 3.0a ASL Input: asp5520g-ok-3.asl - 7141 lines, 242150 bytes, 2974 keywords AML Output: /tmp/acpidump.aml - 24543 bytes 878 named objects 2096 executable opcodes Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 731 Optimizations I copied /tmp/acpidump.aml to /boot/DSDT.aml and added acpi_dsdt_load="YES" and acpi_dsdt_name="/boot/DSDT.aml" to /boot/loader.conf. But... i still have console errors and acpiconf doesn't see battery :( Nothing has changed :( So, help pls, i was so glad yesterday :) From owner-freebsd-acpi@FreeBSD.ORG Fri Sep 5 16:42:31 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66AF4106566C; Fri, 5 Sep 2008 16:42:31 +0000 (UTC) (envelope-from gahr@FreeBSD.org) Received: from cpanel03.rubas-s03.net (cpanel03.rubas-s03.net [195.182.222.73]) by mx1.freebsd.org (Postfix) with ESMTP id 24C3B8FC1C; Fri, 5 Sep 2008 16:42:30 +0000 (UTC) (envelope-from gahr@FreeBSD.org) Received: from [213.142.183.219] (helo=gahrtop.localhost) by cpanel03.rubas-s03.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1KbcCV-0005yS-7q; Fri, 05 Sep 2008 16:22:15 +0200 Message-ID: <48C14091.4060309@FreeBSD.org> Date: Fri, 05 Sep 2008 16:22:09 +0200 From: Pietro Cerutti Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.16 (X11/20080807) MIME-Version: 1.0 To: bug-followup@FreeBSD.org, gahr@FreeBSD.org, freebsd-acpi@freebsd.org X-Enigmail-Version: 0.95.6 OpenPGP: id=9571F78E; url=http://gahr.ch/pgp/ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel03.rubas-s03.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - FreeBSD.org X-Source: X-Source-Args: X-Source-Dir: Cc: Subject: Re: kern/124223: [acpi] [patch] acpi_battery.c -- Notify user-defined critical level via devd(8) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2008 16:42:31 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 POKE! Anybody interested in reviewing it? - -- Pietro Cerutti gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkjBQI8ACgkQwMJqmJVx946CrQCfY7I1sTPwoPte89cP5zXg5j8S YNUAnjO41f8uzOPFDRR9XAvcEiHcB9ID =ef6A -----END PGP SIGNATURE----- From owner-freebsd-acpi@FreeBSD.ORG Fri Sep 5 16:50:05 2008 Return-Path: Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F7A41065674 for ; Fri, 5 Sep 2008 16:50:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1E1DE8FC14 for ; Fri, 5 Sep 2008 16:50:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m85Go3Qx097108 for ; Fri, 5 Sep 2008 16:50:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m85Go3fu097107; Fri, 5 Sep 2008 16:50:03 GMT (envelope-from gnats) Date: Fri, 5 Sep 2008 16:50:03 GMT Message-Id: <200809051650.m85Go3fu097107@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Pietro Cerutti Cc: Subject: Re: kern/124223: [acpi] [patch] acpi_battery.c -- Notify user-defined critical level via devd(8) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pietro Cerutti List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2008 16:50:05 -0000 The following reply was made to PR kern/124223; it has been noted by GNATS. From: Pietro Cerutti To: bug-followup@FreeBSD.org, gahr@FreeBSD.org, freebsd-acpi@freebsd.org Cc: Subject: Re: kern/124223: [acpi] [patch] acpi_battery.c -- Notify user-defined critical level via devd(8) Date: Fri, 05 Sep 2008 16:22:09 +0200 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 POKE! Anybody interested in reviewing it? - -- Pietro Cerutti gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkjBQI8ACgkQwMJqmJVx946CrQCfY7I1sTPwoPte89cP5zXg5j8S YNUAnjO41f8uzOPFDRR9XAvcEiHcB9ID =ef6A -----END PGP SIGNATURE----- From owner-freebsd-acpi@FreeBSD.ORG Fri Sep 5 17:10:43 2008 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C8941065670 for ; Fri, 5 Sep 2008 17:10:43 +0000 (UTC) (envelope-from nate@root.org) Received: from nlpi087.prodigy.net (nlpi087.prodigy.net [207.115.36.103]) by mx1.freebsd.org (Postfix) with ESMTP id E94058FC19 for ; Fri, 5 Sep 2008 17:10:42 +0000 (UTC) (envelope-from nate@root.org) X-ORBL: [71.139.2.87] Received: from [10.0.5.18] (ppp-71-139-2-87.dsl.snfc21.pacbell.net [71.139.2.87]) by nlpi087.prodigy.net (8.13.8 out.dk.spool/8.13.8) with ESMTP id m85HAeZZ026856; Fri, 5 Sep 2008 12:10:41 -0500 Message-ID: <48C16810.2030003@root.org> Date: Fri, 05 Sep 2008 10:10:40 -0700 From: Nate Lawson User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: Pietro Cerutti References: <48C14091.4060309@FreeBSD.org> In-Reply-To: <48C14091.4060309@FreeBSD.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: kern/124223: [acpi] [patch] acpi_battery.c -- Notify user-defined critical level via devd(8) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2008 17:10:43 -0000 There are a few problems with your approach. Critical status is already reported with a flag when usermode polls for the battery status: > if (sc->bst.state & ACPI_BATT_STAT_CRITICAL) { > if ((sc->flags & ACPI_BATT_STAT_CRITICAL) == 0) { > sc->flags |= ACPI_BATT_STAT_CRITICAL; > device_printf(dev, "critically low charge!\n"); > } > } Since usermode utilities already poll, they can handle that flag or implement their own notion of critical battery level. Why introduce a new kernel thread to do that same polling? Don't common battery status tools that poll (say, xbatt) have their own way to set a critical level? -Nate Pietro Cerutti wrote: > POKE! > > Anybody interested in reviewing it? -- Nate From owner-freebsd-acpi@FreeBSD.ORG Fri Sep 5 17:30:05 2008 Return-Path: Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80258106566B for ; Fri, 5 Sep 2008 17:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6E5E18FC1C for ; Fri, 5 Sep 2008 17:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m85HU5ef000158 for ; Fri, 5 Sep 2008 17:30:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m85HU5q6000155; Fri, 5 Sep 2008 17:30:05 GMT (envelope-from gnats) Date: Fri, 5 Sep 2008 17:30:05 GMT Message-Id: <200809051730.m85HU5q6000155@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Nate Lawson Cc: Subject: Re: kern/124223: [acpi] [patch] acpi_battery.c -- Notify user-defined critical level via devd(8) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Nate Lawson List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2008 17:30:05 -0000 The following reply was made to PR kern/124223; it has been noted by GNATS. From: Nate Lawson To: Pietro Cerutti Cc: bug-followup@FreeBSD.org, freebsd-acpi@FreeBSD.org Subject: Re: kern/124223: [acpi] [patch] acpi_battery.c -- Notify user-defined critical level via devd(8) Date: Fri, 05 Sep 2008 10:10:40 -0700 There are a few problems with your approach. Critical status is already reported with a flag when usermode polls for the battery status: > if (sc->bst.state & ACPI_BATT_STAT_CRITICAL) { > if ((sc->flags & ACPI_BATT_STAT_CRITICAL) == 0) { > sc->flags |= ACPI_BATT_STAT_CRITICAL; > device_printf(dev, "critically low charge!\n"); > } > } Since usermode utilities already poll, they can handle that flag or implement their own notion of critical battery level. Why introduce a new kernel thread to do that same polling? Don't common battery status tools that poll (say, xbatt) have their own way to set a critical level? -Nate Pietro Cerutti wrote: > POKE! > > Anybody interested in reviewing it? -- Nate