From owner-freebsd-acpi@FreeBSD.ORG Sun Jun 6 05:14:35 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8961516A4CE for ; Sun, 6 Jun 2004 05:14:35 -0700 (PDT) Received: from mx.x123.info (165.Red-80-37-224.pooles.rima-tde.net [80.37.224.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA00A43D58 for ; Sun, 6 Jun 2004 05:14:34 -0700 (PDT) (envelope-from esn@x123.info) Received: by mx.x123.info (Postfix, from userid 80) id 319B8174B4; Sun, 6 Jun 2004 14:14:17 +0200 (CEST) Received: from brawebdproxy2.net.external.hp.com(Horde) with HTTP for ; Sun, 6 Jun 2004 14:14:16 +0200 Message-ID: <20040606141416.jl4ows88osw8c8g8@www.x123.info> X-Priority: 3 (Normal) Date: Sun, 6 Jun 2004 14:14:16 +0200 From: "Sebastian Yepes F. [ESN]" To: freebsd-acpi@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs Subject: Re: ACPI info on Dell i8500 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, 06 Jun 2004 12:14:35 -0000 haves any one successfully put into work the modes S3 or S4 in the Dell Inspiron 8500 I have just rebuilded my kernel and striped all unnecessary stuff usb,pcm,net cards.... S1 Works OK S3 Still Reboots the system S4 Still Hangs the System S5 Works OK Any one working on this issus with this notebook? -- if (Better You Treat Them) { return "Worst You Get Treated"; } Love can kill you like a Hammer or a 220 Kv AC line in the head, but it's the most beautiful and strange sensation, I Just Love, Love ; ) /* www: http://www.x123.info Contect: FingerPrint: esn aT x123.info 0D42 F870 F650 6B86 CA9E esn aT freshpkgsrc.org E199 A57D 3824 F8AA A934 sebastian.yepes aT hp.com */ From owner-freebsd-acpi@FreeBSD.ORG Sun Jun 6 13:06:52 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8B4616A4CE for ; Sun, 6 Jun 2004 13:06:52 -0700 (PDT) Received: from clever.eusc.inter.net (clever.eusc.inter.net [213.73.101.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59A4643D53 for ; Sun, 6 Jun 2004 13:06:52 -0700 (PDT) (envelope-from plexus@snafu.de) Received: from pd9e0e7d2.dip.t-dialin.net ([217.224.231.210] helo=snafu.de) by clever.eusc.inter.net with asmtp (Exim 3.36 #4) id 1BX3us-00002o-00; Sun, 06 Jun 2004 22:06:51 +0200 Message-ID: <40C3795C.4070205@snafu.de> Date: Sun, 06 Jun 2004 22:06:52 +0200 From: "Oliver B. Fischer" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040605 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <40C1F228.8060401@snafu.de> <20040605132007.R60990@root.org> <40C23E60.7010503@snafu.de> <20040605194248.W62622@root.org> In-Reply-To: <20040605194248.W62622@root.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@freebsd.org Subject: Re: Screen stays black after resume X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jun 2004 20:06:52 -0000 Nate Lawson wrote: > Um, safe mode disables ACPI so how can you suspend/resume in safe mode? By pressing Fn + F4. The interesting thing is that the acpi device is not present, so I am not able to use acpiconf -s 3. But as I said, I am able to suspend via Fn + F4. If I suspend the system from the console, I can resume. Regards, Oliver Fischer From owner-freebsd-acpi@FreeBSD.ORG Sun Jun 6 13:47:56 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D20DB16A4D0 for ; Sun, 6 Jun 2004 13:47:56 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 93ECE43D54 for ; Sun, 6 Jun 2004 13:47:56 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 66758 invoked by uid 1000); 6 Jun 2004 20:47:43 -0000 Date: Sun, 6 Jun 2004 13:47:43 -0700 (PDT) From: Nate Lawson To: "Oliver B. Fischer" In-Reply-To: <40C3795C.4070205@snafu.de> Message-ID: <20040606134632.Y66744@root.org> References: <40C1F228.8060401@snafu.de> <20040605132007.R60990@root.org> <40C23E60.7010503@snafu.de> <20040605194248.W62622@root.org> <40C3795C.4070205@snafu.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org Subject: Re: Screen stays black after resume X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jun 2004 20:47:57 -0000 On Sun, 6 Jun 2004, Oliver B. Fischer wrote: > Nate Lawson wrote: > > Um, safe mode disables ACPI so how can you suspend/resume in safe mode? > > By pressing Fn + F4. The interesting thing is that the acpi device is > not present, so I am not able to use acpiconf -s 3. But as I said, I am > able to suspend via Fn + F4. If I suspend the system from the console, I > can resume. That's using SMM mode then. You need "device apm" when ACPI is disabled to properly suspend/resume. Without apm or acpi, you're trusting in the BIOS to do everything for you, which is not supported. -Nate From owner-freebsd-acpi@FreeBSD.ORG Sun Jun 6 13:58:42 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3206D16A4CE for ; Sun, 6 Jun 2004 13:58:42 -0700 (PDT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCED543D2D for ; Sun, 6 Jun 2004 13:58:41 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i56Kw4sJ005715; Sun, 6 Jun 2004 14:58:04 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 06 Jun 2004 14:58:10 -0600 (MDT) Message-Id: <20040606.145810.34371505.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <20040606134632.Y66744@root.org> References: <20040605194248.W62622@root.org> <40C3795C.4070205@snafu.de> <20040606134632.Y66744@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: acpi@freebsd.org Subject: Re: Screen stays black after resume X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jun 2004 20:58:42 -0000 In message: <20040606134632.Y66744@root.org> Nate Lawson writes: : On Sun, 6 Jun 2004, Oliver B. Fischer wrote: : > Nate Lawson wrote: : > > Um, safe mode disables ACPI so how can you suspend/resume in safe mode? : > : > By pressing Fn + F4. The interesting thing is that the acpi device is : > not present, so I am not able to use acpiconf -s 3. But as I said, I am : > able to suspend via Fn + F4. If I suspend the system from the console, I : > can resume. : : That's using SMM mode then. You need "device apm" when ACPI is disabled : to properly suspend/resume. Without apm or acpi, you're trusting in the : BIOS to do everything for you, which is not supported. and in many cases cannot possibly work :-( Warner From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 7 05:10:06 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0E3C16A4CE for ; Mon, 7 Jun 2004 05:10:06 +0000 (GMT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id B045843D49 for ; Mon, 7 Jun 2004 05:10:06 +0000 (GMT) (envelope-from nate@root.org) Received: (qmail 68691 invoked by uid 1000); 7 Jun 2004 05:10:04 -0000 Date: Sun, 6 Jun 2004 22:10:04 -0700 (PDT) From: Nate Lawson To: j.e.drews@att.net In-Reply-To: <060220040117.21540.40BD2ABA0008FE0E000054242160281302FF8C889A8D9BD19AD1@att.net> Message-ID: <20040606215445.R68528@root.org> References: <060220040117.21540.40BD2ABA0008FE0E000054242160281302FF8C889A8D9BD19AD1@att.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org cc: current@freebsd.org Subject: Re: ACPI Error: AE_NO_HARDWARE_RESPONSE 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, 07 Jun 2004 05:10:06 -0000 On Wed, 2 Jun 2004 j.e.drews@att.net wrote: > I made the polling adjustment that you suggested: > sysctl hw.acpi.thermal.polling_rate=1 > > and then ran the script while compiling qt33 and Mozilla at the same time. > the initial reading was at: hw.acpi.thermal.tz0.temperature: 3112 > the high temps were: > hw.acpi.thermal.tz0.temperature: 3242 > hw.acpi.thermal.tz0.temperature: 3252 > > the fan kicked on at 3232. I could not get the error again, even though > I ran the computer under load for quite a while. Ok, thanks for all the debugging info. There are two issues here: --- GEOM: Configure ad0s1f, start 1851564032 length 22418914816 end 24270478847 acpi_ec0: info: new max delay is 75 us acpi_ec0: info: new max delay is 90 us acpi_ec0: info: new max delay is 210 us acpi_ec0: info: new max delay is 805 us acpi_ec0: info: new max delay is 900 us system power profile changed to 'economy' --- 1. Embedded controller read times out during boot. As seen above, during the probe of your flash key, the EC hits higher and higher delays until finally timing out. The issue is that ACPI acquires Giant and so does CAM (which is probing your flash drive). Try booting without your flash key inserted and see if the error goes away. I am working on a patch for ACPI to run Giant-free that should address this. It's almost done. --- POWERRES-0257 [20] acpi_pwr_register_cons: registered power consumer \\_SB_.PCI0.USB7 POWERRES-0350 [19] acpi_pwr_switch_consum: setup to switch \\_SB_.PCI0.USB7 D255 -> D3 POWERRES-0479 [19] acpi_pwr_switch_consum: attempt to set unsupported state D3 pci0: Failed to set ACPI power state D3 on (null): AE_BAD_PARAMETER POWERRES-0257 [20] acpi_pwr_register_cons: registered power consumer \\_SB_.PCI0.MODM POWERRES-0350 [19] acpi_pwr_switch_consum: setup to switch \\_SB_.PCI0.MODM D255 -> D3 POWERRES-0479 [19] acpi_pwr_switch_consum: attempt to set unsupported state D3 pci0: Failed to set ACPI power state D3 on (null): AE_BAD_PARAMETER --- 2. Error messages for power switching consumer. These are harmless but I'll remove them. The power state routines try to power down your USB7 and built-in modem since no driver attached them. However, they don't offer power control via ACPI so the attempt returns a harmless error message. I'll add checks for this. Thanks for the help, Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 7 05:11:25 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48A0116A4CE for ; Mon, 7 Jun 2004 05:11:25 +0000 (GMT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 1581243D4C for ; Mon, 7 Jun 2004 05:11:25 +0000 (GMT) (envelope-from nate@root.org) Received: (qmail 68714 invoked by uid 1000); 7 Jun 2004 05:11:17 -0000 Date: Sun, 6 Jun 2004 22:11:17 -0700 (PDT) From: Nate Lawson To: j.e.drews@att.net In-Reply-To: <20040606215445.R68528@root.org> Message-ID: <20040606221049.X68528@root.org> References: <060220040117.21540.40BD2ABA0008FE0E000054242160281302FF8C889A8D9BD19AD1@att.net> <20040606215445.R68528@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org cc: current@freebsd.org Subject: Re: ACPI Error: AE_NO_HARDWARE_RESPONSE 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, 07 Jun 2004 05:11:25 -0000 On Sun, 6 Jun 2004, Nate Lawson wrote: > On Wed, 2 Jun 2004 j.e.drews@att.net wrote: > > I made the polling adjustment that you suggested: > > sysctl hw.acpi.thermal.polling_rate=1 > > > > and then ran the script while compiling qt33 and Mozilla at the same time. > > the initial reading was at: hw.acpi.thermal.tz0.temperature: 3112 > > the high temps were: > > hw.acpi.thermal.tz0.temperature: 3242 > > hw.acpi.thermal.tz0.temperature: 3252 > > > > the fan kicked on at 3232. I could not get the error again, even though > > I ran the computer under load for quite a while. > > Ok, thanks for all the debugging info. There are two issues here: One more thing -- you're running the Radeon driver. It's likely that would interfere with suspend/resume. But feel free to test. -Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 7 06:09:15 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC2CC16A4CE; Mon, 7 Jun 2004 06:09:15 +0000 (GMT) Received: from mtiwmhc12.worldnet.att.net (mtiwmhc12.worldnet.att.net [204.127.131.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EFC943D4C; Mon, 7 Jun 2004 06:09:15 +0000 (GMT) (envelope-from j.e.drews@att.net) Received: from 204.127.135.57 ([204.127.135.57]) by worldnet.att.net (mtiwmhc12) with SMTP id <2004060706091111200jakk5e>; Mon, 7 Jun 2004 06:09:11 +0000 Received: from [64.105.56.145] by 204.127.135.57; Mon, 07 Jun 2004 06:09:13 +0000 From: j.e.drews@att.net To: Nate Lawson Date: Mon, 07 Jun 2004 06:09:13 +0000 Message-Id: <060720040609.22380.40C406880008851B0000576C21603763169C990A9D0BD20AD206@att.net> X-Mailer: AT&T Message Center Version 1 (May 27 2004) X-Authenticated-Sender: ai5lLmRyZXdzQGF0dC5uZXQ= cc: acpi@freebsd.org cc: current@freebsd.org Subject: Re: ACPI Error: AE_NO_HARDWARE_RESPONSE 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, 07 Jun 2004 06:09:15 -0000 Hi: When I was shutting down I got this output from tty0: evregion-0502: *** Error: Handler for [EmbeddedControl] returned AE_NO_HARDWARE_ RESPONSE **** Exception AE_NO_HARDWARE_RESPONSE during execution of method [\_TZ_.THRM._T MP] (Node 0xc1a777a8) Method Execution Stack: Method [_TMP] executing: 7 # 70 Store (\_SB.PCI0.LPCB.EC0.CTMP, Local1) Local Variables for method [_TMP]: Local0: 0 Local1: 0 Local2: 0 Local3: 0 Local4: 0 Local5: 0 Local6: 0 Local7: 0 Arguments for Method [_TMP]: (0 arguments defined, max concurrency = ff) Arg0: 0 Arg1: 0 Arg2: 0 Arg3: 0 Arg4: 0 Arg5: 0 Arg6: 0 psparse-1303: *** Error: Method execution failed [\_TZ_.THRM._TMP] (Node 0xc1a7 77a8), AE_NO_HARDWARE_RESPONSE I thought I would pass this info along. from: FreeBSD 5.2-CURRENT #0: Sun Jun 6 17:03:51 CDT 2004 > On Wed, 2 Jun 2004 j.e.drews@att.net wrote: > > I made the polling adjustment that you suggested: > > sysctl hw.acpi.thermal.polling_rate=1 > > > > and then ran the script while compiling qt33 and Mozilla at the same time. > > the initial reading was at: hw.acpi.thermal.tz0.temperature: 3112 > > the high temps were: > > hw.acpi.thermal.tz0.temperature: 3242 > > hw.acpi.thermal.tz0.temperature: 3252 > > > > the fan kicked on at 3232. I could not get the error again, even though > > I ran the computer under load for quite a while. > > Ok, thanks for all the debugging info. There are two issues here: > > --- > GEOM: Configure ad0s1f, start 1851564032 length 22418914816 end 24270478847 > acpi_ec0: info: new max delay is 75 us > acpi_ec0: info: new max delay is 90 us > acpi_ec0: info: new max delay is 210 us > acpi_ec0: info: new max delay is 805 us > acpi_ec0: info: new max delay is 900 us > system power profile changed to 'economy' > --- > > 1. Embedded controller read times out during boot. > As seen above, during the probe of your flash key, the EC hits higher and > higher delays until finally timing out. The issue is that ACPI acquires > Giant and so does CAM (which is probing your flash drive). Try booting > without your flash key inserted and see if the error goes away. I am > working on a patch for ACPI to run Giant-free that should address this. > It's almost done. > > --- > POWERRES-0257 [20] acpi_pwr_register_cons: registered power consumer > \\_SB_.PCI0.USB7 > POWERRES-0350 [19] acpi_pwr_switch_consum: setup to switch > \\_SB_.PCI0.USB7 D255 -> D3 > POWERRES-0479 [19] acpi_pwr_switch_consum: attempt to set unsupported state D3 > pci0: Failed to set ACPI power state D3 on (null): AE_BAD_PARAMETER > POWERRES-0257 [20] acpi_pwr_register_cons: registered power consumer > \\_SB_.PCI0.MODM > POWERRES-0350 [19] acpi_pwr_switch_consum: setup to switch > \\_SB_.PCI0.MODM D255 -> D3 > POWERRES-0479 [19] acpi_pwr_switch_consum: attempt to set unsupported state D3 > pci0: Failed to set ACPI power state D3 on (null): AE_BAD_PARAMETER > --- > > 2. Error messages for power switching consumer. > These are harmless but I'll remove them. The power state routines try to > power down your USB7 and built-in modem since no driver attached them. > However, they don't offer power control via ACPI so the attempt returns a > harmless error message. I'll add checks for this. > > Thanks for the help, > Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 7 06:31:38 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDE5916A4CE for ; Mon, 7 Jun 2004 06:31:38 +0000 (GMT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 8C56D43D2D for ; Mon, 7 Jun 2004 06:31:38 +0000 (GMT) (envelope-from nate@root.org) Received: (qmail 69218 invoked by uid 1000); 7 Jun 2004 06:31:34 -0000 Date: Sun, 6 Jun 2004 23:31:34 -0700 (PDT) From: Nate Lawson To: j.e.drews@att.net In-Reply-To: <060720040609.22380.40C406880008851B0000576C21603763169C990A9D0BD20AD206@att.net> Message-ID: <20040606233110.I69215@root.org> References: <060720040609.22380.40C406880008851B0000576C21603763169C990A9D0BD20AD206@att.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org cc: current@freebsd.org Subject: Re: ACPI Error: AE_NO_HARDWARE_RESPONSE 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, 07 Jun 2004 06:31:38 -0000 On Mon, 7 Jun 2004 j.e.drews@att.net wrote: > Hi: > > When I was shutting down I got this output from tty0: > evregion-0502: *** Error: Handler for [EmbeddedControl] returned AE_NO_HARDWARE_ > RESPONSE > > **** Exception AE_NO_HARDWARE_RESPONSE during execution of method [\_TZ_.THRM._T > MP] (Node 0xc1a777a8) > > Method Execution Stack: > Method [_TMP] executing: 7 # 70 Store (\_SB.PCI0.LPCB.EC0.CTMP, Local1) It's the same problem. Giant contention. -Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 7 11:01:56 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32C6B16A4F5 for ; Mon, 7 Jun 2004 11:01:56 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B34C43D41 for ; Mon, 7 Jun 2004 11:01:56 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i57B1uoL043376 for ; Mon, 7 Jun 2004 11:01:56 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i57B1tKT043370 for freebsd-acpi@freebsd.org; Mon, 7 Jun 2004 11:01:55 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 7 Jun 2004 11:01:55 GMT Message-Id: <200406071101.i57B1tKT043370@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, 07 Jun 2004 11:01:56 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/09/10] kern/56659 acpi ACPI trouble on IBM ThinkPad X31 f [2004/01/31] kern/62194 acpi kern/acpi: Unable to map IRQ on device cb 2 problems total. 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/20] kern/55822 acpi No ACPI power off with SMP kernel o [2003/12/17] i386/60317 acpi FreeBSD 5.2rc1 doesn't boot with ACPI ena 3 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/08/11] i386/55473 acpi Mouse broken on some AWARD BIOS with ACPI o [2004/03/17] misc/64365 acpi ACPI problems o [2004/05/28] kern/67309 acpi zzz reboot computer (ACPI S3) 3 problems total. From owner-freebsd-acpi@FreeBSD.ORG Tue Jun 8 03:19:01 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 421C116A4CE for ; Tue, 8 Jun 2004 03:19:01 +0000 (GMT) Received: from imf20aec.mail.bellsouth.net (imf20aec.mail.bellsouth.net [205.152.59.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id B754F43D48 for ; Tue, 8 Jun 2004 03:19:00 +0000 (GMT) (envelope-from xionnon@bellsouth.net) Received: from heavensdevil ([68.19.80.226]) by imf20aec.mail.bellsouth.net SMTP <20040608031856.VUN18130.imf20aec.mail.bellsouth.net@heavensdevil> for ; Mon, 7 Jun 2004 23:18:56 -0400 Message-ID: <000601c44d07$3dc4bd30$6700a8c0@heavensdevil> From: "xionnon" To: Date: Mon, 7 Jun 2004 23:18:16 -0400 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailman-Approved-At: Tue, 08 Jun 2004 04:35:02 +0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: freebsd laptops 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, 08 Jun 2004 03:19:01 -0000 Hi, I found a message board where you said you hacked ASL for thermal = support, can you point me to a site for this? I also have a averatec = 3150H and the constant fan noise is driving me up a wall. Thanks Jonathan From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 10 11:18:50 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E385216A4D0 for ; Thu, 10 Jun 2004 11:18:50 +0000 (GMT) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0736043D39 for ; Thu, 10 Jun 2004 11:18:44 +0000 (GMT) (envelope-from avg@icyb.net.ua) Received: from [212.40.38.87] (oddity.topspin.kiev.ua [212.40.38.87]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA15396 for ; Thu, 10 Jun 2004 14:18:36 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <40C8438C.7050709@icyb.net.ua> Date: Thu, 10 Jun 2004 14:18:36 +0300 From: Andriy Gapon User-Agent: Mozilla Thunderbird 0.6 (X11/20040525) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: kernel trap with ACPI on 4.10-release 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, 10 Jun 2004 11:18:51 -0000 I am aware that ACPI support in stable is more experimental than stable, and almost undocumented, but I tried it out of curiousity anyway, so when I got a reproducable kernel trap I was not suprpised at all. I didn't even want to investigate the problem, but again, out of curiousity I looked at crash dump and seeing that the trap occured in syncronization-related code I decided that it might be of interest/help to ACPI developers/hackers. I can readily provide more debugging information if necessary. IdlePTD at physical address 0x0041f000 initial pcb at physical address 0x00333100 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x70 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0193f30 stack pointer = 0x10:0xc030b6d0 frame pointer = 0x10:0xc030b6f4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty bio cam trap number = 12 panic: page fault syncing disks... done Uptime: 34s dumping to dev #ad/0x20021, offset 295923 dump ata2: resetting devices .. ata2: mask=03 ostat0=50 ostat2=00 ad4: ATAPI 00 00 ata2-slave: ATAPI 00 00 ata2: mask=03 stat0=50 stat1=00 ad4: ATA 01 a5 ata2: devices=01 ad4: success setting PIO4 on generic chip done 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 #0 dumpsys () at /export/src/sys/kern/kern_shutdown.c:487 487 if (dumping++) { (kgdb) bt #0 dumpsys () at /export/src/sys/kern/kern_shutdown.c:487 #1 0xc0190dd8 in boot (howto=256) at /export/src/sys/kern/kern_shutdown.c:316 #2 0xc019120c in poweroff_wait (junk=0xc03037ac, howto=-1070583121) at /export/src/sys/kern/kern_shutdown.c:595 #3 0xc02ac1eb in trap_fatal (frame=0xc030b690, eva=112) at /export/src/sys/i386/i386/trap.c:974 #4 0xc02abea5 in trap_pfault (frame=0xc030b690, usermode=0, eva=112) at /export/src/sys/i386/i386/trap.c:867 #5 0xc02aba7b in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 256, tf_esi = -1058817664, tf_ebp = -1070549260, tf_isp = -1070549316, tf_ebx = 0, tf_edx = 765930, tf_ecx = -1070549208, tf_eax = -1, tf_trapno = 12, tf_err = 0, tf_eip = -1072087248, tf_cs = 8, tf_eflags = 66118, tf_esp = -1058817664, tf_ss = 0}) at /export/src/sys/i386/i386/trap.c:466 #6 0xc0193f30 in tsleep (ident=0xc0e3b980, priority=256, wmesg=0xc02cf8f3 "acsem", timo=0) at /export/src/sys/kern/kern_synch.c:436 #7 0xc015cb13 in AcpiOsWaitSemaphore (Handle=0xc0e3b980, Units=1, Timeout=65535) at /export/src/sys/dev/acpica/Osd/OsdSynch.c:240 #8 0xc014f167 in AcpiUtAcquireMutex (MutexId=0) at /export/src/sys/contrib/dev/acpica/utmisc.c:844 #9 0xc0143fbb in AcpiExEnterInterpreter () at /export/src/sys/contrib/dev/acpica/exutils.c:166 #10 0xc0145de9 in AcpiNsExecuteControlMethod (MethodNode=0xc266d5a0, Params=0x0, ReturnObjDesc=0xc030b790) at /export/src/sys/contrib/dev/acpica/nseval.c:521 #11 0xc0145d84 in AcpiNsEvaluateByHandle (Handle=0xc266d5a0, Params=0x0, ReturnObject=0xc030b814) at /export/src/sys/contrib/dev/acpica/nseval.c:409 #12 0xc0145c55 in AcpiNsEvaluateRelative (Handle=0xc266d5e0, Pathname=0xc030b89c "_AC0", Params=0x0, ReturnObject=0xc030b814) at /export/src/sys/contrib/dev/acpica/nseval.c:225 #13 0xc0147321 in AcpiEvaluateObject (Handle=0xc266d5e0, Pathname=0xc030b89c "_AC0", ExternalParams=0x0, ReturnBuffer=0xc030b83c) at /export/src/sys/contrib/dev/acpica/nsxfeval.c:357 #14 0xc0156081 in acpi_EvaluateInteger (handle=0xc266d5e0, path=0xc030b89c "_AC0", number=0xc266ad30) at /export/src/sys/dev/acpica/acpi.c:1119 #15 0xc015b9c8 in acpi_tz_getparam (sc=0xc266ad00, node=0xc030b89c "_AC0", data=0xc266ad30) at /export/src/sys/dev/acpica/acpi_thermal.c:636 #16 0xc015b273 in acpi_tz_establish (sc=0xc266ad00) at /export/src/sys/dev/acpica/acpi_thermal.c:311 #17 0xc015c8a0 in AcpiOsExecuteQueue (arg=0xc2729e40, pending=1) at /export/src/sys/dev/acpica/Osd/OsdSchedule.c:234 #18 0xc01a004a in taskqueue_run (queue=0xc0e3b9e0) at /export/src/sys/kern/subr_taskqueue.c:186 #19 0xc01a0086 in taskqueue_swi_run () at /export/src/sys/kern/subr_taskqueue.c:202 #20 0xc02a14f0 in splz_swi () (kgdb) fr 6 #6 0xc0193f30 in tsleep (ident=0xc0e3b980, priority=256, wmesg=0xc02cf8f3 "acsem", timo=0) at /export/src/sys/kern/kern_synch.c:436 436 return (0); (kgdb) i loc ident = (void *) 0xc0e3b980 wmesg = 0x0 p = (struct proc *) 0xffffffff s = -1 sig = -1058817664 catch = 256 thandle = {callout = 0x0} (kgdb) fr 7 #7 0xc015cb13 in AcpiOsWaitSemaphore (Handle=0xc0e3b980, Units=1, Timeout=65535) at /export/src/sys/dev/acpica/Osd/OsdSynch.c:240 240 rv = msleep(as, &as->as_mtx, PCATCH, "acsem", tmo); (kgdb) i loc Timeout = 65535 as = (struct acpi_semaphore *) 0xc0e3b980 result = 0 rv = 0 tmo = 0 timeouttv = {tv_sec = 1086868951, tv_usec = 765930} currenttv = {tv_sec = 1086868885, tv_usec = 765930} timelefttv = {tv_sec = -1058817856, tv_usec = 6292480} s = 6292480 -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 10 15:52:49 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F40A316A4CE for ; Thu, 10 Jun 2004 15:52:48 +0000 (GMT) Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.136.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B5DD43D2F for ; Thu, 10 Jun 2004 15:52:48 +0000 (GMT) (envelope-from jfrherve@ing.uc3m.es) Received: from smtp02.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 70F4C27A7B for ; Thu, 10 Jun 2004 17:52:43 +0200 (CEST) Received: from [163.117.139.95] (cimborrio.it.uc3m.es [163.117.139.95]) by smtp02.uc3m.es (Postfix) with ESMTP id 5DDA927937 for ; Thu, 10 Jun 2004 17:52:43 +0200 (CEST) From: Juan Rodriguez Hervella Organization: UC3M To: freebsd-acpi@freebsd.org Date: Thu, 10 Jun 2004 17:52:36 +0200 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200406101752.38184.jfrherve@ing.uc3m.es> Subject: How to use ACPI ? 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, 10 Jun 2004 15:52:49 -0000 Hello, I'm using FreeBSD-4.10-release When I try "acpiconf -s 3", it seems to work, but when I open the screen of the laptop, it is always black and nothing comes up again. What can be the problem ? My laptop is "hp/compaq nx9010" Thanks in advance From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 10 17:25:57 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5915C16A4CE for ; Thu, 10 Jun 2004 17:25:57 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F73043D31 for ; Thu, 10 Jun 2004 17:25:57 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 19290 invoked from network); 10 Jun 2004 17:25:44 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 10 Jun 2004 17:25:44 -0000 Received: from 10.50.41.233 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i5AHPbfC027103; Thu, 10 Jun 2004 13:25:37 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Thu, 10 Jun 2004 13:26:28 -0400 User-Agent: KMail/1.6 References: <200406101752.38184.jfrherve@ing.uc3m.es> In-Reply-To: <200406101752.38184.jfrherve@ing.uc3m.es> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406101326.28511.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: How to use ACPI ? 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, 10 Jun 2004 17:25:57 -0000 On Thursday 10 June 2004 11:52 am, Juan Rodriguez Hervella wrote: > Hello, > > I'm using FreeBSD-4.10-release > > When I try "acpiconf -s 3", it seems to work, > but when I open the screen of the laptop, it is > always black and nothing comes up again. > > What can be the problem ? > > My laptop is "hp/compaq nx9010" > > Thanks in advance You probably have to hit the power button for it to resume. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 10 22:11:54 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF7A216A4CE for ; Thu, 10 Jun 2004 22:11:54 +0000 (GMT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 89D2F43D58 for ; Thu, 10 Jun 2004 22:11:54 +0000 (GMT) (envelope-from nate@root.org) Received: (qmail 95206 invoked by uid 1000); 10 Jun 2004 22:11:46 -0000 Date: Thu, 10 Jun 2004 15:11:46 -0700 (PDT) From: Nate Lawson To: John Baldwin In-Reply-To: <200406101326.28511.jhb@FreeBSD.org> Message-ID: <20040610151105.G95036@root.org> References: <200406101752.38184.jfrherve@ing.uc3m.es> <200406101326.28511.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@FreeBSD.org Subject: Re: How to use ACPI ? 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, 10 Jun 2004 22:11:54 -0000 On Thu, 10 Jun 2004, John Baldwin wrote: > On Thursday 10 June 2004 11:52 am, Juan Rodriguez Hervella wrote: > > Hello, > > > > I'm using FreeBSD-4.10-release 4.x is not well-supported for ACPI so suspend/resume is not likely to work. Use apm or wait for 5.3-RELEASE. > > When I try "acpiconf -s 3", it seems to work, > > but when I open the screen of the laptop, it is > > always black and nothing comes up again. > > > > What can be the problem ? > > > > My laptop is "hp/compaq nx9010" -Nate From owner-freebsd-acpi@FreeBSD.ORG Fri Jun 11 07:19:22 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D474416A4CE; Fri, 11 Jun 2004 07:19:22 +0000 (GMT) Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.136.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E02743D45; Fri, 11 Jun 2004 07:19:22 +0000 (GMT) (envelope-from jrh@it.uc3m.es) Received: from smtp01.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 3062E39FEE; Fri, 11 Jun 2004 09:19:21 +0200 (CEST) Received: from [163.117.139.95] (cimborrio.it.uc3m.es [163.117.139.95]) by smtp01.uc3m.es (Postfix) with ESMTP id 1BF7E39FE1; Fri, 11 Jun 2004 09:19:21 +0200 (CEST) From: Juan Rodriguez Hervella Organization: UC3M To: freebsd-acpi@freebsd.org Date: Fri, 11 Jun 2004 09:19:15 +0200 User-Agent: KMail/1.6.2 References: <200406101752.38184.jfrherve@ing.uc3m.es> <200406101326.28511.jhb@FreeBSD.org> <20040610151105.G95036@root.org> In-Reply-To: <20040610151105.G95036@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406110919.15801.jrh@it.uc3m.es> Subject: Re: How to use ACPI ? 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, 11 Jun 2004 07:19:22 -0000 On Friday 11 June 2004 00:11, Nate Lawson wrote: > On Thu, 10 Jun 2004, John Baldwin wrote: > > On Thursday 10 June 2004 11:52 am, Juan Rodriguez Hervella wrote: > > > Hello, > > > > > > I'm using FreeBSD-4.10-release > > 4.x is not well-supported for ACPI so suspend/resume is not likely to > work. Use apm or wait for 5.3-RELEASE. I think APM doesn't work either (the same problem, it doesn't come up again...). One question, can I test all these things with the laptop plugged into the dockstation ? I've just visited this page: http://demira.shopkeeper.de/~sascha/nx9005/ which describes a laptop very similar to mine (my laptop is nx9010 and the only difference AFAIK is that mine is Intel Pentium IV processor and it doesn't have serial port...) The thing is that in that page it's said that ACPI doesn't resume.... I've tried to push the power buttom, and nothing happens...if I try hard to push it, it reboots :-) sigh, thanks anyway... > > > When I try "acpiconf -s 3", it seems to work, > > > but when I open the screen of the laptop, it is > > > always black and nothing comes up again. > > > > > > What can be the problem ? > > > > > > My laptop is "hp/compaq nx9010" > > -Nate > _______________________________________________ > 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" -- ****** JFRH ****** World War Three can be averted by adherence to a strictly enforced dress code! From owner-freebsd-acpi@FreeBSD.ORG Fri Jun 11 07:20:05 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E037116A4CE for ; Fri, 11 Jun 2004 07:20:05 +0000 (GMT) Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.136.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEF4F43D2F for ; Fri, 11 Jun 2004 07:20:02 +0000 (GMT) (envelope-from jfrherve@ing.uc3m.es) Received: from smtp03.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id B8B972A1FF for ; Fri, 11 Jun 2004 09:19:58 +0200 (CEST) Received: from [163.117.139.95] (cimborrio.it.uc3m.es [163.117.139.95]) by smtp03.uc3m.es (Postfix) with ESMTP id 6E27F29E02 for ; Fri, 11 Jun 2004 09:19:58 +0200 (CEST) From: Juan Rodriguez Hervella Organization: UC3M To: freebsd-acpi@freebsd.org Date: Fri, 11 Jun 2004 09:19:53 +0200 User-Agent: KMail/1.6.2 References: <200406101752.38184.jfrherve@ing.uc3m.es> <200406101326.28511.jhb@FreeBSD.org> <20040610151105.G95036@root.org> In-Reply-To: <20040610151105.G95036@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406110919.53373.jfrherve@ing.uc3m.es> Subject: Re: How to use ACPI ? 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, 11 Jun 2004 07:20:06 -0000 On Friday 11 June 2004 00:11, Nate Lawson wrote: > On Thu, 10 Jun 2004, John Baldwin wrote: > > On Thursday 10 June 2004 11:52 am, Juan Rodriguez Hervella wrote: > > > Hello, > > > > > > I'm using FreeBSD-4.10-release > > 4.x is not well-supported for ACPI so suspend/resume is not likely to > work. Use apm or wait for 5.3-RELEASE. I think APM doesn't work either (the same problem, it doesn't come up again...). One question, can I test all these things with the laptop plugged into the dockstation ? I've just visited this page: http://demira.shopkeeper.de/~sascha/nx9005/ which describes a laptop very similar to mine (my laptop is nx9010 and the only difference AFAIK is that mine is Intel Pentium IV processor and it doesn't have serial port...) The thing is that in that page it's said that ACPI doesn't resume.... I've tried to push the power buttom, and nothing happens...if I try hard to push it, it reboots :-) sigh, thanks anyway... > > > When I try "acpiconf -s 3", it seems to work, > > > but when I open the screen of the laptop, it is > > > always black and nothing comes up again. > > > > > > What can be the problem ? > > > > > > My laptop is "hp/compaq nx9010" > > -Nate > _______________________________________________ > 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" -- ****** JFRH ****** World War Three can be averted by adherence to a strictly enforced dress code! From owner-freebsd-acpi@FreeBSD.ORG Fri Jun 11 12:21:12 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AFC116A4CE for ; Fri, 11 Jun 2004 12:21:12 +0000 (GMT) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4BF143D49 for ; Fri, 11 Jun 2004 12:21:06 +0000 (GMT) (envelope-from avg@icyb.net.ua) Received: from [212.40.38.87] (oddity.topspin.kiev.ua [212.40.38.87]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA26984 for ; Fri, 11 Jun 2004 15:20:57 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <40C9A3A9.6010508@icyb.net.ua> Date: Fri, 11 Jun 2004 15:20:57 +0300 From: Andriy Gapon User-Agent: Mozilla Thunderbird 0.6 (X11/20040525) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-acpi@freebsd.org References: <40C8438C.7050709@icyb.net.ua> In-Reply-To: <40C8438C.7050709@icyb.net.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: kernel trap with ACPI on 4.10-release 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, 11 Jun 2004 12:21:12 -0000 Out of curiosity again I looked through the sources and became very surprised that acpi can work for anybody using 4.10-RELEASE :-) Of course, I am not sure I got everything right. ... > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x70 > fault code = supervisor read, page not present ... > current process = Idle ... > #6 0xc0193f30 in tsleep (ident=0xc0e3b980, priority=256, > wmesg=0xc02cf8f3 "acsem", timo=0) at /export/src/sys/kern/kern_synch.c:436 > #7 0xc015cb13 in AcpiOsWaitSemaphore (Handle=0xc0e3b980, Units=1, > Timeout=65535) at /export/src/sys/dev/acpica/Osd/OsdSynch.c:240 > #8 0xc014f167 in AcpiUtAcquireMutex (MutexId=0) at > /export/src/sys/contrib/dev/acpica/utmisc.c:844 ... >From these pieces of debug information it seems that trap actually occured at kern_synch.c:444 if (p->p_wchan != NULL) because p assigned from curpoc was equal to NULL - curpoc is equal to NULL in the dump and p_wchan field has offset 0x70 in struct proc. I believe that cuproc being NULL is a correct thing because in 4.10 ACPI tasks are executed from SWI task queue i.e. from software interrupt handler, as a part of kernel. But I may be mistaken here. Then, I think, the call to tsleep i.e the need to wait on semaphore resulted from the fact that some ACPI Thermal routines are executed both from ACPI taskqueue and a separate ACPI Thermal kernel thread, so probabalistically there can be "parallel" access to the same resources. Now, I see 3 obvious ways of making this work: 1. change tsleep() to handle curproc == NULL 2. run ACPI tasks on kernel thread taskqueue instead of SWI taskqueue, so that there would be kernel process to run them on 3. somehow make sure that there is no parallel execution of ACPI tasks, so that tsleep() is never called (eliminate ACPI Thermal kthread) Having no knowledge in ACPI internals and very little knowledge in kernel internals I can not dare suggest what would be most appropriate to do. Nevertheless, it seems that (1) would be too intrusive and global; (3) is complex and might not be too reliable; (2) seems to be the easiest, one line change from "taskqueue_swi" to "taskqueue_thread" in OsdSchedule.c I hope my investigation has something helpful in it, and any feedback would also be very helpful for my self-education on kernel matters. -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Sat Jun 12 18:03:35 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E39516A517 for ; Sat, 12 Jun 2004 18:03:34 +0000 (GMT) Received: from relay3.mail.uk.clara.net (relay3.mail.uk.clara.net [80.168.70.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE5C643D5D for ; Sat, 12 Jun 2004 18:03:33 +0000 (GMT) (envelope-from tab1@clara.co.uk) Received: from adsl-solo-40-50.claranet.co.uk ([213.253.40.50] helo=[10.0.0.30]) by relay3.mail.uk.clara.net with esmtp (Exim 4.22) id 1BZCoC-0003KB-Do for freebsd-acpi@freebsd.org; Sat, 12 Jun 2004 19:00:48 +0100 Mime-Version: 1.0 (Apple Message framework v618) Content-Transfer-Encoding: 7bit Message-Id: <99998F62-BC9A-11D8-95A2-000A95C5DE30@clara.co.uk> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-acpi@freebsd.org From: Tom Bowyer Date: Sat, 12 Jun 2004 19:01:59 +0100 X-Mailer: Apple Mail (2.618) Subject: vr0: watchdog timeout 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, 12 Jun 2004 18:03:35 -0000 The machine in question has a VIA EPIA CL motherboard with the BIOS at the latest version: http://www.viavpsd.com/product/epia_cl_spec.jsp?motherboardId=181 I originally installed 5.2.1-Release which worked without problem. I then cvsuped to current (at 12 June 22:13 BST) rebuilt world and a custom kernel and started getting the error "vr0: watchdog timeout" on the console and there was no networking, by which I mean I could not ping anything. The card vr0 was still correctly listed in the output of ifconfig -a. Placing hint.acpi.0.disabled="1" in /boot/loader.conf has got things working again so I assume it is some kind of ACPI problem. I've put the debugging information suggested in the handbook at http://moose.org.uk/~tab/ Is there anything else I can try? thanks, Tom. From owner-freebsd-acpi@FreeBSD.ORG Sat Jun 12 22:44:27 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AA4916A4CE; Sat, 12 Jun 2004 22:44:27 +0000 (GMT) Received: from tomoyo.MyBSD.org.my (duke.void.net.my [202.157.186.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7310A43D2F; Sat, 12 Jun 2004 22:44:24 +0000 (GMT) (envelope-from skywizard@MyBSD.org.my) Received: from kasumi.MyBSD.org.my (unknown [219.94.60.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tomoyo.MyBSD.org.my (Postfix) with ESMTP id 9C1BE6CC1F; Sun, 13 Jun 2004 06:44:52 +0800 (MYT) Date: Sun, 13 Jun 2004 06:43:51 +0800 From: Ariff Abdullah To: freebsd-current@FreeBSD.org Message-Id: <20040613064351.44f05257.skywizard@MyBSD.org.my> Organization: MyBSD X-Mailer: /usr/local/lib/ruby/1.8/net/smtp.rb Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org Subject: MSI 6712 KT4AV asl/dsdt acpi + floppy hack 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, 12 Jun 2004 22:44:27 -0000 Those with MSI 6712 KT4AV motherboard plagued with floppy controller disability can try this to *re*enable your controller back. The trick is to move 0x03F0 resource out of SYSR , and put it under FDC0. Take a look at http://staff.mybsd.org.my/skywizard/FreeBSD/msi_acpi/ . Perhaps other simmilar cases can be cured using this trick. Good luck. -- Ariff Abdullah MyBSD http://www.MyBSD.org.my (IPv6/IPv4) http://staff.MyBSD.org.my (IPv6/IPv4) http://tomoyo.MyBSD.org.my (IPv6/IPv4)