From owner-freebsd-acpi@FreeBSD.ORG Thu Jan 1 16:26:28 2009 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 D4342106566C for ; Thu, 1 Jan 2009 16:26:28 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.248]) by mx1.freebsd.org (Postfix) with ESMTP id 89B588FC18 for ; Thu, 1 Jan 2009 16:26:28 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: by an-out-0708.google.com with SMTP id c2so2184756anc.13 for ; Thu, 01 Jan 2009 08:26:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=8ryTTrEdp8a+Kkz+MUKyZ6drqo8a6tTdX2V/iX3ya9c=; b=qeON/S2HgH7qIeqzDpLMNG4718tpjaWsvnInZQYQphCZXj3Uyf+VihGtIVpXWxsflL dpJyvoCNF1C0f6KotOI9v13nushXhVdRWJkN9/mr8qIDpyB+99mgLYAjPCOPKImGdFrk ZQKZPfbcLxvMXllOSOAXsHwQNsUnASyihuptk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=GUqnXhzecIhVSWk0I/IkPyFDm6Sw8orlxO4xhxxG1oIIL97HLp+Ga1iYLiAmWXoAZi QllDdhDWaU95WXWY4mCciQnXkEqHVtSAuPuYFOVIITOcAgBP19yo2GTPxe4sAP7x8+ON p06zBr617L3IQiMmBoP4UcxEKsyNrqJY3wSWc= Received: by 10.100.6.16 with SMTP id 16mr9435397anf.108.1230825728731; Thu, 01 Jan 2009 08:02:08 -0800 (PST) Received: from ?10.0.3.231? (pool-70-111-173-38.nwrk.east.verizon.net [70.111.173.38]) by mx.google.com with ESMTPS id b7sm24321079ana.11.2009.01.01.08.02.07 (version=SSLv3 cipher=RC4-MD5); Thu, 01 Jan 2009 08:02:08 -0800 (PST) From: "Alexandre \"Sunny\" Kovalenko" To: "J.R. Oldroyd" In-Reply-To: <20081230185743.12fd1c3a@avera> References: <20081230185743.12fd1c3a@avera> Content-Type: text/plain; charset=utf-8 Date: Thu, 01 Jan 2009 11:01:53 -0500 Message-Id: <1230825713.1182.10.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-acpi@freebsd.org Subject: Re: ACPI issues on Averatec 3250 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jan 2009 16:26:29 -0000 On Tue, 2008-12-30 at 18:57 -0500, J.R. Oldroyd wrote: > I have just put 7-stable on an Averatec 3250HX laptop. Three things > connected with ACPI do not work as they should. > [skip] > 2. Thermal Zone > The thermal zone reporting is not working. > From the boot info: > acpi_tz0: on acpi0 > But sysctl info: > hw.acpi.thermal.min_runtime: 0 > hw.acpi.thermal.polling_rate: 10 > hw.acpi.thermal.user_override: 0 > hw.acpi.thermal.tz0.temperature: 0.0C > hw.acpi.thermal.tz0.active: -1 > hw.acpi.thermal.tz0.passive_cooling: 1 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: 90.0C > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 110.0C > hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 > hw.acpi.thermal.tz0._TC1: 2 > hw.acpi.thermal.tz0._TC2: 4 > hw.acpi.thermal.tz0._TSP: 30 > About four years ago I have cobbled together thermal zones for Averatec 3150H. Quick look at you ASL shows that they still adjust fan speed using RTEP() function, which, in turn, gets called from (off all places) _PSV. The trick is to break RTEP() into pieces at different temperature levels, create fan devices and plug them into proper _ACx. I still have modified ASL laying around, but no longer have access to the laptop to make a diff with the original. If you are interested, I can send you ASL off list -- it should not be that hard to follow, especially if you keep thermal chapter of the ACPI spec close at hand (it is about 13 pages long). Let me know. -- Alexandre "Sunny" Kovalenko (Олександр Коваленко) From owner-freebsd-acpi@FreeBSD.ORG Thu Jan 1 17:09:55 2009 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 C31EA1065673 for ; Thu, 1 Jan 2009 17:09:55 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.246]) by mx1.freebsd.org (Postfix) with ESMTP id 728BB8FC18 for ; Thu, 1 Jan 2009 17:09:55 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: by an-out-0708.google.com with SMTP id c2so2187686anc.13 for ; Thu, 01 Jan 2009 09:09:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=Tebr4ZsOTD9m3whlyC1jCDJoruMxQMx4oMTmm8eYgBM=; b=AV8ChoyIG1Sqk35JM/FajPnvXqqRtmlg0+V0MDCyYc72nMfdiAHiTpTohXi2Ikqlda VxTQpZ84ooJvWsCFRT4L5XfVZOFuY47A24Cv5fbYWLpxYmRH+hxMx7SL/YnJZzIAnF17 Uro7kp37shpZ8Csbynz+h1eFAos+dcaVl2KiM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=Gs2doVCw7e3kUEaJHFCNAiXuG135DtXYF0XLzHWoElsiqTM3lGRR0pnmaZFjyRZtfO +reqwOPtgA23Y2+Rmn36j8+HCjg3wmbznMoR6E1ZKlXlwN0gmBSqfELP6U1fgUfwpQLM hEmskLbx5O7kvoJnbtLT2rlZgkKT+/LVKWDQU= Received: by 10.100.178.9 with SMTP id a9mr9474405anf.59.1230829794839; Thu, 01 Jan 2009 09:09:54 -0800 (PST) Received: from ?10.0.3.231? (pool-70-111-173-38.nwrk.east.verizon.net [70.111.173.38]) by mx.google.com with ESMTPS id b37sm22444174ana.10.2009.01.01.09.09.53 (version=SSLv3 cipher=RC4-MD5); Thu, 01 Jan 2009 09:09:54 -0800 (PST) From: "Alexandre \"Sunny\" Kovalenko" To: Ian Smith In-Reply-To: <20081228124345.D51566@sola.nimnet.asn.au> References: <20081221233822.7E92545020@ptavv.es.net> <49500088.2080609@bigfoot.com> <7d6fde3d0812221315s4d03e15dw4b84679b98a6308f@mail.gmail.com> <49534F10.7040305@bigfoot.com> <7d6fde3d0812261912r1d5abd6cic1513f11cc59f1c5@mail.gmail.com> <20081227160941.I29108@sola.nimnet.asn.au> <1230388519.1270.1.camel@RabbitsDen> <20081228124345.D51566@sola.nimnet.asn.au> Content-Type: text/plain; charset=utf-8 Date: Thu, 01 Jan 2009 12:09:39 -0500 Message-Id: <1230829779.1182.17.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: acpi Subject: Re: Problem 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: Thu, 01 Jan 2009 17:09:56 -0000 On Sun, 2008-12-28 at 13:20 +1100, Ian Smith wrote: > On Sat, 27 Dec 2008, Alexandre "Sunny" Kovalenko wrote: > > On Sat, 2008-12-27 at 17:13 +1100, Ian Smith wrote: > > > On Fri, 26 Dec 2008, Garrett Cooper wrote: > > > > On Thu, Dec 25, 2008 at 1:14 AM, David van Kuijk wrote: > > > [..] > > > > >> Look into the following sysctls: > > > > >> > > > > >> hw.acpi.cpu.cx_lowest > > > > >> hw.acpi.cpu.cx_highest > > > > >> > > > > > > > > > > I tried to find out what I can do with those sysctls. > > > > > hw.acpi.cpu.cx_highest is not available on my system. > > > > > > I don't think it exists; C1 state is always available AFAIK. > > > > > > > > hw.acpi.cpu.cx_lowest is available and can be set. Are you suggesting I > > > > > should set it to C2 or C3??? > > > > > > Give it a try. Setting it to C3 won't hurt, whether it's used or not. > > > Actually it just might (hurt that is). See below for the discussion. > > > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=0+2482 > > +/usr/local/www/db/text/2008/freebsd-acpi/20081109.freebsd-acpi > > Thanks. Yes that was indeed an interesting discussion. FWIW, I find > that interface awkward, without threading. For me it's easier from: > http://lists.freebsd.org/pipermail/freebsd-acpi/2008-November/005182.html > > Could I then safely say, setting it to C2 won't hurt? It is hard to generalize. I am using: RabbitsDen# sysctl dev.cpu.1.cx_lowest=C3 dev.cpu.1.cx_lowest: C2 -> C3 RabbitsDen# sysctl dev.cpu | grep cx dev.cpu.0.cx_supported: C1/1 C2/1 C3/57 dev.cpu.0.cx_lowest: C2 dev.cpu.0.cx_usage: 0.00% 100.00% 0.00% dev.cpu.1.cx_supported: C1/1 C2/1 C3/57 dev.cpu.1.cx_lowest: C3 dev.cpu.1.cx_usage: 0.00% 30.43% 69.56% without any obvious ill effects. Whether having C3 on one of the cores is makes any difference in power consumption or heat dissipation, I do not know. I also do not know whether there are machines out there which would exhibit odd behavior with C2 set. As usual, YMMV. -- Alexandre "Sunny" Kovalenko (Олександр Коваленко) From owner-freebsd-acpi@FreeBSD.ORG Fri Jan 2 17:06:57 2009 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 3389C1065670 for ; Fri, 2 Jan 2009 17:06:57 +0000 (UTC) (envelope-from cokane@FreeBSD.org) Received: from mail-out1.fuse.net (mail-out1.fuse.net [216.68.8.175]) by mx1.freebsd.org (Postfix) with ESMTP id E5A778FC21 for ; Fri, 2 Jan 2009 17:06:56 +0000 (UTC) (envelope-from cokane@FreeBSD.org) X-CNFS-Analysis: v=1.0 c=1 a=scPTdAk-8dwA:10 a=ITL-bk1Uq2MA:10 a=LkYvsgB9u1MH7Ao0BLhsLg==:17 a=2CI21kIDZ0sT2DbAtOgA:9 a=mydRwWTdTgv0aGc0MXoA:7 a=nguO5mvbI8eiTynQsNMSPP_Y_U0A:4 a=LY0hPdMaydYA:10 a=IbrloX19zc8ysH39tTsA:9 a=hnxAGN43zMUaNmcqUUSD13BEg70A:4 a=rPt6xJ-oxjAA:10 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Received: from [74.215.227.9] ([74.215.227.9:50918] helo=discordia) by mail-out1.fuse.net (ecelerity 2.1.1.22 r(17669)) with ESMTP id 95/FC-28972-1A94E594 for ; Fri, 02 Jan 2009 12:06:56 -0500 Received: by discordia (Postfix, from userid 103) id 9C6EC1DB2FA; Fri, 2 Jan 2009 12:06:41 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.1.8-gr1 (2007-02-13) on discordia X-Spam-Level: X-Spam-Status: No, score=-4.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.8-gr1 Received: from [172.31.1.6] (unknown [172.31.1.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by discordia (Postfix) with ESMTP id 314EA1DB2F9; Fri, 2 Jan 2009 12:06:30 -0500 (EST) From: Coleman Kane To: Nate Lawson In-Reply-To: <495A7309.2060400@root.org> References: <1230564886.2280.11.camel@localhost> <4958F887.2010203@root.org> <1230579699.2386.5.camel@localhost> <49593036.4030306@root.org> <1230662172.1702.2.camel@localhost> <495A7309.2060400@root.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-smiwB2JwJOk/B1JP4nNe" Organization: FreeBSD Project Date: Fri, 02 Jan 2009 12:06:32 -0500 Message-Id: <1230915992.4841.4.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Cc: freebsd-acpi@FreeBSD.org Subject: Re: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 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, 02 Jan 2009 17:06:57 -0000 --=-smiwB2JwJOk/B1JP4nNe Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2008-12-30 at 11:14 -0800, Nate Lawson wrote: > Coleman Kane wrote: > > On Mon, 2008-12-29 at 12:16 -0800, Nate Lawson wrote: > >> Coleman Kane wrote: > >>> On Mon, 2008-12-29 at 08:19 -0800, Nate Lawson wrote: > >>>> Coleman Kane wrote: > >>>>> I've been testing Jung-uk Kim's recent amd64 suspend patch on my HP > >>>>> notebook, and it seems to be very close to working well. > >>>>> > >>>>> The notebook goes into S3 state properly, but when it comes back ou= t it > >>>>> seems that the hardware is left in a bad state. I cannot attach my > >>>>> if_bge and if_ndis network drivers after a resume. > >>>> Dump the pci config register states for those devices both before an= d > >>>> after the resume. Where the bits differ is probably where you'll fin= d > >>>> the problem. > >>>> > >>>> Example to read 256 bytes: > >>>> pciconf -r pci0:4:0 0:256 > >>>> > >>> Tried that, and I also tried to use pciconf -w to set the registers t= o > >>> the initial state of the hardware before if_bge is loaded. I still ge= t > >>> the following messages when I attempt to reload the kld after the > >>> resume, followed by a failed attach: > >>> > >>> bge0: mem 0xd0000000-0= xd000ffff irq 16 at device 0.0 on pci16 > >>> bge0: firmware handshake timed out, found 0x4b657654 > >>> bge0: firmware handshake timed out, found 0x4b657654 > >>> bge0: RX CPU self-diagnostics failed! > >>> bge0: chip initialization failed > >>> device_attach: bge0 attach returned 6 > >>> > >>> Anyone have success with S3 on amd64 or i386 with if_bge cards? > >> Did you post the register states before and after? > >> > > Attached are the before and after snapshots of the device's PCI registe= r > > space. I need to track down a good table to mate these with. In this > > case, I didn't unload the driver, as the if_bge driver is supposed to b= e > > able to properly handle suspend/resume now. > >=20 > > These are dumps of the whole 256-byte register space, using: > > pciconf -r -b pci0:16:0:0 0:0x100 >=20 > Great. So far in FreeBSD, anything after the first 64 bytes is the > driver's responsibility. According to your dump, that is where all the > differences are. >=20 So, my guess is that the bge_suspend and bge_resume methods in the bge driver need some tweaking to support my hardware (the BCM5754/5787) when it comes out of resume... Any pointers on who I might be able to work on this with? --=20 Coleman Kane --=-smiwB2JwJOk/B1JP4nNe Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkleSZIACgkQcMSxQcXat5fotgCdGddLhKJYzUyLZ7nI0sdWRjZ1 1bYAn0S/4aoUBdb27ULORSKgn5A8A8rX =Gup7 -----END PGP SIGNATURE----- --=-smiwB2JwJOk/B1JP4nNe-- From owner-freebsd-acpi@FreeBSD.ORG Fri Jan 2 19:09:11 2009 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 F223D1065670 for ; Fri, 2 Jan 2009 19:09:10 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.247]) by mx1.freebsd.org (Postfix) with ESMTP id 9F4748FC1A for ; Fri, 2 Jan 2009 19:09:10 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by an-out-0708.google.com with SMTP id c2so2303419anc.13 for ; Fri, 02 Jan 2009 11:09:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:x-mailer :mime-version:subject:date:cc; bh=v4ygFvTVW7Sc2izxdPLwJ6rB5HonLIkUB6oMgfBhC78=; b=X9Db6saF4TEarw2XLB2OsQ4a2k8sPACS4DseoeB6qmEhA/RuwNR+3bi2BzErHNMHVm t4HfUDRZi4CZdiAqHt1+M3Gy9qfOFnJIPQTCFL8o7dNLwof3w0RUe7YcNvhl6h7J3hyz 0nCNgQwq+ucw59JQSP1PsrT75PR8cDHrwrSfs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date:cc; b=Krabmjw7uRgmwL/Gpst4MqiIkwy0hpSAg0GUfHEsHg4UjcPGJCX2yjnUMiz+qWLGwl VWyQO4dgBThme3Zbf8Ix0Hvjvrhf0VpnARy65JbwD2/LWfDPfufN23FdvRG0sZ0pQ69B qgF7yfuVDQEv52tFgU9i8VrumzAfmUfx9lWqE= Received: by 10.100.128.2 with SMTP id a2mr9946682and.93.1230923349789; Fri, 02 Jan 2009 11:09:09 -0800 (PST) Received: from ?10.88.62.48? ([32.156.137.7]) by mx.google.com with ESMTPS id b29sm31961512ana.33.2009.01.02.11.09.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 02 Jan 2009 11:09:08 -0800 (PST) References: <1230564886.2280.11.camel@localhost> <4958F887.2010203@root.org> <1230579699.2386.5.camel@localhost> <49593036.4030306@root.org> <1230662172.1702.2.camel@localhost> <495A7309.2060400@root.org> <1230915992.4841.4.camel@localhost> Message-Id: <3533670F-754C-40C8-B76A-0C17333E7569@gmail.com> From: Garrett Cooper To: Coleman Kane In-Reply-To: <1230915992.4841.4.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (5G77) Mime-Version: 1.0 (iPhone Mail 5G77) Date: Fri, 2 Jan 2009 11:08:56 -0800 Cc: "freebsd-acpi@FreeBSD.org" Subject: Re: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 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, 02 Jan 2009 19:09:11 -0000 On Jan 2, 2009, at 9:06, Coleman Kane wrote: > On Tue, 2008-12-30 at 11:14 -0800, Nate Lawson wrote: >> Coleman Kane wrote: >>> On Mon, 2008-12-29 at 12:16 -0800, Nate Lawson wrote: >>>> Coleman Kane wrote: >>>>> On Mon, 2008-12-29 at 08:19 -0800, Nate Lawson wrote: >>>>>> Coleman Kane wrote: >>>>>>> I've been testing Jung-uk Kim's recent amd64 suspend patch on >>>>>>> my HP >>>>>>> notebook, and it seems to be very close to working well. >>>>>>> >>>>>>> The notebook goes into S3 state properly, but when it comes >>>>>>> back out it >>>>>>> seems that the hardware is left in a bad state. I cannot >>>>>>> attach my >>>>>>> if_bge and if_ndis network drivers after a resume. >>>>>> Dump the pci config register states for those devices both >>>>>> before and >>>>>> after the resume. Where the bits differ is probably where >>>>>> you'll find >>>>>> the problem. >>>>>> >>>>>> Example to read 256 bytes: >>>>>> pciconf -r pci0:4:0 0:256 >>>>>> >>>>> Tried that, and I also tried to use pciconf -w to set the >>>>> registers to >>>>> the initial state of the hardware before if_bge is loaded. I >>>>> still get >>>>> the following messages when I attempt to reload the kld after the >>>>> resume, followed by a failed attach: >>>>> >>>>> bge0: mem >>>>> 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 >>>>> bge0: firmware handshake timed out, found 0x4b657654 >>>>> bge0: firmware handshake timed out, found 0x4b657654 >>>>> bge0: RX CPU self-diagnostics failed! >>>>> bge0: chip initialization failed >>>>> device_attach: bge0 attach returned 6 >>>>> >>>>> Anyone have success with S3 on amd64 or i386 with if_bge cards? >>>> Did you post the register states before and after? >>>> >>> Attached are the before and after snapshots of the device's PCI >>> register >>> space. I need to track down a good table to mate these with. In this >>> case, I didn't unload the driver, as the if_bge driver is supposed >>> to be >>> able to properly handle suspend/resume now. >>> >>> These are dumps of the whole 256-byte register space, using: >>> pciconf -r -b pci0:16:0:0 0:0x100 >> >> Great. So far in FreeBSD, anything after the first 64 bytes is the >> driver's responsibility. According to your dump, that is where all >> the >> differences are. >> > > So, my guess is that the bge_suspend and bge_resume methods in the bge > driver need some tweaking to support my hardware (the BCM5754/5787) > when > it comes out of resume... > > Any pointers on who I might be able to work on this with? Dumb observation: driver maintainer? -Garrett From owner-freebsd-acpi@FreeBSD.ORG Fri Jan 2 19:23:46 2009 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 DC5C4106566B for ; Fri, 2 Jan 2009 19:23:46 +0000 (UTC) (envelope-from cokane@FreeBSD.org) Received: from mail-out1.fuse.net (mail-out1.fuse.net [216.68.8.175]) by mx1.freebsd.org (Postfix) with ESMTP id 95E428FC17 for ; Fri, 2 Jan 2009 19:23:46 +0000 (UTC) (envelope-from cokane@FreeBSD.org) X-CNFS-Analysis: v=1.0 c=1 a=scPTdAk-8dwA:10 a=ITL-bk1Uq2MA:10 a=LkYvsgB9u1MH7Ao0BLhsLg==:17 a=dWW-95MeczEfff130YAA:9 a=IlRXZro6xXz2S144_qIA:7 a=N8-C98bUJkIWJcpjIL102q3Qe8QA:4 a=SV7veod9ZcQA:10 a=LY0hPdMaydYA:10 a=KfFdPdi3WSKCQeZbFY8A:9 a=vojBmfgcI3rjrUG7SvHd8Lb-F_gA:4 a=rPt6xJ-oxjAA:10 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Received: from [74.215.227.9] ([74.215.227.9:50756] helo=discordia) by mail-out1.fuse.net (ecelerity 2.1.1.22 r(17669)) with ESMTP id AB/68-28972-5B96E594 for ; Fri, 02 Jan 2009 14:23:46 -0500 Received: by discordia (Postfix, from userid 103) id CA09D35A7D4; Fri, 2 Jan 2009 14:23:33 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.1.8-gr1 (2007-02-13) on discordia X-Spam-Level: X-Spam-Status: No, score=-4.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.8-gr1 Received: from [172.31.1.6] (unknown [172.31.1.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by discordia (Postfix) with ESMTP id 021AE1DB2F9; Fri, 2 Jan 2009 14:23:26 -0500 (EST) From: Coleman Kane To: Garrett Cooper In-Reply-To: <3533670F-754C-40C8-B76A-0C17333E7569@gmail.com> References: <1230564886.2280.11.camel@localhost> <4958F887.2010203@root.org> <1230579699.2386.5.camel@localhost> <49593036.4030306@root.org> <1230662172.1702.2.camel@localhost> <495A7309.2060400@root.org> <1230915992.4841.4.camel@localhost> <3533670F-754C-40C8-B76A-0C17333E7569@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-+fo6Cvou/B7JDhX/Hk/0" Organization: FreeBSD Project Date: Fri, 02 Jan 2009 14:23:32 -0500 Message-Id: <1230924212.4841.7.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Cc: "freebsd-acpi@FreeBSD.org" Subject: Re: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 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, 02 Jan 2009 19:23:47 -0000 --=-+fo6Cvou/B7JDhX/Hk/0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2009-01-02 at 11:08 -0800, Garrett Cooper wrote: > On Jan 2, 2009, at 9:06, Coleman Kane wrote: >=20 > > On Tue, 2008-12-30 at 11:14 -0800, Nate Lawson wrote: > >> Coleman Kane wrote: > >>> On Mon, 2008-12-29 at 12:16 -0800, Nate Lawson wrote: > >>>> Coleman Kane wrote: > >>>>> On Mon, 2008-12-29 at 08:19 -0800, Nate Lawson wrote: > >>>>>> Coleman Kane wrote: > >>>>>>> I've been testing Jung-uk Kim's recent amd64 suspend patch on =20 > >>>>>>> my HP > >>>>>>> notebook, and it seems to be very close to working well. > >>>>>>> > >>>>>>> The notebook goes into S3 state properly, but when it comes =20 > >>>>>>> back out it > >>>>>>> seems that the hardware is left in a bad state. I cannot =20 > >>>>>>> attach my > >>>>>>> if_bge and if_ndis network drivers after a resume. > >>>>>> Dump the pci config register states for those devices both =20 > >>>>>> before and > >>>>>> after the resume. Where the bits differ is probably where =20 > >>>>>> you'll find > >>>>>> the problem. > >>>>>> > >>>>>> Example to read 256 bytes: > >>>>>> pciconf -r pci0:4:0 0:256 > >>>>>> > >>>>> Tried that, and I also tried to use pciconf -w to set the =20 > >>>>> registers to > >>>>> the initial state of the hardware before if_bge is loaded. I =20 > >>>>> still get > >>>>> the following messages when I attempt to reload the kld after the > >>>>> resume, followed by a failed attach: > >>>>> > >>>>> bge0: mem =20 > >>>>> 0xd0000000-0xd000ffff irq 16 at device 0.0 on pci16 > >>>>> bge0: firmware handshake timed out, found 0x4b657654 > >>>>> bge0: firmware handshake timed out, found 0x4b657654 > >>>>> bge0: RX CPU self-diagnostics failed! > >>>>> bge0: chip initialization failed > >>>>> device_attach: bge0 attach returned 6 > >>>>> > >>>>> Anyone have success with S3 on amd64 or i386 with if_bge cards? > >>>> Did you post the register states before and after? > >>>> > >>> Attached are the before and after snapshots of the device's PCI =20 > >>> register > >>> space. I need to track down a good table to mate these with. In this > >>> case, I didn't unload the driver, as the if_bge driver is supposed =20 > >>> to be > >>> able to properly handle suspend/resume now. > >>> > >>> These are dumps of the whole 256-byte register space, using: > >>> pciconf -r -b pci0:16:0:0 0:0x100 > >> > >> Great. So far in FreeBSD, anything after the first 64 bytes is the > >> driver's responsibility. According to your dump, that is where all =20 > >> the > >> differences are. > >> > > > > So, my guess is that the bge_suspend and bge_resume methods in the bge > > driver need some tweaking to support my hardware (the BCM5754/5787) =20 > > when > > it comes out of resume... > > > > Any pointers on who I might be able to work on this with? >=20 > Dumb observation: driver maintainer? > -Garrett Yeah, bge isn't listed in MAINTAINERS so I was hoping someone here might know. The original author is wpaul, but marius, jhb, and others have been working on it since then... I'll just ping them and try to find out who's today's contact on bge. --=20 Coleman Kane --=-+fo6Cvou/B7JDhX/Hk/0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkleaa4ACgkQcMSxQcXat5cdKACfTP+YtWHz8KVvPFpN8z1E4xzX ihAAnjXn3SgBzZL1TM4++o02hjCPcGE2 =rbLO -----END PGP SIGNATURE----- --=-+fo6Cvou/B7JDhX/Hk/0-- From owner-freebsd-acpi@FreeBSD.ORG Fri Jan 2 20:34:39 2009 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 818221065670 for ; Fri, 2 Jan 2009 20:34:39 +0000 (UTC) (envelope-from cokane@FreeBSD.org) Received: from mail-out1.fuse.net (mail-out1.fuse.net [216.68.8.175]) by mx1.freebsd.org (Postfix) with ESMTP id 3B4258FC0C for ; Fri, 2 Jan 2009 20:34:38 +0000 (UTC) (envelope-from cokane@FreeBSD.org) X-CNFS-Analysis: v=1.0 c=1 a=scPTdAk-8dwA:10 a=ITL-bk1Uq2MA:10 a=LkYvsgB9u1MH7Ao0BLhsLg==:17 a=nO88W1uug3fyoC0eCuEA:9 a=YegcanVqxk52qpsGpNYA:7 a=QcktCFiHzbWctO0lFdBr5e9yAYkA:4 a=LY0hPdMaydYA:10 a=01REpkqBiSr-XUyVoTUA:9 a=5ksFTYtDYioYvCVB8wUN01YTcpoA:4 a=rPt6xJ-oxjAA:10 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Received: from [74.215.227.9] ([74.215.227.9:50768] helo=discordia) by mail-out1.fuse.net (ecelerity 2.1.1.22 r(17669)) with ESMTP id 77/91-28972-E5A7E594 for ; Fri, 02 Jan 2009 15:34:38 -0500 Received: by discordia (Postfix, from userid 103) id 663AA35A7D4; Fri, 2 Jan 2009 15:34:38 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.1.8-gr1 (2007-02-13) on discordia X-Spam-Level: X-Spam-Status: No, score=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.8-gr1 Received: from [172.31.1.6] (unknown [172.31.1.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by discordia (Postfix) with ESMTP id B3DDB1DB2F9; Fri, 2 Jan 2009 15:34:31 -0500 (EST) From: Coleman Kane To: Nate Lawson In-Reply-To: <1230915992.4841.4.camel@localhost> References: <1230564886.2280.11.camel@localhost> <4958F887.2010203@root.org> <1230579699.2386.5.camel@localhost> <49593036.4030306@root.org> <1230662172.1702.2.camel@localhost> <495A7309.2060400@root.org> <1230915992.4841.4.camel@localhost> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-0MKT+9/XASj1pGGjEHli" Organization: FreeBSD Project Date: Fri, 02 Jan 2009 15:34:37 -0500 Message-Id: <1230928477.4841.21.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Cc: freebsd-acpi@FreeBSD.org Subject: Re: amd64 S3 patch on HP 6715b: NICs won't work after resume from S3 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, 02 Jan 2009 20:34:39 -0000 --=-0MKT+9/XASj1pGGjEHli Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2009-01-02 at 12:06 -0500, Coleman Kane wrote: > On Tue, 2008-12-30 at 11:14 -0800, Nate Lawson wrote: > > Coleman Kane wrote: > > > On Mon, 2008-12-29 at 12:16 -0800, Nate Lawson wrote: > > >> Coleman Kane wrote: > > >>> On Mon, 2008-12-29 at 08:19 -0800, Nate Lawson wrote: > > >>>> Coleman Kane wrote: > > >>>>> I've been testing Jung-uk Kim's recent amd64 suspend patch on my = HP > > >>>>> notebook, and it seems to be very close to working well. > > >>>>> > > >>>>> The notebook goes into S3 state properly, but when it comes back = out it > > >>>>> seems that the hardware is left in a bad state. I cannot attach m= y > > >>>>> if_bge and if_ndis network drivers after a resume. > > >>>> Dump the pci config register states for those devices both before = and > > >>>> after the resume. Where the bits differ is probably where you'll f= ind > > >>>> the problem. > > >>>> > > >>>> Example to read 256 bytes: > > >>>> pciconf -r pci0:4:0 0:256 > > >>>> > > >>> Tried that, and I also tried to use pciconf -w to set the registers= to > > >>> the initial state of the hardware before if_bge is loaded. I still = get > > >>> the following messages when I attempt to reload the kld after the > > >>> resume, followed by a failed attach: > > >>> > > >>> bge0: mem 0xd0000000= -0xd000ffff irq 16 at device 0.0 on pci16 > > >>> bge0: firmware handshake timed out, found 0x4b657654 > > >>> bge0: firmware handshake timed out, found 0x4b657654 > > >>> bge0: RX CPU self-diagnostics failed! > > >>> bge0: chip initialization failed > > >>> device_attach: bge0 attach returned 6 > > >>> > > >>> Anyone have success with S3 on amd64 or i386 with if_bge cards? > > >> Did you post the register states before and after? > > >> > > > Attached are the before and after snapshots of the device's PCI regis= ter > > > space. I need to track down a good table to mate these with. In this > > > case, I didn't unload the driver, as the if_bge driver is supposed to= be > > > able to properly handle suspend/resume now. > > >=20 > > > These are dumps of the whole 256-byte register space, using: > > > pciconf -r -b pci0:16:0:0 0:0x100 > >=20 > > Great. So far in FreeBSD, anything after the first 64 bytes is the > > driver's responsibility. According to your dump, that is where all the > > differences are. > >=20 >=20 > So, my guess is that the bge_suspend and bge_resume methods in the bge > driver need some tweaking to support my hardware (the BCM5754/5787) when > it comes out of resume... >=20 > Any pointers on who I might be able to work on this with? >=20 I did find that one register that does get trashed by the resume is the high-part of the MSI Address Register (0x5C, BGE_PCI_MSI_ADDR_HIGH from sys/dev/bge/if_bgereg.h). Am I correct in assuming that the PCI 2.2 register addresses in the middle of if_bgereg.h correlate to the addresses in these reg dumps? --=20 Coleman Kane --=-0MKT+9/XASj1pGGjEHli Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkleeloACgkQcMSxQcXat5cpSQCcDM0OF7zTWXz0eShSTj0ug9qE N4wAn3uSqBQPrSN7wUCBdPb38Ex3JiMI =ldRV -----END PGP SIGNATURE----- --=-0MKT+9/XASj1pGGjEHli-- From owner-freebsd-acpi@FreeBSD.ORG Sat Jan 3 17:26:26 2009 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 A018C106566B for ; Sat, 3 Jan 2009 17:26:26 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 6D3BC8FC17 for ; Sat, 3 Jan 2009 17:26:26 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LJAGX-0000Di-Kq for freebsd-acpi@freebsd.org; Sat, 03 Jan 2009 09:26:25 -0800 Message-ID: <21267094.post@talk.nabble.com> Date: Sat, 3 Jan 2009 09:26:25 -0800 (PST) From: dvg_lab To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: dvg@tjc.ru Subject: ACPI errors on MSI MegaBook PR300 (aka MS1313) 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: Sat, 03 Jan 2009 17:26:27 -0000 I run amd64 CURRENT from 31 dec 2008, here are errors at boot time Jan 3 13:42:38 dvg-nb kernel: acpi0: on motherboard Jan 3 13:42:38 dvg-nb kernel: acpi0: [ITHREAD] Jan 3 13:42:38 dvg-nb kernel: acpi0: Power Button (fixed) Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [Embedde dControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._S TA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (No de 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [Embedde dControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._S TA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (No de 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [Embedde dControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._S TA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (No de 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [Embedde dControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._S TA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (No de 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [Embedde dControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._S TA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (No de 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [Embedde dControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._S TA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (No de 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (evregion-0427): No handler for Region [EC__] (0xffffff000151b900) [EmbeddedControl] [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (exfldio-0390): Region EmbeddedControl(3) has no handler [20070320] Jan 3 13:42:38 dvg-nb kernel: ACPI Error (psparse-0626): Method parse/execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: ACPI Error (uteval-0309): Method execution failed [\_SB_.PCI0.SBRG.EC__.BAT1._STA] (Node 0xffffff000151a8e0), AE_NOT_EXIST Jan 3 13:42:38 dvg-nb kernel: acpi0: reservation of 0, a0000 (3) failed Jan 3 13:42:38 dvg-nb kernel: acpi0: reservation of 100000, bf700000 (3) failed Jan 3 13:42:38 dvg-nb kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Jan 3 13:42:38 dvg-nb kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 Jan 3 13:42:38 dvg-nb kernel: acpi_ec0: port 0x62,0x66 on acpi0 Jan 3 13:42:38 dvg-nb kernel: acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 from time to time acpi sysctl variables looks buggy hw.acpi.acline: 0 hw.acpi.battery.life: 54 hw.acpi.battery.time: 100 hw.acpi.battery.state: 1 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 the 2nd and the 3d params sometimes sets to 0 or -1, I can't get the dependency. I can't configure kdeutils-klaptopdaemon to shutdown the laptop if batt level less then 5%, it shutdowns the laptop when acpi sysctls gets buggy values. -- View this message in context: http://www.nabble.com/ACPI-errors-on-MSI-MegaBook-PR300-%28aka-MS1313%29-tp21267094p21267094.html Sent from the freebsd-acpi mailing list archive at Nabble.com. From owner-freebsd-acpi@FreeBSD.ORG Sat Jan 3 18:46:05 2009 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 0B8F81065670 for ; Sat, 3 Jan 2009 18:46:05 +0000 (UTC) (envelope-from invite+a2=690a6@facebookmail.com) Received: from vipmx-out.facebook.com (outmail002.sctm.tfbnw.net [204.15.20.237]) by mx1.freebsd.org (Postfix) with ESMTP id E61798FC29 for ; Sat, 3 Jan 2009 18:46:04 +0000 (UTC) (envelope-from invite+a2=690a6@facebookmail.com) Received: from localhost.localdomain ([10.18.255.175]) by vipmx-out.facebook.com [vipemail006.snc1.facebook.com] (8.13.1/8.13.6) with ESMTP id n03Ik4kL030112 for ; Sat, 3 Jan 2009 10:46:04 -0800 X-Facebook: from zuckmail by localhost.localdomain with local (ZuckMail); Date: Sat, 3 Jan 2009 10:46:04 -0800 To: Freebsd-acpi From: Maitri Karuna R Message-ID: <99ed546838f3c5b8aadf77bde8f806ed@localhost.localdomain> X-Priority: 3 X-Mailer: ZuckMail [version 1.00] X-Facebook-Notify: general_invite Errors-To: invite+a2=690a6@facebookmail.com MIME-Version: 1.0 Content-Type: text/plain; charset = "UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Check out my Facebook profile X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Maitri Karuna R List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jan 2009 18:46:05 -0000 Hi Freebsd-acpi, I invited you to join Facebook a while back and wanted to remind you that once you join, we'll be able to connect online, share photos, organize groups and events, and more. Thanks, Maitri To sign up for Facebook, follow the link below: http://www.facebook.com/p.php?i=3D1005079607&k=3D63D2425ZQZYM5BE1Q1VUTV&r