From owner-freebsd-acpi@FreeBSD.ORG Sun Jul 18 02:16:29 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 1719C16A4CE for ; Sun, 18 Jul 2004 02:16:29 +0000 (GMT) Received: from mps7.plala.or.jp (c150240.vh.plala.or.jp [210.150.150.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id D591C43D2F for ; Sun, 18 Jul 2004 02:16:27 +0000 (GMT) (envelope-from t-ogawa@triaez.kaisei.org) Received: from solder.dyndns.org ([220.221.88.1]) by mps7.plala.or.jp with SMTP id <20040718021626.UUWM6937.mps7.plala.or.jp@solder.dyndns.org> for ; Sun, 18 Jul 2004 11:16:26 +0900 Received: (qmail 44366 invoked from network); 18 Jul 2004 02:16:26 -0000 Received: from localhost (HELO gandalf.middle.earth) (127.0.0.1) by localhost with SMTP; 18 Jul 2004 02:16:26 -0000 Date: Sun, 18 Jul 2004 11:16:26 +0900 Message-ID: <86hds6njph.wl.t-ogawa@triaez.kaisei.org> From: OGAWA Takaya To: Takahashi Yoshihiro In-Reply-To: <20040717.183512.74706779.nyan@jp.FreeBSD.org> References: <20040712.200815.74734634.nyan@jp.FreeBSD.org> <86llhpz354.wl.t-ogawa@triaez.kaisei.org> <20040713.011631.74707278.nyan@jp.FreeBSD.org> <20040717.183512.74706779.nyan@jp.FreeBSD.org> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=ISO-2022-JP cc: acpi@FreeBSD.org cc: njl@FreeBSD.org Subject: Re: Panasonic acpi driver 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, 18 Jul 2004 02:16:29 -0000 At Sat, 17 Jul 2004 18:35:12 +0900 (JST), Takahashi Yoshihiro wrote: > I put new patch to > http://home.jp.freebsd.org/~nyan/patches/acpi_pana2.diff.gz Thank you. That looks great! It does the job without any problem here. I'd suggest updating the manual page as attached below. The patch contais some documentation error corrections, a couple of grammartical fixes and a few structural improvements. --- acpi_panasonic.4.orig Sun Jul 18 01:57:27 2004 +++ acpi_panasonic.4 Sun Jul 18 03:28:46 2004 @@ -43,7 +43,17 @@ Toughbook, outside Japan) CF-R1N, CF-R2A and CF-R3. It may also work on other models as well. .Pp -On these models there are 9 hotkeys available: +The driver consists of three functionalities. +The first is to detect hotkey events and take corresponding actions, +which include changing LCD luminance and speaker mute state. +The second role is to notify occurences of the event by way of +.Xr devctl 4 +and eventually to +.Xr devd 8 . +The third and last is to provide a way to adjust LCD brightness and +sound mute state via sysctl. +.Ss Hotkeys +There are 9 hotkeys available on the supported hardwares: .Pp .Bl -tag -compact -offset indent .It Sy \&Fn+F1 @@ -52,11 +62,11 @@ Make LCD backlight brighter. .It Sy \&Fn+F3 Switch video output between LCD and CRT. -Not supported within the +Not supported by the .Nm driver. .It Sy \&Fn+F4 -Toggle muting a speaker. +Toggle muting the speaker. .It Sy \&Fn+F5 Turn the mixer volume down. .It Sy \&Fn+F6 @@ -69,14 +79,16 @@ Enter suspend-to-disk state. .El .Pp -The driver consists of two functionality. -The first is to notify the occurence of the hotkey event by way of -.Xr devctl 4 -and eventually to -.Xr devd 8 . -The second role is to provide the way to adjust LCD brightness and -sound mute state via sysctl. -.Sh DEVD EVENTS +Actions are automatically taken within the driver for +.Sy \&Fn+F1 , +.Sy \&Fn+F2 +and +.Sy \&Fn+F4 . +For the other events such as +mixer control and showing battery status, +.Xr devd 8 +should take the role as described below. +.Ss Devd Events When notified to .Xr devd 8 , the hotkey event provides the following information: @@ -112,17 +124,18 @@ and so on. .El .Sh SYSCTLS -The following MIBs are available: -.Bl -tag -offset indent -.It Sy hw.acpi.panasonic.lcd_brightness_max +The following read-write MIBs are available: +.Bl -tag -width indent +.It Va hw.acpi.panasonic.lcd_brightness_max The max level of brightness. The value ranges from 0 to 255. -CF-R1N and CF-R2A should be 255, CF-R3 is 32. -.It Sy hw.acpi.panasonic.lcd_brightness +CF-R1N and CF-R2A should be 255, CF-R3 is 31. +.It Va hw.acpi.panasonic.lcd_brightness Current brightness level of the LCD. -The value ranges from 0 to 15. -.It Sy hw.acpi.panasonic.sound_mute -Boolean flag to control whether to mute the speaker. +The value ranges from 0 to +.Va hw.acpi.panasonic.lcd_brightness_max . +.It Va hw.acpi.panasonic.sound_mute +A boolean flag to control whether to mute the speaker. The value 1 means to mute and 0 not. .El .Sh SEE ALSO ---------- おがわ たかや t-ogawa@triaez.kaisei.org From owner-freebsd-acpi@FreeBSD.ORG Mon Jul 19 11:01:45 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 0BBF716A4D0 for ; Mon, 19 Jul 2004 11:01:45 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0687A43D2F for ; Mon, 19 Jul 2004 11:01:45 +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 i6JB1ix5015384 for ; Mon, 19 Jul 2004 11:01:44 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i6JB1iGL015378 for freebsd-acpi@freebsd.org; Mon, 19 Jul 2004 11:01:44 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 19 Jul 2004 11:01:44 GMT Message-Id: <200407191101.i6JB1iGL015378@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, 19 Jul 2004 11:01:45 -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 Mon Jul 19 20:25: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 BEA0116A4CE for ; Mon, 19 Jul 2004 20:25:01 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87C7443D58 for ; Mon, 19 Jul 2004 20:25:01 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465 for ; Mon, 19 Jul 2004 13:25:01 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id EC6725D08 for ; Mon, 19 Jul 2004 13:24:59 -0700 (PDT) To: freebsd-acpi@FreeBSD.org Date: Mon, 19 Jul 2004 13:24:58 -0700 From: "Kevin Oberman" Message-Id: <20040719202459.EC6725D08@ptavv.es.net> Subject: ACPI cmbat regression 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, 19 Jul 2004 20:25:01 -0000 Since the recent addition of support for battery removal to ACPI, my T30 (running current BIOS) now simply turns off (ouch) when the secondary battery is removed. There are not messages or delays. The instant I eject the battery, the system is powered off (with the attendant problems of sudden power failure on a file system running with soft updates). I don't know if this happens with any other laptop, but it's pretty disastrous on mine. acpidump, config, and whatever can be made available on request. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 20 05:14:24 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 8088916A4CE for ; Tue, 20 Jul 2004 05:14:24 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id E147543D3F for ; Tue, 20 Jul 2004 05:14:23 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.102] (ddsl-66-42-172-210.fuse.net [66.42.172.210]) (authenticated bits=0)i6K54S2S030479 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 20 Jul 2004 01:04:28 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: Mark Santcroos Date: Tue, 20 Jul 2004 01:15:19 -0400 User-Agent: KMail/1.6.2 References: <200401121945.59585.mistry.7@osu.edu> <200407021147.52966.mistry.7@osu.edu> <20040713152727.GA1018@laptop.6bone.nl> In-Reply-To: <20040713152727.GA1018@laptop.6bone.nl> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200407200115.27009.mistry.7@osu.edu> X-Spam-Status: No, hits=-4.9 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE, QUOTED_EMAIL_TEXT,RCVD_IN_ORBS,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_KMAIL version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-acpi@freebsd.org Subject: Re: [acpi-jp 3000] Re: Fujitsu Function Button ACPI Module (FJEX) 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, 20 Jul 2004 05:14:24 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 13 July 2004 11:27 am, you wrote: > On Fri, Jul 02, 2004 at 11:47:36AM -0400, Anish Mistry wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On Monday 12 January 2004 08:29 pm, Nate Lawson wrote: > > > On Mon, 12 Jan 2004, Anish Mistry wrote: > > > > I've been sitting on this for a while waiting to hear back from the > > > > primary author, but no word after a few weeks, so I'm posting it to > > > > see what people think. This module allows a program to receive > > > > events when the function buttons are pressed. It's companion > > > > userland program fujiapp hooks in and receives and event when a > > > > button is pressed and show the level. It has only been tested on t= he > > > > Fujitsu P2000 series laptops, but may work on other models with the > > > > FJEX acpi device. > > > > > > > > Sean's website: > > > > http://www.stalker.org/~sean/freebsd-p2040/FujiApp/ > > > > > > > > My modifications to make it a loadable module: > > > > http://am-productions.biz/docs/acpi_fjex.tgz > > > > and just fujiapp without the module source included: > > > > http://am-productions.biz/docs/fujiapp-1.1.tgz > > > > > > You should use acpi_UserNotify() to send events to userland. The > > > events will appear on /dev/devctl and can be parsed by devd. If you > > > can do what you want via devd.conf, fine. If you want to have your o= wn > > > program reading /dev/devctl, you'll have to implement device cloning > > > for /dev/devctl first or not run devd. (A current deficiently in devc= tl > > > is that only one reader can be present at a time.) > > > > > > -Nate > > > > After much procrastination I've finally updated this module to CURRENT > > and match the Toshiba driver. Test if you have a Fujitsu P2000 (I've > > heard this device also appears on the P5000 and the S series). > > > > http://am-productions.biz/docs/acpi_fuji.tgz > > > > FYI: My network has been a bit flaky you might have to request it a > > couple of times before it goes through. > > > > Opps, sent it to the old list. I know that there are some style issues, > > but I'd like to get comments about anything that is wrong with the way > > I've done things, or just suggestions. > > Hi, > > I forgot whether I mentioned it already, but I'm having a look at it > (again). We should get it ready for import this time, I tried to get some > Fujitsu laptop, but that failed, so you have to do the testing for me. > > Mark I've finally got the userland part down, it's a bit slow since it's all she= ll=20 scripts but it works for me. The following is added to my devd.conf to relay the acpi_fuji events: notify 10 { match "system" "ACPI"; match "subsystem" "FUJI"; action "/etc/rc.d/acpi_fuji_exec.sh $notify"; }; Then into /etc/rc.d I put this: http://am-productions.biz/docs/acpi_fuji_exec.sh Then from an xterm or similar run the following from an X session (This is= =20 actually good for displaying the logger event from the syslog)=20 requires /usr/ports/misc/xosd : http://am-productions.biz/docs/fuji_display.sh =2D --=20 Anish Mistry =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/KpuxqA5ziudZT0RArX4AKC+Z0vhXiZU8HiqJuvhV3ILUozqTACglp96 03EZ06J9tybGkIuAiv0/KO8=3D =3D8I3/ =2D----END PGP SIGNATURE----- From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 20 08:11: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 B179216A4CE; Tue, 20 Jul 2004 08:11:12 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94DEE43D5C; Tue, 20 Jul 2004 08:11:12 +0000 (GMT) (envelope-from vs@FreeBSD.org) Received: from freefall.freebsd.org (vs@localhost [127.0.0.1]) i6K8BC8M010258; Tue, 20 Jul 2004 08:11:12 GMT (envelope-from vs@freefall.freebsd.org) Received: (from vs@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i6K8BCmW010254; Tue, 20 Jul 2004 08:11:12 GMT (envelope-from vs) Date: Tue, 20 Jul 2004 08:11:12 GMT From: Volker Stolz Message-Id: <200407200811.i6K8BCmW010254@freefall.freebsd.org> To: bobhamm49@cox.net, vs@FreeBSD.org, freebsd-i386@FreeBSD.org, acpi@FreeBSD.org Subject: Re: i386/67770: X11 kills system after upgrade to 5.2.1 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, 20 Jul 2004 08:11:12 -0000 Synopsis: X11 kills system after upgrade to 5.2.1 State-Changed-From-To: open->analyzed State-Changed-By: vs State-Changed-When: Tue Jul 20 08:08:14 GMT 2004 State-Changed-Why: Workaround available Responsible-Changed-From-To: freebsd-i386->acpi Responsible-Changed-By: vs Responsible-Changed-When: Tue Jul 20 08:08:14 GMT 2004 Responsible-Changed-Why: ACPI issue http://www.freebsd.org/cgi/query-pr.cgi?pr=67770 From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 20 16:51: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 AF1A916A4CE; Tue, 20 Jul 2004 16:51:15 +0000 (GMT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9038643D2F; Tue, 20 Jul 2004 16:51:15 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from pun.isi.edu (pun.isi.edu [128.9.160.150]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i6KGoGJ03791; Tue, 20 Jul 2004 09:50:16 -0700 (PDT) Received: from pun.isi.edu (localhost [127.0.0.1]) by pun.isi.edu (8.12.11/8.12.11) with ESMTP id i6KGoGjf036140; Tue, 20 Jul 2004 09:50:16 -0700 (PDT) (envelope-from faber@pun.isi.edu) Received: (from faber@localhost) by pun.isi.edu (8.12.11/8.12.11/Submit) id i6KGoGkk036139; Tue, 20 Jul 2004 09:50:16 -0700 (PDT) (envelope-from faber) Date: Tue, 20 Jul 2004 09:50:16 -0700 From: Ted Faber To: frebsd-hackers@freebsd.org, freebsd-acpi@freebsd.org Message-ID: <20040720165016.GA35412@pun.isi.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="69pVuxX8awAiJ7fD" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-url: http://www.isi.edu/~faber X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: faber@isi.edu Subject: Dell Latitude 610 CPU clock rate degrading (debug info included) 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, 20 Jul 2004 16:51:15 -0000 --69pVuxX8awAiJ7fD Content-Type: multipart/mixed; boundary="i9LlY+UWpKt15+FH" Content-Disposition: inline --i9LlY+UWpKt15+FH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline My Dell Latatude 610 is having its clock rate go from 1000 Mhz to 733 Mhz under -CURRENT that was cvsupped and installed yesterday. I'm honestly not sure how long this has been happening, since I only got the clock speed monitor (the one that runs under gkrellm) hooked up a couple weeks ago. I hooked it up because the machine seemed slow. It had been happening for a couple weeks at least. The rate seems to change after using the CPU hard for a while - a big compile, like make buildworld seems to do it, though even a few minutes of compilation seems sufficient. When the CPU speed changes I get a message in the logs saying cpu0: Performance states changed The state never seems to change back to a high performance one. I've configured the BIOS not to do power management with the AC connected, and this happens with the AC connected. I tried booting without ACPI, but my time of day clock ran consistenty slow - which might mean that the same degredation was occurring without the OS readjusting for it. In any case it wasn't clear that no ACPI helped. Attached are a sysctl hw.acpi before and after the speed change and a dmesg from a -v boot up to when the states change. The attachments are in that order. ASL is at http://www.isi.edu/~faber/tmp/faber-dell-L610.asl Please let me know if I can help debug this. -- Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG --i9LlY+UWpKt15+FH Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=before hw.acpi.supported_sleep_state: S1 S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 1 hw.acpi.verbose: 1 hw.acpi.reset_video: 1 hw.acpi.cpu.cx_supported: C1/0 C2/50 C3/50 hw.acpi.cpu.cx_lowest: C3 hw.acpi.cpu.cx_usage: 2.13% 97.86% 0.00% hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.tz0.temperature: 3227 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: -1 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3732 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.acline: 1 hw.acpi.battery.life: 100 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 --i9LlY+UWpKt15+FH Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=after hw.acpi.supported_sleep_state: S1 S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 1 hw.acpi.verbose: 1 hw.acpi.reset_video: 1 hw.acpi.cpu.cx_supported: C1/0 C2/50 C3/50 hw.acpi.cpu.cx_lowest: C3 hw.acpi.cpu.cx_usage: 2.12% 97.87% 0.00% hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.tz0.temperature: 3297 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: -1 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3732 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.acline: 1 hw.acpi.battery.life: 100 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 --i9LlY+UWpKt15+FH Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="local.dmsg" Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.2-CURRENT #24: Mon Jul 19 11:49:37 PDT 2004 root@bug.isi.edu:/usr/obj/usr/src/sys/BUG Preloaded elf kernel "/boot/kernel/kernel" at 0xc0773000. Preloaded elf module "/boot/kernel/if_an.ko" at 0xc07731d8. Preloaded elf module "/boot/kernel/wlan.ko" at 0xc0773284. Preloaded elf module "/boot/kernel/rc4.ko" at 0xc0773330. Preloaded elf module "/boot/kernel/snd_ich.ko" at 0xc07733d8. Preloaded elf module "/boot/kernel/sound.ko" at 0xc0773484. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0773530. Calibrating clock(s) ... i8254 clock: 1193076 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 996787763 Hz CPU: Intel(R) Pentium(R) III Mobile CPU 1000MHz (996.79-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383f9ff real memory = 536686592 (511 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000829000 - 0x000000001f6a2fff, 518496256 bytes (126586 pages) avail memory = 519680000 (495 MB) bios32: Found BIOS32 Service Directory header at 0xc00ffe80 bios32: Entry = 0xffe90 (c00ffe90) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xbfee pnpbios: Found PnP BIOS data at 0xc00fe2d0 pnpbios: Entry = f0000:e2f4 Rev = 1.0 pnpbios: Event flag at 4b4 Other BIOS signatures found: wlan: <802.11 Link Layer> null: mem: Pentium Pro MTRR support enabled random: npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: [GIANT-LOCKED] pci_open(1): mode 1 addr port (0x0cf8) is 0x80010014 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=35758086) pcibios: BIOS version 2.10 Found $PIR table, 11 entries at 0xc00fbb90 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded 0 29 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 B 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 D 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 0 30 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 30 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 0 30 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 30 D 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 0 31 A 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 31 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 1 0 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 2 0 A 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 2 1 A 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 2 3 A 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 2 3 B 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 2 8 A 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 2 12 A 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 2 12 B 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 2 12 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 2 12 D 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 8 0 A 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 8 1 A 0x61 3 4 5 6 7 9 10 11 12 14 15 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 atpic: Programming IRQ9 as level/low acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 29 func 1 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 29 func 2 ACPI timer looks GOOD min = 2, max = 3, width = 1 ACPI timer looks GOOD min = 2, max = 3, width = 1 ACPI timer looks GOOD min = 2, max = 3, width = 1 ACPI timer looks GOOD min = 2, max = 3, width = 1 ACPI timer looks GOOD min = 2, max = 3, width = 1 ACPI timer looks GOOD min = 2, max = 3, width = 1 ACPI timer looks GOOD min = 2, max = 3, width = 1 ACPI timer looks GOOD min = 2, max = 3, width = 1 ACPI timer looks GOOD min = 2, max = 3, width = 1 ACPI timer looks GOOD min = 2, max = 3, width = 1 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_tz0: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 ACPI PCI link initial configuration: \\_SB_.PCI0.LNKA irq 11: [ 9 10 11] low,level,sharable 0.31.0 \\_SB_.PCI0.LNKB irq 11: [ 5 7] low,level,sharable 0.31.1 \\_SB_.PCI0.LNKC irq 11: [ 9 10 11] low,level,sharable 0.31.2 \\_SB_.PCI0.LNKD irq 11: [ 5 7 9 10 11] low,level,sharable 0.31.3 \\_SB_.PCI0.LNKA irq 11: [ 9 10 11] low,level,sharable 0.29.0 \\_SB_.PCI0.LNKD irq 11: [ 5 7 9 10 11] low,level,sharable 0.29.1 \\_SB_.PCI0.LNKC irq 11: [ 9 10 11] low,level,sharable 0.29.2 \\_SB_.PCI0.LNKA irq 11: [ 9 10 11] low,level,sharable 0.2.0 \\_SB_.PCI0.LNKA irq 11: [ 9 10 11] low,level,sharable 0.1.0 \\_SB_.PCI0.LNKB irq 11: [ 5 7] low,level,sharable 0.1.1 ACPI PCI link before setting link priority: ACPI PCI link before fixup for boot-disabled links: ACPI PCI link after fixup for boot-disabled links: ACPI PCI link arbitrated configuration: \\_SB_.PCI0.LNKA irq 11: [ 9 10 11] low,level,sharable 0.31.0 \\_SB_.PCI0.LNKB irq 11: [ 5 7] low,level,sharable 0.31.1 \\_SB_.PCI0.LNKC irq 11: [ 9 10 11] low,level,sharable 0.31.2 \\_SB_.PCI0.LNKD irq 11: [ 5 7 9 10 11] low,level,sharable 0.31.3 \\_SB_.PCI0.LNKA irq 11: [ 9 10 11] low,level,sharable 0.29.0 \\_SB_.PCI0.LNKD irq 11: [ 5 7 9 10 11] low,level,sharable 0.29.1 \\_SB_.PCI0.LNKC irq 11: [ 9 10 11] low,level,sharable 0.29.2 \\_SB_.PCI0.LNKA irq 11: [ 9 10 11] low,level,sharable 0.2.0 \\_SB_.PCI0.LNKA irq 11: [ 9 10 11] low,level,sharable 0.1.0 \\_SB_.PCI0.LNKB irq 11: [ 5 7] low,level,sharable 0.1.1 pci0: on pcib0 pci0: physical bus=0 map[10]: type 3, range 32, base d0000000, size 28, enabled found-> vendor=0x8086, dev=0x3575, revid=0x04 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x2010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x3576, revid=0x04 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x0c (3000 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 0000bf80, size 5, enabled pcib0: matched entry for 0.29.INTA (src \\_SB_.PCI0.LNKA) pcib0: slot 29 INTA is routed to irq 11 found-> vendor=0x8086, dev=0x2482, revid=0x02 bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 found-> vendor=0x8086, dev=0x2448, revid=0x42 bus=0, slot=30, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0080, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x06 (1500 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x248c, revid=0x02 bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x010f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 0000bfa0, size 4, enabled found-> vendor=0x8086, dev=0x248a, revid=0x02 bus=0, slot=31, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[10]: type 4, range 32, base 0000d800, size 8, enabled map[14]: type 4, range 32, base 0000dc80, size 6, enabled pcib0: matched entry for 0.31.INTB (src \\_SB_.PCI0.LNKB) pcib0: slot 31 INTB is routed to irq 11 found-> vendor=0x8086, dev=0x2485, revid=0x02 bus=0, slot=31, func=5 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 map[10]: type 4, range 32, base 0000d400, size 8, enabled map[14]: type 4, range 32, base 0000dc00, size 7, enabled pcib0: matched entry for 0.31.INTB (src \\_SB_.PCI0.LNKB) pcib0: slot 31 INTB is routed to irq 11 found-> vendor=0x8086, dev=0x2486, revid=0x02 bus=0, slot=31, func=6 class=07-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 agp0: mem 0xd0000000-0xdfffffff at device 0.0 on pci0 agp0: Reserved 0x10000000 bytes for rid 0x10 type 3 at 0xd0000000 agp0: allocating GATT for aperture of size 228M pcib1: at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xc000-0xcfff pcib1: memory decode 0xfc000000-0xfdffffff pcib1: prefetched decode 0xe0000000-0xe7ffffff ACPI PCI link initial configuration: \\_SB_.PCI0.LNKA irq 11: [ 9 10 11] low,level,sharable 1.0.0 ACPI PCI link before setting link priority: ACPI PCI link before fixup for boot-disabled links: ACPI PCI link after fixup for boot-disabled links: ACPI PCI link arbitrated configuration: \\_SB_.PCI0.LNKA irq 11: [ 9 10 11] low,level,sharable 1.0.0 pci1: on pcib1 pci1: physical bus=1 map[10]: type 3, range 32, base e0000000, size 27, enabled pcib1: device (null) requested decoded memory range 0xe0000000-0xe7ffffff map[14]: type 4, range 32, base 0000c000, size 8, enabled pcib1: device (null) requested decoded I/O range 0xc000-0xc0ff map[18]: type 1, range 32, base fcff0000, size 16, enabled pcib1: device (null) requested decoded memory range 0xfcff0000-0xfcffffff pcib1: matched entry for 1.0.INTA (src \\_SB_.PCI0.LNKA) pcib1: slot 0 INTA is routed to irq 11 found-> vendor=0x1002, dev=0x4c59, revid=0x00 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x01a7, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 pci1: at device 0.0 (no driver attached) uhci0: port 0xbf80-0xbf9f irq 11 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xbf80 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pcib2: at device 30.0 on pci0 pcib2: secondary bus 2 pcib2: subordinate bus 16 pcib2: I/O decode 0xe000-0xffff pcib2: memory decode 0xf4000000-0xfbffffff pcib2: prefetched decode 0xfff00000-0xfffff pcib2: Subtractively decoded bridge. ACPI PCI link initial configuration: \\_SB_.PCI0.LNKD irq 11: [ 5 7 9 10 11] low,level,sharable 2.1.0 \\_SB_.PCI0.LNKD irq 11: [ 5 7 9 10 11] low,level,sharable 2.1.1 \\_SB_.PCI0.LNKD irq 11: [ 5 7 9 10 11] low,level,sharable 2.1.2 \\_SB_.PCI0.LNKB irq 11: [ 5 7] low,level,sharable 2.3.0 \\_SB_.PCI0.LNKD irq 11: [ 5 7 9 10 11] low,level,sharable 2.3.1 \\_SB_.PCI0.LNKC irq 11: [ 9 10 11] low,level,sharable 2.0.0 \\_SB_.PCI0.LNKC irq 11: [ 9 10 11] low,level,sharable 2.8.0 ACPI PCI link before setting link priority: ACPI PCI link before fixup for boot-disabled links: ACPI PCI link after fixup for boot-disabled links: ACPI PCI link arbitrated configuration: \\_SB_.PCI0.LNKD irq 11: [ 5 7 9 10 11] low,level,sharable 2.1.0 \\_SB_.PCI0.LNKD irq 11: [ 5 7 9 10 11] low,level,sharable 2.1.1 \\_SB_.PCI0.LNKD irq 11: [ 5 7 9 10 11] low,level,sharable 2.1.2 \\_SB_.PCI0.LNKB irq 11: [ 5 7] low,level,sharable 2.3.0 \\_SB_.PCI0.LNKD irq 11: [ 5 7 9 10 11] low,level,sharable 2.3.1 \\_SB_.PCI0.LNKC irq 11: [ 9 10 11] low,level,sharable 2.0.0 \\_SB_.PCI0.LNKC irq 11: [ 9 10 11] low,level,sharable 2.8.0 pci2: on pcib2 pci2: physical bus=2 map[10]: type 4, range 32, base 0000ec80, size 7, enabled pcib2: device (null) requested decoded I/O range 0xec80-0xecff map[14]: type 1, range 32, base f8fffc00, size 7, enabled pcib2: device (null) requested decoded memory range 0xf8fffc00-0xf8fffc7f pcib2: matched entry for 2.0.INTA (src \\_SB_.PCI0.LNKC) pcib2: slot 0 INTA is routed to irq 11 found-> vendor=0x10b7, dev=0x9200, revid=0x78 bus=2, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x0a (2500 ns), maxlat=0x0a (2500 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base 00000000, size 12, memory disabled found-> vendor=0x104c, dev=0xac51, revid=0x00 bus=2, slot=1, func=0 class=06-07-00, hdrtype=0x02, mfdev=1 cmdreg=0x0000, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x40 (16000 ns), maxlat=0x07 (1750 ns) intpin=a, irq=255 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base 00000000, size 12, memory disabled found-> vendor=0x104c, dev=0xac51, revid=0x00 bus=2, slot=1, func=1 class=06-07-00, hdrtype=0x02, mfdev=1 cmdreg=0x0000, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x40 (16000 ns), maxlat=0x07 (1750 ns) intpin=a, irq=255 powerspec 1 supports D0 D1 D2 D3 current D0 pci2: at device 0.0 (no driver attached) cbb0: at device 1.0 on pci2 pcib2: device cbb0 requested decoded memory range 0xf4000000-0xfbffffff cbb0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xf4000000 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcib2: matched entry for 2.1.INTA (src \\_SB_.PCI0.LNKD) pcib2: slot 1 INTA is routed to irq 11 cbb0: [MPSAFE] cbb0: PCI Configuration space: 0x00: 0xac51104c 0x02100007 0x06070000 0x00822008 0x10: 0xf4000000 0x020000a0 0x20040400 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x0740010b 0x40: 0x00e31028 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x2024d025 0x00000000 0x00000000 0x01261222 0x90: 0x6064a6c0 0x00000000 0x00000000 0x00000000 0xa0: 0xfe110001 0x00c00000 0x00000000 0x00000017 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x00000000 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 cbb1: at device 1.1 on pci2 pcib2: device cbb1 requested decoded memory range 0xf4000000-0xfbffffff cbb1: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xf4001000 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 pcib2: matched entry for 2.1.INTA (src \\_SB_.PCI0.LNKD) pcib2: slot 1 INTA is routed to irq 11 cbb1: [MPSAFE] cbb1: PCI Configuration space: 0x00: 0xac51104c 0x02100007 0x06070000 0x00822008 0x10: 0xf4001000 0x020000a0 0x20050500 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x0740010b 0x40: 0x00e31028 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x2024d025 0x00000000 0x00000000 0x01261222 0x90: 0x6064a6c0 0x00000000 0x00000000 0x00000000 0xa0: 0xfe110001 0x00c00000 0x00000000 0x00000017 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x00000000 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xbfa0-0xbfaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xbfa0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata0-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1-master: stat=0x10 err=0x01 lsb=0x14 msb=0xeb ata1-slave: stat=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=10 stat1=00 devices=0x4 ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] pcm0: port 0xdc80-0xdcbf,0xd800-0xd8ff irq 11 at device 31.5 on pci0 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xd800 pcm0: Reserved 0x40 bytes for rid 0x14 type 4 at 0xdc80 pcm0: [GIANT-LOCKED] pcm0: pcm0: Codec features mic channel, tone, simulated stereo, bass boost, 20 bit DAC, 18 bit ADC, 5 bit master volume, SRS 3D Stereo Enhancement pcm0: Primary codec extended features variable rate PCM, variable rate mic, AMAP pcm0: sndbuf_setmap 2b9000, 4000; 0xe4fd1000 -> 2b9000 pcm0: sndbuf_setmap 2c1000, 4000; 0xe4fd5000 -> 2c1000 pcm0: sndbuf_setmap 2cb000, 4000; 0xe4fd9000 -> 2cb000 pci0: at device 31.6 (no driver attached) psmcpnp0 irq 12 on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: current command byte:0065 psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 fd1: <1440-KB 3.5" drive> on fdc0 drive 1 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 port 0x280-0x287,0x2f8-0x2ff irq 3 drq 3 on acpi0 sio1: type 16550A ppc0: using extended I/O port range ppc0: ECP SPP ECP+EPP SPP ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 1 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 unknown: not probed (disabled) unknown: not probed (disabled) ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 already exists; skipping it ppc: ppc0 already exists; skipping it sc: sc0 already exists; skipping it sio: sio0 already exists; skipping it sio: sio1 already exists; skipping it vga: vga0 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k vga0: vga: WARNING: video mode switching is not fully supported on this adapter VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 e7 a3 4f 67 8f 6a 1b 24 b3 00 6f 0d 0e 00 00 07 80 49 8f 8f 28 1f 47 6d a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 e7 a3 4f 67 8f 6a 1b 24 b3 00 6f 0d 0e 00 00 07 80 49 8f 8f 28 1f 47 6d a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fe0: not probed (disabled) ie0: not probed (disabled) lnc0: not probed (disabled) pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0 pcic1: not probed (disabled) sio2: configured irq 5 not in bitmap of probed irqs 0 sio2: port may not be enabled sio2: irq maps: 0x1 0x1 0x1 0x1 sio2: probe failed test(s): 0 1 2 4 6 7 9 sio2 failed to probe at port 0x3e8-0x3ef irq 5 on isa0 sio3: configured irq 9 not in bitmap of probed irqs 0 sio3: port may not be enabled sio3: irq maps: 0x1 0x1 0x1 0x1 sio3: probe failed test(s): 0 1 2 4 6 7 9 sio3 failed to probe at port 0x2e8-0x2ef irq 9 on isa0 sn0: not probed (disabled) vt0: not probed (disabled) isa_probe_children: probing PnP devices Device configuration finished. Timecounter "TSC" frequency 996787763 Hz quality 800 Timecounters tick every 10.000 msec lo0: bpf attached acpi_acad0: acline initialization start acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times acpi_cmbat0: battery initialization start acpi_cmbat0: battery initialization done, tried 1 times acpi_cmbat1: battery initialization start ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ata0-master: setting PIO4 on Intel ICH3 chip ata0-master: setting UDMA100 on Intel ICH3 chip ad0: ATA-5 disk at ata0-master ad0: 28615MB (58605120 sectors), 58140 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA100 GEOM: new disk ad0 ata1-master: pio=0x0c wdma=0x22 udma=0xffffffff cable=40pin ata1-master: setting PIO4 on Intel ICH3 chip acd0: CDRW drive at ata1 as master acd0: read 4134KB/s (4134KB/s) write 1377KB/s (1377KB/s), 2048KB buffer, PIO4 acd0: Reads: CDR, CDRW, CDDA stream, packet acd0: Writes: CDR, CDRW, test write, burnproof acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc pcm0: measured ac97 link rate at 48012 Hz, will use 48000 Hz [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/15/63 s:63 l:58605057 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad0s1, start 32256 length 30005789184 end 30005821439 GEOM: Configure ad0s1a, start 0 length 268435456 end 268435455 GEOM: Configure ad0s1b, start 268435456 length 2147483648 end 2415919103 GEOM: Configure ad0s1c, start 0 length 30005789184 end 30005789183 GEOM: Configure ad0s1d, start 2415919104 length 2147483648 end 4563402751 GEOM: Configure ad0s1e, start 4563402752 length 25442386432 end 30005789183 Mounting root from ufs:/dev/ad0s1a start_init: trying /sbin/init procfs registered Linux ELF exec handler installed linprocfs registered pci0: driver added found-> vendor=0x8086, dev=0x2486, revid=0x02 bus=0, slot=31, func=6 class=07-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 pci0:31:6: reprobing on driver added pci0:31:6: Transition from D0 to D3 pci1: driver added found-> vendor=0x1002, dev=0x4c59, revid=0x00 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x01a7, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 pci1:0:0: reprobing on driver added pci2: driver added found-> vendor=0x10b7, dev=0x9200, revid=0x78 bus=2, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x0a (2500 ns), maxlat=0x0a (2500 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 pci2:0:0: reprobing on driver added xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xec80-0xecff mem 0xf8fffc00-0xf8fffc7f irq 11 at device 0.0 on pci2 xl0: Reserved 0x80 bytes for rid 0x14 type 3 at 0xf8fffc00 xl0: using memory mapped I/O xl0: media options word: a xl0: found MII/AUTO xl0: bpf attached xl0: Ethernet address: 00:06:5b:e4:de:9c xl0: [GIANT-LOCKED] miibus0: on xl0 ukphy0: on miibus0 ukphy0: OUI 0x00105a, model 0x0000, rev. 0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: driver added found-> vendor=0x8086, dev=0x2486, revid=0x02 bus=0, slot=31, func=6 class=07-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 pci0:31:6: reprobing on driver added pci0:31:6: Transition from D0 to D3 pci1: driver added found-> vendor=0x1002, dev=0x4c59, revid=0x00 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x01a7, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 pci1:0:0: reprobing on driver added drm0: port 0xc000-0xc0ff mem 0xfcff0000-0xfcffffff,0xe0000000-0xe7ffffff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xd0000000 256MB info: [drm] Initialized radeon 1.11.0 20020828 on minor 0 pci2: driver added agp0: Setting AGP v2 mode 1 drm0: [MPSAFE] acpi_cmbat1: battery initialization failed, giving up pid 795 (gkrellm), uid 2139: exited on signal 11 cpu0: Performance states changed --i9LlY+UWpKt15+FH-- --69pVuxX8awAiJ7fD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/U1IaUz3f+Zf+XsRAlWsAKCWoJ+YGm4z9NmqnAwVAztA70cKfACgkeW3 XwYu/mbA9NNpW6upoWci0IY= =Zh7v -----END PGP SIGNATURE----- --69pVuxX8awAiJ7fD-- From owner-freebsd-acpi@FreeBSD.ORG Tue Jul 20 19:03: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 8AFC116A4CE; Tue, 20 Jul 2004 19:03:15 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28D1B43D48; Tue, 20 Jul 2004 19:03:15 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-63-195-111-154.dsl.snfc21.pacbell.net [63.195.111.154]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i6KJ3Dra028232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 20 Jul 2004 12:03:14 -0700 Message-ID: <40FD6BEB.4060102@root.org> Date: Tue, 20 Jul 2004 12:00:59 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.6 (X11/20040518) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ted Faber References: <20040720165016.GA35412@pun.isi.edu> In-Reply-To: <20040720165016.GA35412@pun.isi.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: frebsd-hackers@freebsd.org Subject: Re: Dell Latitude 610 CPU clock rate degrading (debug info included) 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, 20 Jul 2004 19:03:15 -0000 Ted Faber wrote: > My Dell Latatude 610 is having its clock rate go from 1000 Mhz to 733 > Mhz under -CURRENT that was cvsupped and installed yesterday. I'm > honestly not sure how long this has been happening, since I only got the > clock speed monitor (the one that runs under gkrellm) hooked up a couple > weeks ago. I hooked it up because the machine seemed slow. It had been > happening for a couple weeks at least. > > The rate seems to change after using the CPU hard for a while - a big > compile, like make buildworld seems to do it, though even a few minutes > of compilation seems sufficient. > > When the CPU speed changes I get a message in the logs saying > > cpu0: Performance states changed > > The state never seems to change back to a high performance one. I've > configured the BIOS not to do power management with the AC connected, > and this happens with the AC connected. This transition is being done by the BIOS for passive cooling. We can't control it until the cpufreq driver is committed. When the system gets hot, the BIOS steps the processor down to 733 mhz but the timecounters have no way of knowing it happened. > I tried booting without ACPI, but my time of day clock ran consistenty > slow - which might mean that the same degredation was occurring without > the OS readjusting for it. In any case it wasn't clear that no ACPI > helped. Same problem. What timecounter are you using? Switching away from TSC would help this. > Attached are a sysctl hw.acpi before and after the speed change and a > dmesg from a -v boot up to when the states change. The attachments are > in that order. ASL is at > http://www.isi.edu/~faber/tmp/faber-dell-L610.asl > > Please let me know if I can help debug this. -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Jul 21 16:40: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 204C316A4CF for ; Wed, 21 Jul 2004 16:40:22 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id D00D843D55 for ; Wed, 21 Jul 2004 16:40:21 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-63-195-111-154.dsl.snfc21.pacbell.net [63.195.111.154]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i6LGeGra019063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Jul 2004 09:40:21 -0700 Message-ID: <40FE9BEA.7060802@root.org> Date: Wed, 21 Jul 2004 09:38:02 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.6 (X11/20040518) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Takahashi Yoshihiro References: <20040712.200815.74734634.nyan@jp.FreeBSD.org> <86llhpz354.wl.t-ogawa@triaez.kaisei.org> <20040713.011631.74707278.nyan@jp.FreeBSD.org> <20040717.183512.74706779.nyan@jp.FreeBSD.org> <86hds6njph.wl.t-ogawa@triaez.kaisei.org> In-Reply-To: <86hds6njph.wl.t-ogawa@triaez.kaisei.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: acpi@FreeBSD.org Subject: Re: Panasonic acpi driver X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 16:40:22 -0000 OGAWA Takaya wrote: > At Sat, 17 Jul 2004 18:35:12 +0900 (JST), > Takahashi Yoshihiro wrote: > >>I put new patch to >>http://home.jp.freebsd.org/~nyan/patches/acpi_pana2.diff.gz > > > Thank you. That looks great! > It does the job without any problem here. Thank you for importing the driver, Yoshihiro-san. I wanted to also let the list know that anyone who is considering committing a userland hotkeys script should talk to me first. I don't want us to import any device-specific hotkey scripts (i.e., asus, panasonic, toshiba, etc.) but instead have a single general-purpose script and have the kernel translate device-specific tables of hotkey values to generic ones. That way a single script can look for the generic "volume up/down" buttons and act accordingly. Please email me if you're interested in working on that. -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Jul 21 17:20:47 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 D094516A4CE for ; Wed, 21 Jul 2004 17:20:47 +0000 (GMT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 649BF43D54 for ; Wed, 21 Jul 2004 17:20:47 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from pun.isi.edu (pun.isi.edu [128.9.160.150]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i6LHIrJ12747; Wed, 21 Jul 2004 10:18:53 -0700 (PDT) Received: from pun.isi.edu (localhost [127.0.0.1]) by pun.isi.edu (8.12.11/8.12.11) with ESMTP id i6LHIrQp046864; Wed, 21 Jul 2004 10:18:53 -0700 (PDT) (envelope-from faber@pun.isi.edu) Received: (from faber@localhost) by pun.isi.edu (8.12.11/8.12.11/Submit) id i6LHIrwi046863; Wed, 21 Jul 2004 10:18:53 -0700 (PDT) (envelope-from faber) Date: Wed, 21 Jul 2004 10:18:53 -0700 From: Ted Faber To: Nate Lawson Message-ID: <20040721171853.GB45921@pun.isi.edu> References: <20040720165016.GA35412@pun.isi.edu> <40FD6BEB.4060102@root.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2B/JsCI69OhZNC5r" Content-Disposition: inline In-Reply-To: <40FD6BEB.4060102@root.org> User-Agent: Mutt/1.4.2.1i X-url: http://www.isi.edu/~faber X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: faber@isi.edu cc: freebsd-acpi@freebsd.org Subject: Re: Dell Latitude 610 CPU clock rate degrading (debug info included) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 17:20:48 -0000 --2B/JsCI69OhZNC5r Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jul 20, 2004 at 12:00:59PM -0700, Nate Lawson wrote: > Ted Faber wrote: > >My Dell Latatude 610 is having its clock rate go from 1000 Mhz to 733 > >Mhz under -CURRENT that was cvsupped and installed yesterday. I'm > >honestly not sure how long this has been happening, since I only got the > >clock speed monitor (the one that runs under gkrellm) hooked up a couple > >weeks ago. I hooked it up because the machine seemed slow. It had been > >happening for a couple weeks at least. > > > >The rate seems to change after using the CPU hard for a while - a big > >compile, like make buildworld seems to do it, though even a few minutes > >of compilation seems sufficient. > > > >When the CPU speed changes I get a message in the logs saying > > > >cpu0: Performance states changed > > > >The state never seems to change back to a high performance one. I've > >configured the BIOS not to do power management with the AC connected, > >and this happens with the AC connected. > > This transition is being done by the BIOS for passive cooling. We can't > control it until the cpufreq driver is committed. When the system gets > hot, the BIOS steps the processor down to 733 mhz but the timecounters have > no way of knowing it happened. Thanks for the info. If you've got a list of people to ping when the cpufreq driver appears, put me on it. I'll be watching for the HEADSUP in any case. > > >I tried booting without ACPI, but my time of day clock ran consistenty > >slow - which might mean that the same degredation was occurring without > >the OS readjusting for it. In any case it wasn't clear that no ACPI > >helped. > > Same problem. What timecounter are you using? Switching away from TSC > would help this. With ACPI there's no clock skew problem, so that's how I've been running. Just for my information, how might I switch timecounters? (It sounds like it won't solve the problem to switch away from ACPI, but I'm curious). Thanks again for your quick response. -- Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG --2B/JsCI69OhZNC5r Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA/qV9aUz3f+Zf+XsRAqumAKD1beqQU66u4HOQ1bOZny0AqbHe2QCgmfY4 rY56EkotXoIqWoLwDrIgRC8= =isyl -----END PGP SIGNATURE----- --2B/JsCI69OhZNC5r-- From owner-freebsd-acpi@FreeBSD.ORG Wed Jul 21 18:36: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 5EE4D16A4CE for ; Wed, 21 Jul 2004 18:36:54 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id DBB5443D41 for ; Wed, 21 Jul 2004 18:36:53 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-63-195-111-154.dsl.snfc21.pacbell.net [63.195.111.154]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i6LIaqrb021002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Jul 2004 11:36:52 -0700 Message-ID: <40FEB73E.7020102@root.org> Date: Wed, 21 Jul 2004 11:34:38 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ted Faber References: <20040720165016.GA35412@pun.isi.edu> <40FD6BEB.4060102@root.org> <20040721171853.GB45921@pun.isi.edu> In-Reply-To: <20040721171853.GB45921@pun.isi.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: Dell Latitude 610 CPU clock rate degrading (debug info included) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 18:36:54 -0000 Ted Faber wrote: > On Tue, Jul 20, 2004 at 12:00:59PM -0700, Nate Lawson wrote: > >>Ted Faber wrote: >>>I tried booting without ACPI, but my time of day clock ran consistenty >>>slow - which might mean that the same degredation was occurring without >>>the OS readjusting for it. In any case it wasn't clear that no ACPI >>>helped. >> >>Same problem. What timecounter are you using? Switching away from TSC >>would help this. > > With ACPI there's no clock skew problem, so that's how I've been > running. Just for my information, how might I switch timecounters? (It > sounds like it won't solve the problem to switch away from ACPI, but I'm > curious). When running without ACPI, you should use the i8254 timecounter. Switch it with this command (or put it in /etc/sysctl.conf): sysctl kern.timecounter.hardware="i8254" -- -Nate From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 23 00:17: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 4316016A4CE for ; Fri, 23 Jul 2004 00:17:05 +0000 (GMT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5FE643D48 for ; Fri, 23 Jul 2004 00:17:04 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from [10.0.3.231] ([141.153.201.221]) by out001.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040723001704.TKFH1464.out001.verizon.net@[10.0.3.231]>; Thu, 22 Jul 2004 19:17:04 -0500 From: "Alexandre \"Sunny\" Kovalenko" To: Nate Lawson In-Reply-To: <40FEB73E.7020102@root.org> References: <20040720165016.GA35412@pun.isi.edu> <40FD6BEB.4060102@root.org> <20040721171853.GB45921@pun.isi.edu> <40FEB73E.7020102@root.org> Content-Type: text/plain Message-Id: <1090541770.643.7.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 22 Jul 2004 20:16:10 -0400 Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [141.153.201.221] at Thu, 22 Jul 2004 19:17:03 -0500 cc: freebsd-acpi@freebsd.org Subject: Timecounter configuration [Was: Dell Latitude 610 CPU clock rate degrading (debug info included)] 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, 23 Jul 2004 00:17:05 -0000 On Wed, 2004-07-21 at 14:34, Nate Lawson wrote: > Ted Faber wrote: > > On Tue, Jul 20, 2004 at 12:00:59PM -0700, Nate Lawson wrote: > > > >>Ted Faber wrote: > >>>I tried booting without ACPI, but my time of day clock ran consistenty > >>>slow - which might mean that the same degredation was occurring without > >>>the OS readjusting for it. In any case it wasn't clear that no ACPI > >>>helped. > >> > >>Same problem. What timecounter are you using? Switching away from TSC > >>would help this. > > > > With ACPI there's no clock skew problem, so that's how I've been > > running. Just for my information, how might I switch timecounters? (It > > sounds like it won't solve the problem to switch away from ACPI, but I'm > > curious). > > When running without ACPI, you should use the i8254 timecounter. Switch > it with this command (or put it in /etc/sysctl.conf): > > sysctl kern.timecounter.hardware="i8254" While we are on the subject, would this work for those of us who have acpi timer broken: acpi_timer0: couldn't allocate I/O resource (port 0x808) acpi_timer0 port 0x808-0x80b on acpi0 pmtimer0 on isa0 I have seen somebody else posting this problem before, but if you need any details or want to try patch, I'll be glad to. Right now if I use powernow_k7 to throttle, my clock slows down accordingly. Problem have started few weeks ago, however, acpi_timer.c did not change between working and non-working kernel. Alexandre "Sunny" Kovalenko. From owner-freebsd-acpi@FreeBSD.ORG Sat Jul 24 22:13:48 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 AE48916A568 for ; Sat, 24 Jul 2004 22:13:48 +0000 (GMT) Received: from gateway.nixsys.be (gateway.nixsys.be [195.144.77.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EBA143D2F for ; Sat, 24 Jul 2004 22:13:48 +0000 (GMT) (envelope-from philip@paeps.cx) Received: from erda.home.paeps.cx (erda.home.paeps.cx [IPv6:2001:838:37f:10::1]) by gateway.nixsys.be (Postfix) with ESMTP id 0EDF558 for ; Sun, 25 Jul 2004 00:13:46 +0200 (CEST) Received: from fasolt.home.paeps.cx (fasolt.home.paeps.cx [10.0.0.2]) by erda.home.paeps.cx (Postfix) with ESMTP id 569762149 for ; Sun, 25 Jul 2004 00:13:40 +0200 (CEST) Received: from fasolt.home.paeps.cx (philip@localhost [127.0.0.1]) by fasolt.home.paeps.cx (8.12.11/8.12.11) with ESMTP id i6OMDjKE086674 for ; Sun, 25 Jul 2004 00:13:45 +0200 (CEST) (envelope-from philip@fasolt.home.paeps.cx) Received: (from philip@localhost) by fasolt.home.paeps.cx (8.12.11/8.12.11/Submit) id i6OMDiN0086673 for acpi@FreeBSD.org; Sun, 25 Jul 2004 00:13:44 +0200 (CEST) (envelope-from philip) Date: Sun, 25 Jul 2004 00:13:44 +0200 From: Philip Paeps To: acpi@FreeBSD.org Message-ID: <20040724221344.GE85709@fasolt.home.paeps.cx> Mail-Followup-To: acpi@FreeBSD.org References: <20040712.200815.74734634.nyan@jp.FreeBSD.org> <86llhpz354.wl.t-ogawa@triaez.kaisei.org> <20040713.011631.74707278.nyan@jp.FreeBSD.org> <20040717.183512.74706779.nyan@jp.FreeBSD.org> <86hds6njph.wl.t-ogawa@triaez.kaisei.org> <40FE9BEA.7060802@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40FE9BEA.7060802@root.org> X-Date-in-Rome: ante diem IX Kalendas Augustas MMDCCLVII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! User-Agent: Mutt/1.5.6i Subject: Generic hotkey script (was: Re: Panasonic acpi driver) 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, 24 Jul 2004 22:13:48 -0000 On 2004-07-21 09:38:02 (-0700), Nate Lawson wrote: > I don't want us to import any device-specific hotkey scripts (i.e., asus, > panasonic, toshiba, etc.) but instead have a single general-purpose script > and have the kernel translate device-specific tables of hotkey values to > generic ones. That way a single script can look for the generic "volume > up/down" buttons and act accordingly. > > Please email me if you're interested in working on that. I've been thinking about this a while ago, but it somehow got itself stuck on my 'maybe later' stack. My idea was to have devd do the magic here. Agree on some constants (ACPI_VOLUME_UP, ACPI_VOLUME_MUTE, ACPI_HOTKEY_1,...) that the specific drivers could send to devd using acpi_UserNotify(). We could then have a devd script (much like we also have power_profile, or we could rename that to 'acpi_event' or something similar) to catch these events. notify 10 { match "system" "ACPI"; match "subsystem" "HOTKEY"; action "/etc/rc.d/acpi_event $notify"; }; To avoid having a notify section for every different device specific acpi driver, we could either have them all be ACPI_MODULE_NAME("HOTKEY"), or we could register them under an umbrella hotkey driver. The latter approach might be nicer. Then we could also add other non-acpi hotkey gadgets (ir remote controls maybe? :-)) under it? I'd be interested in hacking at this. - Philip -- Philip Paeps Please don't CC me, I am subscribed to the list. He who dies with the most toys wins.