From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 13 13:20:06 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 4691516A41F; Sun, 13 Nov 2005 13:20:06 +0000 (GMT) (envelope-from dsh@vlink.ru) Received: from deliver.smtp.vlink.ru (vlink-0.avtlg.ru [83.239.142.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB94F43D45; Sun, 13 Nov 2005 13:20:05 +0000 (GMT) (envelope-from dsh@vlink.ru) Received: from smtp.smtp.vlink.ru (clamav.smtp.vlink.ru [192.168.4.1]) by deliver.smtp.vlink.ru (Postfix) with ESMTP id DDECBFECF27; Sun, 13 Nov 2005 16:20:03 +0300 (MSK) Received: from neva.vlink.ru (neva.vlink.ru [217.107.252.29]) by smtp.smtp.vlink.ru (Postfix) with ESMTP id A375310098B7; Sun, 13 Nov 2005 16:20:03 +0300 (MSK) Received: from neva.vlink.ru (localhost [127.0.0.1]) by neva.vlink.ru (8.13.4/8.13.4) with ESMTP id jADDK11t007831; Sun, 13 Nov 2005 16:20:01 +0300 (MSK) (envelope-from dsh@vlink.ru) Received: (from dsh@localhost) by neva.vlink.ru (8.13.4/8.13.4/Submit) id jADDK0N6007825; Sun, 13 Nov 2005 16:20:00 +0300 (MSK) (envelope-from dsh@vlink.ru) To: freebsd-current@freebsd.org, freebsd-acpi@freebsd.org References: <87zmo87ltu.fsf@neva.vlink.ru> From: Denis Shaposhnikov Date: Sun, 13 Nov 2005 16:20:00 +0300 In-Reply-To: <87zmo87ltu.fsf@neva.vlink.ru> (Denis Shaposhnikov's message of "Sun, 13 Nov 2005 15:51:09 +0300") Message-ID: <87br0owupr.fsf@neva.vlink.ru> User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.17 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: ClamAV using ClamSMTP Cc: Subject: Re: short time freeze on CURRENT X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 13:20:06 -0000 >>>>> "Denis" == Denis Shaposhnikov writes: Denis> About every 10 seconds the system freeze for about 0.5 Denis> second. I feel it on mplayer, for example, and on a Denis> keyboard. The system lost my keypresses. I see it on friday's I've tried to boot without ACPI and everything is OK. So, something strange with ACPI on fresh CURRENT. -- DSS5-RIPE DSS-RIPN 2:550/5068@fidonet 2:550/5069@fidonet mailto:dsh@vlink.ru http://neva.vlink.ru/~dsh/ From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 08:57:21 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 8BD5216A41F for ; Mon, 14 Nov 2005 08:57:21 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A33543D7C for ; Mon, 14 Nov 2005 08:57:17 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp3-g19.free.fr (Postfix) with ESMTP id 1CE273742F for ; Mon, 14 Nov 2005 09:57:15 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id jAE8v7mb013530 for ; Mon, 14 Nov 2005 09:57:12 +0100 (CET) From: Thierry Herbelot To: freebsd-acpi@freebsd.org Date: Mon, 14 Nov 2005 09:56:58 +0100 User-Agent: KMail/1.8.3 X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200511140957.00179.thierry@herbelot.com> Subject: No powerNow/cpufreq for a desktop Athlon-XP ? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 08:57:21 -0000 Hello, I'm using FreeBSD 6.0 on an Athlon-based desktop machine. I have loaded the= =20 acpi and cpufreq kernel modules, but powerd does not want to start : 'powerd: lookup freq: No such file or directory' =46rom a little googling, it seems that cpufreq will not work on this machi= ne as=20 PowerNow is active only on mobile Athlons (see for example=20 http://forums.pcper.com/showthread.php?t=3D357591) Am I correct ? or is there any way to enable powernow on a desktop Athlon ? TfH From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 09:37:28 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 578A616A427 for ; Mon, 14 Nov 2005 09:37:28 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0283543D4C for ; Mon, 14 Nov 2005 09:37:27 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1Ebam7-0008JB-00; Mon, 14 Nov 2005 10:37:19 +0100 Date: Mon, 14 Nov 2005 10:37:19 +0100 To: Thierry Herbelot Message-ID: <20051114093719.GA31670@poupinou.org> References: <200511140957.00179.thierry@herbelot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511140957.00179.thierry@herbelot.com> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-acpi@freebsd.org Subject: Re: No powerNow/cpufreq for a desktop Athlon-XP ? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 09:37:28 -0000 On Mon, Nov 14, 2005 at 09:56:58AM +0100, Thierry Herbelot wrote: > Hello, > > I'm using FreeBSD 6.0 on an Athlon-based desktop machine. I have loaded the > acpi and cpufreq kernel modules, but powerd does not want to start : > 'powerd: lookup freq: No such file or directory' > > From a little googling, it seems that cpufreq will not work on this machine as > PowerNow is active only on mobile Athlons (see for example > http://forums.pcper.com/showthread.php?t=357591) > > Am I correct ? or is there any way to enable powernow on a desktop Athlon ? > Some people reported that it's possible to use powernow on athlon-based desktop (report under Linux). I don't know the full detail though, but IIRC you have to buy a low-powered processor, and change the driver code in order to add the differents entry for the differents states available. On the other hand, it is not possible to change the voltages associated (this require a special VRM part, available only on mobile systems). I'm sure this would not save power then (especially because all athlon-xp support a very good C2 power state), though this will likely allow you to cool the processor. Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 11:02:18 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 EBC3B16A41F for ; Mon, 14 Nov 2005 11:02:18 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8C7443D5F for ; Mon, 14 Nov 2005 11:02:18 +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 jAEB2IOY073602 for ; Mon, 14 Nov 2005 11:02:18 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAEB2HRJ073595 for freebsd-acpi@freebsd.org; Mon, 14 Nov 2005 11:02:17 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 14 Nov 2005 11:02:17 GMT Message-Id: <200511141102.jAEB2HRJ073595@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 Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 11:02:19 -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 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 o [2005/03/21] i386/79080 acpi acpi thermal changes freezes HP nx6110 o [2005/03/21] i386/79081 acpi ACPI suspend/resume not working on HP nx6 o [2005/11/11] kern/88859 acpi ACPI broken on Compaq DL360 11 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/03/17] kern/64365 acpi ACPI problems o [2004/05/28] kern/67309 acpi zzz reboot computer (ACPI S3) o [2004/07/29] i386/69750 acpi Boot without ACPI failed on ASUS L5 o [2004/11/11] i386/73822 acpi [request] add thermal support to ACPI o [2004/11/11] kern/73823 acpi [feature request] acpi / power-on by time o [2004/11/17] kern/74030 acpi Unplugging AC causes battery % to stay lo o [2004/11/21] kern/74215 acpi [request] add ACPI headers to /usr/includ o [2005/05/09] kern/80815 acpi ACPI(pci_link) problem in 5.4-STABLE: TIM 8 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 16:08:10 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 009F716A41F for ; Mon, 14 Nov 2005 16:08:09 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 684BC43D4C for ; Mon, 14 Nov 2005 16:08:09 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1EbgsK-00014S-00; Mon, 14 Nov 2005 17:08:08 +0100 Date: Mon, 14 Nov 2005 17:08:07 +0100 To: Thierry Herbelot Message-ID: <20051114160807.GB31670@poupinou.org> References: <200511140957.00179.thierry@herbelot.com> <20051114093719.GA31670@poupinou.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051114093719.GA31670@poupinou.org> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-acpi@freebsd.org Subject: Re: No powerNow/cpufreq for a desktop Athlon-XP ? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 16:08:10 -0000 On Mon, Nov 14, 2005 at 10:37:19AM +0100, Bruno Ducrot wrote: > On Mon, Nov 14, 2005 at 09:56:58AM +0100, Thierry Herbelot wrote: > > Hello, > > > > I'm using FreeBSD 6.0 on an Athlon-based desktop machine. I have loaded the > > acpi and cpufreq kernel modules, but powerd does not want to start : > > 'powerd: lookup freq: No such file or directory' > > > > From a little googling, it seems that cpufreq will not work on this machine as > > PowerNow is active only on mobile Athlons (see for example > > http://forums.pcper.com/showthread.php?t=357591) > > > > Am I correct ? or is there any way to enable powernow on a desktop Athlon ? > > > > Some people reported that it's possible to use powernow on athlon-based > desktop (report under Linux). I don't know the full detail though, but > IIRC you have to buy a low-powered processor, and change the driver code > in order to add the differents entry for the differents states > available. On the other hand, it is not possible to change the > voltages associated (this require a special VRM part, available only > on mobile systems). > I'm sure this would not save power then (especially because all > athlon-xp support a very good C2 power state), though this > will likely allow you to cool the processor. > Hrmm, I remember now that an Athlon-XP can be changed somewhat. Maybe this page could help. -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 16:40:26 2005 Return-Path: X-Original-To: freebsd-acpi@hub.freebsd.org Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 113EC16A422 for ; Mon, 14 Nov 2005 16:40:26 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DE2E43D58 for ; Mon, 14 Nov 2005 16:40:25 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jAEGeP73036744 for ; Mon, 14 Nov 2005 16:40:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jAEGeP61036741; Mon, 14 Nov 2005 16:40:25 GMT (envelope-from gnats) Date: Mon, 14 Nov 2005 16:40:25 GMT Message-Id: <200511141640.jAEGeP61036741@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: John Baldwin Cc: Subject: Re: kern/88859: ACPI broken on Compaq DL360 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Baldwin List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 16:40:26 -0000 The following reply was made to PR kern/88859; it has been noted by GNATS. From: John Baldwin To: bug-followup@freebsd.org, tedm@ipinc.net Cc: Subject: Re: kern/88859: ACPI broken on Compaq DL360 Date: Mon, 14 Nov 2005 10:51:58 -0500 Hmm, I think that we actually are handling the FAKE device ok given its definition (_CRS is empty). Would you be able to provide a verbose boot dmesg (boot -v) as well so I can see how far long it is with probing pci_link1? Thanks. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 17:47:08 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 9E23C16A41F for ; Mon, 14 Nov 2005 17:47:08 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE0F243D6A for ; Mon, 14 Nov 2005 17:47:07 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp5-g19.free.fr (Postfix) with ESMTP id 83FD595E2 for ; Mon, 14 Nov 2005 18:47:06 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id jAEHkTfo030396; Mon, 14 Nov 2005 18:46:33 +0100 (CET) From: Thierry Herbelot To: Bruno Ducrot Date: Mon, 14 Nov 2005 18:46:20 +0100 User-Agent: KMail/1.8.3 References: <200511140957.00179.thierry@herbelot.com> <20051114093719.GA31670@poupinou.org> <20051114160807.GB31670@poupinou.org> In-Reply-To: <20051114160807.GB31670@poupinou.org> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200511141846.22188.thierry@herbelot.com> Cc: freebsd-acpi@freebsd.org Subject: Re: No powerNow/cpufreq for a desktop Athlon-XP ? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 17:47:08 -0000 Le Monday 14 November 2005 17:08, Bruno Ducrot a écrit : > Hrmm, I remember now that an Athlon-XP can be changed somewhat. > > Maybe this page > > could help. Thanks for the link : I did not remember having already seen it. The manipulation is a bit scary for me : I'll stick with my "normal" XP. TfH From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 15 10:24:31 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 061AA16A41F for ; Tue, 15 Nov 2005 10:24:31 +0000 (GMT) (envelope-from dsh@vlink.ru) Received: from deliver.smtp.vlink.ru (vlink-1.avtlg.ru [83.239.142.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6967943D49 for ; Tue, 15 Nov 2005 10:24:30 +0000 (GMT) (envelope-from dsh@vlink.ru) Received: from smtp.smtp.vlink.ru (clamav.smtp.vlink.ru [192.168.4.1]) by deliver.smtp.vlink.ru (Postfix) with ESMTP id 5CB1DFECD93 for ; Tue, 15 Nov 2005 13:24:28 +0300 (MSK) Received: from neva.vlink.ru (neva.vlink.ru [217.107.252.29]) by smtp.smtp.vlink.ru (Postfix) with ESMTP id 395321009807 for ; Tue, 15 Nov 2005 13:24:28 +0300 (MSK) Received: from neva.vlink.ru (localhost [127.0.0.1]) by neva.vlink.ru (8.13.4/8.13.4) with ESMTP id jAFAOPvE021028 for ; Tue, 15 Nov 2005 13:24:25 +0300 (MSK) (envelope-from dsh@vlink.ru) Received: (from dsh@localhost) by neva.vlink.ru (8.13.4/8.13.4/Submit) id jAFAOP2S021025 for freebsd-acpi@freebsd.org; Tue, 15 Nov 2005 13:24:25 +0300 (MSK) (envelope-from dsh@vlink.ru) Resent-To: freebsd-acpi@freebsd.org Resent-From: Denis Shaposhnikov Resent-Date: Tue, 15 Nov 2005 13:24:25 +0300 Resent-Message-ID: <87veyui4yu.fsf@neva.vlink.ru> X-From-Line: nobody Tue Nov 15 11:56:32 2005 To: freebsd-acpi@freebsd.org References: <87zmo87ltu.fsf@neva.vlink.ru> <87br0owupr.fsf@neva.vlink.ru> From: Denis Shaposhnikov Date: Tue, 15 Nov 2005 11:56:31 +0300 In-Reply-To: <87br0owupr.fsf@neva.vlink.ru> (Denis Shaposhnikov's message of "Sun, 13 Nov 2005 16:20:00 +0300") Message-ID: <87ek5ijnls.fsf@neva.vlink.ru> User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.17 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 14 X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: short time freeze on CURRENT X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 10:24:31 -0000 >>>>> "Denis" == Denis Shaposhnikov writes: Denis> About every 10 seconds the system freeze for about 0.5 Denis> second. I feel it on mplayer, for example, and on a Denis> keyboard. The system lost my keypresses. I see it on friday's Denis> I've tried to boot without ACPI and everything is OK. So, Denis> something strange with ACPI on fresh CURRENT. I've found that debug.acpi.disabled="cmbat" fixes that behaviour. -- DSS5-RIPE DSS-RIPN 2:550/5068@fidonet 2:550/5069@fidonet mailto:dsh@vlink.ru http://neva.vlink.ru/~dsh/ From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 15 17:00:02 2005 Return-Path: X-Original-To: acpi@freebsd.org 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 8FC4916A41F; Tue, 15 Nov 2005 17:00:02 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C55243D58; Tue, 15 Nov 2005 16:59:58 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:wyqfoZEgbd8ITSypHsM3LhgFThd1jXMM1HN/KC94lseEFAvpX27afsQyyet4H3fO@kasuga-iwi.mahoroba.org [IPv6:3ffe:501:185b:8010:212:f0ff:fe52:6ac]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.4/8.13.4) with ESMTP/inet6 id jAFGxmno002369 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Nov 2005 01:59:52 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 16 Nov 2005 01:59:47 +0900 Message-ID: From: Hajimu UMEMOTO To: Pierre-Luc Drouin In-Reply-To: <4378CC14.2020109@pldrouin.net> References: <4377775B.3080606@pldrouin.net> <20051114105854.GA1041@galgenberg.net> <4378CC14.2020109@pldrouin.net> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.0) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.0-STABLE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Wed, 16 Nov 2005 01:59:53 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ameno.mahoroba.org Cc: acpi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Performance problem since updating from 6.0-RELEASE to 6.0-STABLE last friday X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 17:00:02 -0000 Hi, >>>>> On Mon, 14 Nov 2005 12:40:36 -0500 >>>>> Pierre-Luc Drouin said: pldrouin> Yep, smart battery is definately the problem. The performance of my pldrouin> laptop is back to normal when I remove the xfce4-battery-plugin. pldrouin> acpiconf -i loop reproduces the problem for me too. So it looks like pldrouin> there is something wrong in smart battery. The cmbat has similar issue on some laptops. So, acpi_cmbat.c uses cache for retrieval to reduce its influence, and its expiration time is set by hw.acpi.battery.info_expire. However, acpi_smbat.c doesn't use cache. So, I made a patch. Since I don't have a laptop which has smbat, I cannot test it by myself. Please test it and let me know the result. Index: sys/dev/acpica/acpi_smbat.c diff -u -p sys/dev/acpica/acpi_smbat.c.orig sys/dev/acpica/acpi_smbat.c --- sys/dev/acpica/acpi_smbat.c.orig Sun Nov 6 08:55:56 2005 +++ sys/dev/acpica/acpi_smbat.c Tue Nov 15 16:41:00 2005 @@ -44,11 +44,18 @@ __FBSDID("$FreeBSD: src/sys/dev/acpica/a struct acpi_smbat_softc { uint8_t sb_base_addr; device_t ec_dev; + + struct acpi_bif bif; + struct acpi_bst bst; + struct timespec bif_lastupdated; + struct timespec bst_lastupdated; }; static int acpi_smbat_probe(device_t dev); static int acpi_smbat_attach(device_t dev); static int acpi_smbat_shutdown(device_t dev); +static int acpi_smbat_info_expired(struct timespec *lastupdated); +static void acpi_smbat_info_updated(struct timespec *lastupdated); static int acpi_smbat_get_bif(device_t dev, struct acpi_bif *bif); static int acpi_smbat_get_bst(device_t dev, struct acpi_bst *bst); @@ -114,6 +121,9 @@ acpi_smbat_attach(device_t dev) return (ENXIO); } + timespecclear(&sc->bif_lastupdated); + timespecclear(&sc->bst_lastupdated); + if (acpi_battery_register(dev) != 0) { device_printf(dev, "cannot register battery\n"); return (ENXIO); @@ -132,6 +142,34 @@ acpi_smbat_shutdown(device_t dev) } static int +acpi_smbat_info_expired(struct timespec *lastupdated) +{ + struct timespec curtime; + + ACPI_SERIAL_ASSERT(smbat); + + if (lastupdated == NULL) + return (TRUE); + if (!timespecisset(lastupdated)) + return (TRUE); + + getnanotime(&curtime); + timespecsub(&curtime, lastupdated); + return (curtime.tv_sec < 0 || + curtime.tv_sec > acpi_battery_get_info_expire()); +} + +static void +acpi_smbat_info_updated(struct timespec *lastupdated) +{ + + ACPI_SERIAL_ASSERT(smbat); + + if (lastupdated != NULL) + getnanotime(lastupdated); +} + +static int acpi_smbus_read_2(struct acpi_smbat_softc *sc, uint8_t addr, uint8_t cmd, uint16_t *ptr) { @@ -284,6 +322,11 @@ acpi_smbat_get_bst(device_t dev, struct error = ENXIO; sc = device_get_softc(dev); + if (!acpi_smbat_info_expired(&sc->bst_lastupdated)) { + error = 0; + goto out; + } + if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_BATTERY_MODE, &val)) goto out; if (val & SMBATT_BM_CAPACITY_MODE) { @@ -299,7 +342,7 @@ acpi_smbat_get_bst(device_t dev, struct goto out; if (val & SMBATT_BS_DISCHARGING) { - bst->state |= ACPI_BATT_STAT_DISCHARG; + sc->bst.state |= ACPI_BATT_STAT_DISCHARG; /* * If the rate is negative, it is discharging. Otherwise, @@ -308,27 +351,31 @@ acpi_smbat_get_bst(device_t dev, struct if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_AT_RATE, &val)) goto out; if (val < 0) - bst->rate = (-val) * factor; + sc->bst.rate = (-val) * factor; else - bst->rate = -1; + sc->bst.rate = -1; } else { - bst->state |= ACPI_BATT_STAT_CHARGING; - bst->rate = -1; + sc->bst.state |= ACPI_BATT_STAT_CHARGING; + sc->bst.rate = -1; } if (val & SMBATT_BS_REMAINING_CAPACITY_ALARM) - bst->state |= ACPI_BATT_STAT_CRITICAL; + sc->bst.state |= ACPI_BATT_STAT_CRITICAL; if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_REMAINING_CAPACITY, &val)) goto out; - bst->cap = val * factor; + sc->bst.cap = val * factor; if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_VOLTAGE, &val)) goto out; - bst->volt = val; + sc->bst.volt = val; + + acpi_smbat_info_updated(&sc->bst_lastupdated); + error = 0; out: + memcpy(bst, &sc->bst, sizeof(sc->bst)); ACPI_SERIAL_END(smbat); return (error); } @@ -348,55 +395,63 @@ acpi_smbat_get_bif(device_t dev, struct error = ENXIO; sc = device_get_softc(dev); + if (!acpi_smbat_info_expired(&sc->bif_lastupdated)) { + error = 0; + goto out; + } + if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_BATTERY_MODE, &val)) goto out; if (val & SMBATT_BM_CAPACITY_MODE) { factor = 10; - bif->units = ACPI_BIF_UNITS_MW; + sc->bif.units = ACPI_BIF_UNITS_MW; } else { factor = 1; - bif->units = ACPI_BIF_UNITS_MA; + sc->bif.units = ACPI_BIF_UNITS_MA; } if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_DESIGN_CAPACITY, &val)) goto out; - bif->dcap = val * factor; + sc->bif.dcap = val * factor; if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_FULL_CHARGE_CAPACITY, &val)) goto out; - bif->lfcap = val * factor; - bif->btech = 1; /* secondary (rechargeable) */ + sc->bif.lfcap = val * factor; + sc->bif.btech = 1; /* secondary (rechargeable) */ if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_DESIGN_VOLTAGE, &val)) goto out; - bif->dvol = val; + sc->bif.dvol = val; - bif->wcap = bif->dcap / 10; - bif->lcap = bif->dcap / 10; + sc->bif.wcap = sc->bif.dcap / 10; + sc->bif.lcap = sc->bif.dcap / 10; - bif->gra1 = factor; /* not supported */ - bif->gra2 = factor; /* not supported */ + sc->bif.gra1 = factor; /* not supported */ + sc->bif.gra2 = factor; /* not supported */ if (acpi_smbus_read_multi_1(sc, addr, SMBATT_CMD_DEVICE_NAME, - bif->model, sizeof(bif->model))) + sc->bif.model, sizeof(sc->bif.model))) goto out; if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_SERIAL_NUMBER, &val)) goto out; - snprintf(bif->serial, sizeof(bif->serial), "0x%04x", val); + snprintf(sc->bif.serial, sizeof(sc->bif.serial), "0x%04x", val); if (acpi_smbus_read_multi_1(sc, addr, SMBATT_CMD_DEVICE_CHEMISTRY, - bif->type, sizeof(bif->type))) + sc->bif.type, sizeof(sc->bif.type))) goto out; if (acpi_smbus_read_multi_1(sc, addr, SMBATT_CMD_MANUFACTURER_DATA, - bif->oeminfo, sizeof(bif->oeminfo))) + sc->bif.oeminfo, sizeof(sc->bif.oeminfo))) goto out; + acpi_smbat_info_updated(&sc->bif_lastupdated); + /* XXX check if device was replugged during read? */ error = 0; out: + memcpy(bif, &sc->bif, sizeof(sc->bif)); ACPI_SERIAL_END(smbat); return (error); } Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 15 19:38:09 2005 Return-Path: X-Original-To: acpi@freebsd.org 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 47A2216A41F; Tue, 15 Nov 2005 19:38:09 +0000 (GMT) (envelope-from pldrouin@pldrouin.net) Received: from smtp.cyberfingers.net (smtp.cyberfingers.net [198.177.254.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 980E743D5C; Tue, 15 Nov 2005 19:38:07 +0000 (GMT) (envelope-from pldrouin@pldrouin.net) Received: from [134.117.23.170] (pldrouinlap-pc.physics.carleton.ca [134.117.23.170]) by smtp.cyberfingers.net (Postfix) with ESMTP id 5AAEF17002D; Tue, 15 Nov 2005 14:38:06 -0500 (EST) Message-ID: <437A3901.8010001@pldrouin.net> Date: Tue, 15 Nov 2005 14:37:37 -0500 From: Pierre-Luc Drouin User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051107) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4377775B.3080606@pldrouin.net> <20051114105854.GA1041@galgenberg.net> <4378CC14.2020109@pldrouin.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org Subject: Re: Performance problem since updating from 6.0-RELEASE to 6.0-STABLE last friday X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 19:38:09 -0000 Hajimu UMEMOTO wrote: >Hi, > > > >>>>>>On Mon, 14 Nov 2005 12:40:36 -0500 >>>>>>Pierre-Luc Drouin said: >>>>>> >>>>>> > >pldrouin> Yep, smart battery is definately the problem. The performance of my >pldrouin> laptop is back to normal when I remove the xfce4-battery-plugin. >pldrouin> acpiconf -i loop reproduces the problem for me too. So it looks like >pldrouin> there is something wrong in smart battery. > >The cmbat has similar issue on some laptops. So, acpi_cmbat.c uses >cache for retrieval to reduce its influence, and its expiration >time is set by hw.acpi.battery.info_expire. >However, acpi_smbat.c doesn't use cache. So, I made a patch. Since I >don't have a laptop which has smbat, I cannot test it by myself. >Please test it and let me know the result. > >Index: sys/dev/acpica/acpi_smbat.c >diff -u -p sys/dev/acpica/acpi_smbat.c.orig sys/dev/acpica/acpi_smbat.c >--- sys/dev/acpica/acpi_smbat.c.orig Sun Nov 6 08:55:56 2005 >+++ sys/dev/acpica/acpi_smbat.c Tue Nov 15 16:41:00 2005 >@@ -44,11 +44,18 @@ __FBSDID("$FreeBSD: src/sys/dev/acpica/a > struct acpi_smbat_softc { > uint8_t sb_base_addr; > device_t ec_dev; >+ >+ struct acpi_bif bif; >+ struct acpi_bst bst; >+ struct timespec bif_lastupdated; >+ struct timespec bst_lastupdated; > }; > > static int acpi_smbat_probe(device_t dev); > static int acpi_smbat_attach(device_t dev); > static int acpi_smbat_shutdown(device_t dev); >+static int acpi_smbat_info_expired(struct timespec *lastupdated); >+static void acpi_smbat_info_updated(struct timespec *lastupdated); > static int acpi_smbat_get_bif(device_t dev, struct acpi_bif *bif); > static int acpi_smbat_get_bst(device_t dev, struct acpi_bst *bst); > >@@ -114,6 +121,9 @@ acpi_smbat_attach(device_t dev) > return (ENXIO); > } > >+ timespecclear(&sc->bif_lastupdated); >+ timespecclear(&sc->bst_lastupdated); >+ > if (acpi_battery_register(dev) != 0) { > device_printf(dev, "cannot register battery\n"); > return (ENXIO); >@@ -132,6 +142,34 @@ acpi_smbat_shutdown(device_t dev) > } > > static int >+acpi_smbat_info_expired(struct timespec *lastupdated) >+{ >+ struct timespec curtime; >+ >+ ACPI_SERIAL_ASSERT(smbat); >+ >+ if (lastupdated == NULL) >+ return (TRUE); >+ if (!timespecisset(lastupdated)) >+ return (TRUE); >+ >+ getnanotime(&curtime); >+ timespecsub(&curtime, lastupdated); >+ return (curtime.tv_sec < 0 || >+ curtime.tv_sec > acpi_battery_get_info_expire()); >+} >+ >+static void >+acpi_smbat_info_updated(struct timespec *lastupdated) >+{ >+ >+ ACPI_SERIAL_ASSERT(smbat); >+ >+ if (lastupdated != NULL) >+ getnanotime(lastupdated); >+} >+ >+static int > acpi_smbus_read_2(struct acpi_smbat_softc *sc, uint8_t addr, uint8_t cmd, > uint16_t *ptr) > { >@@ -284,6 +322,11 @@ acpi_smbat_get_bst(device_t dev, struct > error = ENXIO; > sc = device_get_softc(dev); > >+ if (!acpi_smbat_info_expired(&sc->bst_lastupdated)) { >+ error = 0; >+ goto out; >+ } >+ > if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_BATTERY_MODE, &val)) > goto out; > if (val & SMBATT_BM_CAPACITY_MODE) { >@@ -299,7 +342,7 @@ acpi_smbat_get_bst(device_t dev, struct > goto out; > > if (val & SMBATT_BS_DISCHARGING) { >- bst->state |= ACPI_BATT_STAT_DISCHARG; >+ sc->bst.state |= ACPI_BATT_STAT_DISCHARG; > > /* > * If the rate is negative, it is discharging. Otherwise, >@@ -308,27 +351,31 @@ acpi_smbat_get_bst(device_t dev, struct > if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_AT_RATE, &val)) > goto out; > if (val < 0) >- bst->rate = (-val) * factor; >+ sc->bst.rate = (-val) * factor; > else >- bst->rate = -1; >+ sc->bst.rate = -1; > } else { >- bst->state |= ACPI_BATT_STAT_CHARGING; >- bst->rate = -1; >+ sc->bst.state |= ACPI_BATT_STAT_CHARGING; >+ sc->bst.rate = -1; > } > > if (val & SMBATT_BS_REMAINING_CAPACITY_ALARM) >- bst->state |= ACPI_BATT_STAT_CRITICAL; >+ sc->bst.state |= ACPI_BATT_STAT_CRITICAL; > > if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_REMAINING_CAPACITY, &val)) > goto out; >- bst->cap = val * factor; >+ sc->bst.cap = val * factor; > > if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_VOLTAGE, &val)) > goto out; >- bst->volt = val; >+ sc->bst.volt = val; >+ >+ acpi_smbat_info_updated(&sc->bst_lastupdated); >+ > error = 0; > > out: >+ memcpy(bst, &sc->bst, sizeof(sc->bst)); > ACPI_SERIAL_END(smbat); > return (error); > } >@@ -348,55 +395,63 @@ acpi_smbat_get_bif(device_t dev, struct > error = ENXIO; > sc = device_get_softc(dev); > >+ if (!acpi_smbat_info_expired(&sc->bif_lastupdated)) { >+ error = 0; >+ goto out; >+ } >+ > if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_BATTERY_MODE, &val)) > goto out; > if (val & SMBATT_BM_CAPACITY_MODE) { > factor = 10; >- bif->units = ACPI_BIF_UNITS_MW; >+ sc->bif.units = ACPI_BIF_UNITS_MW; > } else { > factor = 1; >- bif->units = ACPI_BIF_UNITS_MA; >+ sc->bif.units = ACPI_BIF_UNITS_MA; > } > > if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_DESIGN_CAPACITY, &val)) > goto out; >- bif->dcap = val * factor; >+ sc->bif.dcap = val * factor; > > if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_FULL_CHARGE_CAPACITY, &val)) > goto out; >- bif->lfcap = val * factor; >- bif->btech = 1; /* secondary (rechargeable) */ >+ sc->bif.lfcap = val * factor; >+ sc->bif.btech = 1; /* secondary (rechargeable) */ > > if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_DESIGN_VOLTAGE, &val)) > goto out; >- bif->dvol = val; >+ sc->bif.dvol = val; > >- bif->wcap = bif->dcap / 10; >- bif->lcap = bif->dcap / 10; >+ sc->bif.wcap = sc->bif.dcap / 10; >+ sc->bif.lcap = sc->bif.dcap / 10; > >- bif->gra1 = factor; /* not supported */ >- bif->gra2 = factor; /* not supported */ >+ sc->bif.gra1 = factor; /* not supported */ >+ sc->bif.gra2 = factor; /* not supported */ > > if (acpi_smbus_read_multi_1(sc, addr, SMBATT_CMD_DEVICE_NAME, >- bif->model, sizeof(bif->model))) >+ sc->bif.model, sizeof(sc->bif.model))) > goto out; > > if (acpi_smbus_read_2(sc, addr, SMBATT_CMD_SERIAL_NUMBER, &val)) > goto out; >- snprintf(bif->serial, sizeof(bif->serial), "0x%04x", val); >+ snprintf(sc->bif.serial, sizeof(sc->bif.serial), "0x%04x", val); > > if (acpi_smbus_read_multi_1(sc, addr, SMBATT_CMD_DEVICE_CHEMISTRY, >- bif->type, sizeof(bif->type))) >+ sc->bif.type, sizeof(sc->bif.type))) > goto out; > > if (acpi_smbus_read_multi_1(sc, addr, SMBATT_CMD_MANUFACTURER_DATA, >- bif->oeminfo, sizeof(bif->oeminfo))) >+ sc->bif.oeminfo, sizeof(sc->bif.oeminfo))) > goto out; > >+ acpi_smbat_info_updated(&sc->bif_lastupdated); >+ > /* XXX check if device was replugged during read? */ > error = 0; > > out: >+ memcpy(bif, &sc->bif, sizeof(sc->bif)); > ACPI_SERIAL_END(smbat); > return (error); > } > > >Sincerely, > >-- >Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan >ume@mahoroba.org ume@{,jp.}FreeBSD.org >http://www.imasy.org/~ume/ > > > The patch seams to do its job correctly, but it is still very annoying to have the whole computer to freeze for 1 second when the cache expires. What does make the whole system to freeze? Before the code was changed in 6.0-stable, FreeBSD was able to read the battery status without freezing my laptop... I have been running 3 OSes (FreeBSD, Ubuntu and Win XP) on my laptop for a while and never experienced that kind of problem with either Linux or Win XP. I guess there is something wrong in the new code added after 6.0-release. Thank you! Pierre-Luc Drouin From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 15 19:49:17 2005 Return-Path: X-Original-To: acpi@freebsd.org 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 6829D16A41F; Tue, 15 Nov 2005 19:49:17 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ED5043D66; Tue, 15 Nov 2005 19:49:11 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (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 jAFJn9De020201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 15 Nov 2005 11:49:12 -0800 Message-ID: <437A3B96.4040300@root.org> Date: Tue, 15 Nov 2005 11:48:38 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pierre-Luc Drouin References: <4377775B.3080606@pldrouin.net> <20051114105854.GA1041@galgenberg.net> <4378CC14.2020109@pldrouin.net> <437A3901.8010001@pldrouin.net> In-Reply-To: <437A3901.8010001@pldrouin.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Performance problem since updating from 6.0-RELEASE to 6.0-STABLE last friday X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 19:49:17 -0000 Pierre-Luc Drouin wrote: > Hajimu UMEMOTO wrote: >>>>>>> On Mon, 14 Nov 2005 12:40:36 -0500 >>>>>>> Pierre-Luc Drouin said: >> pldrouin> Yep, smart battery is definately the problem. The >> performance of my pldrouin> laptop is back to normal when I remove the >> xfce4-battery-plugin. pldrouin> acpiconf -i loop reproduces the >> problem for me too. So it looks like pldrouin> there is something >> wrong in smart battery. >> >> The cmbat has similar issue on some laptops. So, acpi_cmbat.c uses >> cache for retrieval to reduce its influence, and its expiration >> time is set by hw.acpi.battery.info_expire. >> However, acpi_smbat.c doesn't use cache. So, I made a patch. Since I >> don't have a laptop which has smbat, I cannot test it by myself. >> Please test it and let me know the result. >> >> > The patch seams to do its job correctly, but it is still very annoying > to have the whole computer to freeze for 1 second when the cache > expires. What does make the whole system to freeze? Before the code was > changed in 6.0-stable, FreeBSD was able to read the battery status > without freezing my laptop... I have been running 3 OSes (FreeBSD, > Ubuntu and Win XP) on my laptop for a while and never experienced that > kind of problem with either Linux or Win XP. I guess there is something > wrong in the new code added after 6.0-release. If you have both smbat and cmbat, just disable smbat if you don't like it. Add this to /boot/loader.conf: debug.acpi.disabled="smbat" The pause is related to a buggy or slow EC. Caching the values happens to hide it. Do you get pauses with smbat disabled (see above for how to do this)? Can you still get battery status from cmbat? -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 15 19:58:08 2005 Return-Path: X-Original-To: acpi@freebsd.org 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 ECE3C16A41F for ; Tue, 15 Nov 2005 19:58:08 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9495143D46 for ; Tue, 15 Nov 2005 19:58:08 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (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 jAFJw8De020301 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 15 Nov 2005 11:58:09 -0800 Message-ID: <437A3DB1.4030904@root.org> Date: Tue, 15 Nov 2005 11:57:37 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ulrich Spoerlein References: <20051108082057.GB1067@galgenberg.net> In-Reply-To: <20051108082057.GB1067@galgenberg.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org Subject: Re: Battery woes since going 6.0-BETA3 -> 6.0-STABLE X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 19:58:09 -0000 Ulrich Spoerlein wrote: > I updated my system yesterday from BETA3 to the current RELENG_6. > Booting my system this morning, I found it in a rather unusable state. > > First of all, there were problems with BETA3 before. When charging the > battery (only when charging!) wmbsdbatt would periodically freeze the > system which made MP3 playback impossible. Ok, I first thought wmbsdbatt > is calling sysctl to get the values and sysctl is under Giant. So no > problem. > > Funny thing is, it only occurred when charging, not when running on > batteries or without them. Something in how your system implements the EC means the _BST method is taking a very long time when charging batteries. You can work around this (but lose battery status) with: debug.acpi.disabled="cmbat" To verify this, put some printfs in acpi_cmbat.c around this line: as = AcpiEvaluateObject(h, "_BST", NULL, &bst_buffer); You'll see that when it hangs, you'll get the printf before but not after this method. This won't help solve the problem though since the actual battery access will be performed by the EC and that is a separate CPU (microcontroller). So we can't exactly debug it. However, I suspect what I'm working on right now (burst mode support) will alleviate the problems. I probably won't have time to work on this until the next holiday (in a few weeks). > Now updating to the current RELENG_6 I get the system freezes whenever > running wmbsdbatt. This goes as far as the USB devices losing contact > (!!). I thought my kbd/mouse went wacko, and found the following in > messages > > This is because wmbsdbatt is polling the battery (which right now, is > not even present, as I'm running on AC). > > I'm running a Dell Inspiron 8600, these are the relevant acpi lines from > dmesg > acpi0: on motherboard > pci_link0: irq 11 on acpi0 > pci_link1: irq 11 on acpi0 > pci_link2: irq 11 on acpi0 > pci_link3: irq 11 on acpi0 > pci_link4: on acpi0 > pci_link5: irq 11 on acpi0 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > cpu0: on acpi0 > est0: on cpu0 > p4tcc0: on cpu0 > acpi_acad0: on acpi0 > battery0: on acpi0 > battery1: on acpi0 > acpi_lid0: on acpi0 > acpi_button0: on acpi0 > acpi_button1: on acpi0 > > I will revert 6.0-RELEASE for now, I guess the smart battery support is > causing problems for me. You don't have smart battery, therefore it can't be the issue. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 15 21:59:42 2005 Return-Path: X-Original-To: acpi@freebsd.org 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 E250B16A41F; Tue, 15 Nov 2005 21:59:42 +0000 (GMT) (envelope-from pldrouin@pldrouin.net) Received: from smtp.cyberfingers.net (smtp.cyberfingers.net [198.177.254.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8942043D45; Tue, 15 Nov 2005 21:59:42 +0000 (GMT) (envelope-from pldrouin@pldrouin.net) Received: from [192.168.0.7] (modemcable041.248-200-24.mc.videotron.ca [24.200.248.41]) by smtp.cyberfingers.net (Postfix) with ESMTP id DD3B417005F; Tue, 15 Nov 2005 16:59:41 -0500 (EST) Message-ID: <437A5A4D.7050902@pldrouin.net> Date: Tue, 15 Nov 2005 16:59:41 -0500 From: Pierre-Luc Drouin User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051107) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, acpi@freebsd.org References: <4377775B.3080606@pldrouin.net> <20051114105854.GA1041@galgenberg.net> <4378CC14.2020109@pldrouin.net> <437A3901.8010001@pldrouin.net> <437A3B96.4040300@root.org> In-Reply-To: <437A3B96.4040300@root.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Performance problem since updating from 6.0-RELEASE to 6.0-STABLE last friday X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 21:59:43 -0000 Nate Lawson wrote: > Pierre-Luc Drouin wrote: > >> Hajimu UMEMOTO wrote: >> >>>>>>>> On Mon, 14 Nov 2005 12:40:36 -0500 >>>>>>>> Pierre-Luc Drouin said: >>>>>>> >>> pldrouin> Yep, smart battery is definately the problem. The >>> performance of my pldrouin> laptop is back to normal when I remove >>> the xfce4-battery-plugin. pldrouin> acpiconf -i loop reproduces the >>> problem for me too. So it looks like pldrouin> there is something >>> wrong in smart battery. >>> >>> The cmbat has similar issue on some laptops. So, acpi_cmbat.c uses >>> cache for retrieval to reduce its influence, and its expiration >>> time is set by hw.acpi.battery.info_expire. >>> However, acpi_smbat.c doesn't use cache. So, I made a patch. Since I >>> don't have a laptop which has smbat, I cannot test it by myself. >>> Please test it and let me know the result. >>> >>> >> The patch seams to do its job correctly, but it is still very >> annoying to have the whole computer to freeze for 1 second when the >> cache expires. What does make the whole system to freeze? Before the >> code was changed in 6.0-stable, FreeBSD was able to read the battery >> status without freezing my laptop... I have been running 3 OSes >> (FreeBSD, Ubuntu and Win XP) on my laptop for a while and never >> experienced that kind of problem with either Linux or Win XP. I guess >> there is something wrong in the new code added after 6.0-release. > > > If you have both smbat and cmbat, just disable smbat if you don't like > it. Add this to /boot/loader.conf: > > debug.acpi.disabled="smbat" > > The pause is related to a buggy or slow EC. Caching the values > happens to hide it. Do you get pauses with smbat disabled (see above > for how to do this)? Can you still get battery status from cmbat? > Ok, there is new development. I realized by playing with debug.acpi.disabled="smbat", debug.acpi.disabled="smbat cmbat" and debug.acpi.disabled="cmbat", that my laptop battery is not a smbat, but a cmbat. When I played with hw.acpi.battery.info_expire after to have applied the patch for acpi_smbat.c, it was freezing less often because that sysctl variable was shared by both cmbat and smbat. So I can only get battery status from cmbat (disabling cmbat disables the use of acpiconf -i loop). To get the status of my battery via cmbat was working fine up to 6.0-RELEASE (included), but makes my laptop to freeze since I upgraded to 6.0-stable with Nov 10th sources. What change related to cmbat between 6.0-release and 6.0-stable could be causing this? From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 15 22:29:50 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 BB48316A424 for ; Tue, 15 Nov 2005 22:29:50 +0000 (GMT) (envelope-from gofda-freebsd-acpi@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7BE043D46 for ; Tue, 15 Nov 2005 22:29:49 +0000 (GMT) (envelope-from gofda-freebsd-acpi@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ec9ER-0006U0-FK for freebsd-acpi@freebsd.org; Tue, 15 Nov 2005 23:24:51 +0100 Received: from r5k101.chello.upc.cz ([86.49.10.101]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 15 Nov 2005 23:24:51 +0100 Received: from martinkov by r5k101.chello.upc.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 15 Nov 2005 23:24:51 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-acpi@freebsd.org From: martinko Date: Tue, 15 Nov 2005 23:17:14 +0100 Lines: 20 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: r5k101.chello.upc.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051114 X-Accept-Language: sk, cs, en-gb, en-us, en Sender: news Cc: freebsd-mobile@freebsd.org Subject: supported CX states -- regression? X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 22:29:50 -0000 hello, when i started on freebsd 5.3 i could see something like the following from sysctl: hw.acpi.cpu.cx_supported: C1/1 C2/10 C3/100 and i remember that my system changed among those states (or at least 2 of them iirc). since 5.5 and now on 6.0 all i can see is: hw.acpi.cpu.cx_supported: C1/1 hw.acpi.cpu.cx_lowest: C1 why is this so, what does it mean and what can i do about it pls ?? regards, martin From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 15 22:41:45 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 35E8F16A41F for ; Tue, 15 Nov 2005 22:41:45 +0000 (GMT) (envelope-from gofda-freebsd-acpi@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B60CC43D49 for ; Tue, 15 Nov 2005 22:41:44 +0000 (GMT) (envelope-from gofda-freebsd-acpi@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1Ec9Tq-0003a9-Gi for freebsd-acpi@freebsd.org; Tue, 15 Nov 2005 23:40:47 +0100 Received: from r5k101.chello.upc.cz ([86.49.10.101]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 15 Nov 2005 23:40:46 +0100 Received: from martinkov by r5k101.chello.upc.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 15 Nov 2005 23:40:46 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-acpi@freebsd.org From: martinko Date: Tue, 15 Nov 2005 23:09:35 +0100 Lines: 20 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: r5k101.chello.upc.cz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051114 X-Accept-Language: sk, cs, en-gb, en-us, en Sender: news Cc: freebsd-mobile@freebsd.org Subject: powerd vs power_profile X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2005 22:41:45 -0000 hello, powerd(8) man page says that when used with power_profile they may override each other. and indeed i experienced a strange behaviour that might be contributed to it -- i unplugged/plugged my laptop a few times with a few seconds interval between and suddenly it stopped responding to AC line changes together with some strange behaviour like for instance bubblemon dockapp freeze etc. it got back to normal in 30 secs or so. i did not find, though, an explanation/example on what to do if one wants to use powerd. (?) martin ps: bubblemon is a good indicator for me if something goes wrong with my laptop. i believe there's a bug in my bios because sometimes when i try to change LCD brightness quicky the system sort of freezes -- some applications run correctly while others stop (i think the ones that sleep and redraw their window regularly) -- this happens on freebsd as well as on windows and linux. :-(( From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 17 22:25:33 2005 Return-Path: X-Original-To: acpi@freebsd.org 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 DCC7F16A41F for ; Thu, 17 Nov 2005 22:25:32 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3398443D45 for ; Thu, 17 Nov 2005 22:25:32 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2139412 for ; Thu, 17 Nov 2005 17:25:33 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAHMPPb8029333 for ; Thu, 17 Nov 2005 17:25:27 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: acpi@freebsd.org Date: Thu, 17 Nov 2005 17:25:27 -0500 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_XNQfD9rFPouyaeS" Message-Id: <200511171725.27877.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: [PATCH] Fix weird PCI bus numbers with pci_linkX 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, 17 Nov 2005 22:25:33 -0000 --Boundary-00=_XNQfD9rFPouyaeS Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline I think I figured out why some people get messages like: pci_linkX: BIOS IRQ 11 for -17777216.6.INTA is invalid I was not reading the bus number from the bridge device correctly (the normal __BUS_ACCESSOR() macros assume that the passed in argument is a child device, but at the time I'm reading the bus there is no child device, so I was passing in the pcib device, the parent of the pcib device probably returned an error, and the bus variable ended up being some random stack garbage). The attached patch (also at URL) should fix it I think. http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org --Boundary-00=_XNQfD9rFPouyaeS-- From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 17 22:33:05 2005 Return-Path: X-Original-To: acpi@freebsd.org 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 F2BEE16A41F; Thu, 17 Nov 2005 22:33:04 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B03143D46; Thu, 17 Nov 2005 22:33:04 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (ppp-71-139-0-107.dsl.snfc21.pacbell.net [71.139.0.107]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jAHMX1De023304 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 17 Nov 2005 14:33:06 -0800 Message-ID: <437D04FC.90707@root.org> Date: Thu, 17 Nov 2005 14:32:28 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200511171725.27877.jhb@freebsd.org> In-Reply-To: <200511171725.27877.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org Subject: Re: [PATCH] Fix weird PCI bus numbers with pci_linkX 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, 17 Nov 2005 22:33:05 -0000 John Baldwin wrote: > I think I figured out why some people get messages like: > > pci_linkX: BIOS IRQ 11 for -17777216.6.INTA is invalid > > I was not reading the bus number from the bridge device correctly (the normal > __BUS_ACCESSOR() macros assume that the passed in argument is a child device, > but at the time I'm reading the bus there is no child device, so I was > passing in the pcib device, the parent of the pcib device probably returned > an error, and the bus variable ended up being some random stack garbage). > The attached patch (also at URL) should fix it I think. > > http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch Excellent, patch looks good to me except the printf/panic message could be improved. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Thu Nov 17 22:52:06 2005 Return-Path: X-Original-To: acpi@freebsd.org 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 E74E916A41F for ; Thu, 17 Nov 2005 22:52:06 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id A56B443D45 for ; Thu, 17 Nov 2005 22:52:05 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2140308 for multiple; Thu, 17 Nov 2005 17:51:36 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAHMpTCX030461; Thu, 17 Nov 2005 17:51:30 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Nate Lawson Date: Thu, 17 Nov 2005 17:50:51 -0500 User-Agent: KMail/1.8.2 References: <200511171725.27877.jhb@freebsd.org> <437D04FC.90707@root.org> In-Reply-To: <437D04FC.90707@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511171750.52720.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: acpi@freebsd.org Subject: Re: [PATCH] Fix weird PCI bus numbers with pci_linkX 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, 17 Nov 2005 22:52:07 -0000 On Thursday 17 November 2005 05:32 pm, Nate Lawson wrote: > John Baldwin wrote: > > I think I figured out why some people get messages like: > > > > pci_linkX: BIOS IRQ 11 for -17777216.6.INTA is invalid > > > > I was not reading the bus number from the bridge device correctly (the > > normal __BUS_ACCESSOR() macros assume that the passed in argument is a > > child device, but at the time I'm reading the bus there is no child > > device, so I was passing in the pcib device, the parent of the pcib > > device probably returned an error, and the bus variable ended up being > > some random stack garbage). The attached patch (also at URL) should fix > > it I think. > > > > http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch > > Excellent, patch looks good to me except the printf/panic message could > be improved. I wanna see if it triggers first. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org