From owner-freebsd-acpi@FreeBSD.ORG Sun Mar 20 06:00:52 2005 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 3CE6516A4CE for ; Sun, 20 Mar 2005 06:00:52 +0000 (GMT) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 603B043D53 for ; Sun, 20 Mar 2005 06:00:51 +0000 (GMT) (envelope-from gofda-freebsd-acpi@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1DCtSe-0006W1-Pe for freebsd-acpi@freebsd.org; Sun, 20 Mar 2005 06:58:52 +0100 Received: from rms.gnu-rox.org ([62.212.121.152]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 20 Mar 2005 06:58:52 +0100 Received: from zedek by rms.gnu-rox.org with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 20 Mar 2005 06:58:52 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: freebsd-acpi@freebsd.org To: freebsd-acpi@freebsd.org From: Xavier Maillard Date: Sun, 20 Mar 2005 07:00:30 +0100 Organization: GNU Rox ! Lines: 25 Message-ID: References: <54502.81.84.174.5.1111104772.squirrel@mail.revolutionsp.com> <423A250B.3030208@root.org> <54554.81.84.174.5.1111147042.squirrel@mail.revolutionsp.com> <423B7BFC.2010903@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: rms.gnu-rox.org X-Face: "qG{UC8GPzro#PZ!Jgisuj0]=k10 f#d596CJMPGOGwB'j\^JR2g0']N%L:ylC`?.l8u#JuS#CygUA}avHHVJJ!#ub7CxX#u]g}?z,hQ;c q%v]"[$!BfS Mail-Copies-To: never X-Attribution: zeDek X-Accept-Language: fr-fr, en-en, en-fr User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/22.0.50 (berkeley-unix) Cancel-Lock: sha1:Tj+rok+ePdjlGzfV89dyjiYJ6YU= Sender: news X-Gmane-MailScanner: Found to be clean X-Gmane-MailScanner: Found to be clean X-MailScanner-From: gofda-freebsd-acpi@m.gmane.org X-MailScanner-To: freebsd-acpi@freebsd.org Subject: Re: Acer laptops - smart battery support 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: Sun, 20 Mar 2005 06:00:52 -0000 On 19 Mar 2005, Nate Lawson wrote: > Xavier Maillard wrote: > > On 18 Mar 2005, H. S. wrote: > > > > > Hey, > > > > > > Wow, nice! > > > > > > When you need some testing I'll be available, take your > > > time :-) > > Dumb question: how can I know if my laptop uses smart > > battery ? I got a ACER TravelMate 800 Thank you. > > Yes. Ok, thank you very much. I will RTFM about Smart Battery now ;) -- GnusFR (http://www.gnusfr.org) EmacsFR (http://www.emacsfr.org) .emacs: Because customisation is fun! From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 21 06:50:54 2005 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 08FAF16A4CE; Mon, 21 Mar 2005 06:50:54 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id A58D243D2F; Mon, 21 Mar 2005 06:50:53 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.115] (adsl-64-171-184-204.dsl.snfc21.pacbell.net [64.171.184.204])j2L6oOnr025565; Mon, 21 Mar 2005 01:50:25 -0500 Message-ID: <423E6ECA.7010101@root.org> Date: Sun, 20 Mar 2005 22:50:50 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041205) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <423AD2F3.50602@centtech.com> <423AD585.2010500@centtech.com> <423ADF0D.5090605@centtech.com> In-Reply-To: <423ADF0D.5090605@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: FreeBSD Current Subject: Re: Pentium-M - not recognized? 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, 21 Mar 2005 06:50:54 -0000 Eric Anderson wrote: > Eric Anderson wrote: > >> Eric Anderson wrote: >> >>> I have a Dell Latitude D610 laptop, and my kernel says: >>> >>> CPU claims to support Enhanced Speedstep, but is not recognized. >>> Please update driver or contact the maintainer. >>> cpu_vendor = GenuineIntel msr = 6120e2606000e26, bus_clk = 64 >>> >>> What does that mean to me? How can I fix it? >>> >>> All my various info (full dmesg, acpi dumps, etc) are available here: >>> http://www.googlebit.com/freebsd/ >> > > Looks like I'm in over my head. I think a section for the 750 needs to > be added, but I'm not sure what to add exactly, and I'm now afraid I'll > light my computer on fire if I try. The Intel doc with the specs is here: Ok, I've committed a patch to est.c that should add support of acpi detection of EST parameters. Please give it a try. It probably won't work on all systems since it appears some systems need _PDC support (something I'm working on). Actually, if yours doesn't work with est, it should work with acpi_perf. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 21 07:13:33 2005 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 47C3416A4CE for ; Mon, 21 Mar 2005 07:13:33 +0000 (GMT) Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id B289A43D2D for ; Mon, 21 Mar 2005 07:13:32 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.115] (adsl-64-171-184-204.dsl.snfc21.pacbell.net [64.171.184.204])j2L7DVbq030337; Mon, 21 Mar 2005 02:13:31 -0500 Message-ID: <423E7418.5060609@root.org> Date: Sun, 20 Mar 2005 23:13:28 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041205) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Oberman References: <20050309192938.23DCB5D07@ptavv.es.net> In-Reply-To: <20050309192938.23DCB5D07@ptavv.es.net> Content-Type: multipart/mixed; boundary="------------040509050201070607060202" cc: acpi@freebsd.org Subject: Re: Issues with powerd 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, 21 Mar 2005 07:13:33 -0000 This is a multi-part message in MIME format. --------------040509050201070607060202 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Kevin Oberman wrote: > I have finally had a little time to play with powerd and I didn't find > adaptive mode worked too well for me on my T30 running a Gnome desktop. > > The effect of running powerd was to move the freq in a rapid sawtooth > dropping quickly to 150 MHz and them jumping back to 1800 and > repeating. If the CPU was busy, the low point of the sawtooth would be > elevated to 300or 600, but the basic pattern was constant oscillation. > > I looked at the source and decided that two things were wrong. > > 1. Dropping to half of the initial CPU speed was to a good choice. The > drop is speed was too quick and it resulted in reducing the number of > CPU performance levels to a small number instead of the 15 that should > be available. > > 2. When the CPU got busier, jumping all the way to full speed was > excessive and would always result in the sawtooth oscillation. > > I modified powerd to increase or decrease cpufreq in single steps instead > of jumping (in either direction) and lowered DEFAULT_ACTIVE_PERCENT to > 75. This results in a system that wanders between 150 and 450 when idle > and climbs to full speed when under load. > > I suspect this is sub-optimal, but I think it's a lot better then the > current operation. I will try to spend some time tweaking the algorithm > a bit to see what makes things run best (for my personal idea of "best". > > Ideally, I'd like to see it stay constant an an idle or constantly > loaded system and I suspect that I will need to add hysteresis to get > there. Please try the attached patch. It delays IDLE_DECAY_COUNT poll cycles before starting the descent to slowest speed. The current value of 4 waits a second. This should slow the "sawtooth" issue. Once it starts the decay, it drops one setting per poll interval. It still jumps immediately to full speed once below 80% idle but I think this will solve your issue. If not, try tweaking IDLE_DECAY_COUNT. -- Nate --------------040509050201070607060202 Content-Type: text/plain; name="powerd.c.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="powerd.c.diff" Index: powerd.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/powerd/powerd.c,v retrieving revision 1.4 diff -u -r1.4 powerd.c --- powerd.c 27 Feb 2005 01:58:49 -0000 1.4 +++ powerd.c 21 Mar 2005 07:10:16 -0000 @@ -46,6 +46,7 @@ #define DEFAULT_ACTIVE_PERCENT 80 #define DEFAULT_IDLE_PERCENT 90 #define DEFAULT_POLL_INTERVAL 500 +#define IDLE_DECAY_COUNT 4 enum modes_t { MODE_MIN, @@ -237,7 +238,7 @@ main(int argc, char * argv[]) { long idle, total; - int curfreq, *freqs, i, numfreqs; + int curfreq, *freqs, i, idle_count, numfreqs; int ch, mode_ac, mode_battery, mode_none, acline, mode, vflag; size_t len; @@ -246,7 +247,7 @@ cpu_running_mark = DEFAULT_ACTIVE_PERCENT; cpu_idle_mark = DEFAULT_IDLE_PERCENT; poll_ival = DEFAULT_POLL_INTERVAL; - vflag = 0; + vflag = idle_count = 0; apm_fd = -1; while ((ch = getopt(argc, argv, "a:b:i:n:p:r:v")) != EOF) @@ -380,11 +381,13 @@ /* * If we're idle less than the active mark, jump the CPU to * its fastest speed if we're not there yet. If we're idle - * more than the idle mark, drop down to the first setting - * that is half the current speed (exponential backoff). + * more than the idle mark, drop down to the next lower + * setting after a short delay to be sure we're really idle. */ - if (idle < (total * cpu_running_mark) / 100 && - curfreq < freqs[0]) { + if (idle < (total * cpu_running_mark) / 100) { + idle_count = 0; + if (curfreq == freqs[0]) + continue; if (vflag) { printf("idle time < %d%%, increasing clock" " speed from %d MHz to %d MHz\n", @@ -395,8 +398,11 @@ freqs[0]); } else if (idle > (total * cpu_idle_mark) / 100 && curfreq > freqs[numfreqs - 1]) { + if (++idle_count < IDLE_DECAY_COUNT) + continue; + for (i = 0; i < numfreqs - 1; i++) { - if (freqs[i] <= curfreq / 2) + if (freqs[i] < curfreq) break; } if (vflag) { --------------040509050201070607060202-- From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 21 11:01:21 2005 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 1118B16A4CF for ; Mon, 21 Mar 2005 11:01:21 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E30EB43D5F for ; Mon, 21 Mar 2005 11:01:20 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j2LB1KsD013453 for ; Mon, 21 Mar 2005 11:01:20 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j2LB1Jbr013447 for freebsd-acpi@freebsd.org; Mon, 21 Mar 2005 11:01:19 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 21 Mar 2005 11:01:19 GMT Message-Id: <200503211101.j2LB1Jbr013447@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, 21 Mar 2005 11:01:21 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- 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 10 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 o [2004/11/11] i386/73822 acpi acpi / thermal support o [2004/11/21] kern/74215 acpi [request] add ACPI headers to /usr/includ 8 problems total. From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 22 04:03:34 2005 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 1257F16A4CE; Tue, 22 Mar 2005 04:03:34 +0000 (GMT) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D30443D31; Tue, 22 Mar 2005 04:03:33 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.22] (andersonbox2.centtech.com [192.168.42.22]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j2M43V3i063949; Mon, 21 Mar 2005 22:03:32 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <423F9904.2060800@centtech.com> Date: Mon, 21 Mar 2005 22:03:16 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <423AD2F3.50602@centtech.com> <423AD585.2010500@centtech.com> <423ADF0D.5090605@centtech.com> <423E6ECA.7010101@root.org> In-Reply-To: <423E6ECA.7010101@root.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/778/Mon Mar 21 04:48:43 2005 on mh1.centtech.com X-Virus-Status: Clean cc: freebsd-acpi@freebsd.org cc: FreeBSD Current Subject: Re: Pentium-M - not recognized? 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, 22 Mar 2005 04:03:34 -0000 Nate Lawson wrote: > Eric Anderson wrote: > >> Eric Anderson wrote: >> >>> Eric Anderson wrote: >>> >>>> I have a Dell Latitude D610 laptop, and my kernel says: >>>> >>>> CPU claims to support Enhanced Speedstep, but is not recognized. >>>> Please update driver or contact the maintainer. >>>> cpu_vendor = GenuineIntel msr = 6120e2606000e26, bus_clk = 64 >>>> >>>> What does that mean to me? How can I fix it? >>>> >>>> All my various info (full dmesg, acpi dumps, etc) are available here: >>>> http://www.googlebit.com/freebsd/ >>> >>> >> >> Looks like I'm in over my head. I think a section for the 750 needs >> to be added, but I'm not sure what to add exactly, and I'm now afraid >> I'll light my computer on fire if I try. The Intel doc with the specs >> is here: > > > Ok, I've committed a patch to est.c that should add support of acpi > detection of EST parameters. Please give it a try. It probably won't > work on all systems since it appears some systems need _PDC support > (something I'm working on). Actually, if yours doesn't work with est, > it should work with acpi_perf. > Rebuilt everything, and I'm not certain anything is different. Latest output is at the URL above. As a side note - when this laptop goes from AC to battery, the machine hangs for 10 seconds. From battery to AC, there is no hang. I think it might be some kind of interrupt storm (USB?). Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology I have seen the future and it is just like the present, only longer. ------------------------------------------------------------------------ From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 22 04:53:36 2005 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 0E89116A4CE; Tue, 22 Mar 2005 04:53:36 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AF3443D53; Tue, 22 Mar 2005 04:53:35 +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 j2M4rTZj026179 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 21 Mar 2005 20:53:30 -0800 Message-ID: <423FA4BB.4090002@root.org> Date: Mon, 21 Mar 2005 20:53:15 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <423AD2F3.50602@centtech.com> <423AD585.2010500@centtech.com> <423ADF0D.5090605@centtech.com> <423E6ECA.7010101@root.org> <423F9904.2060800@centtech.com> In-Reply-To: <423F9904.2060800@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: FreeBSD Current Subject: Re: Pentium-M - not recognized? 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, 22 Mar 2005 04:53:36 -0000 Eric Anderson wrote: > Nate Lawson wrote: > >> Eric Anderson wrote: >> >>> Eric Anderson wrote: >>> >>>> Eric Anderson wrote: >>>> >>>>> I have a Dell Latitude D610 laptop, and my kernel says: >>>>> >>>>> CPU claims to support Enhanced Speedstep, but is not recognized. >>>>> Please update driver or contact the maintainer. >>>>> cpu_vendor = GenuineIntel msr = 6120e2606000e26, bus_clk = 64 >>>>> >>>>> What does that mean to me? How can I fix it? >>>>> >>>>> All my various info (full dmesg, acpi dumps, etc) are available here: >>>>> http://www.googlebit.com/freebsd/ >> >> Ok, I've committed a patch to est.c that should add support of acpi >> detection of EST parameters. Please give it a try. It probably won't >> work on all systems since it appears some systems need _PDC support >> (something I'm working on). Actually, if yours doesn't work with est, >> it should work with acpi_perf. >> > > Rebuilt everything, and I'm not certain anything is different. Latest > output is at the URL above. > As a side note - when this laptop goes from AC to battery, the machine > hangs for 10 seconds. From battery to AC, there is no hang. I think it > might be some kind of interrupt storm (USB?). No idea, probably the EC timing out. I don't understand why acpi_perf doesn't attach on your system. Have you added a hint to disable it? Can you boot without cpufreq.ko loaded and see if you get an acpi_perf0? -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 22 23:21:28 2005 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 6C93916A4CE for ; Tue, 22 Mar 2005 23:21:28 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id E74AE43D53 for ; Tue, 22 Mar 2005 23:21:27 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Tue, 22 Mar 2005 15:21:27 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 13B5C5D07; Tue, 22 Mar 2005 15:21:27 -0800 (PST) X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Nate Lawson In-reply-to: Your message of "Wed, 09 Mar 2005 12:21:13 PST." <422F5AB9.7000605@root.org> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-20432722760" Date: Tue, 22 Mar 2005 15:21:27 -0800 From: "Kevin Oberman" Message-Id: <20050322232127.13B5C5D07@ptavv.es.net> cc: acpi@freebsd.org Subject: Re: Issues with powerd 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, 22 Mar 2005 23:21:28 -0000 This is a multipart MIME message. --==_Exmh_-20432722760 Content-Type: text/plain; charset=us-ascii Nate, Sorry about the BL. It's a real pain. I recently found that my home system is on it, too, because it's in the heavily bot infested Comcast space. I'll check and see if I can get root.org white-listed. Just to let you know that I have not fallen off the face of the earth. Real life has pretty much eaten up all of my time to paly with this. I have continued to refine the existing powerd, but I think it really needs a bit more context to work ideally. The first issue is the difference between a system with only a couple of speed settings and one that enables a large number of settings, typically 8 or more. When only a small number of settings are present, they are probably widely spaced and all fast enough to be useful. When there are a lot of settings, they are tightly spaced and the slowest may be too slow to have practical use. At 150 MHz, my system is pretty useless. More importantly, the tight spacing with the only a 10% range in utilization makes powerd unstable. When the system drops to 150 MHz while idling, even the slightest demand for CPU will increase the load to 20% and trigger an increase in speed. The standard powerd code will increase CPU speed to the maximum, the system will drop to well under 10% utilization, the the CPU speed will start dropping. With the step so closely spaced, it will invariably reach the point where the utilization on even an "idle" system exceeds 20% and it pops back to maximum. Your latest patch really only helps a bit. The sawtooth is still there, but does move more slowly. The down-side is that it never gets very slow, so the battery dies too quickly. It now oscillates between 1800 and 750 MHz even when nothing is happening on the system. My last patch tried increasing the speed one "notch" at a time. This typically resulted in the system ratcheting between 300, 225, and 150 MHz when "idle", but it did not respond as well when it got really busy as it took several seconds (about 7) to reach full speed. Not really acceptable. I then tried doubling the speed every time an increase was called for. This was better, but tended to cause the machine to spend too much time at higher speeds than was really needed. None the less, this algorithm combined with a 150 ms polling interval is not too bad. Even the step at a time works pretty well at the 150 ms polling rate, though, so I'm not sure which is best. I still have problems setting -r to 80, though. I see things run much better if I change it to 75. My next attempt will be to make the speed-up exponential so that the idle (or near idle) system will not see the CPU speed bumped much. This forces me to have a history. My first attempt (when I get a few minuted) will be to bump up the speed by one notch the first time the CPU gets busy, then by 2 and then by 4 and 8. This will increase the speed to max in .75 seconds but I hope will keep it at the lowest two speeds when the system is "idle". Then I will try setting -r back to 80 to help on I/O issues. There also needs to be a powercontrol capability. You really want to be able to set a few things like force a fixed speed and adjust thresholds on a running daemon. When I play mp3s when traveling, I want the system to run just fast enough that the mp3 don't break up. If the system thinks that means 80% busy (20% idle), that's fine. This is possible by adjusting the -i and -r values, I think. But the values used would be rather odd looking. Also when traveling, I often want to REALLY make the battery last, so I never want the CPU to increase about some maximum speed (probably fairly low), so I want to set freq_max to about 900 MHz or even less. Let the CPU rest when it's idle, but never let it use much power even when doing The papers were interesting, but I can't help but wonder where the point of diminishing returns will hit. The papers talk about disk drives where spin up/down takes a VERY long time. The idea of changing CPU clocking based on the same principles sounds reasonable, but getting code that is tight enough to do it efficiently certainly looks to be difficult. Even though the time to switch may be below a quantum, I know that a significant part of the time a process frees the CPU due to I/O or other synchronization before the end of a quantum and I suspect this needs to be taken into account. On the other hand, a good predictive algorithm would be a possibility, although I am not confident that one is possible. (Then again, branch prediction seemed impossible not too long ago.) -- 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 --==_Exmh_-20432722760 Content-Type: text/plain ; name="powerd.c.diff.fast"; charset=us-ascii Content-Description: powerd.c.diff.fast Content-Disposition: attachment; filename="powerd.c.diff.fast" --- powerd.c.orig Sat Feb 26 17:58:49 2005 +++ powerd.c Tue Mar 22 14:10:10 2005 @@ -43,7 +43,7 @@ #include #include -#define DEFAULT_ACTIVE_PERCENT 80 +#define DEFAULT_ACTIVE_PERCENT 75 #define DEFAULT_IDLE_PERCENT 90 #define DEFAULT_POLL_INTERVAL 500 @@ -379,24 +379,28 @@ /* * If we're idle less than the active mark, jump the CPU to - * its fastest speed if we're not there yet. If we're idle + * the next faster speed if we're not there yet. If we're idle * more than the idle mark, drop down to the first setting * that is half the current speed (exponential backoff). */ if (idle < (total * cpu_running_mark) / 100 && - curfreq < freqs[0]) { + curfreq < freqs[0]) { + for (i = (numfreqs - 1); i > 0; i--) { + if (freqs[i] >= (curfreq * 2)) + break; + } if (vflag) { printf("idle time < %d%%, increasing clock" " speed from %d MHz to %d MHz\n", - cpu_running_mark, curfreq, freqs[0]); + cpu_running_mark, curfreq, freqs[i]); } - if (set_freq(freqs[0])) + if (set_freq(freqs[i])) err(1, "error setting CPU frequency %d", - freqs[0]); + freqs[i]); } else if (idle > (total * cpu_idle_mark) / 100 && curfreq > freqs[numfreqs - 1]) { for (i = 0; i < numfreqs - 1; i++) { - if (freqs[i] <= curfreq / 2) + if (freqs[i] < curfreq) break; } if (vflag) { --==_Exmh_-20432722760-- From owner-freebsd-acpi@FreeBSD.ORG Wed Mar 23 12:30:26 2005 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 E6D4A16A4CE for ; Wed, 23 Mar 2005 12:30:26 +0000 (GMT) Received: from relay1.telegraph.co.uk (relay1.telegraph.co.uk [193.115.165.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id C084D43D1F for ; Wed, 23 Mar 2005 12:30:25 +0000 (GMT) (envelope-from viruschk@telegraph.co.uk) Received: from email-srv-b.telegraph.co.uk ([193.130.188.92]) j2NCUOtV029898 for ; Wed, 23 Mar 2005 12:30:24 GMT Received: from email-srv-b.telegraph.co.uk (localhost [127.0.0.1]) j2NCUNUH023969 for ; Wed, 23 Mar 2005 12:30:23 GMT Received: from localhost (iscan@localhost)j2NCUJRX023967 for ; Wed, 23 Mar 2005 12:30:23 GMT Message-Id: <200503231230.j2NCUJRX023967@email-srv-b.telegraph.co.uk> X-Authentication-Warning: email-srv-b.telegraph.co.uk: iscan owned process doing -bs From: viruschk@telegraph.co.uk To: freebsd-acpi@freebsd.org Date: Wed, 23 Mar 2005 12:30:23 -0000 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Virus Alert 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, 23 Mar 2005 12:30:27 -0000 The mail message (file: email-body) you sent to contains a virus. (on email-srv-b) From owner-freebsd-acpi@FreeBSD.ORG Wed Mar 23 12:30:27 2005 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 BA9BB16A4CE for ; Wed, 23 Mar 2005 12:30:27 +0000 (GMT) Received: from relay1.telegraph.co.uk (relay1.telegraph.co.uk [193.115.165.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4FAC43D39 for ; Wed, 23 Mar 2005 12:30:26 +0000 (GMT) (envelope-from viruschk@telegraph.co.uk) Received: from email-srv-b.telegraph.co.uk ([193.130.188.92]) j2NCUPtV029902 for ; Wed, 23 Mar 2005 12:30:26 GMT Received: from email-srv-b.telegraph.co.uk (localhost [127.0.0.1]) j2NCUPUH023977 for ; Wed, 23 Mar 2005 12:30:25 GMT Received: from localhost (iscan@localhost)j2NCUPeU023976 for ; Wed, 23 Mar 2005 12:30:25 GMT Message-Id: <200503231230.j2NCUPeU023976@email-srv-b.telegraph.co.uk> X-Authentication-Warning: email-srv-b.telegraph.co.uk: iscan owned process doing -bs From: viruschk@telegraph.co.uk To: freebsd-acpi@freebsd.org Date: Wed, 23 Mar 2005 12:30:25 -0000 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Virus Alert 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, 23 Mar 2005 12:30:27 -0000 The mail message (file: message.scr) you sent to contains a virus. (on email-srv-b) From owner-freebsd-acpi@FreeBSD.ORG Thu Mar 24 01:00:13 2005 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 284A816A4CE; Thu, 24 Mar 2005 01:00:13 +0000 (GMT) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5D4643D1D; Thu, 24 Mar 2005 01:00:11 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.22] (andersonbox2.centtech.com [192.168.42.22]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j2O104gm087393; Wed, 23 Mar 2005 19:00:08 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <42421103.4030709@centtech.com> Date: Wed, 23 Mar 2005 18:59:47 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050210 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <423AD2F3.50602@centtech.com> <423AD585.2010500@centtech.com> <423ADF0D.5090605@centtech.com> <423E6ECA.7010101@root.org> <423F9904.2060800@centtech.com> <423FA4BB.4090002@root.org> In-Reply-To: <423FA4BB.4090002@root.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/781/Wed Mar 23 05:58:42 2005 on mh1.centtech.com X-Virus-Status: Clean cc: freebsd-acpi@freebsd.org cc: FreeBSD Current Subject: Re: Pentium-M - not recognized? 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, 24 Mar 2005 01:00:13 -0000 Nate Lawson wrote: > Eric Anderson wrote: > >> Nate Lawson wrote: >> >>> Eric Anderson wrote: >>> >>>> Eric Anderson wrote: >>>> >>>>> Eric Anderson wrote: >>>>> >>>>>> I have a Dell Latitude D610 laptop, and my kernel says: >>>>>> >>>>>> CPU claims to support Enhanced Speedstep, but is not recognized. >>>>>> Please update driver or contact the maintainer. >>>>>> cpu_vendor = GenuineIntel msr = 6120e2606000e26, bus_clk = 64 >>>>>> >>>>>> What does that mean to me? How can I fix it? >>>>>> >>>>>> All my various info (full dmesg, acpi dumps, etc) are available here: >>>>>> http://www.googlebit.com/freebsd/ >>> >>> >>> Ok, I've committed a patch to est.c that should add support of acpi >>> detection of EST parameters. Please give it a try. It probably >>> won't work on all systems since it appears some systems need _PDC >>> support (something I'm working on). Actually, if yours doesn't work >>> with est, it should work with acpi_perf. >>> >> >> Rebuilt everything, and I'm not certain anything is different. Latest >> output is at the URL above. As a side note - when this laptop goes >> from AC to battery, the machine hangs for 10 seconds. From battery to >> AC, there is no hang. I think it might be some kind of interrupt >> storm (USB?). > > > No idea, probably the EC timing out. > > I don't understand why acpi_perf doesn't attach on your system. Have > you added a hint to disable it? Can you boot without cpufreq.ko loaded > and see if you get an acpi_perf0? I haven't changed any of the hints at all. I booted without cpufreq loaded, and the only thing I really noticed was that the p4tcc stuff disappeared from my dmesg. I may have missed some other things (it was early, my brain was foggy, etc). The one thing I did notice (hard not to), is when I unplugged the AC from the laptop, the machine locked up and didn't come back, not even when I plugged AC back in. On that note - I did some experimenting, and watching systat -vmstat 1 showed my interrupts jumping from ~1000 on ath0 to over 25000 during the ~10 hang when going from AC->battery mode. I disabled the minipci slot in the BIOS, and no longer had the interrupt storm (but no wireless too). I didn't have this issue on 5.3-STABLE for sure, and I *think* I didn't have it on -CURRENT from early Feb. This might be a new change in Sam's code. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology I have seen the future and it is just like the present, only longer. ------------------------------------------------------------------------ From owner-freebsd-acpi@FreeBSD.ORG Thu Mar 24 14:04:18 2005 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 921B916A4CE for ; Thu, 24 Mar 2005 14:04:18 +0000 (GMT) Received: from rogue.ncsl.nist.gov (rogue.ncsl.nist.gov [129.6.101.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19AFD43D48 for ; Thu, 24 Mar 2005 14:04:18 +0000 (GMT) (envelope-from ian.soboroff@nist.gov) Received: from rogue.ncsl.nist.gov.nist.gov (localhost.localdomain [127.0.0.1]) by rogue.ncsl.nist.gov (8.12.11/8.12.11) with ESMTP id j2OE4HVH015134 for ; Thu, 24 Mar 2005 09:04:17 -0500 From: Ian Soboroff To: freebsd-acpi@freebsd.org References: <200503181150.02355.mistry.7@osu.edu> Date: Thu, 24 Mar 2005 09:04:17 -0500 In-Reply-To: <200503181150.02355.mistry.7@osu.edu> (Anish Mistry's message of "Fri, 18 Mar 2005 11:49:53 -0500") Message-ID: <9cfzmwtdtsu.fsf@rogue.ncsl.nist.gov> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Suspend power drain problems 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, 24 Mar 2005 14:04:18 -0000 Anish Mistry writes: > I've posted about this before, but now all the power management acpi > code seems to be imported and I've got a bit of time to test things > so I'll ask again. My Fujitsu P2110 is able to suspend and resume > correctly and has been able to do it for quite some time now :). > The problem is that the battery drains abnormally fast verses when I > have it suspended in Windows 2000. I'm using the acpi_video DPMS > patch that helps significantly, but after a day the battery is still > fully drained, where as with Windows it only dropped a few percent. > I've got hw.pci.do_powerstate=1 set so I'm assuming the default power > management for pci devices is working, but this doesn't seem to help > my system. To that end what can I do to debug this problem and tell > what devices aren't being shutoff and are draining the power? I also have the same laptop (and the same problem) and am willing to test fixes! I first noticed this when I switched the laptop from Linux, where I used to suspend with APM. When Anish helped me get ACPI suspend to work, I noticed that the battery drains much more quickly while suspended under FreeBSD than under APM suspend from Linux. (I can't compare to ACPI suspend under Linux, I was never able to get that work...) Ian From owner-freebsd-acpi@FreeBSD.ORG Thu Mar 24 20:45:07 2005 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 CCA5216A4CE for ; Thu, 24 Mar 2005 20:45:07 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70B5743D2D for ; Thu, 24 Mar 2005 20:45:07 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id C9AD1ACC71; Thu, 24 Mar 2005 21:45:05 +0100 (CET) Date: Thu, 24 Mar 2005 21:45:05 +0100 From: Pawel Jakub Dawidek To: acpi@FreeBSD.org Message-ID: <20050324204505.GD591@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hiFLGGPPrqiESHj5" Content-Disposition: inline User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 Subject: acpi_asus(4) small issue. 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, 24 Mar 2005 20:45:07 -0000 --hiFLGGPPrqiESHj5 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. I found that acpi_asus shows garbage in place of driver description. It is caused by using device_set_desc() for not-const strings, instead of device_set_desc_copy(). This patch fixes this issue for me: http://people.freebsd.org/~pjd/patches/acpi_asus.c.patch If there are no objections, I'll commit it. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --hiFLGGPPrqiESHj5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFCQybRForvXbEpPzQRAm3RAKCRqKJ7GK5NUesaJlcZ5w6/JsjXLACgzOWW MAJpQf0XtjwkkWqvkNeFSE0= =nN1J -----END PGP SIGNATURE----- --hiFLGGPPrqiESHj5-- From owner-freebsd-acpi@FreeBSD.ORG Fri Mar 25 19:11:24 2005 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 8E27016A4CE for ; Fri, 25 Mar 2005 19:11:24 +0000 (GMT) Received: from gw01.mail.saunalahti.fi (gw01.mail.saunalahti.fi [195.197.172.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0BAF43D2F for ; Fri, 25 Mar 2005 19:11:22 +0000 (GMT) (envelope-from juho.vuori@kepa.fi) Received: from [85.76.115.253] (ZYMKDCLII.dsl.saunalahti.fi [85.76.115.253]) by gw01.mail.saunalahti.fi (Postfix) with ESMTP id 7058BDDDA0 for ; Fri, 25 Mar 2005 21:11:19 +0200 (EET) Message-ID: <42446256.5090702@kepa.fi> Date: Fri, 25 Mar 2005 21:11:18 +0200 From: Juho Vuori User-Agent: Mozilla Thunderbird 1.0 (X11/20050316) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ACPI_MAX_THREADS 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, 25 Mar 2005 19:11:24 -0000 Are there any drawbacks on defining ACPI_MAX_THREADS=1 on a casual laptop? I've got a system that hangs for a while when it's temperature changes over _ACx limits, but limitting ACPI_MAX_THREADS to 1 makes the problem almost disappear. This far I haven't noticed any problems with the setting, but I'm just trying to figure out the possibilities... Juho Vuori From owner-freebsd-acpi@FreeBSD.ORG Sat Mar 26 17:32:31 2005 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 6EA1116A4CE for ; Sat, 26 Mar 2005 17:32:31 +0000 (GMT) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC34C43D49 for ; Sat, 26 Mar 2005 17:32:30 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.51] (adsl-64-171-184-204.dsl.snfc21.pacbell.net [64.171.184.204])j2QHWR4H000968; Sat, 26 Mar 2005 12:32:27 -0500 Message-ID: <42459CAA.2090802@root.org> Date: Sat, 26 Mar 2005 09:32:26 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041205) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Juho Vuori References: <42446256.5090702@kepa.fi> In-Reply-To: <42446256.5090702@kepa.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: ACPI_MAX_THREADS 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, 26 Mar 2005 17:32:31 -0000 Juho Vuori wrote: > > Are there any drawbacks on defining ACPI_MAX_THREADS=1 on a casual > laptop? I've got a system that hangs for a while when it's temperature > changes over _ACx limits, but limitting ACPI_MAX_THREADS to 1 makes the > problem almost disappear. This far I haven't noticed any problems with > the setting, but I'm just trying to figure out the possibilities... Interesting. Can you try setting this at the loader prompt, both with and without your ACPI_MAX_THREADS=1 change and see if it helps? set hw.acpi.serialize_methods="1" -- Nate