From owner-freebsd-acpi@FreeBSD.ORG Sun Mar 2 12:07:21 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 030941065670 for ; Sun, 2 Mar 2008 12:07:21 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.freebsd.org (Postfix) with ESMTP id 33C308FC16 for ; Sun, 2 Mar 2008 12:07:18 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.5) with SMTP id XAA21491; Sun, 2 Mar 2008 23:07:00 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Sun, 2 Mar 2008 23:06:59 +1100 (EST) From: Ian Smith To: Johannes Dieterich In-Reply-To: <47C99158.4000106@gmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Peter Jeremy , freebsd-acpi@freebsd.org, "Alexandre \"Sunny\" Kovalenko" Subject: Re: [RFC] Patch to enable temperature ceiling in powerd X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Mar 2008 12:07:21 -0000 On Sat, 1 Mar 2008, Johannes Dieterich wrote: > Hello everybody! > > To get back to this discussion (sorry, normal job kicked me quite a bit > last week). > > Peter Jeremy wrote: > > On Wed, Feb 20, 2008 at 05:06:41PM -0500, Daniel Eischen wrote: [..] > > investigating an unrelated problem. We eventually decided it was a > > faulty sensor and a replacement board fixed it. > What I have now is the original hard drive (some 80 gig Fujitsu one) > with a freshly installed Fedora 8 on it. I have been letting two > instances of gnuchess playing against each other for a couple of hours > (yes, I know... best stress test ever... ;-) ) which kept cpu usage at a > nice 100 percent on both cores for all that time. I doubt that it amounts to a buildworld, which flogs the disk pretty hard too, but that should serve well enough for relative comparison. > proc/acpi/thermal_zones/THM1/temperature (and THM0) reported > temperatures around 70 degrees, never over 72 for all that time. Lid was > closed, fan worked (not very noisy even) and blew a good load of hot air > out. I am tempted to say that my overheating problem is not hardware > related. Only parts different were ath0 not working with Fedora and hard > drive being not the 160 gig WD I am using for FreeBSD. You could expect your 160GB drive to run a few degrees warmer, but most likely still inside the tz1._PSV=80C suggested most recently, however you haven't said whether you've yet tried applying the tz1 settings that Alexandre last suggested as working well for his very similar model Thinkpad on Feb 21st (previous message on this thread to yours)? > >> Only under load does the temperature > >> shoot up, but I know the chip isn't getting hot and the fan > >> is running - I've felt around in there and nothing was even > >> close to the 117+C it was sensing. But that was on tz0, wasn't it? Please read Alex's message carefully; if there's still something different about yours we likely need to know. > > Apart from the actual CPU, most parts of a system have a fairly > > significant thermal mass so a rapid change in temperature either > > indicates a catastrophic failure or the temperature sensor isn't > > really reporting the temperature of the relevant zone. > > > I totally agree with you, Peter. And either the hardware just fails > under FreeBSD (or with ath0 and the other hard drive running) OR it is > a FreeBSD problem. > > Everybody is invited to tell me how to stress test the system as brutal > as possible to show that the problem is hardware related. It's possible, but suspecting the hardware may have been a red herring. It does seem more clearly related to some the recent flurry of software changes to acpi_thermal.c, that should detect the fact that your cpu thermal zone tz1 is the one needing monitoring, rather than tz0. Again, please try what Alex suggested and report back in some detail? Even without updating to the latest -STABLE they might work with the overrides mentioned, though as all this appears to have been mfc'd in recent days, running the latest -STABLE would be the acid test. See: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/acpica/acpi_thermal.c HTH, Ian From owner-freebsd-acpi@FreeBSD.ORG Sun Mar 2 13:13:54 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71F49106566C for ; Sun, 2 Mar 2008 13:13:54 +0000 (UTC) (envelope-from ivan@serezhkin.com) Received: from shustrik.urh.ru (shustrik.urh.ru [89.108.81.81]) by mx1.freebsd.org (Postfix) with ESMTP id 2EB498FC20 for ; Sun, 2 Mar 2008 13:13:53 +0000 (UTC) (envelope-from ivan@serezhkin.com) Received: from VANY.yandex.ru (ppp91-76-51-46.pppoe.mtu-net.ru [91.76.51.46]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ivan@serezhkin.com) by shustrik.urh.ru (Postfix) with ESMTP id BF9711CE08 for ; Sun, 2 Mar 2008 15:51:11 +0300 (MSK) Message-ID: <47CAA414.7030802@serezhkin.com> Date: Sun, 02 Mar 2008 15:56:52 +0300 From: "Ivan B. Serezhkin" User-Agent: Thunderbird 2.0.0.12 (X11/20080229) MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Subject: internal wpi on s7110 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Mar 2008 13:13:54 -0000 Good day. I have siemens s7110 notebook and i can not attach internal intel3945 wifi. there is an info about notebook : http://ivan.serezhkin.com/s7110/ and this is a Symptom : When i kldlosd if_wpi it says =====8<==== found-> vendor=0x8086, dev=0x4222, revid=0x02 domain=0, bus=5, slot=0, func=0 class=02-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=18 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit pci0:5:0:0: reprobing on driver added wpi0: mem 0xf0100000-0xf0100fff irq 18 at device 0.0 on pci5 wpi0: Driver Revision 20071127 pcib3: wpi0 requested unsupported memory range 0xf0100000-0xf0100fff (decoding 0-0, 0-0) wpi0: could not allocate memory resource device_attach: wpi0 attach returned 6 =====8<==== It seems that pcib3 does not been initialized properly. It has not any memory resources attached, i saw it by my own eyes, when i try to debug this problem. what can help tune system properly in a boot time ? I thing, that there some relations between pci and dsdt, but i cant prove this. Also, when i turn on ACPI_DEBUG option, system hangs when it loads acpi.ko. What it may be, and how i can turn on debug and avoid hanging ? -- Ivan B. Serezhkin From owner-freebsd-acpi@FreeBSD.ORG Sun Mar 2 13:26:06 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3F051065677 for ; Sun, 2 Mar 2008 13:26:06 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from falcon.cybervisiontech.com (falcon.cybervisiontech.com [217.20.163.9]) by mx1.freebsd.org (Postfix) with ESMTP id 22C7A8FC15 for ; Sun, 2 Mar 2008 13:26:05 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (localhost [127.0.0.1]) by falcon.cybervisiontech.com (Postfix) with ESMTP id 5DAE674400D for ; Sun, 2 Mar 2008 15:26:03 +0200 (EET) X-Virus-Scanned: Debian amavisd-new at falcon.cybervisiontech.com Received: from falcon.cybervisiontech.com ([127.0.0.1]) by localhost (falcon.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id LFFc0cTIWu3L for ; Sun, 2 Mar 2008 15:26:03 +0200 (EET) Received: from [91.193.172.111] (unknown [91.193.172.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by falcon.cybervisiontech.com (Postfix) with ESMTP id 8F777744002 for ; Sun, 2 Mar 2008 15:26:02 +0200 (EET) Message-ID: <47CAAADC.9080500@icyb.net.ua> Date: Sun, 02 Mar 2008 15:25:48 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.9 (X11/20071208) MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: playing with _TZ X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Mar 2008 13:26:06 -0000 I did what is described here a few years ago. My primary drive was to reduce noise level from a CPU fan when a machine was idle. This idea came to my mind when I was reading W83783S specification and noticed that the chip supports PWM control of fan speed. Also, while reading ACPI specification I came to understand that there are different approaches to active cooling. ACPI framework is built on a model where there are several fans and more of them get activated as more cooling is needed. But it is certainly possible to emulate those ACPI fans by setting different speed levels of a single fan. E.g. see section 10.6 of ACPI 2.0 specification. So this is what I decided to implement. In addition I decided to implement hysteresis as described in section 12.1.2.3 of the same specification. Also, I added a "RO" thermal zone to report chipset temperature. Finally I fixed all iasl compiler warning, dropped some unused code and added some comments. Of great help in this process were: 1. ACPI specification, for understanding Thermal Zone and ASL language (it is quite simple assembler-like one, but you still need a reference to understand some methods, be sure of operand order, etc. 2. mbmon code to see how it reads certain measurements via SMB, specifically for the HWM chip that I have 3. HWM chip W83783S specification, to understand details of what it can do and how 4. PIIX4 specification, to understand SMB controller operation Also, through experiments I determined some details about how W83783S was wired on my motherboard. For example, the chip has the following pins related to fan control: 1. FAN1-IN 2. FAN2-IN 3. FAN3-IN / PWM1-OUT 4. PWM2-OUT / SCI So some pins can be wired and configured for different functions. My motherboard (MP2-BX-X) has 3 fan connectors, one specifically designated for CPU fan. Turned out that FAN1-IN and PWM1-OUT are used to measure and regulate speed of the CPU fan. FAN2-IN reads speed of the first chassis fan. PWM2-OUT / SCI is configured to generate SMI. So the for third fan we can not neither nor control speed. I had to play quite a lot to determine the above. Also through the experiments I established a relation between PWM register value (0-0xff) and actual fan RPM speed (mbmon was of great help, as well as a small utility too read/write arbitrary registers of W83783S via SMB). Various temperature levels were also chosen through experiments and guessing. Here are the links to to the original and hacked DSDT ASLs: http://www.icyb.net.ua/~avg/bx.asl.gz http://www.icyb.net.ua/~avg/bx.orig.asl.gz Side-by-side diff would most probably be the most informative. Here's an example of hw.acpi.thermal: hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.user_override: 0 hw.acpi.thermal.tz0.temperature: 40.5C hw.acpi.thermal.tz0.active: 2 hw.acpi.thermal.tz0.passive_cooling: 1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 65.0C hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 70.0C hw.acpi.thermal.tz0._ACx: 60.0C 53.0C 38.0C -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz1.temperature: 32.0C hw.acpi.thermal.tz1.active: -1 hw.acpi.thermal.tz1.passive_cooling: 0 hw.acpi.thermal.tz1.thermal_flags: 0 hw.acpi.thermal.tz1._PSV: -1 hw.acpi.thermal.tz1._HOT: -1 hw.acpi.thermal.tz1._CRT: 52.0C hw.acpi.thermal.tz1._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 BIG WARNING: should you ever decide to try to implement something like what I did on your system, you must understand that you can damage or destroy your hardware, or even come to personal harm. You must be very careful. You must be able to physically observe/monitor your hardware and you must be able interrupt your tests/experiments very quickly. You must know your hardware very well, you must know ACPI Thermal specification very well. You should not try any experiments if your hardware can not withstand some overheating for some time. I take no responsibility for any damage to your hardware or any personal harm that may result for your trying to follow my example. -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Sun Mar 2 18:59:35 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 882081065672 for ; Sun, 2 Mar 2008 18:59:35 +0000 (UTC) (envelope-from dieterich.joh@googlemail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id E5B658FC17 for ; Sun, 2 Mar 2008 18:59:34 +0000 (UTC) (envelope-from dieterich.joh@googlemail.com) Received: by fg-out-1718.google.com with SMTP id 16so4197491fgg.35 for ; Sun, 02 Mar 2008 10:59:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding:from; bh=Dq6fKBb9kBDLxYw4EBYUjxDkqrY579cmucpJQUxw2rk=; b=OQG5WsqdE98XdQtqulmIlEuiY3NPPdvQwZtq1YQwh7aqVRulhbA68WUhUYHGkej/wL4pZwBzpPG+Q1Iw+btxQAzsvXmEaLHzxzwxwjy3cLIia5hTF7mZAmoQJBTCzmsQo3v8XtoengDVToSJRBfNTAQAOkUQ7troE0CCAZ7t7jc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding:from; b=p21L99Vs1Wnyq5Ua/quYj9YwbTRX/Oee8mlGPDha2/xUgGjwivd6SfL6VxVE/ydR51pwoJ2Ie+6vr2FrcqEOLkPTbmXRQXUTimfBxn/fvCqrNgc8N5v1bLJTig1qNEmr8j6fBJ2uOGd5Uhdry/gUMTg+QQ4ivsFOTgwOIOmfyAI= Received: by 10.82.112.3 with SMTP id k3mr28950658buc.33.1204484370102; Sun, 02 Mar 2008 10:59:30 -0800 (PST) Received: from ?192.168.1.103? ( [79.210.89.28]) by mx.google.com with ESMTPS id l12sm10865872fgb.8.2008.03.02.10.59.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 02 Mar 2008 10:59:28 -0800 (PST) Message-ID: <47CAF90D.8090703@gmail.com> Date: Sun, 02 Mar 2008 19:59:25 +0100 User-Agent: Thunderbird 2.0.0.12 (X11/20080229) MIME-Version: 1.0 To: Ian Smith , freebsd-acpi@freebsd.org, "Alexandre \"Sunny\" Kovalenko" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit From: Johannes Dieterich Cc: Subject: Re: [RFC] Patch to enable temperature ceiling in powerd X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Mar 2008 18:59:35 -0000 Hi Ian and Alex, Ian Smith wrote: > On Sat, 1 Mar 2008, Johannes Dieterich wrote: > > Hello everybody! > > > > To get back to this discussion (sorry, normal job kicked me quite a bit > > last week). > > > > Peter Jeremy wrote: > > > On Wed, Feb 20, 2008 at 05:06:41PM -0500, Daniel Eischen wrote: > [..] > > > investigating an unrelated problem. We eventually decided it was a > > > faulty sensor and a replacement board fixed it. > > > What I have now is the original hard drive (some 80 gig Fujitsu one) > > with a freshly installed Fedora 8 on it. I have been letting two > > instances of gnuchess playing against each other for a couple of hours > > (yes, I know... best stress test ever... ;-) ) which kept cpu usage at a > > nice 100 percent on both cores for all that time. > > I doubt that it amounts to a buildworld, which flogs the disk pretty > hard too, but that should serve well enough for relative comparison. I do know that you can't compare it exactly. Although IMHO the missing ath0 is a bigger change than the missing I/O. However... > > > proc/acpi/thermal_zones/THM1/temperature (and THM0) reported > > temperatures around 70 degrees, never over 72 for all that time. Lid was > > closed, fan worked (not very noisy even) and blew a good load of hot air > > out. I am tempted to say that my overheating problem is not hardware > > related. Only parts different were ath0 not working with Fedora and hard > > drive being not the 160 gig WD I am using for FreeBSD. > > You could expect your 160GB drive to run a few degrees warmer, but most > likely still inside the tz1._PSV=80C suggested most recently, however > you haven't said whether you've yet tried applying the tz1 settings that > Alexandre last suggested as working well for his very similar model > Thinkpad on Feb 21st (previous message on this thread to yours)? Trying Alexandre's recommendations was anyway the next thing I wanted to try. Just wanted to once more blame the hardware before... ;-) So, after csup'ing to 7.0-STABLE as of today and setting the new system up, then sysctl hw.acpi.thermal.user_override=1 sysctl hw.acpi.thermal.tz1.passive_cooling=1 sysctl hw.acpi.thermal.tz1._PSV=80C as from Alexandre (thanks again for all your time! :-) ). I see the following behavior when make buildworld (without any -j flags). Temperature rises to around 72 degrees almost instantly, then to something like 83, the fan starts working, cooling the machine down. Frequency drops to 1000 MHz. But, however, I get the make buildworld through almost "out-of-the-box". So far, so good! :-) > > > >> Only under load does the temperature > > >> shoot up, but I know the chip isn't getting hot and the fan > > >> is running - I've felt around in there and nothing was even > > >> close to the 117+C it was sensing. > > But that was on tz0, wasn't it? Please read Alex's message carefully; > if there's still something different about yours we likely need to know. The above thing with "putting the hand into the machine" is not from me. Would also be rather difficult with my flat notebook. ;-) > > > > Apart from the actual CPU, most parts of a system have a fairly > > > significant thermal mass so a rapid change in temperature either > > > indicates a catastrophic failure or the temperature sensor isn't > > > really reporting the temperature of the relevant zone. > > > > > I totally agree with you, Peter. And either the hardware just fails > > under FreeBSD (or with ath0 and the other hard drive running) OR it is > > a FreeBSD problem. > > > > Everybody is invited to tell me how to stress test the system as brutal > > as possible to show that the problem is hardware related. > > It's possible, but suspecting the hardware may have been a red herring. > > It does seem more clearly related to some the recent flurry of software > changes to acpi_thermal.c, that should detect the fact that your cpu > thermal zone tz1 is the one needing monitoring, rather than tz0. Would it be worth/possible finding out where exactly the problem was? Still it is not running completely optimal IMHO (still WAY better than for months). Best regards and thanks again to everybody, Johannes From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 3 11:07:02 2008 Return-Path: Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E736106566B for ; Mon, 3 Mar 2008 11:07:02 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 17C158FC20 for ; Mon, 3 Mar 2008 11:07:02 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m23B71NN021952 for ; Mon, 3 Mar 2008 11:07:01 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m23B71mX021948 for freebsd-acpi@FreeBSD.org; Mon, 3 Mar 2008 11:07:01 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 Mar 2008 11:07:01 GMT Message-Id: <200803031107.m23B71mX021948@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2008 11:07:02 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o kern/81000 acpi [apic] Via 8235 sound card worked great with FreeBSD 5 s kern/91038 acpi [panic] [ata] [acpi] 6.0-RELEASE on Fujitsu Siemens Am s i386/91748 acpi acpi problem on Acer TravelMare 4652LMi (nvidia panic, o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/104625 acpi ACPI on ASUS A8N-32 SLI/ASUS P4P800 does not show ther o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/108954 acpi [acpi] 'sleep(1)' sleeps >1 seconds when speedstep (Cx o kern/114113 acpi [acpi] [patch] ACPI kernel panic during S3 suspend / r o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o amd64/115011 acpi ACPI problem ,reboot system down. o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o bin/118973 acpi [acpi]: Kernel panic with acpi boot o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/120953 acpi [acpi]: FreeBSD 6.3 Release: acpi_tz0: _TMP value is 20 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- f kern/67309 acpi zzz reboot computer (ACPI S3) o i386/69750 acpi Boot without ACPI failed on ASUS L5 s kern/73823 acpi [request] acpi / power-on by timer support o kern/76950 acpi ACPI wrongly blacklisted on Micron ClientPro 766Xi sys o kern/89411 acpi [acpi] acpiconf bug s kern/90243 acpi Laptop fan doesn't turn off (ACPI enabled) (Packard Be o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI o kern/103365 acpi [acpi] acpi poweroff doesn't work with geli device att o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/108017 acpi [acpi]: Acer Aspire 5600 o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/108581 acpi [sysctl] sysctl: hw.acpi.cpu.cx_lowest: Invalid argume o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/111591 acpi [acpi] dev.acpi_ibm.0.events returns I/O error (regres s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/114165 acpi [acpi] Dell C810 - ACPI problem o kern/114649 acpi [patch][acpi] panic: recursed on non-recursive mutex o kern/117605 acpi [acpi] [request] add debug.cpufreq.highest o kern/120515 acpi [acpi] [patch] acpi_alloc_wakeup_handler: can't alloc o amd64/120568 acpi cannot install 7.0-rc1: ACPI problem with abit ip35 pr o kern/121102 acpi [acpi_fujitsu] [patch] update acpi_fujitsu for the P80 21 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 3 18:01:28 2008 Return-Path: Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 304BA1065671; Mon, 3 Mar 2008 18:01:28 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 179BF8FC1E; Mon, 3 Mar 2008 18:01:28 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (gavin@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m23I1RCp060394; Mon, 3 Mar 2008 18:01:27 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m23I1Rrs060390; Mon, 3 Mar 2008 18:01:27 GMT (envelope-from gavin) Date: Mon, 3 Mar 2008 18:01:27 GMT Message-Id: <200803031801.m23I1Rrs060390@freefall.freebsd.org> To: lon_kamikaze@gmx.de, gavin@FreeBSD.org, freebsd-acpi@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: kern/111591: [acpi] dev.acpi_ibm.0.events returns I/O error (regression) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2008 18:01:28 -0000 Synopsis: [acpi] dev.acpi_ibm.0.events returns I/O error (regression) State-Changed-From-To: open->closed State-Changed-By: gavin State-Changed-When: Mon Mar 3 18:00:14 UTC 2008 State-Changed-Why: Submitter reports that this was fixed http://www.freebsd.org/cgi/query-pr.cgi?pr=111591 From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 3 19:40:08 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D9151065670 for ; Mon, 3 Mar 2008 19:40:08 +0000 (UTC) (envelope-from yousif@alumni.jmu.edu) Received: from coruscant.far-far-away.us (coruscant.far-far-away.us [70.91.196.65]) by mx1.freebsd.org (Postfix) with SMTP id E16008FC23 for ; Mon, 3 Mar 2008 19:40:07 +0000 (UTC) (envelope-from yousif@alumni.jmu.edu) Received: (qmail 48068 invoked from network); 3 Mar 2008 14:34:04 -0500 Received: from pknat1.passkey.com (HELO alderaan) (68.162.198.134) by coruscant.far-far-away.us with SMTP; 3 Mar 2008 14:34:04 -0500 Message-ID: <3C1C2FE1ADB147B7AE25E0CEA214A23D@alderaan> From: "Yousif Hassan" To: "Jan-Olof Lindqvist" References: <200802281645.00286.mistry.7@osu.edu> <47C73E8E.40706@gmail.com> <200802291045.39977.mistry.7@osu.edu> <863014ECF11048B78C23D1D31DCAFF40@alderaan> <47C849A8.10809@gmail.com> In-Reply-To: <47C849A8.10809@gmail.com> Date: Mon, 3 Mar 2008 14:41:16 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6000.16480 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16545 Cc: freebsd-acpi@freebsd.org Subject: Re: Fujitsu P8010: est: CPU supports Enhanced Speedstep, but is not recognized X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2008 19:40:08 -0000 Jan-Olof Lindqvist" wrote: > Even if it does attach the est-driver, I don't think it receives the > correct voltage to the processor. For example on my laptop I have been > running FreeBSD i386 and now amd64 with the Core 2 duo T7700, the fan > runs constantly and it feels hot where the processor is located. This is > not the case when running for ex Linux. There are probably two issues we're talking about here. The first issue is the one you mentioned above, which is that the voltage information is not accurate for Core 2 processors. This is probably true. I looked in the datasheets, it looks like Core 2s have more than one VID with a different setting in each. I suspect this means, as Nate Lawson has commented in the source, that the frequency/voltage table method won't work. So unfortunately I doubt it's as simple as adding some new tables. I don't know how Linux deals with this, but I downloaded the Linux kernel and will have a look. This probably explains why the frequencies available to my Core 2 (T7500) are different on FreeBSD. In this case it must be using the acpi_perf settings. Those do work pretty well in terms of keeping my temperature low, so I wonder what is happening in your case. Did you experience the heat issues even with the i386 kernel, or just amd64? The second issue is why est won't attach at all on amd64, like Anish's issue (and mine). Looks like the logic is something like this: if (acpi_perf is actively managing things) use it; else //try to enable est { if (there's a match in est tables) use it; else //try to use acpi_perf "read-only" settings { if (acpi_perf is attached) good, read frequencies from it; else refuse to attach est; } } It would seem that on both i386 and amd64, the table method will fail, since the info is not there. So that can't be the reason for a difference. This means est will resort to querying acpi_perf. acpi_perf, if it attaches in "silent" mode, will provide the frequency info to the est driver, which est then uses. So the question is - why does this fallback method not work for amd64? I need to play around with it and use some printfs / debugger to verify the logic. I might be missing something. > Maybe we should PR this? Probably, but more info would be helpful first. --Yousif From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 4 01:29:36 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFD591065671 for ; Tue, 4 Mar 2008 01:29:36 +0000 (UTC) (envelope-from vishketan@yahoo.com) Received: from web31708.mail.mud.yahoo.com (web31708.mail.mud.yahoo.com [68.142.201.188]) by mx1.freebsd.org (Postfix) with SMTP id D1D5D8FC1F for ; Tue, 4 Mar 2008 01:29:36 +0000 (UTC) (envelope-from vishketan@yahoo.com) Received: (qmail 54818 invoked by uid 60001); 4 Mar 2008 01:02:55 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=TbiempS2eUY4hcffay6eR5gwLRvABXYbnp7LEK1LxINWSFLU78+I+8nMwXN29p34qQwLmK64SSCeJNfANXNUzosc9Gxrt4Pjk+W79Bd0l/TWq6psMiIGFXOkRiWWRPon3FQgSquiVj7LVaq1L3aomUAjFxSvgNauFoF+bcGWc4Q=; X-YMail-OSG: Z3uRiCYVM1lHr.ACwWOEgg1oOS6GRuKCWg0z9F.2luUwTRHc.63MQugd2rKF0.sLnLyYw.LEZuH3Dw1fFwtGrX5vNaBWX3Wfsxl.ROnqSEvdxJ2K1Wo- Received: from [203.143.165.74] by web31708.mail.mud.yahoo.com via HTTP; Mon, 03 Mar 2008 17:02:55 PST Date: Mon, 3 Mar 2008 17:02:55 -0800 (PST) From: Vishwanathan S V N To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <492229.54112.qm@web31708.mail.mud.yahoo.com> Subject: Sony Vaio VGN SZ483NC warm docking issues X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Mar 2008 01:29:37 -0000 Hi, I am running DesktopBSD 1.6.1 live DVD on my sony vaio VGN SZ483NC laptop with a corresponding docking station and am having problems with warm docking the laptop. I am new to BSD but have used various flavors of *Unix (mainly Linux) on and off for the past 10 years. So please let me know if something is unclear or if you me to run any command for more information. Scenario 1: If I boot the laptop while it is docked then the Marvell Yukon Ethernet card (PCI) is recognized correctly and I can do a kldload if_msk and it shows up if I do ifconfig. I can also do a dhclient msk1 and configure it using DHCP. If I now try to undock the laptop by pressing the Undock button on the docking station nothing happens. The "In Use" orange LED continues to glow. But I can detach the laptop from the docking station with no hard lockups or kernel panics. Of course the network card is no longer available, but pciconf -lv still shows the card as available. Scenario 2: If I boot the laptop away from the dock and then subsequently dock it the Ethernet card on the docking station is not recognized at all. The "In Use" LED also does not glow indicating that the OS did not recognize the docking station. The problem only seems to be with the PCI card and not with the other USB devices or the monitor connected to the docking station. Summary: I think a PCI bus scan is not triggered every time the machine docks or undocks thus preventing warm docking. Files: My decompiled asl can be found at http://users.rsise.anu.edu.au/~vishy/FreeBSD/sony-vaio-vgn-sz483nc.asl Output from various commands like uname -a, pciconf -lv, ifconfig etc can be found at http://users.rsise.anu.edu.au/~vishy/FreeBSD/dmesg.txt http://users.rsise.anu.edu.au/~vishy/FreeBSD/hw.acpi.txt http://users.rsise.anu.edu.au/~vishy/FreeBSD/ifconfig.txt http://users.rsise.anu.edu.au/~vishy/FreeBSD/pciconf-lv.txt http://users.rsise.anu.edu.au/~vishy/FreeBSD/uname-a.txt Other Information: This works perfectly under Windows Vista. A similar bug exists under Linux. In fact the machine hard freezes whenever the Ethernet card on the docking station is in use and I undock the machine without pressing the Undock button. More details about the problem can be found at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/194617 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/163211 and http://ubuntuforums.org/showthread.php?t=666757 I believe that the SONY docking stations are slightly different from the IBM ones in that the docking station does not appear as a device under PCI0 but appears as a separate device. This seems to be common feature of most SONY laptops which support a docking station. vishy ps: I am not subscribed to the list. So please CC me on any replies. ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 4 04:29:10 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71C351065742 for ; Tue, 4 Mar 2008 04:29:10 +0000 (UTC) (envelope-from iwasaki@jp.FreeBSD.org) Received: from locore.org (ns01.locore.org [218.45.21.227]) by mx1.freebsd.org (Postfix) with ESMTP id 119928FC18 for ; Tue, 4 Mar 2008 04:29:09 +0000 (UTC) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (celeron.v4.locore.org [192.168.0.10]) by locore.org (8.13.8/8.13.8/iwasaki) with ESMTP/inet id m2445guL026407; Tue, 4 Mar 2008 13:05:42 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Date: Tue, 04 Mar 2008 13:05:38 +0900 (JST) Message-Id: <20080304.130538.78715211.iwasaki@jp.FreeBSD.org> To: vishketan@yahoo.com From: Mitsuru IWASAKI In-Reply-To: <492229.54112.qm@web31708.mail.mud.yahoo.com> References: <492229.54112.qm@web31708.mail.mud.yahoo.com> X-Mailer: Mew version 3.3 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: Sony Vaio VGN SZ483NC warm docking issues X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Mar 2008 04:29:10 -0000 Hi, > Summary: > > I think a PCI bus scan is not triggered every time the > machine docks or undocks thus preventing warm docking. [snip] > Output from various commands like uname -a, pciconf > -lv, ifconfig etc can be found at > > http://users.rsise.anu.edu.au/~vishy/FreeBSD/dmesg.txt It seems that acpi_dock driver is not loaded at boot time. Please add following line into /boot/loader.conf and reboot. ---- acpi_dock_load="YES" --- Thanks From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 4 07:50:49 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F0CC1065679 for ; Tue, 4 Mar 2008 07:50:49 +0000 (UTC) (envelope-from vishketan@yahoo.com) Received: from n15.bullet.mail.mud.yahoo.com (n15.bullet.mail.mud.yahoo.com [68.142.201.238]) by mx1.freebsd.org (Postfix) with SMTP id 5E4428FC3A for ; Tue, 4 Mar 2008 07:50:49 +0000 (UTC) (envelope-from vishketan@yahoo.com) Received: from [68.142.194.243] by n15.bullet.mail.mud.yahoo.com with NNFMP; 04 Mar 2008 07:38:36 -0000 Received: from [209.191.119.164] by t1.bullet.mud.yahoo.com with NNFMP; 04 Mar 2008 07:38:36 -0000 Received: from [127.0.0.1] by omp103.mail.mud.yahoo.com with NNFMP; 04 Mar 2008 07:38:36 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 453813.73295.bm@omp103.mail.mud.yahoo.com Received: (qmail 9553 invoked by uid 60001); 4 Mar 2008 07:38:36 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=C4MWHr78sFlwpLY0805fi9QST8o0eFSdg0YwCLf237nBefo7E4aCE9W0iGVDj3XRSk26HincSubP/qnGyG9Hm670u7FAlA0igB1MzMIA3NTvOD9MSsFYmPVZ3CO4+NJ0Gx4M7KDqrmG8lpMrbPtijOGEhXI7KJoJz5e2B5T5cwY=; X-YMail-OSG: GNqlX6gVM1mAy7EwfOig_YeQYIm165Dmjd_6ztWJt.CqYZDVvMJH2_VMizQY5shsVHUm0ujBrE4VZUHtSoY28YqocwUK6mlSCamrhVCLwRTZgnI- Received: from [203.143.165.94] by web31701.mail.mud.yahoo.com via HTTP; Mon, 03 Mar 2008 23:38:34 PST X-Mailer: YahooMailRC/902.35 YahooMailWebService/0.7.162 Date: Mon, 3 Mar 2008 23:38:34 -0800 (PST) From: Vishwanathan S V N To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <988419.9302.qm@web31701.mail.mud.yahoo.com> Cc: Mitsuru IWASAKI Subject: Re: Sony Vaio VGN SZ483NC warm docking issues X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Mar 2008 07:50:49 -0000 Hi! It seems that acpi_dock driver is not loaded at boot time. Please add following line into /boot/loader.conf and reboot. ---- acpi_dock_load="YES" --- I am using a live DVD so cannot use the /boot/loader.conf option but instead did a kldload acpi_dock. I can undock successfully but I still have problems with redocking the machine :( Updated dmesg http://users.rsise.anu.edu.au/~vishy/FreeBSD/dmesg1.txt and cat /var/log/messages http://users.rsise.anu.edu.au/~vishy/FreeBSD/messages.txt Please let me know if you need any further information. vishy ps: I have similar issues with the latest 2.6.24 Linux kernels. I can undock successfully once but the machine never redocks properly. ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 4 19:37:22 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7AB7D1065673 for ; Tue, 4 Mar 2008 19:37:22 +0000 (UTC) (envelope-from SRS0=9bb1db26f828b9413011f0954821e74d8b1b5bdc=630=es.net=oberman@es.net) Received: from postal1.es.net (postal1.es.net [IPv6:2001:400:14:3::6]) by mx1.freebsd.org (Postfix) with ESMTP id E5A758FC21 for ; Tue, 4 Mar 2008 19:37:21 +0000 (UTC) (envelope-from SRS0=9bb1db26f828b9413011f0954821e74d8b1b5bdc=630=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id KWP05420; Tue, 04 Mar 2008 11:37:20 -0800 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 7073945045; Tue, 4 Mar 2008 11:37:19 -0800 (PST) To: Vishwanathan S V N In-Reply-To: Your message of "Mon, 03 Mar 2008 23:38:34 PST." <988419.9302.qm@web31701.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1204659439_13076P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Tue, 04 Mar 2008 11:37:19 -0800 From: "Kevin Oberman" Message-Id: <20080304193719.7073945045@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ; ; ; X-Sender: X-To_Name: Vishwanathan S V N X-To_Domain: yahoo.com X-To: Vishwanathan S V N X-To_Email: vishketan@yahoo.com X-To_Alias: vishketan Cc: freebsd-acpi@freebsd.org, Mitsuru IWASAKI Subject: Re: Sony Vaio VGN SZ483NC warm docking issues X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Mar 2008 19:37:22 -0000 --==_Exmh_1204659439_13076P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Mon, 3 Mar 2008 23:38:34 -0800 (PST) > From: Vishwanathan S V N > Sender: owner-freebsd-acpi@freebsd.org > > Hi! > > It seems that acpi_dock driver is not loaded at boot time. > Please add following line into /boot/loader.conf and reboot. > ---- > acpi_dock_load="YES" > --- > > I am using a live DVD so cannot use the /boot/loader.conf option but > instead did a kldload acpi_dock. > > I can undock successfully but I still have problems with redocking the > machine :( > > Updated dmesg > > http://users.rsise.anu.edu.au/~vishy/FreeBSD/dmesg1.txt > > and cat /var/log/messages > > http://users.rsise.anu.edu.au/~vishy/FreeBSD/messages.txt > > > Please let me know if you need any further information. > > vishy > > ps: I have similar issues with the latest 2.6.24 Linux kernels. I can > undock successfully once but the machine never redocks properly. kldload won't do the trick. If you can't put it in loader.conf (and you can't), you need to load the module at the loader "OK" prompt (load /kernel/acpi_dock.ko) and then "boot". -- 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 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1204659439_13076P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFHzaTvkn3rs5h7N1ERAg9NAKCDCJn2+DHrpLA/ywdzBDtyKq0BigCfQa00 DQmwhjLn2bxCvyzu6O2rwjA= =xysJ -----END PGP SIGNATURE----- --==_Exmh_1204659439_13076P-- From owner-freebsd-acpi@FreeBSD.ORG Wed Mar 5 00:38:52 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A102A1065675 for ; Wed, 5 Mar 2008 00:38:52 +0000 (UTC) (envelope-from vishketan@yahoo.com) Received: from n7a.bullet.mud.yahoo.com (n7a.bullet.mud.yahoo.com [216.252.100.61]) by mx1.freebsd.org (Postfix) with SMTP id 602D58FC22 for ; Wed, 5 Mar 2008 00:38:52 +0000 (UTC) (envelope-from vishketan@yahoo.com) Received: from [209.191.108.97] by n7.bullet.mud.yahoo.com with NNFMP; 05 Mar 2008 00:26:24 -0000 Received: from [209.191.119.184] by t4.bullet.mud.yahoo.com with NNFMP; 05 Mar 2008 00:26:24 -0000 Received: from [127.0.0.1] by omp107.mail.mud.yahoo.com with NNFMP; 05 Mar 2008 00:26:24 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 643404.5300.bm@omp107.mail.mud.yahoo.com Received: (qmail 67494 invoked by uid 60001); 5 Mar 2008 00:26:24 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=HYXcX8I2qUh+KFtOfE1KATg98N+/h3yV/AoZPdZcmotI5qeTEV2kK1Exba/+hLKSDfdg15wB8TGXQxuooCoSHs2O/222RZrUnAwTGIA0n4Bwzb/5d3ydI9/R/sAYUHbY9rssRNNgcRGQxYJdY2IatKaZ4ZfqN0hLmd9sRHtrYm4=; X-YMail-OSG: YJP6H_IVM1l01TpF4A7gClrpfr0XLrtw4OVpzX_CPQ.jrr2.7xxxTD58zVCkKHq3ESQhjQEcSKFaB0R1olVtAhRDrPW.fB7k9FkNbdIGZsCRGvU- Received: from [203.143.165.94] by web31701.mail.mud.yahoo.com via HTTP; Tue, 04 Mar 2008 16:26:24 PST X-Mailer: YahooMailRC/902.35 YahooMailWebService/0.7.162 Date: Tue, 4 Mar 2008 16:26:24 -0800 (PST) From: Vishwanathan S V N To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <242129.65770.qm@web31701.mail.mud.yahoo.com> Cc: Mitsuru IWASAKI Subject: Re: Sony Vaio VGN SZ483NC warm docking issues X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Mar 2008 00:38:52 -0000 Hi! > kldload won't do the trick. If you can't put it in loader.conf (and you > can't), you need to load the module at the loader "OK" prompt (load > /kernel/acpi_dock.ko) and then "boot". I used load acpi_dock.ko and then boot as suggested by you but the problem still persists. I can undock successfully but cannot redock. Updated dmesg http://users.rsise.anu.edu.au/~vishy/FreeBSD/dmesg2.txt and cat /var/log/messages http://users.rsise.anu.edu.au/~vishy/FreeBSD/messages2.txt Please let me know if you want me to try anything else. vishy ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping From owner-freebsd-acpi@FreeBSD.ORG Wed Mar 5 13:38:31 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAD151065677 for ; Wed, 5 Mar 2008 13:38:31 +0000 (UTC) (envelope-from konrad.rybacki@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id 32B4D8FC27 for ; Wed, 5 Mar 2008 13:38:30 +0000 (UTC) (envelope-from konrad.rybacki@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so3350280uge.37 for ; Wed, 05 Mar 2008 05:38:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date:user-agent:mime-version:content-disposition:content-type:content-transfer-encoding:message-id; bh=kYOacjpzPMv4zrynoxu3g/qwC/ADbbDHaiWqEzBkJTM=; b=RiTd3ihOdPMdJHr2h8aWJtz1gkiVsvOO85/V6hmnz80voYp7zERSY34cHfyymK0j8sth9R2w1eSj74PdR1fwpEyN6Hh8VceMnSPds8lJ0wwqc4WEsi7YNP2V1cxNyPK78uEfW9td/EWmO+FLT0eEdB8fzBPvkPWsTIb5qmTzzTc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:mime-version:content-disposition:content-type:content-transfer-encoding:message-id; b=k8HfqxUzJ6LrlMaTsE9nL8Bu3jf5w3PP/kTjGGYfGwewNzZrt4Lihfnia3w+CBGADRRqDT+tugDAtim3LKzGp+hFqLDO5mqJoFHHO25EN5qbpwxSg1dJ491JzYrkTNB7RL3C4qdZzTPHHSpvBn2R05PSZAIXmMl03gcaQZnYx6E= Received: by 10.66.237.9 with SMTP id k9mr6505699ugh.13.1204722822914; Wed, 05 Mar 2008 05:13:42 -0800 (PST) Received: from ?192.168.1.3? ( [87.207.98.162]) by mx.google.com with ESMTPS id n34sm3784505ugc.64.2008.03.05.05.13.40 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 05 Mar 2008 05:13:41 -0800 (PST) From: KR To: freebsd-acpi@freebsd.org Date: Wed, 5 Mar 2008 14:13:35 +0100 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Message-Id: <200803051413.37111.konrad.rybacki@gmail.com> Subject: ACPI S3 causes system to freeze on Toshiba Tecra A8 with FreeBSD 7.0. X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Mar 2008 13:38:31 -0000 I've built UP kernel and disabled APIC in /boot/loader.conf: hint.apic.0.disabled=1 Issuing zzz or acpiconf -s 3 causes the system to freeze. Only the lcd backlight is turned off - cpu fan, hard disk and led indicators are still working. Pressing power-off button or hitting random keys doesn't wake up the system. The only way is to hold power-off button for longer than 4 seconds and completely turn off the notebook. ASL: http://s.rootnode.net/~rybacki/tecra_a8_148.asl.gz verbose dmesg: http://s.rootnode.net/~rybacki/dmesg sysctl -a | grep hw.acpi: http://s.rootnode.net/~rybacki/acpi From owner-freebsd-acpi@FreeBSD.ORG Wed Mar 5 16:19:35 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A821C1065670 for ; Wed, 5 Mar 2008 16:19:35 +0000 (UTC) (envelope-from iwasaki@jp.FreeBSD.org) Received: from locore.org (ns01.locore.org [218.45.21.227]) by mx1.freebsd.org (Postfix) with ESMTP id 1FDE78FC23 for ; Wed, 5 Mar 2008 16:19:34 +0000 (UTC) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (celeron.v4.locore.org [192.168.0.10]) by locore.org (8.13.8/8.13.8/iwasaki) with ESMTP/inet id m25GJVv4013448; Thu, 6 Mar 2008 01:19:31 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Date: Thu, 06 Mar 2008 01:19:31 +0900 (JST) Message-Id: <20080306.011931.35019967.iwasaki@jp.FreeBSD.org> To: vishketan@yahoo.com From: Mitsuru IWASAKI In-Reply-To: <242129.65770.qm@web31701.mail.mud.yahoo.com> References: <242129.65770.qm@web31701.mail.mud.yahoo.com> X-Mailer: Mew version 3.3 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: Sony Vaio VGN SZ483NC warm docking issues X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Mar 2008 16:19:35 -0000 Hi, > I used load acpi_dock.ko and then boot as suggested by you but the problem still persists. I can undock successfully but cannot redock. Hmm, your \_SB.DOCK._STA method always seems to return zero (i.e. dock status method indicates that the system is undocked all the time) that's why the same problem occurs on Linux kernel, I guess. Could you try the following to prove my guess? Case 1: boot the docked system. Then obtain dock device information by sysctl and dmesg command. # sysctl dev.acpi_dock > acpi_dock-boot.txt # dmesg > dmesg-boot.txt Case 2: boot the undocked system and dock. sysctl command after docking. # sysctl dev.acpi_dock > acpi_dock-docked.txt # dmesg > dmesg-docked.txt Case 3: boot the docked system, undock and redock. sysctl command after redocking. # sysctl dev.acpi_dock > acpi_dock-redocked.txt # dmesg > dmesg-redocked.txt `load /boot/kernel/acpi_dock' and `boot -v (verbose boot) at loader prompt would be helpful. Thanks From owner-freebsd-acpi@FreeBSD.ORG Thu Mar 6 00:01:20 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A47AB1065671 for ; Thu, 6 Mar 2008 00:01:20 +0000 (UTC) (envelope-from vishketan@yahoo.com) Received: from n8c.bullet.mail.mud.yahoo.com (n8c.bullet.mail.mud.yahoo.com [209.191.87.106]) by mx1.freebsd.org (Postfix) with SMTP id 702778FC1D for ; Thu, 6 Mar 2008 00:01:20 +0000 (UTC) (envelope-from vishketan@yahoo.com) Received: from [68.142.194.243] by n8.bullet.mail.mud.yahoo.com with NNFMP; 06 Mar 2008 00:01:19 -0000 Received: from [209.191.119.153] by t1.bullet.mud.yahoo.com with NNFMP; 06 Mar 2008 00:01:19 -0000 Received: from [127.0.0.1] by omp100.mail.mud.yahoo.com with NNFMP; 06 Mar 2008 00:01:19 -0000 X-Yahoo-Newman-Property: ymail-5 X-Yahoo-Newman-Id: 736275.28330.bm@omp100.mail.mud.yahoo.com Received: (qmail 35002 invoked by uid 60001); 6 Mar 2008 00:01:18 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=qVfLAlCOExRiZ8mzt1IAkul0usbDl8AkNGA8d2390WeDf7A1MDzCzKHoMXte+A2arQVjiA7gnfFnSFzh2yLbUyn/peOCfsyIm0Q4/QOtheBvbagdYLrqps4Mj5JGiLF27VeVGR6vlq2/48XSkCpGLdzs56WMkVVxs6fOg/rjLS0=; X-YMail-OSG: hJANcRoVM1moo72rtKjMzb0NWiaKhru4NGqCQ6aciOM1CQ7N8y87z.A_Qg.7.VWaGsV2IVST6HyJpYrrtdGY7VW7aUF0Wz1Y_ndVc2yUEUI8p3s- Received: from [203.143.165.94] by web31704.mail.mud.yahoo.com via HTTP; Wed, 05 Mar 2008 16:01:12 PST X-Mailer: YahooMailRC/902.35 YahooMailWebService/0.7.162 Date: Wed, 5 Mar 2008 16:01:12 -0800 (PST) From: Vishwanathan S V N To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <860839.34422.qm@web31704.mail.mud.yahoo.com> Cc: Mitsuru IWASAKI Subject: Re: Sony Vaio VGN SZ483NC warm docking issues X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Mar 2008 00:01:20 -0000 Hi, > > I used load acpi_dock.ko and then boot as suggested by you but the problem still persists. I can undock successfully but cannot redock. > Hmm, your \_SB.DOCK._STA method always seems to return zero (i.e. dock > status method indicates that the system is undocked all the time) > that's why the same problem occurs on Linux kernel, I guess. It looks like your guess might be right. > Case 1: boot the docked system. > Then obtain dock device information by sysctl and dmesg command. > # sysctl dev.acpi_dock > acpi_dock-boot.txt > # dmesg > dmesg-boot.txt http://users.rsise.anu.edu.au/~vishy/FreeBSD/acpi_dock-boot.txt http://users.rsise.anu.edu.au/~vishy/FreeBSD/dmesg-boot.txt > Case 3: boot the docked system, undock and redock. > sysctl command after redocking. > # sysctl dev.acpi_dock > acpi_dock-redocked.txt > # dmesg > dmesg-redocked.txt http://users.rsise.anu.edu.au/~vishy/FreeBSD/acpi_dock-redocked.txt http://users.rsise.anu.edu.au/~vishy/FreeBSD/dmesg-redocked.txt > Case 2: boot the undocked system and dock. > sysctl command after docking. > # sysctl dev.acpi_dock > acpi_dock-docked.txt > # dmesg > dmesg-docked.txt http://users.rsise.anu.edu.au/~vishy/FreeBSD/acpi_dock-docked.txt http://users.rsise.anu.edu.au/~vishy/FreeBSD/dmesg-docked.txt I did Case 1 and Case 3 in the same boot i.e. I booted docked then obtained the sysctl and dmesg information. Then undocked and redocked and obtained the information again. I hope that is OK. If I understand correctly this method from the decompiled dsdt might be at fault: Method (_STA, 0, NotSerialized) { If (LEqual (\_SB.PCI0.LPCB.EC0.ECOK, 0x00)) { If (LAnd (PHSB (0xD4, 0x9E), 0x40)) { Return (0x0F) } Else { Return (0x00) } } Else { If (\_SB.PCI0.LPCB.EC0.IUSE) { Return (0x0F) } Else { Return (0x00) } } } I can see from the dmesg that when I boot docked then this method returns 0x0F as expected. But when I redock it seems to return 0x00. Can we figure out which of the two cases if(LEqual ...) or else is being triggered when I redock or dock after booting outside? vishy ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping From owner-freebsd-acpi@FreeBSD.ORG Thu Mar 6 00:04:21 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9DB3106566B for ; Thu, 6 Mar 2008 00:04:21 +0000 (UTC) (envelope-from vishketan@yahoo.com) Received: from web31715.mail.mud.yahoo.com (web31715.mail.mud.yahoo.com [68.142.201.195]) by mx1.freebsd.org (Postfix) with SMTP id 92BF78FC19 for ; Thu, 6 Mar 2008 00:04:21 +0000 (UTC) (envelope-from vishketan@yahoo.com) Received: (qmail 40396 invoked by uid 60001); 6 Mar 2008 00:04:20 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=rthKnu4eJGx844uFlF93MonGXelpUYCwGiSU8IC8WQobtac2SGYI1dsknUgvdu81S8Qiccdr6A7YuxJzIWvzJAvGOi4YxrygAO/NXdKdrb9zPn/cEGjw9o0TjzbXFtGje893SXFYK1YreD5tGKJ2Eo4SZpEshP2VhKVXPzmGpzQ=; X-YMail-OSG: CD6RrB8VM1mUM6LjCMkuf5jlSXAgOa9m8m8kCGcSFWrRdD3ww3BXzc07N9OtZujVhbi1ruaq4T3qq6lLMV08P72y1kORn5xoSJKmF8orUfkDQOQoecnIT8kU7MHYYDiaaavc7ubkDf0a Received: from [203.143.165.94] by web31715.mail.mud.yahoo.com via HTTP; Wed, 05 Mar 2008 16:04:20 PST X-Mailer: YahooMailRC/902.35 YahooMailWebService/0.7.162 Date: Wed, 5 Mar 2008 16:04:20 -0800 (PST) From: Vishwanathan S V N To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <639139.36385.qm@web31715.mail.mud.yahoo.com> Subject: Support for Fn keys on a Sony laptop X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Mar 2008 00:04:22 -0000 Hi! I posted this to the freebsd-mobile mailing list and got no response. Maybe someone from the freebsd-acpi list knows the answer. I am new to FreeBSD so please be gentle on me, especially if this is a FAQ. I am running DesktopBSD 1.6.1 live DVD on my sony vaio VGN SZ483NC laptop. I notice that the acpi_ibm module is very feature rich while the acpi_sony module almost feels like a stub. I know that under Linux there has been extensive work to reverse engineer the Fn keys on sony Vaio laptops. See http://tjworld.net/snc/ or http://ubuntuforums.org/showthread.php?t=465491 I am wondering if something similar to that is already available or in the works for FreeBSD as well? If it not available, how much work would it be to port things over? Is the acpi_sony.c the relevant file to look into? vishy ps: Please cc me on the replies since I am not subscribed to the list. ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs From owner-freebsd-acpi@FreeBSD.ORG Thu Mar 6 20:33:45 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE8DF1065670 for ; Thu, 6 Mar 2008 20:33:45 +0000 (UTC) (envelope-from top_gun_canada@yahoo.com) Received: from web30905.mail.mud.yahoo.com (web30905.mail.mud.yahoo.com [68.142.200.158]) by mx1.freebsd.org (Postfix) with SMTP id 99AEF8FC2D for ; Thu, 6 Mar 2008 20:33:45 +0000 (UTC) (envelope-from top_gun_canada@yahoo.com) Received: (qmail 47248 invoked by uid 60001); 6 Mar 2008 20:07:05 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=R18IDvOxTZXkI0EDCt1ijlc5f/dJl4gvlcSCvRoF6+WhC/I2dUK9zemRnc/gNQQCKUo7GzleJR8YjmdFjqNPC6vPdgerRFpFoTdzPIxx8zhOi618GHgg07GJI/61nCxC9kT28HlsJHVnCgiAVRQmwNiBSPe538d2gpsDyZzpRH0=; X-YMail-OSG: wnuhchIVM1klmFdNEkhC4sAPoAHw2Jn55Wm1Trs.caweNNUwccAo9fVabyr41s_ANVMqfK29WcTDR2l27SWc_Gj4svxGpvzo08Q6FZkEu231zPSMhhU- Received: from [70.74.28.140] by web30905.mail.mud.yahoo.com via HTTP; Thu, 06 Mar 2008 12:07:05 PST Date: Thu, 6 Mar 2008 12:07:05 -0800 (PST) From: B J To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <593041.46435.qm@web30905.mail.mud.yahoo.com> Subject: ACPI Problem: "acpi_tz0:_TMP value is absurd" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Mar 2008 20:33:46 -0000 A few weeks ago, I upgraded my Compaq Presario desktop machine from FreeBSD 6.2 to 6.3. I soon noticed this message on the screen. Apparently, the system is measuring the temperature of absolute zero. At first, I thought it to be an installation error on my part, but reformatting the hard drive and re-installing 6.3 didn't change anything. This message still appears in 7.0. I installed 6.3 on a Thinkpad laptop but there doesn't seem to be a problem with that machine. A search through Google showed that other users are having the same difficulty but I haven't found a solution yet. It's quite frustrating as there doesn't seem to be a file which I could edit to reset ACPI, either is there anything in the desktop machine's BIOS. Does anyone have any suggestions? Thank you. BMJ ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs From owner-freebsd-acpi@FreeBSD.ORG Thu Mar 6 23:49:04 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF0FC1065671 for ; Thu, 6 Mar 2008 23:49:04 +0000 (UTC) (envelope-from jim.eberle@fastnlight.com) Received: from pro24.abac.com (pro24.abac.com [66.226.64.25]) by mx1.freebsd.org (Postfix) with ESMTP id AFAAA8FC13 for ; Thu, 6 Mar 2008 23:49:04 +0000 (UTC) (envelope-from jim.eberle@fastnlight.com) Received: from thinkpad.local (adsl-76-229-131-179.dsl.pltn13.sbcglobal.net [76.229.131.179]) (authenticated bits=0) by pro24.abac.com (8.14.1/8.14.1) with ESMTP id m26NMjC1089090 for ; Thu, 6 Mar 2008 15:22:46 -0800 (PST) (envelope-from jim.eberle@fastnlight.com) To: freebsd-acpi@freebsd.org From: Jim Eberle Date: Thu, 06 Mar 2008 15:22:45 -0800 Sender: jeberle@pro24.abac.com Message-Id: <1204845766.1189@thinkpad.local> X-Spam-Score: 1 (FORGED_RCVD_HELO) Subject: ichss makes ThinkPad R31 toasty X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Mar 2008 23:49:05 -0000 I recently upgraded the BIOS (famous last words) on my ThinkPad R31. I've been running FreeBSD 7.0RC3 on it for several months now. I had noticed before the BIOS upgrade, that under high workloads the machine would slow to a crawl. That is in fact why I did the upgrade. I thought the BIOS was flaky or out of sync w/ what FreeBSD expected. After the BIOS upgrade I noticed a new driver was loading: ichss. Unfortunately, the machine now behaves like it had in the past under high workload all the time. Just booting sends the temperature up to 90C (formerly 57C), starts the fan on high, and cuts performance to 70%. Either the temperature readings are wrong (unlikely), or simply enabling SpeedStep ICH is making the machine into a toaster. :) I added the following to device.hints: hint.ichss.0.disabled="1" Obviously, w/o ichss (or est or acpi_perf which aren't supported by this hardware) there are no ".freq/.freq_levels" sysctls, so cpufreq won't run. Without ichss the machine behaves OK under normal loads but still drops into ultra-slow mode when hot. I would like to get cpufreq + ichss working to do some sort of CPU throttling, such that the machine slows down to cool off, and then, and this is the important part, _speeds up again_! Any guidance much appreciated, Jim Eberle [ Sorry for the length of this message, BTW ] /var/log/messages -- trimmed: FreeBSD 7.0-RELEASE #5: Thu Mar 6 12:35:35 PST 2008 root@thinkpad.local:/usr/obj/usr/src/sys/THINKPAD Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(TM) CPU 1066MHz (1067.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383f9ff ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on vgapci0 uhci0: port 0xa4a0-0xa4bf irq 11 at device 29.0 on pci0 /var/log/messages -- with ichss ON: ichss: enabling SpeedStep support ichss: enabling SpeedStep support <-- loads twice??? ichss0: on cpu0 cpufreq: initializing cpufreq0 cpufreq: initializing one-time data for cpufreq0 From owner-freebsd-acpi@FreeBSD.ORG Fri Mar 7 03:57:10 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C00E106566C for ; Fri, 7 Mar 2008 03:57:10 +0000 (UTC) (envelope-from glorgster@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.191]) by mx1.freebsd.org (Postfix) with ESMTP id 6DE1F8FC1A for ; Fri, 7 Mar 2008 03:57:10 +0000 (UTC) (envelope-from glorgster@gmail.com) Received: by rv-out-0910.google.com with SMTP id g13so158724rvb.43 for ; Thu, 06 Mar 2008 19:57:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type; bh=2gQfF7rhhGyNys0wkd6o4jYXodpSKQBrMRtf9ZZw+6U=; b=tS3j8ooX9ocMjY5RuI0InzxrvdQ0oOgQjdmYxdbVd0ycifXEdsw413Sz/25pGxAGvczXTHNWbDOAhu1v9hCvQNBVa4UcK/ycQjBxgljQMxUp2w/DkyUZr5bW0wTKFsfU8ZbrVOCqwfZ20DFSdTESr4R4vSMMv4US9gFLw+3Oaic= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type; b=acqeon7nOWNsogH4pEYEZVGzs0Dp1mo+35VrS7igGQeub0yxgvluriRXMnEigdQTU0I1Ym7m3j9/kS4YuqLpXUdu81UgIZpxSKmxBHNhi4jPfrcWzb+Jdq2RIL4AqfmU71QDUwIdhSLHO/XFjucxOb3uAZQFI02jsGiZTljjwmQ= Received: by 10.141.129.14 with SMTP id g14mr260596rvn.209.1204860770220; Thu, 06 Mar 2008 19:32:50 -0800 (PST) Received: by 10.140.142.15 with HTTP; Thu, 6 Mar 2008 19:32:50 -0800 (PST) Message-ID: Date: Fri, 7 Mar 2008 13:32:50 +1000 From: "Alexey Tarasov" To: freebsd-acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: vishketan@yahoo.com Subject: Re: Support for Fn keys on a Sony laptop X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2008 03:57:10 -0000 I've worked a little bit with it (but after I've binded Fn keys in Gnome to needed for me actions - I've stopped working with keys). Now I'm trying to add nodes for fan speed check (it may be done by reading EC data), but I've some difficulties cause I'm new to FreeBSD drivers. acpi_sony.c is very old and implements some basic functions of SNC. But there is also SPIC related driver, that is even more older and not supports newer models (so-called type 3). Linux driver handles both SNC and SPIC in one module (actually, there were two drivers earlier, but they have united to sony-laptop I've SZ4MRN, FreeBSD 7. If you want, we may collaborate on acpi_sony driver. --- Best regards, Alexey Hi! > > I posted this to the freebsd-mobile mailing list and got no response. > Maybe someone from the freebsd-acpi list knows the answer. > > I am new to FreeBSD so please be gentle on me, especially if this is a > FAQ. > > I am running DesktopBSD 1.6.1 live DVD on my sony vaio VGN SZ483NC laptop. > I notice that the acpi_ibm module is very feature rich while the acpi_sony > module almost feels like a stub. > > I know that under Linux there has been extensive work to reverse engineer > the Fn keys on sony Vaio laptops. See > > http://tjworld.net/snc/ > > or > > http://ubuntuforums.org/showthread.php?t=465491 > > I am wondering if something similar to that is already available or in the > works for FreeBSD as well? > > If it not available, how much work would it be to port things over? Is the > acpi_sony.c the relevant file to look into? > > vishy > > ps: Please cc me on the replies since I am not subscribed to the list. > From owner-freebsd-acpi@FreeBSD.ORG Fri Mar 7 04:48:31 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70527106566B for ; Fri, 7 Mar 2008 04:48:31 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 398B58FC1E for ; Fri, 7 Mar 2008 04:48:31 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 13129 invoked from network); 7 Mar 2008 04:48:32 -0000 Received: from ppp-71-139-53-222.dsl.snfc21.pacbell.net (HELO ?10.0.5.18?) (nate-mail@71.139.53.222) by root.org with ESMTPA; 7 Mar 2008 04:48:32 -0000 Message-ID: <47D0C917.6020904@root.org> Date: Thu, 06 Mar 2008 20:48:23 -0800 From: Nate Lawson User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Jim Eberle References: <1204845766.1189@thinkpad.local> In-Reply-To: <1204845766.1189@thinkpad.local> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: ichss makes ThinkPad R31 toasty X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2008 04:48:31 -0000 Jim Eberle wrote: > I recently upgraded the BIOS (famous last words) on my ThinkPad R31. > I've been running FreeBSD 7.0RC3 on it for several months now. I had > noticed before the BIOS upgrade, that under high workloads the machine > would slow to a crawl. That is in fact why I did the upgrade. I thought > the BIOS was flaky or out of sync w/ what FreeBSD expected. > > After the BIOS upgrade I noticed a new driver was loading: ichss. > Unfortunately, the machine now behaves like it had in the past under > high workload all the time. Just booting sends the temperature up to 90C > (formerly 57C), starts the fan on high, and cuts performance to 70%. > > Either the temperature readings are wrong (unlikely), or simply enabling > SpeedStep ICH is making the machine into a toaster. :) Try running powerd(8): echo 'powerd_enable=YES' >> /etc/rc.conf -- Nate From owner-freebsd-acpi@FreeBSD.ORG Fri Mar 7 07:28:16 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA93B1065670 for ; Fri, 7 Mar 2008 07:28:16 +0000 (UTC) (envelope-from jeberle@pro24.abac.com) Received: from pro24.abac.com (pro24.abac.com [66.226.64.25]) by mx1.freebsd.org (Postfix) with ESMTP id 77CBC8FC28 for ; Fri, 7 Mar 2008 07:28:16 +0000 (UTC) (envelope-from jeberle@pro24.abac.com) Received: from thinkpad.local (adsl-76-229-131-179.dsl.pltn13.sbcglobal.net [76.229.131.179]) (authenticated bits=0) by pro24.abac.com (8.14.1/8.14.1) with ESMTP id m276r0Fh055783; Thu, 6 Mar 2008 22:53:01 -0800 (PST) (envelope-from jeberle) To: Nate Lawson In-reply-to: <47D0C917.6020904@root.org> References: <1204845766.1189@thinkpad.local> <47D0C917.6020904@root.org> Comments: In-reply-to Nate Lawson message dated "Thu, 06 Mar 2008 20:48:23 -0800." Date: Thu, 06 Mar 2008 22:53:00 -0800 From: "Jim Eberle " Message-Id: <1204872781.815@thinkpad.local> X-Spam-Score: 1 (FORGED_RCVD_HELO) Cc: freebsd-acpi@freebsd.org Subject: Re: ichss makes ThinkPad R31 toasty X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2008 07:28:16 -0000 > Jim Eberle wrote: > > ... > > Either the temperature readings are wrong (unlikely), or simply enabling > > SpeedStep ICH is making the machine into a toaster. :) > > ... > > Obviously, w/o ichss (or est or acpi_perf which aren't supported by this > > hardware) there are no ".freq/.freq_levels" sysctls, so cpufreq won't run. > > Try running powerd(8): > echo 'powerd_enable=YES' >> /etc/rc.conf > > -- > Nate I would like to run powerd, but that program wants to see the .freq/.freq_levels sysctls at startup. I'm still trying determine why enabling ichss causes the machine's temperature to spike from 57C to 90C. Weird. Jim From owner-freebsd-acpi@FreeBSD.ORG Fri Mar 7 14:19:04 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 952851065687 for ; Fri, 7 Mar 2008 14:19:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 803528FC25 for ; Fri, 7 Mar 2008 14:19:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id C5F481A4D80; Fri, 7 Mar 2008 06:18:33 -0800 (PST) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Fri, 7 Mar 2008 07:55:26 -0500 User-Agent: KMail/1.9.7 References: <1204845766.1189@thinkpad.local> <47D0C917.6020904@root.org> <1204872781.815@thinkpad.local> In-Reply-To: <1204872781.815@thinkpad.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200803070755.26418.jhb@freebsd.org> Cc: "Jim Eberle " Subject: Re: ichss makes ThinkPad R31 toasty X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2008 14:19:04 -0000 On Friday 07 March 2008 01:53:00 am Jim Eberle wrote: > > Jim Eberle wrote: > > > ... > > > Either the temperature readings are wrong (unlikely), or simply > > > enabling SpeedStep ICH is making the machine into a toaster. :) > > > ... > > > Obviously, w/o ichss (or est or acpi_perf which aren't supported by > > > this hardware) there are no ".freq/.freq_levels" sysctls, so cpufreq > > > won't run. > > > > Try running powerd(8): > > echo 'powerd_enable=YES' >> /etc/rc.conf > > > > -- > > Nate > > I would like to run powerd, but that program wants to see the > .freq/.freq_levels sysctls at startup. > > I'm still trying determine why enabling ichss causes the machine's > temperature to spike from 57C to 90C. Weird. Try this patch perhaps. 1) It would be good to get it tested on a machine with ICHSS, and 2) there's a slim chance that a bug it fixes in the ICHSS setup may make a difference: --- //depot/vendor/freebsd/src/sys/amd64/amd64/legacy.c 2007/09/30 11:13:02 +++ //depot/user/jhb/acpipci/amd64/amd64/legacy.c 2008/03/04 18:34:01 @@ -132,20 +111,10 @@ legacy_attach(device_t dev) { device_t child; - int i; - - /* First, attach the CPU pseudo-driver. */ - for (i = 0; i <= mp_maxid; i++) - if (!CPU_ABSENT(i)) { - child = BUS_ADD_CHILD(dev, 0, "cpu", i); - if (child == NULL) - panic("legacy_attach cpu"); - device_probe_and_attach(child); - } /* - * Second, let our child driver's identify any child devices that - * they can find. Once that is done attach any devices that we + * Let our child drivers identify any child devices that they + * can find. Once that is done attach any devices that we * found. */ bus_generic_probe(dev); @@ -241,6 +210,7 @@ * Legacy CPU attachment when ACPI is not available. Drivers like * cpufreq(4) hang off this. */ +static void cpu_identify(driver_t *driver, device_t parent); static int cpu_read_ivar(device_t dev, device_t child, int index, uintptr_t *result); static device_t cpu_add_child(device_t bus, int order, const char *name, @@ -254,6 +224,7 @@ static device_method_t cpu_methods[] = { /* Device interface */ + DEVMETHOD(device_identify, cpu_identify), DEVMETHOD(device_probe, bus_generic_probe), DEVMETHOD(device_attach, bus_generic_attach), DEVMETHOD(device_detach, bus_generic_detach), @@ -287,6 +258,25 @@ static devclass_t cpu_devclass; DRIVER_MODULE(cpu, legacy, cpu_driver, cpu_devclass, 0, 0); +static void +cpu_identify(driver_t *driver, device_t parent) +{ + device_t child; + int i; + + /* + * Attach a cpuX device for each CPU. We use an order of 150 + * so that these devices are attached after the Host-PCI + * bridges (which are added at order 100). + */ + for (i = 0; i <= mp_maxid; i++) + if (!CPU_ABSENT(i)) { + child = BUS_ADD_CHILD(parent, 150, "cpu", i); + if (child == NULL) + panic("legacy_attach cpu"); + } +} + static device_t cpu_add_child(device_t bus, int order, const char *name, int unit) { --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi.c 2008/01/28 02:00:16 +++ //depot/user/jhb/acpipci/dev/acpica/acpi.c 2008/02/28 13:51:06 @@ -1533,18 +1523,31 @@ static int acpi_probe_order(ACPI_HANDLE handle, int *order) { + ACPI_OBJECT_TYPE type; + u_int addr; /* * 1. I/O port and memory system resource holders * 2. Embedded controllers (to handle early accesses) * 3. PCI Link Devices + * 11 - 266. Host-PCI bridges sorted by _ADR + * 280. CPUs */ + AcpiGetType(handle, &type); if (acpi_MatchHid(handle, "PNP0C01") || acpi_MatchHid(handle, "PNP0C02")) *order = 1; else if (acpi_MatchHid(handle, "PNP0C09")) *order = 2; else if (acpi_MatchHid(handle, "PNP0C0F")) *order = 3; + else if (acpi_MatchHid(handle, "PNP0A03")) { + if (ACPI_SUCCESS(acpi_GetInteger(handle, "_ADR", &addr))) + *order = 11 + ACPI_ADR_PCI_SLOT(addr) * (PCI_FUNCMAX + 1) + + ACPI_ADR_PCI_FUNC(addr); + else + *order = 11; + } else if (type == ACPI_TYPE_PROCESSOR) + *order = 280; return (0); } @@ -1591,14 +1594,17 @@ break; /* - * Create a placeholder device for this node. Sort the placeholder - * so that the probe/attach passes will run breadth-first. Orders - * less than ACPI_DEV_BASE_ORDER are reserved for special objects - * (i.e., system resources). Larger values are used for all other - * devices. + * Create a placeholder device for this node. Sort the + * placeholder so that the probe/attach passes will run + * breadth-first. Orders less than ACPI_DEV_BASE_ORDER + * are reserved for special objects (i.e., system + * resources). Orders between ACPI_DEV_BASE_ORDER and 300 + * are used for Host-PCI bridges (and effectively all + * their children) and CPUs. Larger values are used for + * all other devices. */ ACPI_DEBUG_PRINT((ACPI_DB_OBJECTS, "scanning '%s'\n", handle_str)); - order = (level + 1) * ACPI_DEV_BASE_ORDER; + order = level * 10 + 300; acpi_probe_order(handle, &order); child = BUS_ADD_CHILD(bus, order, NULL, -1); if (child == NULL) --- //depot/vendor/freebsd/src/sys/dev/cpufreq/ichss.c 2006/05/16 14:41:44 +++ //depot/user/jhb/acpipci/dev/cpufreq/ichss.c 2008/03/04 18:27:52 @@ -91,7 +91,7 @@ (bus_space_write_1(rman_get_bustag((reg)), \ rman_get_bushandle((reg)), 0, (val))) -static int ichss_pci_probe(device_t dev); +static void ichss_identify(driver_t *driver, device_t parent); static int ichss_probe(device_t dev); static int ichss_attach(device_t dev); static int ichss_detach(device_t dev); @@ -103,6 +103,7 @@ static device_method_t ichss_methods[] = { /* Device interface */ + DEVMETHOD(device_identify, ichss_identify), DEVMETHOD(device_probe, ichss_probe), DEVMETHOD(device_attach, ichss_attach), DEVMETHOD(device_detach, ichss_detach), @@ -120,15 +121,7 @@ static devclass_t ichss_devclass; DRIVER_MODULE(ichss, cpu, ichss_driver, ichss_devclass, 0, 0); -static device_method_t ichss_pci_methods[] = { - DEVMETHOD(device_probe, ichss_pci_probe), - {0, 0} -}; -static driver_t ichss_pci_driver = { - "ichss_pci", ichss_pci_methods, 0 -}; -static devclass_t ichss_pci_devclass; -DRIVER_MODULE(ichss_pci, pci, ichss_pci_driver, ichss_pci_devclass, 0, 0); +static device_t ich_device; #if 0 #define DPRINT(x...) printf(x) @@ -136,70 +129,69 @@ #define DPRINT(x...) #endif -/* - * We detect the chipset by looking for its LPC bus ID during the PCI - * scan and reading its config registers during the probe. However, - * we add the ichss child under the cpu device since even though the - * chipset provides the control, it really affects the cpu only. - * - * XXX This approach does not work if the module is loaded after boot. - */ -static int -ichss_pci_probe(device_t dev) +static void +ichss_identify(driver_t *driver, device_t parent) { - device_t child, parent; + device_t child; uint32_t pmbase; + if (resource_disabled("ichss", 0)) + return; + /* - * TODO: add a quirk to disable if we see the 82815_MC along - * with the 82801BA and revision < 5. + * It appears that ICH SpeedStep only requires a single CPU to + * set the value (since the chipset is shared by all CPUs.) + * Thus, we only add a child to cpu 0. */ - if (pci_get_vendor(dev) != PCI_VENDOR_INTEL || - (pci_get_device(dev) != PCI_DEV_82801BA && - pci_get_device(dev) != PCI_DEV_82801CA && - pci_get_device(dev) != PCI_DEV_82801DB)) - return (ENXIO); + if (device_get_unit(parent) != 0) + return; - /* Only one CPU is supported for this hardware. */ - if (devclass_get_device(ichss_devclass, 0)) - return (ENXIO); + /* Avoid duplicates. */ + if (device_find_child(parent, "ichss", -1)) + return; /* - * Add a child under the CPU parent. It appears that ICH SpeedStep - * only requires a single CPU to set the value (since the chipset - * is shared by all CPUs.) Thus, we only add a child to cpu 0. + * ICH2/3/4-M I/O Controller Hub is at bus 0, slot 1F, function 0. + * E.g. see Section 6.1 "PCI Devices and Functions" and table 6.1 of + * Intel(r) 82801BA I/O Controller Hub 2 (ICH2) and Intel(r) 82801BAM + * I/O Controller Hub 2 Mobile (ICH2-M). + * + * TODO: add a quirk to disable if we see the 82815_MC along + * with the 82801BA and revision < 5. */ - parent = devclass_get_device(devclass_find("cpu"), 0); - KASSERT(parent != NULL, ("cpu parent is NULL")); - child = BUS_ADD_CHILD(parent, 0, "ichss", 0); - if (child == NULL) { - device_printf(parent, "add SpeedStep child failed\n"); - return (ENXIO); - } + ich_device = pci_find_bsf(0, 0x1f, 0); + if (ich_device == NULL || + pci_get_vendor(ich_device) != PCI_VENDOR_INTEL || + (pci_get_device(ich_device) != PCI_DEV_82801BA && + pci_get_device(ich_device) != PCI_DEV_82801CA && + pci_get_device(ich_device) != PCI_DEV_82801DB)) + return; /* Find the PMBASE register from our PCI config header. */ - pmbase = pci_read_config(dev, ICHSS_PMBASE_OFFSET, sizeof(pmbase)); + pmbase = pci_read_config(ich_device, ICHSS_PMBASE_OFFSET, + sizeof(pmbase)); if ((pmbase & ICHSS_IO_REG) == 0) { printf("ichss: invalid PMBASE memory type\n"); - return (ENXIO); + return; } pmbase &= ICHSS_PMBASE_MASK; if (pmbase == 0) { printf("ichss: invalid zero PMBASE address\n"); - return (ENXIO); + return; } DPRINT("ichss: PMBASE is %#x\n", pmbase); + child = BUS_ADD_CHILD(parent, 0, "ichss", 0); + if (child == NULL) { + device_printf(parent, "add SpeedStep child failed\n"); + return; + } + /* Add the bus master arbitration and control registers. */ bus_set_resource(child, SYS_RES_IOPORT, 0, pmbase + ICHSS_BM_OFFSET, 1); bus_set_resource(child, SYS_RES_IOPORT, 1, pmbase + ICHSS_CTRL_OFFSET, 1); - - /* Attach the new CPU child now. */ - device_probe_and_attach(child); - - return (ENXIO); } static int @@ -207,11 +199,7 @@ { device_t est_dev, perf_dev; int error, type; - uint16_t ss_en; - if (resource_disabled("ichss", 0)) - return (ENXIO); - /* * If the ACPI perf driver has attached and is not just offering * info, let it manage things. Also, if Enhanced SpeedStep is @@ -227,14 +215,6 @@ if (est_dev && device_is_attached(est_dev)) return (ENXIO); - /* Activate SpeedStep control if not already enabled. */ - ss_en = pci_read_config(dev, ICHSS_PMCFG_OFFSET, sizeof(ss_en)); - if ((ss_en & ICHSS_ENABLE) == 0) { - printf("ichss: enabling SpeedStep support\n"); - pci_write_config(dev, ICHSS_PMCFG_OFFSET, - ss_en | ICHSS_ENABLE, sizeof(ss_en)); - } - device_set_desc(dev, "SpeedStep ICH"); return (-1000); } @@ -243,6 +223,7 @@ ichss_attach(device_t dev) { struct ichss_softc *sc; + uint16_t ss_en; sc = device_get_softc(dev); sc->dev = dev; @@ -264,6 +245,14 @@ return (ENXIO); } + /* Activate SpeedStep control if not already enabled. */ + ss_en = pci_read_config(ich_device, ICHSS_PMCFG_OFFSET, sizeof(ss_en)); + if ((ss_en & ICHSS_ENABLE) == 0) { + device_printf(dev, "enabling SpeedStep support\n"); + pci_write_config(ich_device, ICHSS_PMCFG_OFFSET, + ss_en | ICHSS_ENABLE, sizeof(ss_en)); + } + /* Setup some defaults for our exported settings. */ sc->sets[0].freq = CPUFREQ_VAL_UNKNOWN; sc->sets[0].volts = CPUFREQ_VAL_UNKNOWN; --- //depot/vendor/freebsd/src/sys/i386/i386/legacy.c 2007/09/30 11:08:30 +++ //depot/user/jhb/acpipci/i386/i386/legacy.c 2008/03/04 18:34:01 @@ -137,20 +116,10 @@ legacy_attach(device_t dev) { device_t child; - int i; - - /* First, attach the CPU pseudo-driver. */ - for (i = 0; i <= mp_maxid; i++) - if (!CPU_ABSENT(i)) { - child = BUS_ADD_CHILD(dev, 0, "cpu", i); - if (child == NULL) - panic("legacy_attach cpu"); - device_probe_and_attach(child); - } /* - * Second, let our child driver's identify any child devices that - * they can find. Once that is done attach any devices that we + * Let our child drivers identify any child devices that they + * can find. Once that is done attach any devices that we * found. */ bus_generic_probe(dev); @@ -262,6 +231,7 @@ * Legacy CPU attachment when ACPI is not available. Drivers like * cpufreq(4) hang off this. */ +static void cpu_identify(driver_t *driver, device_t parent); static int cpu_read_ivar(device_t dev, device_t child, int index, uintptr_t *result); static device_t cpu_add_child(device_t bus, int order, const char *name, @@ -275,6 +245,7 @@ static device_method_t cpu_methods[] = { /* Device interface */ + DEVMETHOD(device_identify, cpu_identify), DEVMETHOD(device_probe, bus_generic_probe), DEVMETHOD(device_attach, bus_generic_attach), DEVMETHOD(device_detach, bus_generic_detach), @@ -308,6 +279,25 @@ static devclass_t cpu_devclass; DRIVER_MODULE(cpu, legacy, cpu_driver, cpu_devclass, 0, 0); +static void +cpu_identify(driver_t *driver, device_t parent) +{ + device_t child; + int i; + + /* + * Attach a cpuX device for each CPU. We use an order of 150 + * so that these devices are attached after the Host-PCI + * bridges (which are added at order 100). + */ + for (i = 0; i <= mp_maxid; i++) + if (!CPU_ABSENT(i)) { + child = BUS_ADD_CHILD(parent, 150, "cpu", i); + if (child == NULL) + panic("legacy_attach cpu"); + } +} + static device_t cpu_add_child(device_t bus, int order, const char *name, int unit) { -- John Baldwin