From owner-freebsd-acpi@FreeBSD.ORG Sun May 23 07:56:38 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA2D416A4CF; Sun, 23 May 2004 07:56:38 -0700 (PDT) Received: from coruscant.rfc1149.org (coruscant.rfc1149.org [217.160.130.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 818C643D48; Sun, 23 May 2004 07:56:38 -0700 (PDT) (envelope-from arne@rfc2549.org) Received: by coruscant.rfc1149.org (Postfix, from userid 110) id 1D86C3F0E; Sun, 23 May 2004 16:56:21 +0200 (CEST) Received: from kamino.rfc1149.org (kamino.rfc1149.org [2001:8d8:81:11::2]) by coruscant.rfc1149.org (Postfix) with ESMTP id 59EDD3DA6; Sun, 23 May 2004 16:56:18 +0200 (CEST) Received: by kamino.rfc1149.org (Postfix, from userid 1001) id BC3F036F; Sun, 23 May 2004 16:56:16 +0200 (CEST) To: Peter Schuller In-Reply-To: <86wu349u54.fsf@kamino.rfc1149.org> (Arne Schwabe's message of "Sat, 22 May 2004 20:47:03 +0200") References: <863c5s20x9.fsf@kamino.rfc1149.org> <200405221635.05324.peter.schuller@infidyne.com> <86wu349u54.fsf@kamino.rfc1149.org> From: Arne Schwabe Date: Sun, 23 May 2004 16:56:16 +0200 Message-ID: <86hdu719bj.fsf@kamino.rfc1149.org> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on coruscant.rfc1149.org X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.60 X-Spam-Level: cc: acpi@freebsd.org cc: freebsd-mobile@freebsd.org Subject: Re: Very strange behavior of the special keys on a IBM T40 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, 23 May 2004 14:56:39 -0000 Arne Schwabe writes: >>> Would you by any chance be running with an extra ultra bay battery in place on >>> the CD/DVD? If so, try removing it (and rebooting). If you're having the same >>> problem I have on my T40p, that should eliminate the hangs. As a result I'm >>> almost never using the extra battery :( >> >> I have a extra ultra bay battery but I makes no difference. :/ >> >> Could you send me your kernel config, maybe I have something weird in >> my config? > > Okay, I tried your kernel config but the same result brightness > up/down freezes the kernel. > > Without acpi the kernel freezes after something like 1-2 minutes :( Well, I "narrowed" it down, my notebook is now *real* crazy, even with a 5.2.1 kernel (which worked :/) it now shows this behavior. I have now absoluty no idea what I could try next :/ Arne -- Ah, the beauty of OSS. Hundreds of volunteers worldwide volunteering their time inventing and implementing new exciting ways of old fashioned wheels. From owner-freebsd-acpi@FreeBSD.ORG Sun May 23 09:34:20 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 7631216A4CE for ; Sun, 23 May 2004 09:34:20 -0700 (PDT) Received: from smart.eusc.inter.net (smart.eusc.inter.net [213.73.101.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DFEA43D39 for ; Sun, 23 May 2004 09:34:20 -0700 (PDT) (envelope-from plexus@snafu.de) Received: from pd951736e.dip.t-dialin.net ([217.81.115.110] helo=[192.168.0.2]) by smart.eusc.inter.net with asmtp (Exim 3.36 #4) id 1BRvup-0002jU-00 for acpi@freebsd.org; Sun, 23 May 2004 18:33:35 +0200 Message-ID: <40B22412.6070503@snafu.de> Date: Mon, 24 May 2004 18:34:26 +0200 From: "Oliver B. Fischer" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040523 X-Accept-Language: en-us, en MIME-Version: 1.0 To: acpi@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: ThinkPad without support for S1 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, 23 May 2004 16:34:20 -0000 Hello list, I purchased a new ThinkPad, a R51. Unfortunately it seems so, that IBM removed the support for S1 from the BIOS. At least a call to acpiconf -s 1 results in the message "S1 not supported by BIOS" Is it allowed not to support S1? Regards, Oliver Fischer From owner-freebsd-acpi@FreeBSD.ORG Sun May 23 09:44: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 E07A916A4CE for ; Sun, 23 May 2004 09:44:54 -0700 (PDT) Received: from imap.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3654943D48 for ; Sun, 23 May 2004 09:44:54 -0700 (PDT) (envelope-from le@FreeBSD.org) Received: from wireless (adslle.cc.univie.ac.at [131.130.102.11]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id i4NGiNRo1297594; Sun, 23 May 2004 18:44:26 +0200 Date: Sun, 23 May 2004 18:44:22 +0200 (CEST) From: Lukas Ertl To: "Oliver B. Fischer" In-Reply-To: <40B22412.6070503@snafu.de> Message-ID: <20040523184327.Y643@korben> References: <40B22412.6070503@snafu.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mailbox 4247; Body=2 Fuz1=2 Fuz2=2 cc: acpi@FreeBSD.org Subject: Re: ThinkPad without support for S1 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, 23 May 2004 16:44:55 -0000 On Mon, 24 May 2004, Oliver B. Fischer wrote: > I purchased a new ThinkPad, a R51. Unfortunately it seems so, that IBM > removed the support for S1 from the BIOS. At least a call to > > acpiconf -s 1 > > results in the message "S1 not supported by BIOS" > > Is it allowed not to support S1? My T40 doesn't support S1, either. And I can't say I really miss it, since S3 works fine (or at least worked, until some PCI changes broke it). cheers, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-acpi@FreeBSD.ORG Sun May 23 09:52:03 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 36B0A16A4CF for ; Sun, 23 May 2004 09:52:03 -0700 (PDT) Received: from siudong.ath.cx (CPE0004ac237e6f-CM400048293705.cpe.net.cable.rogers.com [24.101.231.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0070343D2D for ; Sun, 23 May 2004 09:52:03 -0700 (PDT) (envelope-from necro@siudong.ath.cx) Received: from siudong.ath.cx (unknown [192.168.0.55]) by siudong.ath.cx (Postfix) with SMTP id 93C57144 for ; Sun, 23 May 2004 12:54:11 -0400 (EDT) Received: by siudong.ath.cx (sSMTP sendmail emulation); Sun, 23 May 2004 12:50:51 +0000 From: "Johnny Wong" Date: Sun, 23 May 2004 12:50:51 +0000 To: freebsd-acpi@freebsd.org Message-ID: <20040523125051.GA14072@siudong.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: freebsd laptops X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 May 2004 16:52:03 -0000 I'm just wondering which laptops and freebsd make good combination? I would like an laptop with as many supported hardware as possible, fully acpi support and around $1000 US. Any suggestion is welcome. thanks From owner-freebsd-acpi@FreeBSD.ORG Sun May 23 10:23:51 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 E836816A4CE; Sun, 23 May 2004 10:23:51 -0700 (PDT) Received: from havoc.eusc.inter.net (havoc.eusc.inter.net [213.73.101.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id B186E43D46; Sun, 23 May 2004 10:23:51 -0700 (PDT) (envelope-from plexus@snafu.de) Received: from pd951736e.dip.t-dialin.net ([217.81.115.110] helo=[192.168.0.2]) by havoc.eusc.inter.net with asmtp (Exim 3.36 #3) id 1BRwhS-0001eF-00; Sun, 23 May 2004 19:23:50 +0200 Message-ID: <40B22FD6.8030903@snafu.de> Date: Mon, 24 May 2004 19:24:38 +0200 From: "Oliver B. Fischer" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040523 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lukas Ertl References: <40B22412.6070503@snafu.de> <20040523184327.Y643@korben> In-Reply-To: <20040523184327.Y643@korben> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@freebsd.org Subject: Re: ThinkPad without support for S1 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, 23 May 2004 17:23:52 -0000 When did it happen? Is 5.2.1 affected? Oliver Lukas Ertl wrote: > My T40 doesn't support S1, either. And I can't say I really miss it, > since S3 works fine (or at least worked, until some PCI changes broke it). From owner-freebsd-acpi@FreeBSD.ORG Sun May 23 10:24:53 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 3274016A4CE for ; Sun, 23 May 2004 10:24:53 -0700 (PDT) Received: from imap.univie.ac.at (mailbox-lmtp.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B2EE43D2D for ; Sun, 23 May 2004 10:24:52 -0700 (PDT) (envelope-from le@FreeBSD.org) Received: from wireless (adslle.cc.univie.ac.at [131.130.102.11]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id i4NHObIx1091790; Sun, 23 May 2004 19:24:39 +0200 Date: Sun, 23 May 2004 19:24:37 +0200 (CEST) From: Lukas Ertl To: "Oliver B. Fischer" In-Reply-To: <40B22FD6.8030903@snafu.de> Message-ID: <20040523192425.K643@korben> References: <40B22412.6070503@snafu.de> <20040523184327.Y643@korben> <40B22FD6.8030903@snafu.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: imap 4248; Body=2 Fuz1=2 Fuz2=2 cc: acpi@FreeBSD.org Subject: Re: ThinkPad without support for S1 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, 23 May 2004 17:24:53 -0000 On Mon, 24 May 2004, Oliver B. Fischer wrote: > When did it happen? Is 5.2.1 affected? 5.2.1 should be fine. cheers, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-acpi@FreeBSD.ORG Sun May 23 11:21:06 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D021916A4CE for ; Sun, 23 May 2004 11:21:06 -0700 (PDT) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CB3D43D39 for ; Sun, 23 May 2004 11:21:06 -0700 (PDT) (envelope-from nork@FreeBSD.org) Received: from nadesico.ninth-nine.com (nadesico.ninth-nine.com [219.127.74.122]) by sakura.ninth-nine.com (8.12.11/8.12.11/NinthNine) with ESMTP id i4NIK5dD067452 for ; Mon, 24 May 2004 03:20:05 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Mon, 24 May 2004 03:20:05 +0900 From: Norikatsu Shigemura To: acpi@FreeBSD.org Message-Id: <20040524032005.57981dbe.nork@FreeBSD.org> X-Mailer: Sylpheed version 0.9.9-gtk2-20040229 (GTK+ 2.4.1; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: FYI: S3 resume almost works 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, 23 May 2004 18:21:06 -0000 I tested S3 suspend/resume on 5-current(2004-05-20) of my notePC. And I was watching on ping/ssh/dconschat/X terminal. # Sharp PC-MT2-F1 (Mobile PentiumIII 1GHz - i830MG) 1. resume is already ok. 2. suspend is almost works. a. X is bad. In xdm, I can suspend. If Xapp is running, suspend is not work. I didn't test with console (no X). b. dcons_crom cannot use. notePC connects to network with if_fwe. ping is ok, so firewire is ok. Maybe dcons_crom is not re-init on resume. I did fwcontrol -r, so I can re-use dcons_crom. c. pcm is set 22050Hz fixed. I can play sound, but hear twice tiems high speed sound:-). But, I can connect with ssh and can use some commands. 3. special parameter In my environment, I can use these parameter. $ sysctl hw.syscons.sc_no_suspend_vtswitch hw.acpi.reset_video hw.syscons.sc_no_suspend_vtswitch: 1 hw.acpi.reset_video: 0 Another parameter(e.g. reset_video=1) doesn't work. From owner-freebsd-acpi@FreeBSD.ORG Sun May 23 12:43:51 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 81BDE16A4CE for ; Sun, 23 May 2004 12:43:51 -0700 (PDT) Received: from havoc.eusc.inter.net (havoc.eusc.inter.net [213.73.101.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36E5E43D45 for ; Sun, 23 May 2004 12:43:49 -0700 (PDT) (envelope-from plexus@snafu.de) Received: from pd9e0e0fe.dip.t-dialin.net ([217.224.224.254] helo=[192.168.0.2]) by havoc.eusc.inter.net with asmtp (Exim 3.36 #3) id 1BRysu-0003If-00 for acpi@freebsd.org; Sun, 23 May 2004 21:43:48 +0200 Message-ID: <40B250A6.3050709@snafu.de> Date: Mon, 24 May 2004 21:44:38 +0200 From: "Oliver B. Fischer" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040523 X-Accept-Language: en-us, en MIME-Version: 1.0 To: acpi@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Problems with S3 on ThinkPad R51 1830 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, 23 May 2004 19:43:51 -0000 Hallo, I can't resume properly from S3. Everything works fine except for the USB subsystem, which doesn't work. The error message is: uhub0: illegal enable change, port 2 uhub0: illegal enable change, port 1 What can I do? Regards, Oliver Additional information (asl, sysctls...) can be found at http://www.xshare.com/acpi2/ From owner-freebsd-acpi@FreeBSD.ORG Sun May 23 21:02: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 87C4316A4CE for ; Sun, 23 May 2004 21:02:01 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 5CEDE43D2F for ; Sun, 23 May 2004 21:02:01 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 66630 invoked by uid 1000); 24 May 2004 03:59:34 -0000 Date: Sun, 23 May 2004 20:59:34 -0700 (PDT) From: Nate Lawson To: "Oliver B. Fischer" In-Reply-To: <40B22FD6.8030903@snafu.de> Message-ID: <20040523205842.Q66525@root.org> References: <40B22412.6070503@snafu.de> <20040523184327.Y643@korben> <40B22FD6.8030903@snafu.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org Subject: Re: ThinkPad without support for S1 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, 24 May 2004 04:02:01 -0000 On Mon, 24 May 2004, Oliver B. Fischer wrote: > When did it happen? Is 5.2.1 affected? > > Oliver > > Lukas Ertl wrote: > > My T40 doesn't support S1, either. And I can't say I really miss it, > > since S3 works fine (or at least worked, until some PCI changes broke it). Most modern laptops don't offer S1. As the message told you, the BIOS does not support S1. S3 is better than S1 in terms of power savings. None of this is FreeBSD's fault. -Nate From owner-freebsd-acpi@FreeBSD.ORG Sun May 23 21:05:31 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 77E9A16A4CE for ; Sun, 23 May 2004 21:05:31 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 36DA043D1F for ; Sun, 23 May 2004 21:05:31 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 66677 invoked by uid 1000); 24 May 2004 04:05:02 -0000 Date: Sun, 23 May 2004 21:05:02 -0700 (PDT) From: Nate Lawson To: "Oliver B. Fischer" In-Reply-To: <40B250A6.3050709@snafu.de> Message-ID: <20040523210006.Y66525@root.org> References: <40B250A6.3050709@snafu.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org Subject: Re: Problems with S3 on ThinkPad R51 1830 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, 24 May 2004 04:05:31 -0000 On Mon, 24 May 2004, Oliver B. Fischer wrote: > Hallo, > > I can't resume properly from S3. Everything works fine except for the > USB subsystem, which doesn't work. > > The error message is: > uhub0: illegal enable change, port 2 > uhub0: illegal enable change, port 1 > > What can I do? > > Regards, > > Oliver > > Additional information (asl, sysctls...) can be found at > > http://www.xshare.com/acpi2/ UHCI can't suspend/resume correctly. It's a driver issue. You can save power by modifying the performance/economy values from /etc/defaults/rc.conf -Nate From owner-freebsd-acpi@FreeBSD.ORG Sun May 23 21:06:34 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 AD48216A4CE for ; Sun, 23 May 2004 21:06:34 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 812F943D1F for ; Sun, 23 May 2004 21:06:34 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 66692 invoked by uid 1000); 24 May 2004 04:06:03 -0000 Date: Sun, 23 May 2004 21:06:03 -0700 (PDT) From: Nate Lawson To: Johnny Wong In-Reply-To: <20040523125051.GA14072@siudong.ath.cx> Message-ID: <20040523210515.Y66525@root.org> References: <20040523125051.GA14072@siudong.ath.cx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: freebsd laptops X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 May 2004 04:06:34 -0000 On Sun, 23 May 2004, Johnny Wong wrote: > I'm just wondering which laptops and freebsd make good combination? I would like an laptop with as many supported > hardware as possible, fully acpi support and around $1000 US. Any suggestion is welcome. > thanks I use Thinkpads and generally like them. ASUS sometimes has problems but many of theirs are good. -Nate From owner-freebsd-acpi@FreeBSD.ORG Sun May 23 23:41:55 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 715DC16A4CE for ; Sun, 23 May 2004 23:41:55 -0700 (PDT) Received: from havoc.eusc.inter.net (havoc.eusc.inter.net [213.73.101.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C17C43D2D for ; Sun, 23 May 2004 23:41:55 -0700 (PDT) (envelope-from plexus@snafu.de) Received: from pd9eb1f0a.dip.t-dialin.net ([217.235.31.10] helo=[192.168.0.2]) by havoc.eusc.inter.net with asmtp (Exim 3.36 #3) id 1BS99U-0003kE-00; Mon, 24 May 2004 08:41:36 +0200 Message-ID: <40B2EAD4.3010709@snafu.de> Date: Tue, 25 May 2004 08:42:28 +0200 From: "Oliver B. Fischer" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040523 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <40B250A6.3050709@snafu.de> <20040523210006.Y66525@root.org> In-Reply-To: <20040523210006.Y66525@root.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@freebsd.org Subject: Re: Problems with S3 on ThinkPad R51 1830 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, 24 May 2004 06:41:55 -0000 Nate Lawson wrote: > UHCI can't suspend/resume correctly. It's a driver issue. Does it mean that my usb subsystem and S3 can't go on with each other? > You can save power by modifying the performance/economy values from > /etc/defaults/rc.conf I took a look at defaults/rc.conf and didn't find/see a value, that seems to be responsible for performance or economy. Please, can you give me a hint? :) Regards, Oliver Fischer From owner-freebsd-acpi@FreeBSD.ORG Mon May 24 00:04: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 E0D8616A4CE for ; Mon, 24 May 2004 00:04:54 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 9966243D2D for ; Mon, 24 May 2004 00:04:54 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 67489 invoked by uid 1000); 24 May 2004 07:04:35 -0000 Date: Mon, 24 May 2004 00:04:35 -0700 (PDT) From: Nate Lawson To: "Oliver B. Fischer" In-Reply-To: <40B2EAD4.3010709@snafu.de> Message-ID: <20040524000254.L67471@root.org> References: <40B250A6.3050709@snafu.de> <20040523210006.Y66525@root.org> <40B2EAD4.3010709@snafu.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org Subject: Re: Problems with S3 on ThinkPad R51 1830 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, 24 May 2004 07:04:55 -0000 On Tue, 25 May 2004, Oliver B. Fischer wrote: > Nate Lawson wrote: > > UHCI can't suspend/resume correctly. It's a driver issue. > > Does it mean that my usb subsystem and S3 can't go on with each other? Don't load usb if using suspend/resume. > > You can save power by modifying the performance/economy values from > > /etc/defaults/rc.conf > > I took a look at defaults/rc.conf and didn't find/see a value, that > seems to be responsible for performance or economy. Please, can you give > me a hint? :) /etc/defaults/rc.conf: performance_cx_lowest="HIGH" # Online CPU idle state performance_throttle_state="HIGH" # Online throttling state economy_cx_lowest="LOW" # Offline CPU idle state economy_throttle_state="HIGH" # Offline throttling state You could make your system run cooler while on AC power with: echo 'performance_cx_lowest="LOW"' >> /etc/rc.conf You can also use literal values, i.e. "C3" -Nate From owner-freebsd-acpi@FreeBSD.ORG Mon May 24 00:19: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 23BD316A4CE for ; Mon, 24 May 2004 00:19:45 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id ECC4243D1D for ; Mon, 24 May 2004 00:19:44 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 67538 invoked by uid 1000); 24 May 2004 07:19:05 -0000 Date: Mon, 24 May 2004 00:19:05 -0700 (PDT) From: Nate Lawson To: "Oliver B. Fischer" In-Reply-To: <20040524000254.L67471@root.org> Message-ID: <20040524001827.A67471@root.org> References: <40B250A6.3050709@snafu.de> <20040523210006.Y66525@root.org> <40B2EAD4.3010709@snafu.de> <20040524000254.L67471@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org Subject: Re: Problems with S3 on ThinkPad R51 1830 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, 24 May 2004 07:19:45 -0000 On Mon, 24 May 2004, Nate Lawson wrote: > You could make your system run cooler while on AC power with: > echo 'performance_cx_lowest="LOW"' >> /etc/rc.conf > > You can also use literal values, i.e. "C3" Actually, you're on 5.2.1 so "C3" is the magic value "2". See settings for sysctl hw.acpi.cpu -Nate From owner-freebsd-acpi@FreeBSD.ORG Mon May 24 02:11:13 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 002FE16A4CE for ; Mon, 24 May 2004 02:11:12 -0700 (PDT) Received: from havoc.eusc.inter.net (havoc.eusc.inter.net [213.73.101.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACB7443D3F for ; Mon, 24 May 2004 02:11:12 -0700 (PDT) (envelope-from plexus@snafu.de) Received: from pd9517df7.dip.t-dialin.net ([217.81.125.247] helo=[192.168.0.2]) by havoc.eusc.inter.net with asmtp (Exim 3.36 #3) id 1BSBTq-0003Sn-00; Mon, 24 May 2004 11:10:46 +0200 Message-ID: <40B30DC9.4080804@snafu.de> Date: Tue, 25 May 2004 11:11:37 +0200 From: "Oliver B. Fischer" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040523 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <40B250A6.3050709@snafu.de> <20040523210006.Y66525@root.org> In-Reply-To: <20040523210006.Y66525@root.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@freebsd.org Subject: Re: Problems with S3 on ThinkPad R51 1830 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, 24 May 2004 09:11:13 -0000 Nate Lawson wrote: > UHCI can't suspend/resume correctly. It's a driver issue. Is it planed to solve this problem? I haven't found an pr for it. Regards, Oliver Fischer From owner-freebsd-acpi@FreeBSD.ORG Mon May 24 10:02:40 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 78FB116A4D0 for ; Mon, 24 May 2004 10:02:40 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 578D243D3F for ; Mon, 24 May 2004 10:02:40 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 70625 invoked by uid 1000); 24 May 2004 17:02:15 -0000 Date: Mon, 24 May 2004 10:02:15 -0700 (PDT) From: Nate Lawson To: "Oliver B. Fischer" In-Reply-To: <40B30DC9.4080804@snafu.de> Message-ID: <20040524100133.E70614@root.org> References: <40B250A6.3050709@snafu.de> <20040523210006.Y66525@root.org> <40B30DC9.4080804@snafu.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org Subject: Re: Problems with S3 on ThinkPad R51 1830 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, 24 May 2004 17:02:40 -0000 On Tue, 25 May 2004, Oliver B. Fischer wrote: > Nate Lawson wrote: > > UHCI can't suspend/resume correctly. It's a driver issue. > > Is it planed to solve this problem? I haven't found an pr for it. Bring it up on -current. NetBSD and Linux both have problems with UHCI also on some chipsets so it's unclear how to fix it in the general case. -Nate From owner-freebsd-acpi@FreeBSD.ORG Mon May 24 11:01:50 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5F3D16A4DB for ; Mon, 24 May 2004 11:01:50 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB7D443D55 for ; Mon, 24 May 2004 11:01:50 -0700 (PDT) (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 i4OI1kd0076506 for ; Mon, 24 May 2004 11:01:46 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i4OI1jhx076500 for freebsd-acpi@freebsd.org; Mon, 24 May 2004 11:01:45 -0700 (PDT) (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 24 May 2004 11:01:45 -0700 (PDT) Message-Id: <200405241801.i4OI1jhx076500@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, 24 May 2004 18:01:51 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/09/09] 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/16] 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 2 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon May 24 20:12:55 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 517C016A4CE for ; Mon, 24 May 2004 20:12:55 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 3629B43D39 for ; Mon, 24 May 2004 20:12:55 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 73637 invoked by uid 1000); 25 May 2004 03:12:23 -0000 Date: Mon, 24 May 2004 20:12:23 -0700 (PDT) From: Nate Lawson To: current@freebsd.org Message-ID: <20040524201046.C73624@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org Subject: ACPI-CA 20040514 import 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, 25 May 2004 03:12:55 -0000 This commit fixes the immediate resume upon second suspend problem that Thinkpads had with the last import. Leaving the shared GPE disabled at runtime caused this problem. There are some other nice fixes so please cvsup and test. -Nate ---------- Forwarded message ---------- njl 2004/05/24 19:34:55 PDT FreeBSD src repository src/sys/contrib/dev/acpica - Imported sources Update of /home/ncvs/src/sys/contrib/dev/acpica In directory repoman.freebsd.org:/tmp/cvs-serv16472 Log Message: Vendor import of Intel ACPI-CA 20040514. Status: Vendor Tag: INTEL Release Tags: r20040514 From owner-freebsd-acpi@FreeBSD.ORG Mon May 24 22:09: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 A0B6216A4CE; Mon, 24 May 2004 22:09:24 -0700 (PDT) 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 1D61843D2F; Mon, 24 May 2004 22:09:24 -0700 (PDT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.6] (ppp-67-38-164-11.dsl.wotnoh.ameritech.net [67.38.164.11]) (authenticated bits=0)i4P53QWB058755 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 25 May 2004 01:03:28 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-acpi@freebsd.org Date: Tue, 25 May 2004 01:08:54 -0400 User-Agent: KMail/1.6.2 References: <20040524201046.C73624@root.org> In-Reply-To: <20040524201046.C73624@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200405250108.56959.mistry.7@osu.edu> X-Spam-Status: No, hits=-4.4 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE, QUOTED_EMAIL_TEXT,RCVD_IN_NJABL,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_KMAIL,X_NJABL_DIALUP version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: Nate Lawson Subject: Re: ACPI-CA 20040514 import 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, 25 May 2004 05:09:24 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 24 May 2004 11:12 pm, Nate Lawson wrote: > This commit fixes the immediate resume upon second suspend problem that > Thinkpads had with the last import. Leaving the shared GPE disabled at > runtime caused this problem. There are some other nice fixes so please > cvsup and test. > > -Nate My lid switch events aren't working. I have to suspend the system (S3) usi= ng=20 acpiconf -s 3 then resume, and then the lid switch events start to work=20 again. http://am-productions.biz/debug/littleguy.asl =2D --=20 Anish Mistry =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAstTmxqA5ziudZT0RAiedAKDLTbiH8aTHZiXSPezKLp6ZKeSmYgCdGYzG lvRrNSpMgGhibYWrS/q0seI=3D =3DNLYg =2D----END PGP SIGNATURE----- From owner-freebsd-acpi@FreeBSD.ORG Tue May 25 05:41: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 3DF2D16A4CF; Tue, 25 May 2004 05:41:01 -0700 (PDT) Received: from imap.univie.ac.at (mailbox-lmtp.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4967343D54; Tue, 25 May 2004 05:41:00 -0700 (PDT) (envelope-from le@FreeBSD.org) Received: from pcle2.cc.univie.ac.at (pcle2.cc.univie.ac.at [131.130.2.177]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id i4PCelHd1235434; Tue, 25 May 2004 14:40:48 +0200 Date: Tue, 25 May 2004 14:40:47 +0200 (CEST) From: Lukas Ertl To: Nate Lawson In-Reply-To: <20040524201046.C73624@root.org> Message-ID: <20040525144015.X35966@pcle2.cc.univie.ac.at> References: <20040524201046.C73624@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mailbox 4247; Body=3 Fuz1=3 Fuz2=3 cc: acpi@FreeBSD.org cc: current@FreeBSD.org Subject: Re: ACPI-CA 20040514 import 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, 25 May 2004 12:41:01 -0000 On Mon, 24 May 2004, Nate Lawson wrote: > This commit fixes the immediate resume upon second suspend problem that > Thinkpads had with the last import. Leaving the shared GPE disabled at > runtime caused this problem. There are some other nice fixes so please > cvsup and test. Very nice, thank you, Nate! My T40 seems to suspend/resume fine again. cheers, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-acpi@FreeBSD.ORG Tue May 25 09:19:17 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 8ECBD16A4CE for ; Tue, 25 May 2004 09:19:17 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 49C8043D48 for ; Tue, 25 May 2004 09:19:17 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 77338 invoked by uid 1000); 25 May 2004 16:19:03 -0000 Date: Tue, 25 May 2004 09:19:03 -0700 (PDT) From: Nate Lawson To: Anish Mistry In-Reply-To: <200405250108.56959.mistry.7@osu.edu> Message-ID: <20040525091755.Q77324@root.org> References: <20040524201046.C73624@root.org> <200405250108.56959.mistry.7@osu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: ACPI-CA 20040514 import 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, 25 May 2004 16:19:17 -0000 On Tue, 25 May 2004, Anish Mistry wrote: > On Monday 24 May 2004 11:12 pm, Nate Lawson wrote: > > This commit fixes the immediate resume upon second suspend problem that > > Thinkpads had with the last import. Leaving the shared GPE disabled at > > runtime caused this problem. There are some other nice fixes so please > > cvsup and test. > > > > -Nate > > My lid switch events aren't working. I have to suspend the system (S3) using > acpiconf -s 3 then resume, and then the lid switch events start to work > again. > http://am-productions.biz/debug/littleguy.asl I just committed a workaround that should fix this. Pick up these: Revision Changes Path 1.23 +3 -1 src/sys/dev/acpica/acpi_button.c 1.19 +3 -1 src/sys/dev/acpica/acpi_lid.c -Nate From owner-freebsd-acpi@FreeBSD.ORG Tue May 25 10:37:00 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 19D7616A4CE for ; Tue, 25 May 2004 10:37:00 -0700 (PDT) Received: from mailbox.rainbownet.com (mailbox.rainbownet.com [213.174.191.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id A062143D49 for ; Tue, 25 May 2004 10:36:58 -0700 (PDT) (envelope-from aturetta@commit.it) Received: from nbangx ([81.208.52.78]) (authenticated user aturetta@rainbownet.com) by rainbownet.com (rainbownet.com [127.0.0.1]) (MDaemon.PRO.v6.8.5.R) with ESMTP id 60-md50000000106.tmp for ; Tue, 25 May 2004 19:35:31 +0200 Message-ID: <004001c4427e$ad581540$5a21a8c0@lan> From: "Angelo Turetta" To: References: <00c501c43d00$973c43e0$661da8c0@lan> <20040518223653.D31178@root.org> Date: Tue, 25 May 2004 19:35:30 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Authenticated-Sender: aturetta@rainbownet.com X-Spam-Processed: rainbownet.com, Tue, 25 May 2004 19:35:31 +0200 (not processed: message from valid local sender) X-MDRemoteIP: 81.208.52.78 X-Return-Path: aturetta@commit.it X-MDaemon-Deliver-To: freebsd-acpi@freebsd.org Subject: Re: Panic during halt -p 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, 25 May 2004 17:37:00 -0000 > ----- Original Message ----- > From: "Nate Lawson" > Sent: Wednesday, May 19, 2004 7:37 AM > > On Tue, 18 May 2004, Angelo Turetta wrote: > > A couple weeks ago I installed a system from the ISO image > > 5.2-CURRENT-20040428-JPSNAP, on a new HP DL380G3. The system is stable (not > > much load for now), all the devices are detected correctly. > > > > The only problem is that I cannot power the system off using ACPI: if I type > > 'halt -p', the shutdown is executed correctly (OS-wise), but then I get: > > > It would really help me if at the debugger prompt you typed "tr" to get a > backtrace and sent me the function list. > > You definitely should try a newer snapshot than 2004/4/28 also. > > -Nate You were right, I upgraded to Current built this morning, and the panic went away: the system now correctly shuts down in response to both 'halt -p' and the soft-off button. Ciao, Angelo Turetta. From owner-freebsd-acpi@FreeBSD.ORG Tue May 25 13:13:42 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 041DF16A4CE for ; Tue, 25 May 2004 13:13:42 -0700 (PDT) Received: from moutvdomng.kundenserver.de (moutvdom.kundenserver.de [212.227.126.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id E03EF43D49 for ; Tue, 25 May 2004 13:13:40 -0700 (PDT) (envelope-from liamfoy@sepulcrum.org) Received: from [212.227.126.224] (helo=mrvdomng.kundenserver.de) by moutvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BSiIZ-0004y1-00 for freebsd-acpi@freebsd.org; Tue, 25 May 2004 22:13:19 +0200 Received: from [217.43.131.157] (helo=liamfoy.ath.cx) by mrvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BSiIZ-000849-00 for freebsd-acpi@freebsd.org; Tue, 25 May 2004 22:13:19 +0200 Date: Tue, 25 May 2004 21:12:20 +0100 From: "Liam J. Foy" To: freebsd-acpi@freebsd.org Message-Id: <20040525211220.6f349011.liamfoy@sepulcrum.org> X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: APM Patch - review 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, 25 May 2004 20:13:42 -0000 Hey guys, Just writing to request your views on a patch I have wrote for apm. This patch makes sure single options such as apm -l have their values checked. The print_all_info function seems to do this, so I imagine it should be done for single options also. The single options will return 255 when device is unsupported, -1 when an invalid value and anything else is the correct value. I would love any feedback. Thanks guys, Liam Foy --- /usr/src/usr.sbin/apm/apm.c Sat May 22 17:18:57 2004 +++ /hd3/apm/apm.c Tue May 25 20:24:39 2004 @@ -33,6 +33,8 @@ #include #define APMDEV "/dev/apm" +#define UNKNOWN 255 /* Unknown/unsupported by device */ +#define INVALID -1 /* We return -1 on invalid values for single options */ #define xh(a) (((a) & 0xff00) >> 8) #define xl(a) ((a) & 0xff) @@ -143,55 +145,137 @@ } } -void -print_all_info(int fd, apm_info_t aip, int bioscall_available) +void +print_batt_acline(u_int acline, int return_choice) { - struct apm_bios_arg args; - int apmerr; - - printf("APM version: %d.%d\n", aip->ai_major, aip->ai_minor); - printf("APM Management: %s\n", (aip->ai_status ? "Enabled" : "Disabled")); - printf("AC Line status: "); - if (aip->ai_acline == 255) - printf("unknown"); - else if (aip->ai_acline > 1) - printf("invalid value (0x%x)", aip->ai_acline); + if (acline == UNKNOWN) + if (return_choice) + printf("unknown\n"); + else + printf("%d\n", UNKNOWN); + else if (acline > 1) + if (return_choice) + printf("invalid value 0x%x (%d)\n", acline, acline); + else + printf("%d\n", INVALID); else { - char *messages[] = { "off-line", "on-line" }; - printf("%s", messages[aip->ai_acline]); + if (return_choice) { + char *messages[] = { "off-line", "on-line" }; + printf("%s\n", messages[acline]); + } else + printf("%d\n", acline); } - printf("\n"); - printf("Battery status: "); - if (aip->ai_batt_stat == 255) - printf("unknown"); - else if (aip->ai_batt_stat > 3) - printf("invalid value (0x%x)", aip->ai_batt_stat); +} + +void +print_batt_stat(u_int batt_stat, int return_choice) +{ + if (batt_stat == UNKNOWN) + if (return_choice) + printf("unknown\n"); + else + printf("%d\n", UNKNOWN); + else if (batt_stat > 3) + if (return_choice) + printf("invalid value 0x%x (%d)\n", batt_stat, batt_stat); + else + printf("%d\n", INVALID); else { - char *messages[] = { "high", "low", "critical", "charging" }; - printf("%s", messages[aip->ai_batt_stat]); + if (return_choice) { + char *messages[] = { "high", "low", "critical", "charging" }; + printf("%s\n", messages[batt_stat]); + } else + printf("%d\n", batt_stat); } - printf("\n"); - printf("Remaining battery life: "); - if (aip->ai_batt_life == 255) - printf("unknown\n"); - else if (aip->ai_batt_life <= 100) - printf("%d%%\n", aip->ai_batt_life); +} + +void +print_batt_life(u_int batt_life, int return_choice) +{ + if (batt_life == UNKNOWN) + if (return_choice) + printf("unknown\n"); + else + printf("%d\n", UNKNOWN); + else if (batt_life >= 0 && batt_life <= 100) + if (return_choice) + printf("%d%%\n", batt_life); + else + printf("%d\n", batt_life); else - printf("invalid value (0x%x)\n", aip->ai_batt_life); - printf("Remaining battery time: "); - if (aip->ai_batt_time == -1) - printf("unknown\n"); + if (return_choice) + printf("invalid value 0x%x (%d)\n", batt_life, batt_life); + else + printf("%d\n", INVALID); +} + +void +print_batt_time(int time_seconds,int return_choice) +{ + if (time_seconds == -1) + if (return_choice) + printf("unknown\n"); + else + printf("%d\n", UNKNOWN); else { int t, h, m, s; - - t = aip->ai_batt_time; + + t = time_seconds; s = t % 60; t /= 60; m = t % 60; t /= 60; h = t; - printf("%2d:%02d:%02d\n", h, m, s); + + if (return_choice) + printf("%2d:%02d:%02d\n", h, m, s); + else + printf("%d\n", time_seconds); } +} + +void +print_apm_status(u_int apm_status, int return_choice) +{ + if (apm_status == 1) + if (return_choice) + printf("enabled\n"); + else + printf("%d\n", apm_status); + else if (apm_status == 0) + if(return_choice) + printf("disabled\n"); + else + printf("%d\n", apm_status); + else + if (return_choice) + printf("invalid value 0x%x (%d)\n", apm_status, apm_status); + else + printf("%d\n", INVALID); +} + +void +print_all_info(int fd, apm_info_t aip, int bioscall_available) +{ + struct apm_bios_arg args; + int apmerr; + + printf("APM version: %d.%d\n", aip->ai_major, aip->ai_minor); + printf("APM Management: "); + print_apm_status(aip->ai_status, 1); + + printf("AC Line status: "); + print_batt_acline(aip->ai_acline, 1); + + printf("Battery status: "); + print_batt_stat(aip->ai_batt_stat, 1); + + printf("Remaining battery life: "); + print_batt_life(aip->ai_batt_life, 1); + + printf("Remaining battery time: "); + print_batt_time(aip->ai_batt_time, 1); + if (aip->ai_infoversion >= 1) { printf("Number of batteries: "); if (aip->ai_batteries == (u_int) -1) @@ -208,46 +292,19 @@ continue; printf("Battery %d:\n", i); printf("\tBattery status: "); - if (aps.ap_batt_flag != 255 && + if (aps.ap_batt_flag != UNKNOWN && (aps.ap_batt_flag & APM_BATT_NOT_PRESENT)) { printf("not present\n"); continue; } - if (aps.ap_batt_stat == 255) - printf("unknown\n"); - else if (aps.ap_batt_stat > 3) - printf("invalid value (0x%x)\n", - aps.ap_batt_stat); - else { - char *messages[] = { "high", - "low", - "critical", - "charging" }; - printf("%s\n", - messages[aps.ap_batt_stat]); - } + + print_batt_stat(aps.ap_batt_stat, 1); + printf("\tRemaining battery life: "); - if (aps.ap_batt_life == 255) - printf("unknown\n"); - else if (aps.ap_batt_life <= 100) - printf("%d%%\n", aps.ap_batt_life); - else - printf("invalid value (0x%x)\n", - aps.ap_batt_life); + print_batt_life(aps.ap_batt_life, 1); + printf("\tRemaining battery time: "); - if (aps.ap_batt_time == -1) - printf("unknown\n"); - else { - int t, h, m, s; - - t = aps.ap_batt_time; - s = t % 60; - t /= 60; - m = t % 60; - t /= 60; - h = t; - printf("%2d:%02d:%02d\n", h, m, s); - } + print_batt_time(aps.ap_batt_time, 1); } } } @@ -496,19 +553,18 @@ if (all_info) print_all_info(fd, &info, bioscall_available); if (ac_status) - printf("%d\n", info.ai_acline); + print_batt_acline(info.ai_acline, 0); if (batt_status) - printf("%d\n", info.ai_batt_stat); + print_batt_stat(info.ai_batt_stat, 0); if (batt_life) - printf("%d\n", info.ai_batt_life); + print_batt_life(info.ai_batt_life, 0); if (apm_status) - printf("%d\n", info.ai_status); + print_apm_status(info.ai_status, 0); if (batt_time) - printf("%d\n", info.ai_batt_time); + print_batt_time(info.ai_batt_time, 0); if (display != -1) apm_display(fd, display); } close(fd); exit(0); } - From owner-freebsd-acpi@FreeBSD.ORG Tue May 25 14:14:17 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 3E3E816A4CE; Tue, 25 May 2004 14:14:17 -0700 (PDT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2370943D1D; Tue, 25 May 2004 14:14:17 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465; Tue, 25 May 2004 14:13:25 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 008F05D08; Tue, 25 May 2004 14:13:24 -0700 (PDT) To: Nate Lawson In-reply-to: Your message of "Mon, 24 May 2004 20:12:23 PDT." <20040524201046.C73624@root.org> Date: Tue, 25 May 2004 14:13:24 -0700 From: "Kevin Oberman" Message-Id: <20040525211324.008F05D08@ptavv.es.net> cc: acpi@freebsd.org cc: current@freebsd.org Subject: Re: ACPI-CA 20040514 import 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, 25 May 2004 21:14:17 -0000 > Date: Mon, 24 May 2004 20:12:23 -0700 (PDT) > From: Nate Lawson > Sender: owner-freebsd-acpi@freebsd.org > > This commit fixes the immediate resume upon second suspend problem that > Thinkpads had with the last import. Leaving the shared GPE disabled at > runtime caused this problem. There are some other nice fixes so please > cvsup and test. This did the trick for my T30. I can now suspend and resume repeatedly. I think that I am now down to a single resume problem (assuming jhb commits the acpi_video patches to support DPMS) and that's one that imp actually fixed once with his initial PCI power code commit. I had assumed that, once he had the power code all back in the tree (with fixes to the problems that showed up), it would work properly again, but, as of this morning, no such luck. It's so close that i can almost taste it! (Not that I have any idea what a clean resume tastes like...just that it will almost certainly be very good.) As always, thanks so much for all of your efforts on this, Nate! -- 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 May 25 15:46:30 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 6EDD716A4CE for ; Tue, 25 May 2004 15:46:30 -0700 (PDT) Received: from caduceus.jf.intel.com (fmr06.intel.com [134.134.136.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0463A43D39 for ; Tue, 25 May 2004 15:46:29 -0700 (PDT) (envelope-from andrew.grover@intel.com) Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6]) major-outer.mc,v 1.15 2004/01/30 18:16:28 root Exp $) with ESMTP id i4PMjelE029203 for ; Tue, 25 May 2004 22:45:41 GMT Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) major-inner.mc,v 1.10 2004/03/01 19:21:36 root Exp $) with SMTP id i4PMjxDo025923; Tue, 25 May 2004 22:46:32 GMT Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56]) M2004052515454113527 ; Tue, 25 May 2004 15:45:41 -0700 Received: from orsmsx401.amr.corp.intel.com ([192.168.65.207]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 25 May 2004 15:45:41 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 25 May 2004 15:43:55 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: APM Patch - review Thread-Index: AcRClnlyH4eSiKLhT/SvdnJ6H330MwAEX17g From: "Grover, Andrew" To: "Liam J. Foy" , X-OriginalArrivalTime: 25 May 2004 22:45:41.0653 (UTC) FILETIME=[01DFBC50:01C442AA] X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) Subject: RE: APM Patch - review 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, 25 May 2004 22:46:30 -0000 Valid values for remaining battery life are 0xFF, and 0-100. -1, 255 and 0xFF are the SAME when looking at an 8 bit value. Since this 8 bit value was sign-extended to 32 bits to go into ai_batt_time, if it was 0xFF, it is now 0xFFFFFFFF, and you will never see 0x000000FF. I will email you the APM spec privately (it's big). Please take a look at page 42 especially. Regards -- Andy From owner-freebsd-acpi@FreeBSD.ORG Tue May 25 16:40:51 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 22D1616A4CE for ; Tue, 25 May 2004 16:40:51 -0700 (PDT) Received: from out003.verizon.net (out003pub.verizon.net [206.46.170.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95C6B43D1D for ; Tue, 25 May 2004 16:40:50 -0700 (PDT) (envelope-from Alex.Kovalenko@verizon.net) Received: from RabbitsDen ([138.89.92.234]) by out003.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040525234040.FEKG6671.out003.verizon.net@RabbitsDen> for ; Tue, 25 May 2004 18:40:40 -0500 Date: Tue, 25 May 2004 19:39:55 -0400 From: Alexandre "Sunny" Kovalenko To: freebsd-acpi@freebsd.org Message-Id: <20040525193955.496d3b50.Alex.Kovalenko@verizon.net> In-Reply-To: <20040523125051.GA14072@siudong.ath.cx> References: <20040523125051.GA14072@siudong.ath.cx> Organization: Home X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [138.89.92.234] at Tue, 25 May 2004 18:40:36 -0500 Subject: Re: freebsd laptops X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 May 2004 23:40:51 -0000 On Sun, 23 May 2004 12:50:51 +0000 "Johnny Wong" wrote: > I'm just wondering which laptops and freebsd make good combination? I would like an laptop with as many supported > hardware as possible, fully acpi support and around $1000 US. Any suggestion is welcome. > thanks > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" I am using AVERATEC 3150H (~$800). Had to hack ASL for normal thermal support and use powernow_k7 loadable module to do CPU trottling. Sleep does not work, but is unimportant to me. So it is not 100% ACPI compatible just yet, but this is only new 4-pound laptop under $1000 I know of. HTH. -- Alexandre "Sunny" Kovalenko. From owner-freebsd-acpi@FreeBSD.ORG Tue May 25 17:24: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 ABF2716A4CE for ; Tue, 25 May 2004 17:24:24 -0700 (PDT) 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 E8B9243D39 for ; Tue, 25 May 2004 17:24:23 -0700 (PDT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.6] (ppp-67-38-164-11.dsl.wotnoh.ameritech.net [67.38.164.11]) (authenticated bits=0)i4Q0IgWB084012 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 25 May 2004 20:18:45 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: Nate Lawson Date: Tue, 25 May 2004 20:24:09 -0400 User-Agent: KMail/1.6.2 References: <20040524201046.C73624@root.org> <200405250108.56959.mistry.7@osu.edu> <20040525091755.Q77324@root.org> In-Reply-To: <20040525091755.Q77324@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200405252024.16835.mistry.7@osu.edu> X-Spam-Status: No, hits=-4.4 required=5.0 tests=EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE, QUOTED_EMAIL_TEXT,RCVD_IN_NJABL,REFERENCES, REPLY_WITH_QUOTES,USER_AGENT_KMAIL,X_NJABL_DIALUP 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-CA 20040514 import 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, 26 May 2004 00:24:24 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 25 May 2004 12:19 pm, you wrote: > On Tue, 25 May 2004, Anish Mistry wrote: > > On Monday 24 May 2004 11:12 pm, Nate Lawson wrote: > > > This commit fixes the immediate resume upon second suspend problem th= at > > > Thinkpads had with the last import. Leaving the shared GPE disabled = at > > > runtime caused this problem. There are some other nice fixes so plea= se > > > cvsup and test. > > > > > > -Nate > > > > My lid switch events aren't working. I have to suspend the system (S3) > > using acpiconf -s 3 then resume, and then the lid switch events start to > > work again. > > http://am-productions.biz/debug/littleguy.asl > > I just committed a workaround that should fix this. Pick up these: > > Revision Changes Path > 1.23 +3 -1 src/sys/dev/acpica/acpi_button.c > 1.19 +3 -1 src/sys/dev/acpica/acpi_lid.c > > -Nate Thanks. This fixed it. I've got another problem that seems to happen duri= ng=20 the previous import, but went away sometime before this import, not sure wh= en=20 though. What happens, when I poweroff the system it shuts off, but wheneve= r=20 a lid switch event occurs ie. when I close the lid to put it in it's case i= t=20 boots up again. I've uploaded the new asl, but it looks pretty much the same. http://am-productions.biz/debug/littleguy.asl =2D --=20 Anish Mistry =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAs+OpxqA5ziudZT0RAgl5AJ0SJfQfDyAFhuaM3/z+so5aCnPt9wCfViNL uO0/uPij/s0S+le9zNNTg0s=3D =3DTlBT =2D----END PGP SIGNATURE----- From owner-freebsd-acpi@FreeBSD.ORG Tue May 25 17:42:03 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 3243616A4CE for ; Tue, 25 May 2004 17:42:03 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id BECBE43D1D for ; Tue, 25 May 2004 17:42:02 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 80173 invoked by uid 1000); 26 May 2004 00:41:43 -0000 Date: Tue, 25 May 2004 17:41:43 -0700 (PDT) From: Nate Lawson To: Anish Mistry In-Reply-To: <200405252024.16835.mistry.7@osu.edu> Message-ID: <20040525174024.D80133@root.org> References: <20040524201046.C73624@root.org> <200405250108.56959.mistry.7@osu.edu> <200405252024.16835.mistry.7@osu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: ACPI-CA 20040514 import 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, 26 May 2004 00:42:03 -0000 On Tue, 25 May 2004, Anish Mistry wrote: > On Tuesday 25 May 2004 12:19 pm, you wrote: > > On Tue, 25 May 2004, Anish Mistry wrote: > > > My lid switch events aren't working. I have to suspend the system (S3) > > > using acpiconf -s 3 then resume, and then the lid switch events start to > > > work again. > > > http://am-productions.biz/debug/littleguy.asl > > > > I just committed a workaround that should fix this. Pick up these: > > > > Revision Changes Path > > 1.23 +3 -1 src/sys/dev/acpica/acpi_button.c > > 1.19 +3 -1 src/sys/dev/acpica/acpi_lid.c > > Thanks. This fixed it. I've got another problem that seems to happen during > the previous import, but went away sometime before this import, not sure when > though. What happens, when I poweroff the system it shuts off, but whenever > a lid switch event occurs ie. when I close the lid to put it in it's case it > boots up again. This import should have fixed this as well. Let me know if it reappears. > I've uploaded the new asl, but it looks pretty much the same. > > http://am-productions.biz/debug/littleguy.asl Newer acpidump helps a lot, for instance by decoding buffers. It may look the same to you but it's a big difference to me. -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed May 26 02:53:53 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 5516716A4CE for ; Wed, 26 May 2004 02:53:53 -0700 (PDT) Received: from moutvdomng.kundenserver.de (moutvdom.kundenserver.de [212.227.126.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5FEC43D41 for ; Wed, 26 May 2004 02:53:52 -0700 (PDT) (envelope-from liamfoy@sepulcrum.org) Received: from [212.227.126.224] (helo=mrvdomng.kundenserver.de) by moutvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BSv5z-00036j-00; Wed, 26 May 2004 11:53:11 +0200 Received: from [217.42.210.193] (helo=liamfoy.ath.cx) by mrvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BSv5z-0000I4-00; Wed, 26 May 2004 11:53:11 +0200 Date: Wed, 26 May 2004 10:52:11 +0100 From: "Liam J. Foy" To: "Grover, Andrew" Message-Id: <20040526105211.3b6667ac.liamfoy@sepulcrum.org> In-Reply-To: References: X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: APM Patch - review 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, 26 May 2004 09:53:53 -0000 On Tue, 25 May 2004 15:43:55 -0700 "Grover, Andrew" wrote: > Valid values for remaining battery life are 0xFF, and 0-100. > > -1, 255 and 0xFF are the SAME when looking at an 8 bit value. Since this > 8 bit value was sign-extended to 32 bits to go into ai_batt_time, if it > was 0xFF, it is now 0xFFFFFFFF, and you will never see 0x000000FF. > > I will email you the APM spec privately (it's big). Please take a look > at page 42 especially. > > Regards -- Andy Ah I see. This would mean alot of the apm code in function print_all_info is not needed. Correct? That manual is great Andy! Thanks:)! > From owner-freebsd-acpi@FreeBSD.ORG Wed May 26 17:46:33 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 1BE0616A4CE for ; Wed, 26 May 2004 17:46:33 -0700 (PDT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81EA443D31 for ; Wed, 26 May 2004 17:46:31 -0700 (PDT) (envelope-from sumiya@micom.mng.net) Received: from [202.179.0.164] (helo=sumiya) by publicd.ub.mng.net with smtp (Exim 4.34; FreeBSD) id 1BT94n-0009ag-8V for freebsd-acpi@freebsd.org; Thu, 27 May 2004 09:48:54 +0900 Message-ID: <000801c44383$f58a6100$1e00a8c0@sumiya> From: "Sumiya" To: Date: Thu, 27 May 2004 09:45:48 +0900 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Rebooting problem X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 00:46:33 -0000 Dear All, I recompiled my kernel of freebsd 5.2.1.=20 But it is not rebooting. Error message : Page pault then Shut down acpi = in 15 seconds. Always rebooting.=20 Please help me.=20 Thanks, Sumiya.T From owner-freebsd-acpi@FreeBSD.ORG Wed May 26 21:53:58 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 EE10216A4CE for ; Wed, 26 May 2004 21:53:58 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id D00FE43D46 for ; Wed, 26 May 2004 21:53:58 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 87906 invoked by uid 1000); 27 May 2004 04:53:31 -0000 Date: Wed, 26 May 2004 21:53:31 -0700 (PDT) From: Nate Lawson To: Sumiya In-Reply-To: <000801c44383$f58a6100$1e00a8c0@sumiya> Message-ID: <20040526215215.W87815@root.org> References: <000801c44383$f58a6100$1e00a8c0@sumiya> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: Rebooting problem X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 04:53:59 -0000 On Thu, 27 May 2004, Sumiya wrote: > I recompiled my kernel of freebsd 5.2.1. > But it is not rebooting. Error message : Page pault then Shut down acpi in 15 seconds. Always rebooting. > > Please help me. Need a more complete error message and description of the problem. Start with posting the output of "dmesg". -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed May 26 22:04: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 F3C6C16A4CE for ; Wed, 26 May 2004 22:04:28 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id B4E2343D1D for ; Wed, 26 May 2004 22:04:28 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 87946 invoked by uid 1000); 27 May 2004 05:03:44 -0000 Date: Wed, 26 May 2004 22:03:44 -0700 (PDT) From: Nate Lawson To: "Liam J. Foy" In-Reply-To: <20040520205712.57abc39b.liamfoy@sepulcrum.org> Message-ID: <20040526215940.F87914@root.org> References: <20040520205712.57abc39b.liamfoy@sepulcrum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: apm code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 05:04:29 -0000 On Thu, 20 May 2004, Liam J. Foy wrote: > Hey, > > Just writing to the list to make sure am correct here. The issue concerns /usr/src/usr.sbin/apm/apm.c. > > --- /usr/src/usr.sbin/apm/apm.c Thu May 20 20:30:57 2004 > +++ /hd2/apm.c Thu May 20 20:44:36 2004 > @@ -174,7 +174,7 @@ > printf("Remaining battery life: "); > if (aip->ai_batt_life == 255) > printf("unknown\n"); > - else if (aip->ai_batt_life <= 100) > + else if (aip->ai_batt_life >= 0 && aip->ai_batt_life <= 100) > printf("%d%%\n", aip->ai_batt_life); > else > printf("invalid value (0x%x)\n", aip->ai_batt_life); > > The above patch will make apm print invalid value when ai_batt_life does not equal 0-100. The reason for this was the the current code was printing -1 as a so called valid value(normally when acline is connected). I dont think printing -1 is correct, and really it should be printing invalid value since that is what it is. Do you guys agree with me or does -1 symbolise something? > > Something else I am curious over is this snippet of code: > > if (aip->ai_infoversion >= 1) { > printf("Number of batteries: "); > if (aip->ai_batteries == (u_int) -1) > printf("unknown\n"); > else { > > ai_batteries in machine/apm_bios.h is defined as u_int. Yet the above code is testing for -1. I _think_ this should be testing for 255(unknown). Anyone shead any light on this? I ask since I do not know apm very well. Would you guys agree my patch is correct also? Are you using ACPI or APM for your power management? Also, what values are reported as "invalid" besides "Remaining battery life"? The usermode code is correct in comparing against 255 but it may be that the kernel code is setting things to -1 (0xffffffff) which != 0xff. -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed May 26 22:08:37 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 8797F16A4CE for ; Wed, 26 May 2004 22:08:37 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 6FFCA43D58 for ; Wed, 26 May 2004 22:08:37 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 87989 invoked by uid 1000); 27 May 2004 05:08:26 -0000 Date: Wed, 26 May 2004 22:08:26 -0700 (PDT) From: Nate Lawson To: "Liam J. Foy" In-Reply-To: Message-ID: <20040526220744.T87978@root.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: RE: APM Patch - review X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 05:08:37 -0000 On Tue, 25 May 2004, Grover, Andrew wrote: > Valid values for remaining battery life are 0xFF, and 0-100. > > -1, 255 and 0xFF are the SAME when looking at an 8 bit value. Since this > 8 bit value was sign-extended to 32 bits to go into ai_batt_time, if it > was 0xFF, it is now 0xFFFFFFFF, and you will never see 0x000000FF. Correct. Liam, can you add a printf for the unknown case (%x) that gives the actual value? -Nate From owner-freebsd-acpi@FreeBSD.ORG Wed May 26 23:12:25 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 145D216A4CE for ; Wed, 26 May 2004 23:12:25 -0700 (PDT) Received: from corrupt.co.nz (222-152-15-178.jetstream.xtra.co.nz [222.152.15.178]) by mx1.FreeBSD.org (Postfix) with SMTP id 7BCAF43D2D for ; Wed, 26 May 2004 23:12:21 -0700 (PDT) (envelope-from drew@corrupt.co.nz) Received: (qmail 35953 invoked by uid 1011); 27 May 2004 06:12:46 -0000 Received: from drew@corrupt.co.nz by mail.corrupt.co.nz by uid 1009 with qmail-scanner-1.20st Clear:RC:0(10.10.69.1):SA:0(0.0/3.8):. Processed in 0.889396 secs); 27 May 2004 06:12:46 -0000 X-Spam-Status: No, hits=0.0 required=3.8 Received: from unknown (HELO corrupt.co.nz) (drew@corrupt.co.nz@10.10.69.1) by corrupt.co.nz with SMTP; 27 May 2004 06:12:45 -0000 Message-ID: <40B5868B.5020208@corrupt.co.nz> Date: Thu, 27 May 2004 18:11:23 +1200 From: Drew Broadley User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040505 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <000801c44383$f58a6100$1e00a8c0@sumiya> <20040526215215.W87815@root.org> In-Reply-To: <20040526215215.W87815@root.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: Sumiya Subject: Re: Rebooting problem X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 06:12:25 -0000 Nate Lawson wrote: >On Thu, 27 May 2004, Sumiya wrote: > > >>I recompiled my kernel of freebsd 5.2.1. >>But it is not rebooting. Error message : Page pault then Shut down acpi in 15 seconds. Always rebooting. >> >>Please help me. >> >> > >Need a more complete error message and description of the problem. >Start with posting the output of "dmesg". > > Look at my dmesg output on my thread "kernel panic on boot", same error. - Drew From owner-freebsd-acpi@FreeBSD.ORG Wed May 26 23:48:14 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 4036D16A4D0 for ; Wed, 26 May 2004 23:48:14 -0700 (PDT) Received: from moutvdomng.kundenserver.de (moutvdom.kundenserver.de [212.227.126.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id A185443D3F for ; Wed, 26 May 2004 23:48:13 -0700 (PDT) (envelope-from liamfoy@sepulcrum.org) Received: from [212.227.126.224] (helo=mrvdomng.kundenserver.de) by moutvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BTEgF-0008Us-00; Thu, 27 May 2004 08:47:55 +0200 Received: from [217.43.38.227] (helo=liamfoy.ath.cx) by mrvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BTEgF-0000gW-00; Thu, 27 May 2004 08:47:55 +0200 Date: Thu, 27 May 2004 07:46:54 +0100 From: "Liam J. Foy" To: Nate Lawson Message-Id: <20040527074654.73d5ec7d.liamfoy@sepulcrum.org> In-Reply-To: <20040526220744.T87978@root.org> References: <20040526220744.T87978@root.org> X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: APM Patch - review X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 06:48:14 -0000 On Wed, 26 May 2004 22:08:26 -0700 (PDT) Nate Lawson wrote: > On Tue, 25 May 2004, Grover, Andrew wrote: > > Valid values for remaining battery life are 0xFF, and 0-100. > > > > -1, 255 and 0xFF are the SAME when looking at an 8 bit value. Since this > > 8 bit value was sign-extended to 32 bits to go into ai_batt_time, if it > > was 0xFF, it is now 0xFFFFFFFF, and you will never see 0x000000FF. > > Correct. Liam, can you add a printf for the unknown case (%x) that gives > the actual value? Nate, to do you mean add a printf to the unknown case to print the value instead of have "invalud value (%x)" etc? Or do you mean add printf in order for me to see what happening? > > -Nate From owner-freebsd-acpi@FreeBSD.ORG Thu May 27 01:28:33 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 8693316A4CF for ; Thu, 27 May 2004 01:28:33 -0700 (PDT) Received: from mail001.syd.optusnet.com.au (mail001.syd.optusnet.com.au [211.29.132.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B7D643D3F for ; Thu, 27 May 2004 01:28:32 -0700 (PDT) (envelope-from cox@optushome.com.au) Received: from unknown1i25n9b (c211-28-158-194.thoms1.vic.optusnet.com.au [211.28.158.194])i4R8SAb32459 for ; Thu, 27 May 2004 18:28:11 +1000 Message-ID: <000801c2c14f$8d940360$c29e1cd3@unknown1i25n9b> From: "Adam Cox" To: MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2739.300 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: ACPI Always on suspend 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: , Date: Thu, 27 May 2004 08:28:33 -0000 X-Original-Date: Wed, 22 Jan 2003 00:18:12 +1100 X-List-Received-Date: Thu, 27 May 2004 08:28:33 -0000 My computer is always stuck with a blinking power light and is nearly = impossible to get it started. I know it has something to do with the = ACPI so how can avoid this problem? P.S The current state is S1 but switching it to S3 under ram but it = makes no difference. From owner-freebsd-acpi@FreeBSD.ORG Thu May 27 08:47:42 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63E4216A4CE for ; Thu, 27 May 2004 08:47:42 -0700 (PDT) Received: from moutvdomng.kundenserver.de (moutvdom.kundenserver.de [212.227.126.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC02743D41 for ; Thu, 27 May 2004 08:47:41 -0700 (PDT) (envelope-from liamfoy@sepulcrum.org) Received: from [212.227.126.224] (helo=mrvdomng.kundenserver.de) by moutvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BTN6J-0002nI-00; Thu, 27 May 2004 17:47:23 +0200 Received: from [217.43.38.227] (helo=liamfoy.ath.cx) by mrvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BTN6J-0003l4-00; Thu, 27 May 2004 17:47:23 +0200 Date: Thu, 27 May 2004 16:46:22 +0100 From: "Liam J. Foy" To: "Adam Cox" Message-Id: <20040527164622.43a11651.liamfoy@sepulcrum.org> In-Reply-To: <000801c2c14f$8d940360$c29e1cd3@unknown1i25n9b> References: <000801c2c14f$8d940360$c29e1cd3@unknown1i25n9b> X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org Subject: Re: ACPI Always on suspend X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 15:47:42 -0000 On Wed, 22 Jan 2003 00:18:12 +1100 "Adam Cox" wrote: > My computer is always stuck with a blinking power light and is nearly impossible to get it started. I know it has something to do with the ACPI so how can avoid this problem? > Are you just looking to disable ACPI Adam? > P.S The current state is S1 but switching it to S3 under ram but it makes no difference. Regards, Liam Foy > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" From owner-freebsd-acpi@FreeBSD.ORG Thu May 27 11:58: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 F245516A4CE for ; Thu, 27 May 2004 11:58:24 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id BD3E743D45 for ; Thu, 27 May 2004 11:58:24 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 92441 invoked by uid 1000); 27 May 2004 18:57:36 -0000 Date: Thu, 27 May 2004 11:57:36 -0700 (PDT) From: Nate Lawson To: "Liam J. Foy" In-Reply-To: <20040527074654.73d5ec7d.liamfoy@sepulcrum.org> Message-ID: <20040527115655.M92394@root.org> References: <20040527074654.73d5ec7d.liamfoy@sepulcrum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: APM Patch - review X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 18:58:25 -0000 On Thu, 27 May 2004, Liam J. Foy wrote: > On Wed, 26 May 2004 22:08:26 -0700 (PDT) > Nate Lawson wrote: > > > On Tue, 25 May 2004, Grover, Andrew wrote: > > > Valid values for remaining battery life are 0xFF, and 0-100. > > > > > > -1, 255 and 0xFF are the SAME when looking at an 8 bit value. Since this > > > 8 bit value was sign-extended to 32 bits to go into ai_batt_time, if it > > > was 0xFF, it is now 0xFFFFFFFF, and you will never see 0x000000FF. > > > > Correct. Liam, can you add a printf for the unknown case (%x) that gives > > the actual value? > > Nate, to do you mean add a printf to the unknown case to print the value instead > of have "invalud value (%x)" etc? Oh, I missed that part where you said you get "-1" printed for the "invalid value (%x) case. -Nate From owner-freebsd-acpi@FreeBSD.ORG Thu May 27 12:01:27 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D948E16A4CE for ; Thu, 27 May 2004 12:01:27 -0700 (PDT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7779E43D1F for ; Thu, 27 May 2004 12:01:25 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 20386 invoked from network); 27 May 2004 18:53:55 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 27 May 2004 18:53:55 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i4RIrihc022510 for ; Thu, 27 May 2004 14:53:44 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: acpi@FreeBSD.org Date: Thu, 27 May 2004 14:54:22 -0400 User-Agent: KMail/1.6 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200405271454.22402.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Bug? PCI link device _SRS X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 19:01:28 -0000 Note that in the _PRT, the interrupt associated with a link device object has a source index indicating which resource holds the IRQ. When we do _SRS to route an interrupt, we try to set all the resources of the device to a single IRQ resource. Shouldn't we probably instead be modifying the single resource object crsres points to in crsbuf and resetting all the resources when we call _SRS? Also, the handling of BUS_CONFIG_INTR() is giving me a heartache. We should defer that until bus_alloc_resource() (I have a hack to do this now) as it causes the link devices currently to configure an interrupt for PIC mode that will _never_ be used if we are using the APIC. However, it can do things like screw up the SCI if the SCI isn't using level/low. Grr. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Thu May 27 12:02:40 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 8110916A4CF for ; Thu, 27 May 2004 12:02:40 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 644A343D45 for ; Thu, 27 May 2004 12:02:40 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 92474 invoked by uid 1000); 27 May 2004 19:01:56 -0000 Date: Thu, 27 May 2004 12:01:56 -0700 (PDT) From: Nate Lawson To: Adam Cox In-Reply-To: <000801c2c14f$8d940360$c29e1cd3@unknown1i25n9b> Message-ID: <20040527120050.O92394@root.org> References: <000801c2c14f$8d940360$c29e1cd3@unknown1i25n9b> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@FreeBSD.org Subject: Re: ACPI Always on suspend X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 19:02:40 -0000 On Wed, 22 Jan 2003, Adam Cox wrote: > My computer is always stuck with a blinking power light and is nearly > impossible to get it started. I know it has something to do with the > ACPI so how can avoid this problem? > > P.S The current state is S1 but switching it to S3 under ram but it makes no difference. I think he's saying that after trying to suspend, his system never resumes. It would help if you'd post the make/model of the laptop and whether disabling acpi and enabling apm instead helps. -Nate From owner-freebsd-acpi@FreeBSD.ORG Thu May 27 12:34:37 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 225C616A4CE for ; Thu, 27 May 2004 12:34:37 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 00E7543D31 for ; Thu, 27 May 2004 12:34:37 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 92753 invoked by uid 1000); 27 May 2004 19:34:28 -0000 Date: Thu, 27 May 2004 12:34:28 -0700 (PDT) From: Nate Lawson To: "Liam J. Foy" In-Reply-To: <20040525211220.6f349011.liamfoy@sepulcrum.org> Message-ID: <20040527123407.E92731@root.org> References: <20040525211220.6f349011.liamfoy@sepulcrum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: APM Patch - review X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 19:34:37 -0000 I just committed a workaround that checks for >= 255. Please cvsup, recompile apm and be sure it works for you. -Nate From owner-freebsd-acpi@FreeBSD.ORG Thu May 27 12:40:59 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 8A5AB16A4CE for ; Thu, 27 May 2004 12:40:59 -0700 (PDT) Received: from moutvdomng.kundenserver.de (moutvdom.kundenserver.de [212.227.126.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 204DF43D2F for ; Thu, 27 May 2004 12:40:59 -0700 (PDT) (envelope-from liamfoy@sepulcrum.org) Received: from [212.227.126.224] (helo=mrvdomng.kundenserver.de) by moutvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BTQk6-00062u-00; Thu, 27 May 2004 21:40:42 +0200 Received: from [217.43.38.227] (helo=liamfoy.ath.cx) by mrvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BTQk6-0007RP-00; Thu, 27 May 2004 21:40:42 +0200 Date: Thu, 27 May 2004 20:39:41 +0100 From: "Liam J. Foy" To: Nate Lawson Message-Id: <20040527203941.252c2ba4.liamfoy@sepulcrum.org> In-Reply-To: <20040527123407.E92731@root.org> References: <20040525211220.6f349011.liamfoy@sepulcrum.org> <20040527123407.E92731@root.org> X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: APM Patch - review X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 19:40:59 -0000 On Thu, 27 May 2004 12:34:28 -0700 (PDT) Nate Lawson wrote: > I just committed a workaround that checks for >= 255. Please cvsup, > recompile apm and be sure it works for you. > Right. It will work for sure. > -Nate > -- -Liam Foy http://liamfoy.kerneled.org "Do only what only you can do." From owner-freebsd-acpi@FreeBSD.ORG Thu May 27 12:43:18 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 2B27916A4CE for ; Thu, 27 May 2004 12:43:18 -0700 (PDT) Received: from moutvdomng.kundenserver.de (moutvdom.kundenserver.de [212.227.126.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id E414343D1D for ; Thu, 27 May 2004 12:43:17 -0700 (PDT) (envelope-from liamfoy@sepulcrum.org) Received: from [212.227.126.224] (helo=mrvdomng.kundenserver.de) by moutvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BTQlm-0006Le-00; Thu, 27 May 2004 21:42:26 +0200 Received: from [217.43.38.227] (helo=liamfoy.ath.cx) by mrvdomng.kundenserver.de with esmtp (Exim 3.35 #1) id 1BTQll-0007TK-00; Thu, 27 May 2004 21:42:26 +0200 Date: Thu, 27 May 2004 20:41:25 +0100 From: "Liam J. Foy" To: Nate Lawson Message-Id: <20040527204125.4a69a887.liamfoy@sepulcrum.org> In-Reply-To: <20040527123407.E92731@root.org> References: <20040525211220.6f349011.liamfoy@sepulcrum.org> <20040527123407.E92731@root.org> X-Mailer: Sylpheed version 0.9.10 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: APM Patch - review X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 19:43:18 -0000 On Thu, 27 May 2004 12:34:28 -0700 (PDT) Nate Lawson wrote: > I just committed a workaround that checks for >= 255. Please cvsup, > recompile apm and be sure it works for you. > Also, would be nice to define 255 as UNKNOWN:) > -Nate > -- -Liam Foy http://liamfoy.kerneled.org "Do only what only you can do." From owner-freebsd-acpi@FreeBSD.ORG Thu May 27 15:23:10 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 0E8C716A4CE; Thu, 27 May 2004 15:23:10 -0700 (PDT) Received: from hermes.fm.intel.com (fmr01.intel.com [192.55.52.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1717C43D2D; Thu, 27 May 2004 15:23:09 -0700 (PDT) (envelope-from len.brown@intel.com) Received: from petasus-pilot.fm.intel.com (petasus-pilot.fm.intel.com [10.1.192.44]) 1.15 2004/01/30 18:16:28 root Exp $) with ESMTP id i4RKuB80026168; Thu, 27 May 2004 20:56:11 GMT Received: from fmsmsxvs040.fm.intel.com (fmsmsxvs040.fm.intel.com [132.233.42.124]) major-inner.mc,v 1.10 2004/03/01 19:21:36 root Exp $) with SMTP id i4RKukup018476; Thu, 27 May 2004 20:56:48 GMT Received: from fmsmsx331.amr.corp.intel.com ([132.233.42.135]) M2004052713553705055 ; Thu, 27 May 2004 13:55:37 -0700 Received: from fmsmsx312.amr.corp.intel.com ([132.233.42.227]) by fmsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 27 May 2004 13:55:37 -0700 Received: from hdsmsx404.amr.corp.intel.com ([10.127.2.66]) by fmsmsx312.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.0); Thu, 27 May 2004 13:55:37 -0700 Received: from hdsmsx403.amr.corp.intel.com ([10.127.2.64]) by hdsmsx404.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 27 May 2004 16:55:36 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 27 May 2004 16:55:35 -0400 Message-ID: <29AC424F54821A4FB5D7CBE081922E40928BB1@hdsmsx403.hd.intel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Bug? PCI link device _SRS Thread-Index: AcREHUFpkDgI3IsRQFKIFIRBsBRc0QADeBJg From: "Brown, Len" To: "John Baldwin" , X-OriginalArrivalTime: 27 May 2004 20:55:36.0286 (UTC) FILETIME=[F59837E0:01C4442C] X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) Subject: RE: Bug? PCI link device _SRS X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2004 22:23:10 -0000 John, Dunno if FreeBSD works the same way, but we recently fixed a couple of interesting platform isssue using PCI Interrupt Links on Linux. 1. The enabled bit from _STA for PCI Interrupt Link devices is meaningless on many platforms, ignore it. If a platform gives you a _CRS IRQ that is outside the _PRS list, then do no stick with the _CRS -- select a new (valid) one from the _PRS list. If a platform gives you a _CRS IRQ that is different from the _SRS you just invoked. Assume that the _SRS worked and that the _CRS is bogus. =20 http://bugzilla.kernel.org/show_bug.cgi?id=3D1581 2. Blindly programming all PCI Interrupt Link Devices turns out to be a bad idea. Instead, they should be programmed only when PCI devices using them are installed and enabled in the system. http://bugzilla.kernel.org/show_bug.cgi?id=3D2574 cheers, -Len From owner-freebsd-acpi@FreeBSD.ORG Fri May 28 00:29:28 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 0ECD716A4CF for ; Fri, 28 May 2004 00:29:28 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id C859443D58 for ; Fri, 28 May 2004 00:29:27 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 96451 invoked by uid 1000); 28 May 2004 07:28:39 -0000 Date: Fri, 28 May 2004 00:28:39 -0700 (PDT) From: Nate Lawson To: "Brown, Len" In-Reply-To: <29AC424F54821A4FB5D7CBE081922E40928BB1@hdsmsx403.hd.intel.com> Message-ID: <20040528002701.M96434@root.org> References: <29AC424F54821A4FB5D7CBE081922E40928BB1@hdsmsx403.hd.intel.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org Subject: RE: Bug? PCI link device _SRS 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, 28 May 2004 07:29:28 -0000 On Thu, 27 May 2004, Brown, Len wrote: > John, > Dunno if FreeBSD works the same way, > but we recently fixed a couple of interesting > platform isssue using PCI Interrupt Links > on Linux. There's one more that I have listed on my todo list: http://www.root.org/~nate/freebsd/acpi-todo.html ---- Intel firmware seems to describe the PCI root bridge where chipset configuration space lives with _STA==0x8. The spec says this means "functional, but not present". The current code ignores things that are "not present". It is suggested that this should be handled by not attaching a driver to the device (i.e. bridge) but probe its children. Present on Big Sur and Bull systems. http://sourceforge.net/mailarchive/message.php?msg_id=6923358 ---- -Nate From owner-freebsd-acpi@FreeBSD.ORG Fri May 28 00:39:20 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 BB42216A4CE for ; Fri, 28 May 2004 00:39:20 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 970A643D2F for ; Fri, 28 May 2004 00:39:20 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 96530 invoked by uid 1000); 28 May 2004 07:38:32 -0000 Date: Fri, 28 May 2004 00:38:32 -0700 (PDT) From: Nate Lawson To: current@freebsd.org Message-ID: <20040528003424.E96434@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@freebsd.org Subject: ACPI event testing needed 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, 28 May 2004 07:39:20 -0000 I've just finished a lot of work on acpi events (GPEs). These drive things like the lid switch and device wake capabilities. If your system works for suspend/resume, please make sure it still behaves correctly over multiple suspend/resume cycles. If you're feeling adventurous, try the new wake sysctls: sysctl dev | grep wake By setting them to 0 or 1, you can enable/disable a device waking the system. Note that non-ACPI devices are still not properly hooked in here so they won't work (i.e. sio or modems). But you can change the lid independently of the sleep button, for example. Also, please be sure that your system still powers off correctly when shutdown. I may have fixed some systems that didn't power off correctly as well. Thanks, -Nate From owner-freebsd-acpi@FreeBSD.ORG Fri May 28 09:43:23 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 523C516A4CF for ; Fri, 28 May 2004 09:43:23 -0700 (PDT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1966043D48 for ; Fri, 28 May 2004 09:43:23 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 22633 invoked from network); 28 May 2004 16:36:16 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 28 May 2004 16:36:16 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i4SGaDSX029104; Fri, 28 May 2004 12:36:13 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: "Brown, Len" Date: Fri, 28 May 2004 12:36:52 -0400 User-Agent: KMail/1.6 References: <29AC424F54821A4FB5D7CBE081922E40928BB1@hdsmsx403.hd.intel.com> In-Reply-To: <29AC424F54821A4FB5D7CBE081922E40928BB1@hdsmsx403.hd.intel.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405281236.52812.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org Subject: Re: Bug? PCI link device _SRS 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, 28 May 2004 16:43:23 -0000 On Thursday 27 May 2004 04:55 pm, Brown, Len wrote: > John, > Dunno if FreeBSD works the same way, > but we recently fixed a couple of interesting > platform isssue using PCI Interrupt Links > on Linux. > > 1. The enabled bit from _STA for > PCI Interrupt Link devices is meaningless > on many platforms, ignore it. Ok, thanks. > If a platform gives you a _CRS IRQ that > is outside the _PRS list, then do no > stick with the _CRS -- select > a new (valid) one from the _PRS list. Ah, I have a patch to do this already that I can commit. > If a platform gives you a _CRS IRQ that > is different from the _SRS you just > invoked. Assume that the _SRS worked > and that the _CRS is bogus. Huh, we don't do that type of checking, but we do use _CRS for later devices routed to the same link to see what IRQ they should use. > http://bugzilla.kernel.org/show_bug.cgi?id=1581 > > 2. Blindly programming all PCI Interrupt Link Devices > turns out to be a bad idea. Instead, they should > be programmed only when PCI devices using them are > installed and enabled in the system. > http://bugzilla.kernel.org/show_bug.cgi?id=2574 Yes, we already do this as well. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Fri May 28 10:01:52 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 657BE16A4CE for ; Fri, 28 May 2004 10:01:52 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 34A1643D45 for ; Fri, 28 May 2004 10:01:52 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 99116 invoked by uid 1000); 28 May 2004 17:00:53 -0000 Date: Fri, 28 May 2004 10:00:53 -0700 (PDT) From: Nate Lawson To: John Baldwin In-Reply-To: <200405281236.52812.jhb@FreeBSD.org> Message-ID: <20040528095533.E99072@root.org> References: <29AC424F54821A4FB5D7CBE081922E40928BB1@hdsmsx403.hd.intel.com> <200405281236.52812.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: acpi@FreeBSD.org Subject: Re: Bug? PCI link device _SRS 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, 28 May 2004 17:01:52 -0000 John, great to see you're working on a lot of these already. Appreciate it. On Fri, 28 May 2004, John Baldwin wrote: > On Thursday 27 May 2004 04:55 pm, Brown, Len wrote: > > If a platform gives you a _CRS IRQ that > > is outside the _PRS list, then do no > > stick with the _CRS -- select > > a new (valid) one from the _PRS list. > > Ah, I have a patch to do this already that I can commit. > > > If a platform gives you a _CRS IRQ that > > is different from the _SRS you just > > invoked. Assume that the _SRS worked > > and that the _CRS is bogus. > > Huh, we don't do that type of checking, but we do use _CRS for later devices > routed to the same link to see what IRQ they should use. I think the first one will take care of how we handle this one. We'll do _SRS and ignore the _CRS that comes back. Later, we go to program a device that has the same link and its _CRS will be outside the _PRS list, so we'll fall back to selecting a valid one from _PRS. -Nate From owner-freebsd-acpi@FreeBSD.ORG Fri May 28 10:33: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 41A7116A4CE for ; Fri, 28 May 2004 10:33:48 -0700 (PDT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3E8143D2D for ; Fri, 28 May 2004 10:33:47 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 2479 invoked from network); 28 May 2004 17:33:29 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 28 May 2004 17:33:29 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i4SHXOVo029475; Fri, 28 May 2004 13:33:26 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Fri, 28 May 2004 13:34:03 -0400 User-Agent: KMail/1.6 References: <29AC424F54821A4FB5D7CBE081922E40928BB1@hdsmsx403.hd.intel.com> <200405281236.52812.jhb@FreeBSD.org> <20040528095533.E99072@root.org> In-Reply-To: <20040528095533.E99072@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405281334.03956.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org Subject: Re: Bug? PCI link device _SRS 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, 28 May 2004 17:33:48 -0000 On Friday 28 May 2004 01:00 pm, Nate Lawson wrote: > John, great to see you're working on a lot of these already. Appreciate > it. > > On Fri, 28 May 2004, John Baldwin wrote: > > On Thursday 27 May 2004 04:55 pm, Brown, Len wrote: > > > If a platform gives you a _CRS IRQ that > > > is outside the _PRS list, then do no > > > stick with the _CRS -- select > > > a new (valid) one from the _PRS list. > > > > Ah, I have a patch to do this already that I can commit. > > > > > If a platform gives you a _CRS IRQ that > > > is different from the _SRS you just > > > invoked. Assume that the _SRS worked > > > and that the _CRS is bogus. > > > > Huh, we don't do that type of checking, but we do use _CRS for later > > devices routed to the same link to see what IRQ they should use. > > I think the first one will take care of how we handle this one. We'll do > _SRS and ignore the _CRS that comes back. Later, we go to program a > device that has the same link and its _CRS will be outside the _PRS list, > so we'll fall back to selecting a valid one from _PRS. But what if we chose a different IRQ? Then the routing for the earlier device would be wrong. acpi_pcib_route_interrupt() needs to work with the pci_link code more closely, and we should cache the current IRQ in the softc and use that to determine if it is routed rather than _CRS I think. This is how the new $PIR code works. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Fri May 28 10:33: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 6A66216A4CE for ; Fri, 28 May 2004 10:33:48 -0700 (PDT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BF3043D2D for ; Fri, 28 May 2004 10:33:48 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 2479 invoked from network); 28 May 2004 17:33:29 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 28 May 2004 17:33:29 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i4SHXOVo029475; Fri, 28 May 2004 13:33:26 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Fri, 28 May 2004 13:34:03 -0400 User-Agent: KMail/1.6 References: <29AC424F54821A4FB5D7CBE081922E40928BB1@hdsmsx403.hd.intel.com> <200405281236.52812.jhb@FreeBSD.org> <20040528095533.E99072@root.org> In-Reply-To: <20040528095533.E99072@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405281334.03956.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: acpi@FreeBSD.org Subject: Re: Bug? PCI link device _SRS 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, 28 May 2004 17:33:48 -0000 On Friday 28 May 2004 01:00 pm, Nate Lawson wrote: > John, great to see you're working on a lot of these already. Appreciate > it. > > On Fri, 28 May 2004, John Baldwin wrote: > > On Thursday 27 May 2004 04:55 pm, Brown, Len wrote: > > > If a platform gives you a _CRS IRQ that > > > is outside the _PRS list, then do no > > > stick with the _CRS -- select > > > a new (valid) one from the _PRS list. > > > > Ah, I have a patch to do this already that I can commit. > > > > > If a platform gives you a _CRS IRQ that > > > is different from the _SRS you just > > > invoked. Assume that the _SRS worked > > > and that the _CRS is bogus. > > > > Huh, we don't do that type of checking, but we do use _CRS for later > > devices routed to the same link to see what IRQ they should use. > > I think the first one will take care of how we handle this one. We'll do > _SRS and ignore the _CRS that comes back. Later, we go to program a > device that has the same link and its _CRS will be outside the _PRS list, > so we'll fall back to selecting a valid one from _PRS. But what if we chose a different IRQ? Then the routing for the earlier device would be wrong. acpi_pcib_route_interrupt() needs to work with the pci_link code more closely, and we should cache the current IRQ in the softc and use that to determine if it is routed rather than _CRS I think. This is how the new $PIR code works. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Fri May 28 11:20:27 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AEF316A4CE for ; Fri, 28 May 2004 11:20:27 -0700 (PDT) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 06C9343D39 for ; Fri, 28 May 2004 11:20:27 -0700 (PDT) (envelope-from nate@root.org) Received: (qmail 99604 invoked by uid 1000); 28 May 2004 18:19:27 -0000 Date: Fri, 28 May 2004 11:19:27 -0700 (PDT) From: Nate Lawson To: John Baldwin In-Reply-To: <200405281334.03956.jhb@FreeBSD.org> Message-ID: <20040528111825.I99600@root.org> References: <29AC424F54821A4FB5D7CBE081922E40928BB1@hdsmsx403.hd.intel.com> <200405281236.52812.jhb@FreeBSD.org> <20040528095533.E99072@root.org> <200405281334.03956.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@FreeBSD.org Subject: Re: Bug? PCI link device _SRS 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, 28 May 2004 18:20:27 -0000 On Fri, 28 May 2004, John Baldwin wrote: > On Friday 28 May 2004 01:00 pm, Nate Lawson wrote: > > John, great to see you're working on a lot of these already. Appreciate > > it. > > > > On Fri, 28 May 2004, John Baldwin wrote: > > > On Thursday 27 May 2004 04:55 pm, Brown, Len wrote: > > > > If a platform gives you a _CRS IRQ that > > > > is outside the _PRS list, then do no > > > > stick with the _CRS -- select > > > > a new (valid) one from the _PRS list. > > > > > > Ah, I have a patch to do this already that I can commit. > > > > > > > If a platform gives you a _CRS IRQ that > > > > is different from the _SRS you just > > > > invoked. Assume that the _SRS worked > > > > and that the _CRS is bogus. > > > > > > Huh, we don't do that type of checking, but we do use _CRS for later > > > devices routed to the same link to see what IRQ they should use. > > > > I think the first one will take care of how we handle this one. We'll do > > _SRS and ignore the _CRS that comes back. Later, we go to program a > > device that has the same link and its _CRS will be outside the _PRS list, > > so we'll fall back to selecting a valid one from _PRS. > > But what if we chose a different IRQ? Then the routing for the earlier device > would be wrong. acpi_pcib_route_interrupt() needs to work with the pci_link > code more closely, and we should cache the current IRQ in the softc and use > that to determine if it is routed rather than _CRS I think. This is how the > new $PIR code works. I was assuming that the _PRS selection algorithm was idempotent and deterministic. If this is not the case, you will need to cache the value you set. -Nate From owner-freebsd-acpi@FreeBSD.ORG Fri May 28 14:17:04 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 C754816A4D1 for ; Fri, 28 May 2004 14:17:04 -0700 (PDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id A984A43D45 for ; Fri, 28 May 2004 14:16:59 -0700 (PDT) (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 i4SLGdJ02089 for ; Fri, 28 May 2004 14:16:39 -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 i4SLGdnp026387 for ; Fri, 28 May 2004 14:16:39 -0700 (PDT) (envelope-from faber@pun.isi.edu) Received: (from faber@localhost) by pun.isi.edu (8.12.11/8.12.11/Submit) id i4SLGdYl026386 for acpi@freebsd.org; Fri, 28 May 2004 14:16:39 -0700 (PDT) (envelope-from faber) Date: Fri, 28 May 2004 14:16:39 -0700 From: Ted Faber To: acpi@freebsd.org Message-ID: <20040528211639.GD25131@pun.isi.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YkJPYEFdoxh/AXLE" 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 C610 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, 28 May 2004 21:17:05 -0000 --YkJPYEFdoxh/AXLE Content-Type: multipart/mixed; boundary="pZs/OQEoSSbxGlYw" Content-Disposition: inline --pZs/OQEoSSbxGlYw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi. My Dell Latitiude C610 Laptop reboots (powers down and then up) on suspend (transition to S3 state). Maybe one time in 10 it goes into a more sleeplike state, but there's no way to wake it without using the power switch and rebooting. I didn't see a similar report in the pr database. I've tried both settings of hw.acpi.disable_on_poweroff and get the same result. Usin APM without ACPI gives a different failure (locks up completely, including a nice shrill squeal that can only be stopped by a power cycle if I press a key), though apm suspend under -STABLE always worked. Attached are the dmesg -v and systcl hw.acpi . ASL is at http://www.isi.edu/tmp/faber-dell_latitude_c610.asl . Let me know if there is anything I can do to help debug. -- 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 --pZs/OQEoSSbxGlYw Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg 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 #11: Fri May 28 11:40:31 PDT 2004 root@bug.isi.edu:/usr/obj/usr/src/sys/BUG Preloaded elf kernel "/boot/kernel/kernel" at 0xc0767000. Preloaded elf module "/boot/kernel/if_an.ko" at 0xc07671d8. Preloaded elf module "/boot/kernel/wlan.ko" at 0xc0767284. Preloaded elf module "/boot/kernel/rc4.ko" at 0xc0767330. Preloaded elf module "/boot/kernel/snd_ich.ko" at 0xc07673d8. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc0767484. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0767530. Calibrating clock(s) ... i8254 clock: 1193083 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 996788887 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 = 519639040 (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> random: mem: Pentium Pro MTRR support enabled null: 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 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_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_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 mask=03 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 mask=03 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 2a1000, 4000; 0xe7d4e000 -> 2a1000 pcm0: sndbuf_setmap 2a5000, 4000; 0xe7d52000 -> 2a5000 pcm0: sndbuf_setmap 2b0000, 4000; 0xe7d56000 -> 2b0000 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 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 plip0: on ppbus0 plip0: bpf attached lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) unknown: not probed (disabled) 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: