From owner-freebsd-acpi@FreeBSD.ORG Sun Jan 2 00:37:12 2005 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 B2CFA16A4CE for ; Sun, 2 Jan 2005 00:37:12 +0000 (GMT) Received: from Bastion.VanValzah.Com (Bastion.VanValzah.Com [64.81.228.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42ECD43D2F for ; Sun, 2 Jan 2005 00:37:12 +0000 (GMT) (envelope-from Bob@VanValzah.Com) Received: from Bud.29West.Com (Snarky.VanValzah.Com [64.81.228.121]) j020bBWn025233 for ; Sat, 1 Jan 2005 18:37:11 -0600 (CST) (envelope-from Bob@VanValzah.Com) From: Bob Van Valzah To: FreeBSD-ACPI@FreeBSD.Org Content-Type: text/plain Date: Sat, 01 Jan 2005 18:37:05 -0600 Message-Id: <1104626226.43507.48.camel@Bud.29West.Com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Possible Handbook Typo 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, 02 Jan 2005 00:37:12 -0000 I'm just reading the acpi-debug.html page in the handbook and I see something that looks suspicious (to my eyes at least). Section 11.16.3.2 System Hangs (temporary or permanent) advises setting hint.apic.0.disabled="1" in loader.conf. Shouldn't hints go in /boot/device.hints instead of loader.conf? I'm no expert in this area, so I thought I check it with the ACPI list before submitting a PR. Thanks, Bob From owner-freebsd-acpi@FreeBSD.ORG Sun Jan 2 02:48:02 2005 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 69EBB16A4CE for ; Sun, 2 Jan 2005 02:48:02 +0000 (GMT) Received: from hyperreal.org (taz3.hyperreal.org [209.237.226.90]) by mx1.FreeBSD.org (Postfix) with SMTP id 3E9EE43D41 for ; Sun, 2 Jan 2005 02:48:02 +0000 (GMT) (envelope-from brian@collab.net) Received: (qmail 54505 invoked from network); 2 Jan 2005 02:48:05 -0000 Received: from localhost.hyperreal.org (HELO fez.hyperreal.org) (127.0.0.1) by localhost.hyperreal.org with SMTP; 2 Jan 2005 02:48:05 -0000 Received: (qmail 30660 invoked by uid 1000); 2 Jan 2005 02:47:58 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 2 Jan 2005 02:47:58 -0000 Date: Sat, 1 Jan 2005 18:47:57 -0800 (PST) From: Brian Behlendorf X-X-Sender: brian@fez.hyperreal.org To: acpi@freebsd.org Message-ID: <20041224201017.C21066@fez.hyperreal.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Rating: localhost.hyperreal.org 1.6.2 0/1000/N Subject: zzz from X results in "xl0: no memory for list buffers" 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, 02 Jan 2005 02:48:02 -0000 Sony VAIO C1-XS - under RELENG_4 runs apm suspend/resume works fine. Testing suspend/resume (zzz) with RELENG_5 and acpi updated as of today, suspend/resume *without* X has no problem. From X, everything comes back from a resume, but there's trouble with the ethernet card: Jan 1 17:19:02 vez acpi: suspend at 20050101 17:19:02 Jan 1 17:19:22 vez kernel: fwohci0: fwohci_pci_suspend Jan 1 17:19:22 vez kernel: tdkphy0: detached Jan 1 17:19:22 vez kernel: miibus0: detached Jan 1 17:19:22 vez kernel: xl0: detached Jan 1 17:19:22 vez kernel: wakeup from sleeping stateslept 00:00:18) Jan 1 17:19:23 vez kernel: fwohci0: Phy 1394a available S400, 3 ports. Jan 1 17:19:23 vez kernel: fwohci0: Link S400, max_rec 2048 bytes. Jan 1 17:19:23 vez kernel: fwohci0: Initiate bus reset Jan 1 17:19:23 vez kernel: fwohci0: BUS reset Jan 1 17:19:23 vez kernel: fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode Jan 1 17:19:23 vez kernel: firewire0: 1 nodes, maxhop <= 0, cable IRM = 0me) Jan 1 17:19:23 vez kernel: firewire0: bus manager 0me) Jan 1 17:19:23 vez kernel: fwohci0: txd err= 3 miss Ack err Jan 1 17:19:23 vez kernel: fwohci0: unrecoverable error Jan 1 17:19:23 vez dhclient: send_packet: Network is unreachable Jan 1 17:19:23 vez dhclient: send_packet: please consult README file regarding broadcast address. Jan 1 17:19:23 vez acpi: resumed at 20050101 17:19:23 Jan 1 17:19:25 vez kernel: cardbus0: Resource not specified in CIS: id=14, size=80 Jan 1 17:19:25 vez kernel: cardbus0: Resource not specified in CIS: id=18, size=80 Jan 1 17:19:25 vez kernel: xl0: <3Com 3c575B Fast Etherlink XL> port 0x1080-0x10ff mem 0x20000000-0x2000007f,0x20000080-0x200000ff irq 9 at device 0.0 on cardbus0 Jan 1 17:19:28 vez kernel: xl0: no memory for list buffers! Jan 1 17:19:28 vez kernel: device_attach: xl0 attach returned 12 Jan 1 17:19:28 vez kernel: cbb0: CardBus card activation failed Jan 1 17:19:28 vez dhclient: receive_packet failed on xl0: Network is unreachable Pulling it out and putting it back in doesn't help: Jan 1 17:51:08 vez kernel: cardbus0: Resource not specified in CIS: id=14, size=80 Jan 1 17:51:09 vez kernel: cardbus0: Resource not specified in CIS: id=18, size=80 Jan 1 17:51:09 vez kernel: xl0: <3Com 3c575B Fast Etherlink XL> port 0x1080-0x10ff mem 0x20000000-0x2000007f,0x20000080-0x200000ff irq 9 at device 0.0 on cardbus0 Jan 1 17:51:09 vez kernel: xl0: no memory for list buffers! Jan 1 17:51:09 vez kernel: device_attach: xl0 attach returned 12 Jan 1 17:51:09 vez kernel: cbb0: CardBus card activation failed My non-cardbus Lucent/Orinoco card appears to have no problem: Jan 1 17:52:02 vez kernel: wi0: at port 0x100-0x13f irq 9 function 0 config 1 on pccard0 Jan 1 17:52:02 vez kernel: wi0: using Lucent Technologies, WaveLAN/IEEE Jan 1 17:52:02 vez kernel: wi0: Lucent Firmware: Station6.4.1) Jan 1 17:52:02 vez kernel: wi0: Ethernet address: 00:60:1d:21:7b:87 Jan 1 17:52:02 vez kernel: wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps I also tried out the acpi_pwr5.diff that was posted here the other day, no difference. acpidump -t -d: http://hyperreal.org/~brian/acpidump.out dmesg: http://hyperreal.org/~brian/dmesg.boot I realize this is an older laptop, but I'd love to get this working. I tried getting apm working - the first few times it had the same behavior as acpi (network card wouldn't come back after suspend/resume) but then during the third attempt, the LCD gave a bizarre glow, and I had to force it off with the power button. When it came back, zzz with apm resulted in nothing but a hang. So apm on this laptop might be toast... Brian From owner-freebsd-acpi@FreeBSD.ORG Sun Jan 2 06:33:23 2005 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 204D616A4CE for ; Sun, 2 Jan 2005 06:33:23 +0000 (GMT) Received: from postal3.es.net (postal3.es.net [198.128.3.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id D434743D31 for ; Sun, 2 Jan 2005 06:33:22 +0000 (GMT) (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; Sat, 01 Jan 2005 22:33:22 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 709045D04; Sat, 1 Jan 2005 22:33:21 -0800 (PST) To: Bob Van Valzah In-reply-to: Your message of "Sat, 01 Jan 2005 18:37:05 CST." <1104626226.43507.48.camel@Bud.29West.Com> Date: Sat, 01 Jan 2005 22:33:21 -0800 From: "Kevin Oberman" Message-Id: <20050102063321.709045D04@ptavv.es.net> cc: FreeBSD-ACPI@FreeBSD.Org Subject: Re: Possible Handbook Typo 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, 02 Jan 2005 06:33:23 -0000 > From: Bob Van Valzah > Date: Sat, 01 Jan 2005 18:37:05 -0600 > Sender: owner-freebsd-acpi@freebsd.org > > I'm just reading the acpi-debug.html page in the handbook and I see > something that looks suspicious (to my eyes at least). > > Section 11.16.3.2 System Hangs (temporary or permanent) advises setting > hint.apic.0.disabled="1" in loader.conf. Shouldn't hints go > in /boot/device.hints instead of loader.conf? > > I'm no expert in this area, so I thought I check it with the ACPI list > before submitting a PR. No typo. Hints may be in either the device.hints file or loader.conf, but in the case of ACPI, it's probably better to use loader.conf as it is processed earlier and ACPI starts doing things very early in the boot procedure, -- 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 Sun Jan 2 17:38:35 2005 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 011A616A4CE for ; Sun, 2 Jan 2005 17:38:35 +0000 (GMT) Received: from sana.init-main.com (104.194.138.210.bn.2iij.net [210.138.194.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F40643D49 for ; Sun, 2 Jan 2005 17:38:34 +0000 (GMT) (envelope-from takawata@init-main.com) Received: from init-main.com (localhost.init-main.com [127.0.0.1]) by sana.init-main.com (8.13.1/8.13.1) with ESMTP id j02HZWAs017587; Mon, 3 Jan 2005 02:35:32 +0900 (JST) (envelope-from takawata@init-main.com) Message-Id: <200501021735.j02HZWAs017587@sana.init-main.com> To: freebsd-acpi@freebsd.org, sam@errno.com From: takawata@jp.freebsd.org Date: Mon, 03 Jan 2005 02:35:32 +0900 Sender: takawata@init-main.com Subject: ACPI C3 patch for atheros 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, 02 Jan 2005 17:38:35 -0000 Happy Newyear! I was pity to be unable to use atheros wlan adaptor on FreeBSD with ACPI. I checked madwifi archive and I found problem much alike with me in Linux and the fix. It seems that it can easyly be applyed to FreeBSD, so I tried following patch and it works. How about this? And should it be in PCI framework? Index: if_ath_pci.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ath/if_ath_pci.c,v retrieving revision 1.10 diff -u -r1.10 if_ath_pci.c --- if_ath_pci.c 31 Dec 2004 22:41:45 -0000 1.10 +++ if_ath_pci.c 2 Jan 2005 17:30:21 -0000 @@ -109,6 +109,9 @@ bzero(psc, sizeof (*psc)); sc->sc_dev = dev; + /*Disable RETRY_TIMEOUT */ + pci_write_config(dev, 0x41, 0, 1 ); + cmd = pci_read_config(dev, PCIR_COMMAND, 4); cmd |= PCIM_CMD_MEMEN | PCIM_CMD_BUSMASTEREN; pci_write_config(dev, PCIR_COMMAND, cmd, 4); @@ -248,6 +251,7 @@ struct ath_pci_softc *psc = device_get_softc(dev); u_int16_t cmd; + pci_write_config(dev, 0x41, 0, 1 ); pci_write_config(dev, PCIR_INTLINE, psc->sc_saved_intline, 1); pci_write_config(dev, PCIR_CACHELNSZ, psc->sc_saved_cachelinesz, 1); pci_write_config(dev, PCIR_LATTIMER, psc->sc_saved_lattimer, 1); From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 02:43:29 2005 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 A617316A4CE; Mon, 3 Jan 2005 02:43:29 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4657043D48; Mon, 3 Jan 2005 02:43:29 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-95.dsl.snfc21.pacbell.net [64.171.186.95]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j032hRGV024969 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 2 Jan 2005 18:43:28 -0800 Message-ID: <41D8B108.3030000@root.org> Date: Sun, 02 Jan 2005 18:42:16 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Josef Karthauser References: <20041229093006.GB8264@genius.tao.org.uk> <41D2F750.4080204@root.org> <20041229201236.GB14714@genius.tao.org.uk> <41D33DAA.2010707@root.org> <20041230103231.GA1428@genius.tao.org.uk> In-Reply-To: <20041230103231.GA1428@genius.tao.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org Subject: Re: Sony VGN-A290 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, 03 Jan 2005 02:43:29 -0000 Josef Karthauser wrote: > On Wed, Dec 29, 2004 at 03:28:42PM -0800, Nate Lawson wrote: >>You can see your ACPI view of the device tree with: >> acpidump -d | grep Device >> >>You'll probably have a DCK (dock) device that has some sound device >>under it. We don't have much docking support currently but if you boot >>while docked, devices on it should work fine. I have patches for basic >>docking support but the problem is there are many device drivers that >>don't handle this properly yet. For instance, if you have a floppy >>drive bay in the dock, the fdc(4) driver doesn't know yet how to handle >>an undock event. We're just lucky that most laptops so far let the BIOS >>handle things. > > > I'll take a look when I'm next docked to see what appears there. When > docked I get no sound at all. It would be good to get that working. It doesn't matter when you run the dump. AML is static on all current systems so you can run it whenever and always get the same result. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 02:48:39 2005 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 013D716A4CE for ; Mon, 3 Jan 2005 02:48:39 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id B631443D1D for ; Mon, 3 Jan 2005 02:48:38 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-95.dsl.snfc21.pacbell.net [64.171.186.95]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j032mbGV025056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 2 Jan 2005 18:48:37 -0800 Message-ID: <41D8B23E.9000503@root.org> Date: Sun, 02 Jan 2005 18:47:26 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug White References: <41D1C63E.5020201@nbritton.org> <20050101151558.L87126@carver.gumbysoft.com> In-Reply-To: <20050101151558.L87126@carver.gumbysoft.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: HP OmniBook 6000 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, 03 Jan 2005 02:48:39 -0000 Doug White wrote: > On Tue, 28 Dec 2004, Nikolas Britton wrote: > > >>Any OmniBook 6000 owners out there that can comment on ACPI support in >>FreeBSD 5.x?... or any other problems with this system. I was thinking >>about getting one. As I'm sure there are meny variants of this model the >>specs for the system in question are: PIII@700Mhz, 12GB, 256 or 512MB, >>DVD drive, and 14" LCD > > > It used to be fatally broken, due to violating assumptions in the ACPICA > code at the time regarding probe order. But that was back when those > machines were new, and the code may now handle that case :-) > I don't know how well that system works but the sysresource issues were fixed a while back (before 5.3) -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 02:54:17 2005 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 981E216A4CE for ; Mon, 3 Jan 2005 02:54:17 +0000 (GMT) Received: from rader.servnow.com (rader.servnow.com [69.93.129.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 574F843D1F for ; Mon, 3 Jan 2005 02:54:17 +0000 (GMT) (envelope-from mikes@siralan.org) Received: from 12-210-221-89.client.insightbb.com ([12.210.221.89] helo=familysquires.net) by rader.servnow.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1ClIMD-0001To-90 for freebsd-acpi@freebsd.org; Sun, 02 Jan 2005 21:54:09 -0500 Date: Sun, 2 Jan 2005 21:54:14 -0500 (EST) From: "Michael L. Squires" X-X-Sender: mikes@familysquires.net To: freebsd-acpi@freebsd.org In-Reply-To: <200501021735.j02HZWAs017587@sana.init-main.com> Message-ID: <20050102214343.B46344@familysquires.net> References: <200501021735.j02HZWAs017587@sana.init-main.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - rader.servnow.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - siralan.org X-Source: X-Source-Args: X-Source-Dir: Subject: ACPI problem with Toshiba 8100, 5.3-STABLE 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, 03 Jan 2005 02:54:17 -0000 The 5.3-STABLE compiled on 12/17 from 12/16 sources boots without problems; kernels compiled from sources after 12/28 (12/28;12/30;1/1) have numerous ACPI errors. These errors keep the Lucent WiFi CardBus card from operating at all (12/28 and 12/30; no idea about 1/1) , but don't seem to affect operation when docked (I'm only using the docking station's Ethernet, video passthrough, mouse passthrough, and keyboard passthrough; although the expansion box is attached with a Symbios SCSI card and SCSI CD-ROM it is not used). I updated the BIOS to the last version available for the Toshiba Tecra 8100, v 2.50; no effect. I've but a fragment of a verbose dmesg, acpidump output, and iasl ouput for this system at http://familysquires.net:8080 under "ACPI stuff". All the files were created with a v2.50 BIOS and the 8100 docked and attached to Ethernet, a KVM switch (video, mouse, keyboard) and a bus expansion box with a Symbios SCSI card and SCSI CD-ROM drive. A Supermicro P6DGH (dual PIII/GX chipset) has no problems with the same sources. I have a copy of the 12/17 kernel and will continue to track 5.3-STABLE. Since I have a backup copy of a working kernel this is not a critical problem. Mike Squires From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 02:59:42 2005 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 BC6DF16A4CE for ; Mon, 3 Jan 2005 02:59:42 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B56943D2D for ; Mon, 3 Jan 2005 02:59:42 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-95.dsl.snfc21.pacbell.net [64.171.186.95]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j032xaGV025261 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 2 Jan 2005 18:59:38 -0800 Message-ID: <41D8B4D2.4050700@root.org> Date: Sun, 02 Jan 2005 18:58:26 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: takawata@jp.freebsd.org References: <200501021735.j02HZWAs017587@sana.init-main.com> In-Reply-To: <200501021735.j02HZWAs017587@sana.init-main.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: sam@errno.com cc: freebsd-acpi@freebsd.org Subject: Re: ACPI C3 patch for atheros 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, 03 Jan 2005 02:59:42 -0000 takawata@jp.freebsd.org wrote: > Happy Newyear! > I was pity to be unable to use atheros wlan adaptor on FreeBSD > with ACPI. > > I checked madwifi archive and I found problem much alike with me in Linux > and the fix. It seems that it can easyly be applyed to FreeBSD, > so I tried following patch and it works. > > How about this? > And should it be in PCI framework? > > Index: if_ath_pci.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/ath/if_ath_pci.c,v > retrieving revision 1.10 > diff -u -r1.10 if_ath_pci.c > --- if_ath_pci.c 31 Dec 2004 22:41:45 -0000 1.10 > +++ if_ath_pci.c 2 Jan 2005 17:30:21 -0000 > @@ -109,6 +109,9 @@ > bzero(psc, sizeof (*psc)); > sc->sc_dev = dev; > > + /*Disable RETRY_TIMEOUT */ > + pci_write_config(dev, 0x41, 0, 1 ); > + > cmd = pci_read_config(dev, PCIR_COMMAND, 4); > cmd |= PCIM_CMD_MEMEN | PCIM_CMD_BUSMASTEREN; > pci_write_config(dev, PCIR_COMMAND, cmd, 4); > @@ -248,6 +251,7 @@ > struct ath_pci_softc *psc = device_get_softc(dev); > u_int16_t cmd; > > + pci_write_config(dev, 0x41, 0, 1 ); > pci_write_config(dev, PCIR_INTLINE, psc->sc_saved_intline, 1); > pci_write_config(dev, PCIR_CACHELNSZ, psc->sc_saved_cachelinesz, 1); > pci_write_config(dev, PCIR_LATTIMER, psc->sc_saved_lattimer, 1); Sorry, I don't know enough about the semantics of this config space variable to comment in much detail. 0x41 should be a PCIR_ #define though. It looks like these config writes in ath_pci_attach() should probably be done in the PCI bus but they may be driver-specific. The saves of config space in ath_pci_suspend/resume() are definitely suspect since we save/resume all config space now. See sys/dev/pci/pci.c One other comment: you don't need to bzero a softc since it's allocated with M_ZERO. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 03:02:29 2005 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 B083C16A4CE for ; Mon, 3 Jan 2005 03:02:29 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ACEB43D53 for ; Mon, 3 Jan 2005 03:02:29 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-95.dsl.snfc21.pacbell.net [64.171.186.95]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j0332RGV025332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 2 Jan 2005 19:02:28 -0800 Message-ID: <41D8B57C.6090004@root.org> Date: Sun, 02 Jan 2005 19:01:16 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Michael L. Squires" References: <200501021735.j02HZWAs017587@sana.init-main.com> <20050102214343.B46344@familysquires.net> In-Reply-To: <20050102214343.B46344@familysquires.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: ACPI problem with Toshiba 8100, 5.3-STABLE 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, 03 Jan 2005 03:02:29 -0000 Michael L. Squires wrote: > The 5.3-STABLE compiled on 12/17 from 12/16 sources boots without > problems; kernels compiled from sources after 12/28 (12/28;12/30;1/1) > have numerous ACPI errors. These errors keep the Lucent WiFi CardBus > card from operating at all (12/28 and 12/30; no idea about 1/1) , but > don't seem to affect operation when docked (I'm only using the docking > station's Ethernet, video passthrough, mouse passthrough, and keyboard > passthrough; although the expansion box is attached with a Symbios SCSI > card and SCSI CD-ROM it is not used). I'm tracking this exact problem in the thread "acpi boot error messages after last update (Dec 22nd and 29th)". The problem is that the acpi-ca implicit return workaround is not working properly in the new import. It's top on my list to fix. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 03:07:04 2005 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 D7B0B16A4CE for ; Mon, 3 Jan 2005 03:07:04 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7270343D2F for ; Mon, 3 Jan 2005 03:07:04 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.92] ([66.127.85.92]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j03373Wi067675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 2 Jan 2005 19:07:04 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41D8B6DF.7040703@errno.com> Date: Sun, 02 Jan 2005 19:07:11 -0800 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <200501021735.j02HZWAs017587@sana.init-main.com> <41D8B4D2.4050700@root.org> In-Reply-To: <41D8B4D2.4050700@root.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: ACPI C3 patch for atheros 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, 03 Jan 2005 03:07:05 -0000 Nate Lawson wrote: > takawata@jp.freebsd.org wrote: > >> Happy Newyear! >> I was pity to be unable to use atheros wlan adaptor on FreeBSD >> with ACPI. >> >> I checked madwifi archive and I found problem much alike with me in Linux >> and the fix. It seems that it can easyly be applyed to FreeBSD, >> so I tried following patch and it works. >> >> How about this? And should it be in PCI framework? >> >> Index: if_ath_pci.c >> =================================================================== >> RCS file: /home/ncvs/src/sys/dev/ath/if_ath_pci.c,v >> retrieving revision 1.10 >> diff -u -r1.10 if_ath_pci.c >> --- if_ath_pci.c 31 Dec 2004 22:41:45 -0000 1.10 >> +++ if_ath_pci.c 2 Jan 2005 17:30:21 -0000 >> @@ -109,6 +109,9 @@ >> bzero(psc, sizeof (*psc)); >> sc->sc_dev = dev; >> + /*Disable RETRY_TIMEOUT */ >> + pci_write_config(dev, 0x41, 0, 1 ); >> + >> cmd = pci_read_config(dev, PCIR_COMMAND, 4); >> cmd |= PCIM_CMD_MEMEN | PCIM_CMD_BUSMASTEREN; >> pci_write_config(dev, PCIR_COMMAND, cmd, 4); >> @@ -248,6 +251,7 @@ >> struct ath_pci_softc *psc = device_get_softc(dev); >> u_int16_t cmd; >> >> + pci_write_config(dev, 0x41, 0, 1 ); >> pci_write_config(dev, PCIR_INTLINE, psc->sc_saved_intline, 1); >> pci_write_config(dev, PCIR_CACHELNSZ, >> psc->sc_saved_cachelinesz, 1); >> pci_write_config(dev, PCIR_LATTIMER, psc->sc_saved_lattimer, 1); > > > Sorry, I don't know enough about the semantics of this config space > variable to comment in much detail. 0x41 should be a PCIR_ #define though. > > It looks like these config writes in ath_pci_attach() should probably be > done in the PCI bus but they may be driver-specific. The saves of > config space in ath_pci_suspend/resume() are definitely suspect since we > save/resume all config space now. See sys/dev/pci/pci.c > > One other comment: you don't need to bzero a softc since it's allocated > with M_ZERO. > Lots of old code here; at the time I cribbed the suspend-resume code I don't believe the pci registers were saved for drivers. Here's the code from which the change originated: > /* >> * Suspend/Resume resets the PCI configuration space, so we have to >> * re-disable the RETRY_TIMEOUT register (0x41) to keep >> * PCI Tx retries from interfering with C3 CPU state >> * >> * Code taken from ipw2100 driver - jg >> */ >> pci_read_config_dword(pdev, 0x40, &val); >> if ((val & 0x0000ff00) != 0) >> pci_write_config_dword(pdev, 0x40, val & 0xffff00ff); I was waiting for a reply from Warner about whether or not this belonged in the driver or if the pci layer should be handling this. Sam From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 03:56:33 2005 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 7EF3716A4CE for ; Mon, 3 Jan 2005 03:56:33 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18BCB43D2D for ; Mon, 3 Jan 2005 03:56:33 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.51] (adsl-64-171-186-95.dsl.snfc21.pacbell.net [64.171.186.95])j033uNh2005401; Sun, 2 Jan 2005 22:56:23 -0500 Message-ID: <41D8C26A.8030105@root.org> Date: Sun, 02 Jan 2005 19:56:26 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041205) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Leffler References: <200501021735.j02HZWAs017587@sana.init-main.com> <41D8B4D2.4050700@root.org> <41D8B6DF.7040703@errno.com> In-Reply-To: <41D8B6DF.7040703@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: ACPI C3 patch for atheros 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, 03 Jan 2005 03:56:33 -0000 Sam Leffler wrote: > Lots of old code here; at the time I cribbed the suspend-resume code I > don't believe the pci registers were saved for drivers. > > Here's the code from which the change originated: > > > /* > >> * Suspend/Resume resets the PCI configuration space, so we > have to > >> * re-disable the RETRY_TIMEOUT register (0x41) to keep > >> * PCI Tx retries from interfering with C3 CPU state > >> * > >> * Code taken from ipw2100 driver - jg > >> */ > >> pci_read_config_dword(pdev, 0x40, &val); > >> if ((val & 0x0000ff00) != 0) > >> pci_write_config_dword(pdev, 0x40, val & 0xffff00ff); > > > I was waiting for a reply from Warner about whether or not this belonged > in the driver or if the pci layer should be handling this. If the comment is correct and the value is only lost due to suspend/resume, this should already be covered by us saving/restoring config registers although I believe we only save the normal registers (first 64 bytes). Since RETRY_TIMEOUT is beyond that range, it's probably not currently saved. In any case, I'd prefer we fix pci_cfg_save/restore() instead of doing this in the driver. Overall, it would be useful to analyze and improve coverage of what values we save and restore from config space. We definitely need to cover type 1 and 2 (bridge) devices as well. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 04:05:14 2005 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 A59C216A4CE for ; Mon, 3 Jan 2005 04:05:14 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id C79E543D31 for ; Mon, 3 Jan 2005 04:05:13 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0343iPk021517; Sun, 2 Jan 2005 21:03:44 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 02 Jan 2005 21:04:00 -0700 (MST) Message-Id: <20050102.210400.71551976.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <41D8B4D2.4050700@root.org> References: <200501021735.j02HZWAs017587@sana.init-main.com> <41D8B4D2.4050700@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: sam@errno.com cc: freebsd-acpi@freebsd.org Subject: Re: ACPI C3 patch for atheros 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, 03 Jan 2005 04:05:14 -0000 In message: <41D8B4D2.4050700@root.org> Nate Lawson writes: : takawata@jp.freebsd.org wrote: : > Happy Newyear! : > I was pity to be unable to use atheros wlan adaptor on FreeBSD : > with ACPI. : > : > I checked madwifi archive and I found problem much alike with me in Linux : > and the fix. It seems that it can easyly be applyed to FreeBSD, : > so I tried following patch and it works. : > : > How about this? : > And should it be in PCI framework? : > : > Index: if_ath_pci.c : > =================================================================== : > RCS file: /home/ncvs/src/sys/dev/ath/if_ath_pci.c,v : > retrieving revision 1.10 : > diff -u -r1.10 if_ath_pci.c : > --- if_ath_pci.c 31 Dec 2004 22:41:45 -0000 1.10 : > +++ if_ath_pci.c 2 Jan 2005 17:30:21 -0000 : > @@ -109,6 +109,9 @@ : > bzero(psc, sizeof (*psc)); : > sc->sc_dev = dev; : > : > + /*Disable RETRY_TIMEOUT */ : > + pci_write_config(dev, 0x41, 0, 1 ); : > + : > cmd = pci_read_config(dev, PCIR_COMMAND, 4); : > cmd |= PCIM_CMD_MEMEN | PCIM_CMD_BUSMASTEREN; : > pci_write_config(dev, PCIR_COMMAND, cmd, 4); : > @@ -248,6 +251,7 @@ : > struct ath_pci_softc *psc = device_get_softc(dev); : > u_int16_t cmd; : > : > + pci_write_config(dev, 0x41, 0, 1 ); : > pci_write_config(dev, PCIR_INTLINE, psc->sc_saved_intline, 1); : > pci_write_config(dev, PCIR_CACHELNSZ, psc->sc_saved_cachelinesz, 1); : > pci_write_config(dev, PCIR_LATTIMER, psc->sc_saved_lattimer, 1); : : Sorry, I don't know enough about the semantics of this config space : variable to comment in much detail. 0x41 should be a PCIR_ #define though. 0x41 isn't in the standard config space. It ends at 0x3f. Therefore, it won't have a PCIR_ define, since it is device specific. : It looks like these config writes in ath_pci_attach() should probably be : done in the PCI bus but they may be driver-specific. The saves of : config space in ath_pci_suspend/resume() are definitely suspect since we : save/resume all config space now. See sys/dev/pci/pci.c No, we don't. We save only the specific portion of the config space that we know something about. We also only do the read-write portions of the config space. Drivers are required to save/restore the device specific portion of pci config space. Warner From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 04:08:16 2005 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 0D6A716A4CE for ; Mon, 3 Jan 2005 04:08:16 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 985AF43D39 for ; Mon, 3 Jan 2005 04:08:15 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0346wUm021528; Sun, 2 Jan 2005 21:06:58 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 02 Jan 2005 21:07:14 -0700 (MST) Message-Id: <20050102.210714.82100964.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <41D8C26A.8030105@root.org> References: <41D8B4D2.4050700@root.org> <41D8B6DF.7040703@errno.com> <41D8C26A.8030105@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: sam@errno.com cc: freebsd-acpi@freebsd.org Subject: Re: ACPI C3 patch for atheros 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, 03 Jan 2005 04:08:16 -0000 In message: <41D8C26A.8030105@root.org> Nate Lawson writes: : Sam Leffler wrote: : > Lots of old code here; at the time I cribbed the suspend-resume code I : > don't believe the pci registers were saved for drivers. : > : > Here's the code from which the change originated: : > : > > /* : > >> * Suspend/Resume resets the PCI configuration space, so we : > have to : > >> * re-disable the RETRY_TIMEOUT register (0x41) to keep : > >> * PCI Tx retries from interfering with C3 CPU state : > >> * : > >> * Code taken from ipw2100 driver - jg : > >> */ : > >> pci_read_config_dword(pdev, 0x40, &val); : > >> if ((val & 0x0000ff00) != 0) : > >> pci_write_config_dword(pdev, 0x40, val & 0xffff00ff); : > : > : > I was waiting for a reply from Warner about whether or not this belonged : > in the driver or if the pci layer should be handling this. : : If the comment is correct and the value is only lost due to : suspend/resume, this should already be covered by us saving/restoring : config registers although I believe we only save the normal registers : (first 64 bytes). Since RETRY_TIMEOUT is beyond that range, it's : probably not currently saved. Right. RETRY_LIMIT isn't standard. : In any case, I'd prefer we fix pci_cfg_save/restore() instead of doing : this in the driver. Overall, it would be useful to analyze and improve : coverage of what values we save and restore from config space. We : definitely need to cover type 1 and 2 (bridge) devices as well. We shouldn't, since it is non-standard. Type 1 can all be done in pcib, and type 2 can be done in cbb. Warner From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 04:08:20 2005 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 3588316A4CE for ; Mon, 3 Jan 2005 04:08:20 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EB5C43D46 for ; Mon, 3 Jan 2005 04:08:19 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0345a0r021525; Sun, 2 Jan 2005 21:05:36 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 02 Jan 2005 21:05:52 -0700 (MST) Message-Id: <20050102.210552.75256445.imp@bsdimp.com> To: sam@errno.com From: "M. Warner Losh" In-Reply-To: <41D8B6DF.7040703@errno.com> References: <200501021735.j02HZWAs017587@sana.init-main.com> <41D8B4D2.4050700@root.org> <41D8B6DF.7040703@errno.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: ACPI C3 patch for atheros 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, 03 Jan 2005 04:08:20 -0000 In message: <41D8B6DF.7040703@errno.com> Sam Leffler writes: : Nate Lawson wrote: : > takawata@jp.freebsd.org wrote: : > : >> Happy Newyear! : >> I was pity to be unable to use atheros wlan adaptor on FreeBSD : >> with ACPI. : >> : >> I checked madwifi archive and I found problem much alike with me in Linux : >> and the fix. It seems that it can easyly be applyed to FreeBSD, : >> so I tried following patch and it works. : >> : >> How about this? And should it be in PCI framework? : >> : >> Index: if_ath_pci.c : >> =================================================================== : >> RCS file: /home/ncvs/src/sys/dev/ath/if_ath_pci.c,v : >> retrieving revision 1.10 : >> diff -u -r1.10 if_ath_pci.c : >> --- if_ath_pci.c 31 Dec 2004 22:41:45 -0000 1.10 : >> +++ if_ath_pci.c 2 Jan 2005 17:30:21 -0000 : >> @@ -109,6 +109,9 @@ : >> bzero(psc, sizeof (*psc)); : >> sc->sc_dev = dev; : >> + /*Disable RETRY_TIMEOUT */ : >> + pci_write_config(dev, 0x41, 0, 1 ); : >> + : >> cmd = pci_read_config(dev, PCIR_COMMAND, 4); : >> cmd |= PCIM_CMD_MEMEN | PCIM_CMD_BUSMASTEREN; : >> pci_write_config(dev, PCIR_COMMAND, cmd, 4); : >> @@ -248,6 +251,7 @@ : >> struct ath_pci_softc *psc = device_get_softc(dev); : >> u_int16_t cmd; : >> : >> + pci_write_config(dev, 0x41, 0, 1 ); : >> pci_write_config(dev, PCIR_INTLINE, psc->sc_saved_intline, 1); : >> pci_write_config(dev, PCIR_CACHELNSZ, : >> psc->sc_saved_cachelinesz, 1); : >> pci_write_config(dev, PCIR_LATTIMER, psc->sc_saved_lattimer, 1); : > : > : > Sorry, I don't know enough about the semantics of this config space : > variable to comment in much detail. 0x41 should be a PCIR_ #define though. : > : > It looks like these config writes in ath_pci_attach() should probably be : > done in the PCI bus but they may be driver-specific. The saves of : > config space in ath_pci_suspend/resume() are definitely suspect since we : > save/resume all config space now. See sys/dev/pci/pci.c : > : > One other comment: you don't need to bzero a softc since it's allocated : > with M_ZERO. : > : : Lots of old code here; at the time I cribbed the suspend-resume code I : don't believe the pci registers were saved for drivers. : : Here's the code from which the change originated: : : > /* : >> * Suspend/Resume resets the PCI configuration space, so we : have to : >> * re-disable the RETRY_TIMEOUT register (0x41) to keep : >> * PCI Tx retries from interfering with C3 CPU state : >> * : >> * Code taken from ipw2100 driver - jg : >> */ : >> pci_read_config_dword(pdev, 0x40, &val); : >> if ((val & 0x0000ff00) != 0) : >> pci_write_config_dword(pdev, 0x40, val & 0xffff00ff); : : : I was waiting for a reply from Warner about whether or not this belonged : in the driver or if the pci layer should be handling this. I believe it belongs in the driver. 0x40 is the device specific config space, not defined by the standards.. Well, at least not as of 2.2... Warner From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 04:08:26 2005 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 D09CE16A4CE for ; Mon, 3 Jan 2005 04:08:26 +0000 (GMT) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6755943D46 for ; Mon, 3 Jan 2005 04:08:26 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.51] (adsl-64-171-186-95.dsl.snfc21.pacbell.net [64.171.186.95])j0348NvE011429; Sun, 2 Jan 2005 23:08:23 -0500 Message-ID: <41D8C536.8020301@root.org> Date: Sun, 02 Jan 2005 20:08:22 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041205) X-Accept-Language: en-us, en MIME-Version: 1.0 To: acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi-devel@lists.sourceforge.net Subject: Bug in "implicit return" 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: Mon, 03 Jan 2005 04:08:26 -0000 I have identified a problem in the implicit return code in dsutils.c. Various Toshiba laptops have a _STA method that is similar to this: DefinitionBlock ("DSDT.aml", "DSDT", 1, "TOSHIB", "8100 ", 536872468) { Device (LNKA) { Name (_HID, EisaId ("PNP0C0F")) Method (_STA, 0, NotSerialized) { STAL (0x60) } } Method (STAL, 1, NotSerialized) { /* Various link accesses removed for clarity. */ Return (0x0B) } } If you compile and run this snippet in the debugger, you'll see that _STA doesn't return anything even with EnableInterpreterSlack set to TRUE. This means the implicit return code doesn't work properly. I examined the AcpiDsIsResultUsed() function and found that the check that was failing was this one: /* * If there is no parent, we are executing at the method level. * An executing method typically has no parent, since each method * is parsed separately. */ if (!Op->Common.Parent) So it appears that there _is_ a parent and the implicit return code below is never executed for this method. I'm not sure the proper way to change this check for the above AML case but hopefully the Intel people will know. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 04:11:01 2005 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 5914816A4CE for ; Mon, 3 Jan 2005 04:11:01 +0000 (GMT) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id E542A43D46 for ; Mon, 3 Jan 2005 04:11:00 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.51] (adsl-64-171-186-95.dsl.snfc21.pacbell.net [64.171.186.95])j034AtvE012804; Sun, 2 Jan 2005 23:10:56 -0500 Message-ID: <41D8C5CF.4020606@root.org> Date: Sun, 02 Jan 2005 20:10:55 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041205) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <200501021735.j02HZWAs017587@sana.init-main.com> <41D8B4D2.4050700@root.org> <20050102.210400.71551976.imp@bsdimp.com> In-Reply-To: <20050102.210400.71551976.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: sam@errno.com cc: freebsd-acpi@freebsd.org Subject: Re: ACPI C3 patch for atheros 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, 03 Jan 2005 04:11:01 -0000 M. Warner Losh wrote: > 0x41 isn't in the standard config space. It ends at 0x3f. Therefore, > it won't have a PCIR_ define, since it is device specific. Ah, didn't notice that. It should have an ATH_PCIR define then. > : It looks like these config writes in ath_pci_attach() should probably be > : done in the PCI bus but they may be driver-specific. The saves of > : config space in ath_pci_suspend/resume() are definitely suspect since we > : save/resume all config space now. See sys/dev/pci/pci.c > > No, we don't. We save only the specific portion of the config space > that we know something about. We also only do the read-write portions > of the config space. Drivers are required to save/restore the device > specific portion of pci config space. Correct, this is a device-specific config register although the others I pointed out (INTLINE, etc.) are standard and are covered by the PCI bus. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 04:14:11 2005 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 DD3B716A4EC for ; Mon, 3 Jan 2005 04:14:11 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 320A843D1F for ; Mon, 3 Jan 2005 04:14:11 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j034Dlcv021604; Sun, 2 Jan 2005 21:13:47 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 02 Jan 2005 21:14:03 -0700 (MST) Message-Id: <20050102.211403.112818487.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <41D8C5CF.4020606@root.org> References: <41D8B4D2.4050700@root.org> <20050102.210400.71551976.imp@bsdimp.com> <41D8C5CF.4020606@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: sam@errno.com cc: freebsd-acpi@freebsd.org Subject: Re: ACPI C3 patch for atheros 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, 03 Jan 2005 04:14:12 -0000 In message: <41D8C5CF.4020606@root.org> Nate Lawson writes: : M. Warner Losh wrote: : > 0x41 isn't in the standard config space. It ends at 0x3f. Therefore, : > it won't have a PCIR_ define, since it is device specific. : : Ah, didn't notice that. It should have an ATH_PCIR define then. : : > : It looks like these config writes in ath_pci_attach() should probably be : > : done in the PCI bus but they may be driver-specific. The saves of : > : config space in ath_pci_suspend/resume() are definitely suspect since we : > : save/resume all config space now. See sys/dev/pci/pci.c : > : > No, we don't. We save only the specific portion of the config space : > that we know something about. We also only do the read-write portions : > of the config space. Drivers are required to save/restore the device : > specific portion of pci config space. : : Correct, this is a device-specific config register although the others I : pointed out (INTLINE, etc.) are standard and are covered by the PCI bus. True. Those are now saved/restored... I thought you were specifically talking about this one... Warner From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 11:01:58 2005 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 5C7CB16A4CE for ; Mon, 3 Jan 2005 11:01:58 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49B8F43D54 for ; Mon, 3 Jan 2005 11:01:58 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j03B1vrl006068 for ; Mon, 3 Jan 2005 11:01:57 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j03B1vhR006062 for freebsd-acpi@freebsd.org; Mon, 3 Jan 2005 11:01:57 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 3 Jan 2005 11:01:57 GMT Message-Id: <200501031101.j03B1vhR006062@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, 03 Jan 2005 11:01:58 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/07/22] i386/54756 acpi ACPI suspend/resume problem on CF-W2 lapt o [2003/08/17] i386/55661 acpi ACPI suspend/resume problem on ARMADA M70 o [2003/08/20] kern/55822 acpi No ACPI power off with SMP kernel o [2003/08/27] kern/56024 acpi ACPI suspend drains battery while in S3 o [2003/09/03] i386/56372 acpi acpi don't work on TYAN tiger100 M/B f [2003/09/10] kern/56659 acpi ACPI trouble on IBM ThinkPad X31 f [2003/12/17] i386/60317 acpi FreeBSD 5.2rc1 doesn't boot with ACPI ena o [2004/03/09] i386/64002 acpi acpi problem o [2004/05/27] i386/67273 acpi [hang] system hangs with acpi and Xfree o [2004/10/12] i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Arma 10 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [2004/01/22] i386/61703 acpi ACPI + Sound + Boot = Reboot o [2004/03/17] kern/64365 acpi ACPI problems f [2004/05/25] i386/67189 acpi ACPI S3 reboot computer on Dell Latitude o [2004/05/28] kern/67309 acpi zzz reboot computer (ACPI S3) f [2004/06/23] i386/68219 acpi ACPI + snd_maestro3 problem o [2004/07/29] i386/69750 acpi Boot without ACPI failed on ASUS L5 o [2004/11/11] i386/73822 acpi acpi / thermal support o [2004/11/21] kern/74215 acpi [request] add ACPI headers to /usr/includ 8 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 12:06:47 2005 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 291A616A4CE for ; Mon, 3 Jan 2005 12:06:47 +0000 (GMT) Received: from mailhost.tao.org.uk (transwarp.tao.org.uk [212.135.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5528543D1F for ; Mon, 3 Jan 2005 12:06:45 +0000 (GMT) (envelope-from joe@tao.org.uk) Received: from genius.tao.org.uk (genius.tao.org.uk [212.135.162.51]) by mailhost.tao.org.uk (Postfix) with ESMTP id 9EB6B7519; Mon, 3 Jan 2005 12:06:35 +0000 (GMT) Received: by genius.tao.org.uk (Postfix, from userid 100) id 982F4408E; Mon, 3 Jan 2005 12:06:34 +0000 (GMT) Date: Mon, 3 Jan 2005 12:06:34 +0000 From: Josef Karthauser To: Nate Lawson Message-ID: <20050103120634.GA47864@genius.tao.org.uk> References: <20041229093006.GB8264@genius.tao.org.uk> <41D2F750.4080204@root.org> <20041229201236.GB14714@genius.tao.org.uk> <41D33DAA.2010707@root.org> <20041230103231.GA1428@genius.tao.org.uk> <41D8B108.3030000@root.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: <41D8B108.3030000@root.org> User-Agent: Mutt/1.5.6i cc: freebsd-acpi@FreeBSD.org Subject: Re: Sony VGN-A290 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, 03 Jan 2005 12:06:47 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 02, 2005 at 06:42:16PM -0800, Nate Lawson wrote: > >>You can see your ACPI view of the device tree with: > >> acpidump -d | grep Device > >> > >>You'll probably have a DCK (dock) device that has some sound device=20 > >>under it. >=20 > It doesn't matter when you run the dump. AML is static on all current=20 > systems so you can run it whenever and always get the same result. >=20 Ah, ok. This is what I got, there doesn't appear to be a DCK there. Device (PCI0) Device (P0P1) Device (VGA0) Device (CRT) Device (TVO) Device (LCD) Device (P0P2) Device (MLAN) Device (CBS0) Device (CBS2) Device (CBS3) Device (MPCI) Device (GLAN) Device (NUB0) Device (NUB1) Device (NEUB) Device (SBRG) Device (PIC) Device (DMAD) Device (TMR) Device (RTC0) Device (PS2K) Device (PS2M) Device (SPKR) Device (COPR) Device (SYSR) Device (FWH) Device (OSYS) Device (PWRB) Device (EC0) Device (SPIC) Device (SNC) Device (ACAD) Device (BAT1) Device (ATKD) Device (LID) Device (IDE0) Device (CHN0) Device (DRV0) Device (CHN1) Device (DRV0) Device (SMBC) Device (AUDI) Device (MODM) Device (USB1) Device (USB2) Device (USB3) Device (EHCI) Device (LNKA) Device (LNKB) Device (LNKC) Device (LNKD) Device (LNKE) Device (LNKF) Device (LNKG) Device (LNKH) Joe --=20 Josef Karthauser (joe@tao.org.uk) http://www.josef-k.net/ FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/ Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/ =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D An eclectic mix of fact an= d theory. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iEYEARECAAYFAkHZNUkACgkQXVIcjOaxUBZjcgCgn8/LFANqbuZJov8AtlxY8n+q //MAn21anL+SDaC9jQTIgw3xjSnmPyAu =Mc/A -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 18:30:01 2005 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 DB17016A4CE for ; Mon, 3 Jan 2005 18:30:01 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E23143D53 for ; Mon, 3 Jan 2005 18:30:01 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 7ED2372DD4; Mon, 3 Jan 2005 10:30:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 78F6F72DCB; Mon, 3 Jan 2005 10:30:01 -0800 (PST) Date: Mon, 3 Jan 2005 10:30:01 -0800 (PST) From: Doug White To: Nate Lawson In-Reply-To: <41D8B23E.9000503@root.org> Message-ID: <20050103102700.W6665@carver.gumbysoft.com> References: <41D1C63E.5020201@nbritton.org> <20050101151558.L87126@carver.gumbysoft.com> <41D8B23E.9000503@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-acpi@freebsd.org Subject: Re: HP OmniBook 6000 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, 03 Jan 2005 18:30:02 -0000 On Sun, 2 Jan 2005, Nate Lawson wrote: > > It used to be fatally broken, due to violating assumptions in the ACPICA > > code at the time regarding probe order. But that was back when those > > machines were new, and the code may now handle that case :-) > > > > I don't know how well that system works but the sysresource issues were > fixed a while back (before 5.3) The problem was that one device required a region defined by a child of another bus that had not yet been initialized. The code would then get in in an infinite loop. I have pretty complete traces of this laying around. I'm pretty sure it was fixed later since the screaming stopped :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 22:25:59 2005 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 AA5DA16A4CE for ; Mon, 3 Jan 2005 22:25:59 +0000 (GMT) Received: from mail25.syd.optusnet.com.au (mail25.syd.optusnet.com.au [211.29.133.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EF3943D1D for ; Mon, 3 Jan 2005 22:25:59 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j03MPvFX024827 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 4 Jan 2005 09:25:57 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j03MPuxP036581 for ; Tue, 4 Jan 2005 09:25:57 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id j03MPu7p036580 for freebsd-acpi@freebsd.org; Tue, 4 Jan 2005 09:25:56 +1100 (EST) (envelope-from pjeremy) Date: Tue, 4 Jan 2005 09:25:56 +1100 From: Peter Jeremy To: freebsd-acpi@freebsd.org Message-ID: <20050103222556.GW79646@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i Subject: ACPI + SMBus disables ISA bus 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, 03 Jan 2005 22:25:59 -0000 I originally sent this to -stable but have received no response. It's possible that it's an ACPI problem so I'm trying here. I'm trying to upgrade a system from 4.10 to 5.3p2 and am running into problems with the ISA bus disappearing (not probing or attaching) when I have both ACPI and SMBus enabled. This leads to a panic when something tries to do a sysctl on the (non-existent) console. The problem is masked if I use a serial console because the only ISA device I need is the VGA adapter and the lack of vga0 and syscons doesn't worry the serial console. I've had a google around and it looks like this combination should work. At least, I can't find anything forbidding it and can find some dmesgs showing both ACPI and SMBus. The relevant sections of a GENERIC "boot -v" shows: ... AcpiOsDerivePciId: bus 0 dev 17 func 0 AcpiOsDerivePciId: bus 0 dev 17 func 0 ... found-> vendor=0x1106, dev=0x3147, revid=0x00 bus=0, slot=17, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0087, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 map[20]: type 4, range 32, base 0000fc00, size 4, enabled ... pci1: at device 0.0 (no driver attached) pci0: at device 8.0 (no driver attached) pci0: at device 11.0 (no driver attached) isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 If I add the following options to GENERIC: device smbus device viapm device smb device iicbb device iicbus then the ISA bus vanishes and the above probe messages change to: ... pci1: at device 0.0 (no driver attached) pci0: at device 8.0 (no driver attached) pci0: at device 11.0 (no driver attached) viapropm0: SMBus I/O base at 0x400 viapropm0: port 0x400-0x40f at device 17.0 on pci0 viapropm0: SMBus revision code 0x0 smbus0: on viapropm0 smb0: on smbus0 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 I can't get ACPI running properly in 4.x but I can have both SMBus and ACPI loaded and dmesg shows: ... viapropm0: SMBus I/O base at 0x400 viapropm0: port 0x400-0x40f at device 17.0 on pci0 viapropm0: SMBus revision code 0x0 smb0: on smbus0 ... isa0: on motherboard The motherboard is a Gigabyte GA-7VRXP with F12 BIOS (the latest AFAIK). Switching between PIC and APIC modes in the BIOS has no effect. There's no explicit "PnP/nonPnP" option. Should this work? If so, where should I look for clues as to why it doesn't for me? -- Peter Jeremy From owner-freebsd-acpi@FreeBSD.ORG Tue Jan 4 09:51:51 2005 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 A1E9D16A4CE for ; Tue, 4 Jan 2005 09:51:51 +0000 (GMT) Received: from beta.netcraft.com (beta.netcraft.com [195.92.95.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EA3843D53 for ; Tue, 4 Jan 2005 09:51:50 +0000 (GMT) (envelope-from jez@netcraft.com) Received: from chagford.netcraft.com (chagford.netcraft.com [195.92.95.48]) by beta.netcraft.com (8.12.10/8.12.10) with ESMTP id j049pn58050671 for ; Tue, 4 Jan 2005 09:51:49 GMT (envelope-from jez@netcraft.com) From: Jeremy Prior To: freebsd-acpi@freebsd.org Content-Type: text/plain Organization: Netcraft Ltd Date: Tue, 04 Jan 2005 09:51:47 +0000 Message-Id: <1104832307.1004.2.camel@chagford.netcraft.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Sony Vaio Z600RE incessant fan 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, 04 Jan 2005 09:51:51 -0000 Hi! I've recently updated my laptop to a recent version of RELENG_5 and the fan is now running constantly - it's very annoying! :-) It's a Sony Vaio Z600RE (a 500MHz Pentium 3 laptop) and was previously running a version of RELENG_5 from 2004/04/27. It's now running one dated 2005/01/02: % uname -a FreeBSD chagford.netcraft.com 5.3-STABLE FreeBSD 5.3-STABLE #3: Sun Jan 2 01:14:59 GMT 2005 root@chagford.netcraft.com:/usr/obj/usr/src/sys/CHAGFORD i386 The machine was working fine before, using ACPI, and I can still do Suspend/Resume (STR only). My hw.acpi sysctl looks like this: hw.acpi.supported_sleep_state: S1 S3 S4 S5 hw.acpi.power_button_state: S3 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: NONE hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 1 hw.acpi.s4bios: 0 hw.acpi.verbose: 0 hw.acpi.reset_video: 1 hw.acpi.cpu.throttle_max: 8 hw.acpi.cpu.throttle_state: 8 hw.acpi.cpu.cx_supported: C1/0 C2/10 hw.acpi.cpu.cx_lowest: C2 hw.acpi.cpu.cx_usage: 0.00% 99.99% hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 10 hw.acpi.thermal.tz0.temperature: 70.9C hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 84.9C hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 99.9C hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: 100 hw.acpi.battery.time: -1 hw.acpi.battery.state: 2 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 (I've mapped the power switch to S3, otherwise untouched). The hw.acpi.thermal.tz0.active and hw.acpi.thermal.tz0._ACx look ominous! Booting without ACPI causes the fan to revert to normal behaviour (only on when under load), but causes other components to be mis-detected and is obviously not a desirable choice. I've put up the verbose boot.dmesg with/without ACPI at http://zanussi.netcraft.com/acpi/ along with a copy of my eprom ASL I've also tried combinations of the following: * building ACPI as a module (was compiled into kernel) * fixing the one error in the ASL (patch available at above URL) * changing the hw.acpi.osname to "Microsoft Windows NT" * disabling the thermal section using debug.acpi.disabled="thermal" and debug.acpi.avoid="\_TZ" in loader.conf None of these had any effect. I did try to upgrade my BIOS, but the version on Sony's site appears to be older than the one I've got (I'm running R0116Z1, but the website only has R0114Z1) and the DOS upgrade program refused to do it. Any suggestions on how to fix this? jez -- Jeremy Prior http://www.netcraft.com/ Netcraft Ltd, Treenwood Ho, Rowden La, Bradford-on-Avon, BA15 2AZ. UK Tel: +44-1225-867111 (switchboard) Fax: +44-8700-517767 From owner-freebsd-acpi@FreeBSD.ORG Tue Jan 4 13:58:03 2005 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 66BF116A4CE for ; Tue, 4 Jan 2005 13:58:03 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id B373143D5D for ; Tue, 4 Jan 2005 13:58:02 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.5] (adsl-69-208-54-135.dsl.wotnoh.ameritech.net [69.208.54.135]) (authenticated bits=0)j04DYZWp044934 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 4 Jan 2005 08:34:37 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: Nate Lawson Date: Tue, 4 Jan 2005 09:01:21 -0500 User-Agent: KMail/1.7 References: <48908.1096571186@critter.freebsd.dk> <200410211526.48432.mistry.7@osu.edu> <41783E96.90908@root.org> In-Reply-To: <41783E96.90908@root.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3011248.Fb2WFiFyWU"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501040901.29358.mistry.7@osu.edu> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: freebsd-acpi@freebsd.org Subject: Re: RELENG_5 panic: mtx_lock() with ACPI X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 13:58:03 -0000 --nextPart3011248.Fb2WFiFyWU Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 21 October 2004 06:56 pm, you wrote: > Anish Mistry wrote: > > On Monday 18 October 2004 03:35 pm, you wrote: > >>Anish Mistry wrote: > >>>On Thursday 30 September 2004 03:06 pm, Poul-Henning Kamp wrote: > >>>>In message <415C4F5A.2080701@root.org>, Nate Lawson writes: > >>>>>I assume phk would be handling this since it's in the tty code. If > >>>>> not, please let us know so one of us can address this before the > >>>>> release. > >>>>> > >>>>>>>>struct tty * > >>>>>>>>ttymalloc(struct tty *tp) > >>>>>>>>{ > >>>>>>>> static int once; > >>>>>>>> > >>>>>>>> if (!once) { > >>>>>>>> mtx_init(&tty_list_mutex, "ttylist", NULL, > >>>>>>>> MTX_DEF); once++; > >>>>>>>> } > >>>>>>>> > >>>>>>>>This code is not MP safe as multiple processors could attempt to > >>>>>>>> call mtx_init() twice. > >>>> > >>>>We have no calls to ttymalloc() which are not protected by Giant, > >>>>so this theory doesn't explain the problem. > >>> > >>>Any progress, I'd hate to have to disable ACPI for the release. Is > >>> there any way I could provide more info? > >> > >>I'll try to look at it on the bus tonight. See if you can narrow down > >>if one ACPI component is contributing to this, i.e. > >>debug.acpi.disabled=3D"cpu" or whatever (see acpi.4 for the full list). > >>The sysctl run from the rc scripts to get entropy is what triggers the > >>panic. > > > > My monitor died, sorry for the slow response. > > Well I've gone through to try to figure out which component is causing > > the issue, and I've narrowed it down to 3. I couldn't get any better > > since when one of these are disabled then the hard drives aren't > > detect and thus can't boot. > > pci bus children > > > >>I have no idea how acpi can affect the tty mutex. > > Interesting, I'll try to look into this in more detail. I'm just > slammed with work at my Real Job currently. I just found the problem. I had viapm in my kernel config. I've updated=20 to -STABLE and removed that and the system now boots with ACPI. =2D-=20 Anish Mistry --nextPart3011248.Fb2WFiFyWU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB2qG5xqA5ziudZT0RArt1AJ4l/D5qUAbwPlB1LzD7TDtl0jZe3wCgtxpf 04hvrzGe4h3WA+Nsf6Q9ocE= =MHx5 -----END PGP SIGNATURE----- --nextPart3011248.Fb2WFiFyWU-- From owner-freebsd-acpi@FreeBSD.ORG Tue Jan 4 18:20:40 2005 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 E12B516A4CE for ; Tue, 4 Jan 2005 18:20:40 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id A17F643D45 for ; Tue, 4 Jan 2005 18:20:40 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 811 invoked from network); 4 Jan 2005 18:20:40 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 4 Jan 2005 18:20:40 -0000 Received: from [10.50.41.243] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id j04IKYXN067988; Tue, 4 Jan 2005 13:20:36 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Tue, 4 Jan 2005 09:49:19 -0500 User-Agent: KMail/1.6.2 References: <20050102063321.709045D04@ptavv.es.net> In-Reply-To: <20050102063321.709045D04@ptavv.es.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501040949.19697.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Bob Van Valzah Subject: Re: Possible Handbook Typo 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, 04 Jan 2005 18:20:41 -0000 On Sunday 02 January 2005 01:33 am, Kevin Oberman wrote: > > From: Bob Van Valzah > > Date: Sat, 01 Jan 2005 18:37:05 -0600 > > Sender: owner-freebsd-acpi@freebsd.org > > > > I'm just reading the acpi-debug.html page in the handbook and I see > > something that looks suspicious (to my eyes at least). > > > > Section 11.16.3.2 System Hangs (temporary or permanent) advises setting > > hint.apic.0.disabled="1" in loader.conf. Shouldn't hints go > > in /boot/device.hints instead of loader.conf? > > > > I'm no expert in this area, so I thought I check it with the ACPI list > > before submitting a PR. > > No typo. > > Hints may be in either the device.hints file or loader.conf, but in the > case of ACPI, it's probably better to use loader.conf as it is processed > earlier and ACPI starts doing things very early in the boot procedure, Nah, the boot only checks to see if ACPI is there, but that info isn't used by the kernel if the disable hint is set. Setting it in either file is find. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Jan 4 18:20:43 2005 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 48BAC16A4CE for ; Tue, 4 Jan 2005 18:20:43 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A25643D2F for ; Tue, 4 Jan 2005 18:20:43 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 855 invoked from network); 4 Jan 2005 18:20:42 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 4 Jan 2005 18:20:42 -0000 Received: from [10.50.41.243] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id j04IKYXO067988; Tue, 4 Jan 2005 13:20:38 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Tue, 4 Jan 2005 10:06:12 -0500 User-Agent: KMail/1.6.2 References: <20050103222556.GW79646@cirb503493.alcatel.com.au> In-Reply-To: <20050103222556.GW79646@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501041006.12235.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: ACPI + SMBus disables ISA bus 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, 04 Jan 2005 18:20:43 -0000 On Monday 03 January 2005 05:25 pm, Peter Jeremy wrote: > I originally sent this to -stable but have received no response. It's > possible that it's an ACPI problem so I'm trying here. > > I'm trying to upgrade a system from 4.10 to 5.3p2 and am running into > problems with the ISA bus disappearing (not probing or attaching) when > I have both ACPI and SMBus enabled. This leads to a panic when > something tries to do a sysctl on the (non-existent) console. > > The problem is masked if I use a serial console because the only ISA > device I need is the VGA adapter and the lack of vga0 and syscons > doesn't worry the serial console. > > I've had a google around and it looks like this combination should work. > At least, I can't find anything forbidding it and can find some dmesgs > showing both ACPI and SMBus. > > The relevant sections of a GENERIC "boot -v" shows: > ... > AcpiOsDerivePciId: bus 0 dev 17 func 0 > AcpiOsDerivePciId: bus 0 dev 17 func 0 > ... > found-> vendor=0x1106, dev=0x3147, revid=0x00 > bus=0, slot=17, func=0 > class=06-01-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0087, statreg=0x0210, cachelnsz=0 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > powerspec 2 supports D0 D3 current D0 > map[20]: type 4, range 32, base 0000fc00, size 4, enabled > ... > pci1: at device 0.0 (no driver attached) > pci0: at device 8.0 (no driver attached) > pci0: at device 11.0 (no driver attached) > isab0: at device 17.0 on pci0 > isa0: on isab0 > atapci0: port > 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 > > If I add the following options to GENERIC: > device smbus > device viapm > device smb > device iicbb > device iicbus > then the ISA bus vanishes and the above probe messages change to: > ... > pci1: at device 0.0 (no driver attached) > pci0: at device 8.0 (no driver attached) > pci0: at device 11.0 (no driver attached) > viapropm0: SMBus I/O base at 0x400 > viapropm0: port 0x400-0x40f at device > 17.0 on pci0 viapropm0: SMBus revision code 0x0 > smbus0: on viapropm0 > smb0: on smbus0 > atapci0: port > 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0 > > I can't get ACPI running properly in 4.x but I can have both SMBus and ACPI > loaded and dmesg shows: > ... > viapropm0: SMBus I/O base at 0x400 > viapropm0: port 0x400-0x40f at device > 17.0 on pci0 viapropm0: SMBus revision code 0x0 > smb0: on smbus0 > ... > isa0: on motherboard > > The motherboard is a Gigabyte GA-7VRXP with F12 BIOS (the latest AFAIK). > Switching between PIC and APIC modes in the BIOS has no effect. There's > no explicit "PnP/nonPnP" option. > > Should this work? If so, where should I look for clues as to why it > doesn't for me? It should work, but the problem is that the viapropm0 device needs to create an isab0 child as well, or perhaps it should be an isab driver and it should have both isa and smbus children devices. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-acpi@FreeBSD.ORG Tue Jan 4 19:55:48 2005 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 D35A616A4CE; Tue, 4 Jan 2005 19:55:48 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 817FA43D46; Tue, 4 Jan 2005 19:55:48 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j04JtkGV009578 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 4 Jan 2005 11:55:47 -0800 Message-ID: <41DAF4B5.8050701@root.org> Date: Tue, 04 Jan 2005 11:55:33 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20050102063321.709045D04@ptavv.es.net> <200501040949.19697.jhb@FreeBSD.org> In-Reply-To: <200501040949.19697.jhb@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org cc: Bob Van Valzah Subject: Re: Possible Handbook Typo 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, 04 Jan 2005 19:55:48 -0000 John Baldwin wrote: > On Sunday 02 January 2005 01:33 am, Kevin Oberman wrote: > >>>From: Bob Van Valzah >>>Date: Sat, 01 Jan 2005 18:37:05 -0600 >>>Sender: owner-freebsd-acpi@freebsd.org >>> >>>I'm just reading the acpi-debug.html page in the handbook and I see >>>something that looks suspicious (to my eyes at least). >>> >>>Section 11.16.3.2 System Hangs (temporary or permanent) advises setting >>>hint.apic.0.disabled="1" in loader.conf. Shouldn't hints go >>>in /boot/device.hints instead of loader.conf? >>> >>>I'm no expert in this area, so I thought I check it with the ACPI list >>>before submitting a PR. >> >>No typo. >> >>Hints may be in either the device.hints file or loader.conf, but in the >>case of ACPI, it's probably better to use loader.conf as it is processed >>earlier and ACPI starts doing things very early in the boot procedure, > > > Nah, the boot only checks to see if ACPI is there, but that info isn't used by > the kernel if the disable hint is set. Setting it in either file is find. > I recommend loader.conf since device.hints is overwritten during a full kernel upgrade while mergemaster handles loader.conf just fine (see src/UPDATING). -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Jan 4 20:00:32 2005 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 5586816A50A; Tue, 4 Jan 2005 20:00:32 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA71A43D31; Tue, 4 Jan 2005 20:00:31 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j04JxNtT048321; Tue, 4 Jan 2005 12:59:23 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Tue, 04 Jan 2005 12:59:23 -0700 (MST) Message-Id: <20050104.125923.85365613.imp@harmony.village.org> To: nate@root.org From: Warner Losh In-Reply-To: <41DAF4B5.8050701@root.org> References: <20050102063321.709045D04@ptavv.es.net> <200501040949.19697.jhb@FreeBSD.org> <41DAF4B5.8050701@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: Bob@VanValzah.Com Subject: Re: Possible Handbook Typo 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, 04 Jan 2005 20:00:32 -0000 > I recommend loader.conf since device.hints is overwritten during a full > kernel upgrade while mergemaster handles loader.conf just fine (see > src/UPDATING). loader.conf is for user updates. device.hints really should be merged in there, in many ways, but isn't (you can put hints in loader.conf if you want). I agree with Nate. Warner From owner-freebsd-acpi@FreeBSD.ORG Wed Jan 5 15:10:15 2005 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 40C4516A4CE for ; Wed, 5 Jan 2005 15:10:15 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09AE943D49 for ; Wed, 5 Jan 2005 15:10:15 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 9374 invoked from network); 5 Jan 2005 15:10:14 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 5 Jan 2005 15:10:14 -0000 Received: from [10.50.41.243] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id j05F9xQX074119; Wed, 5 Jan 2005 10:10:00 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Tue, 4 Jan 2005 15:45:43 -0500 User-Agent: KMail/1.6.2 References: <20050102063321.709045D04@ptavv.es.net> <200501040949.19697.jhb@FreeBSD.org> <41DAF4B5.8050701@root.org> In-Reply-To: <41DAF4B5.8050701@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501041545.43418.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Bob Van Valzah Subject: Re: Possible Handbook Typo 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, 05 Jan 2005 15:10:15 -0000 On Tuesday 04 January 2005 02:55 pm, Nate Lawson wrote: > John Baldwin wrote: > > On Sunday 02 January 2005 01:33 am, Kevin Oberman wrote: > >>>From: Bob Van Valzah > >>>Date: Sat, 01 Jan 2005 18:37:05 -0600 > >>>Sender: owner-freebsd-acpi@freebsd.org > >>> > >>>I'm just reading the acpi-debug.html page in the handbook and I see > >>>something that looks suspicious (to my eyes at least). > >>> > >>>Section 11.16.3.2 System Hangs (temporary or permanent) advises setting > >>>hint.apic.0.disabled="1" in loader.conf. Shouldn't hints go > >>>in /boot/device.hints instead of loader.conf? > >>> > >>>I'm no expert in this area, so I thought I check it with the ACPI list > >>>before submitting a PR. > >> > >>No typo. > >> > >>Hints may be in either the device.hints file or loader.conf, but in the > >>case of ACPI, it's probably better to use loader.conf as it is processed > >>earlier and ACPI starts doing things very early in the boot procedure, > > > > Nah, the boot only checks to see if ACPI is there, but that info isn't > > used by the kernel if the disable hint is set. Setting it in either file > > is find. > > I recommend loader.conf since device.hints is overwritten during a full > kernel upgrade while mergemaster handles loader.conf just fine (see > src/UPDATING). That's because the instructions are broken. It does say '# as needed', but it really should be more like '# if you don't have one already'. -- 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 Jan 6 14:20:59 2005 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 01B4D16A4CE for ; Thu, 6 Jan 2005 14:20:59 +0000 (GMT) Received: from beta.netcraft.com (beta.netcraft.com [195.92.95.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAC8543D45 for ; Thu, 6 Jan 2005 14:20:57 +0000 (GMT) (envelope-from jez@netcraft.com) Received: from chagford.netcraft.com (chagford.netcraft.com [195.92.95.48]) by beta.netcraft.com (8.12.10/8.12.10) with ESMTP id j06EKu58055583 for ; Thu, 6 Jan 2005 14:20:56 GMT (envelope-from jez@netcraft.com) From: Jeremy Prior To: freebsd-acpi@freebsd.org In-Reply-To: <1104832307.1004.2.camel@chagford.netcraft.com> References: <1104832307.1004.2.camel@chagford.netcraft.com> Content-Type: text/plain Organization: Netcraft Ltd Date: Thu, 06 Jan 2005 14:20:55 +0000 Message-Id: <1105021256.76427.18.camel@chagford.netcraft.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: Sony Vaio Z600RE incessant fan 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, 06 Jan 2005 14:20:59 -0000 On Tue, 2005-01-04 at 09:51 +0000, Jeremy Prior wrote: > I've recently updated my laptop to a recent version of RELENG_5 and the > fan is now running constantly - it's very annoying! :-) > > It's a Sony Vaio Z600RE (a 500MHz Pentium 3 laptop) and was previously > running a version of RELENG_5 from 2004/04/27. It's now running one > dated 2005/01/02: > > % uname -a > FreeBSD chagford.netcraft.com 5.3-STABLE FreeBSD 5.3-STABLE #3: Sun Jan 2 01:14:59 GMT 2005 root@chagford.netcraft.com:/usr/obj/usr/src/sys/CHAGFORD i386 > > The machine was working fine before, using ACPI, and I can still do > Suspend/Resume (STR only). > ... > > I've put up the verbose boot.dmesg with/without ACPI at > http://zanussi.netcraft.com/acpi/ along with a copy of my eprom ASL > ... > Any suggestions on how to fix this? I know it's bad etiquette to reply to your own posts but nobody else has! :-) I've found a workaround for this - an S3 suspend/resume seems to reset the fan to its normal behaviour (only cutting in when the machine gets hot). The problematic sysctl entries are unchanged: hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 I've put the dmesg output (with ACPI_DEBUG) taken after hibernation at http://zanussi.netcraft.com/acpi/ Hope this helps, jez -- Jeremy Prior http://www.netcraft.com/ Netcraft Ltd, Treenwood Ho, Rowden La, Bradford-on-Avon, BA15 2AZ. UK Tel: +44-1225-867111 (switchboard) Fax: +44-8700-517767 From owner-freebsd-acpi@FreeBSD.ORG Fri Jan 7 12:09:18 2005 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 2A19816A4CE for ; Fri, 7 Jan 2005 12:09:18 +0000 (GMT) Received: from relay3.poste.it (relay3.poste.it [62.241.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6C3043D54 for ; Fri, 7 Jan 2005 12:09:17 +0000 (GMT) (envelope-from eugenio@lumachedelcervello.cjb.net) Received: from [192.168.1.4] (82.49.148.48) by relay3.poste.it (7.0.028) (authenticated as eugenio.modesti@poste.it) id 418F84D300142437 for freebsd-acpi@freebsd.org; Fri, 7 Jan 2005 13:09:15 +0100 Message-ID: <41DE7BF3.1060406@lumachedelcervello.cjb.net> Date: Fri, 07 Jan 2005 13:09:23 +0100 From: Eugenio User-Agent: Mozilla Thunderbird 1.0 (X11/20050106) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: suspend on asus 3500 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, 07 Jan 2005 12:09:18 -0000 i use freebsd 5.3 -stable on this asus 3500. all seems to work well except the suspend states. S4 cruelly shut down the machine, while S3 suspends it, but on resume i receive on console an error like this: ad0: FAILURE ATA_IDENTIFY timed out ad0: WARNING removed from configuration the machine then hangs (mouse and keyboard worked for the first seconds) and the fun starts to make a lot of noise. any hint? P.S. is there something to catch acpi events (like low battery) and execute some command? thank you. Eugenio eugenio@lumachedelcervello.cjb.net From owner-freebsd-acpi@FreeBSD.ORG Sat Jan 8 09:05:28 2005 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 0BB5B16A4CE for ; Sat, 8 Jan 2005 09:05:28 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EC3C43D1D for ; Sat, 8 Jan 2005 09:05:27 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.51] (adsl-64-171-186-95.dsl.snfc21.pacbell.net [64.171.186.95])j0895Kh2025253; Sat, 8 Jan 2005 04:05:21 -0500 Message-ID: <41DFA254.8090704@root.org> Date: Sat, 08 Jan 2005 01:05:24 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041205) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ACPI Developers Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@FreeBSD.org Subject: acpi-ca reports \_SB as a device X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 09:05:28 -0000 If you call AcpiGetType on \_SB, you get "device" and \_TZ gives "thermal". I don't think this is valid since these are system scopes, not devices and thermal zones. I found this while testing a patch that scans the whole namespace (\) for devices. It turns out some systems put PCI link devices (PNP0C0F) in \, so we weren't probing them. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Sat Jan 8 23:20:48 2005 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 1B33A16A4CE; Sat, 8 Jan 2005 23:20:48 +0000 (GMT) Received: from fearlessleader.lhr-its.com (fearlessleader.lhr-its.com [64.204.249.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92B0B43D1F; Sat, 8 Jan 2005 23:20:47 +0000 (GMT) (envelope-from chris@vindaloo.com) Received: from yavin.vindaloo.com (unknown [172.24.144.34]) by fearlessleader.lhr-its.com (Postfix) with ESMTP id 7676B3C5; Sat, 8 Jan 2005 18:20:39 -0500 (EST) Received: by yavin.vindaloo.com (Postfix, from userid 1001) id C5E4A253AA; Sat, 8 Jan 2005 18:20:38 -0500 (EST) Date: Sat, 8 Jan 2005 18:20:38 -0500 From: Christopher Sean Hilton To: freebsd-stable@freebsd.org, freebsd-acpi@freebsd.org, freebsd-modile@freebsd.org Message-ID: <20050108232038.GA28906@yavin.vindaloo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i Subject: Suspend problem on FreeBSD 5.3-STABLE X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 23:20:48 -0000 Hi, I'm having trouble moving to FreeBSD 5.3-STABLE on my laptop. My problems concern the behaviour of the laptop when suspend/resume is used. Firstly I'd like to congratulate the FreeBSD team on this release. It resolves several problems that I had with FreeBSD 4.x on this hardware so the draw to upgrade to 5-STABLE is very strong. My problems all circulate around suspend/resume. My laptop is a Gateway 450ROG with 512Mb and 40Gb of Disk. I'm running 5.3 Stable cvsuped and built about last week monday. I'm running the GENERIC kernel and my configuration is fairly vanilla. Firstly what is definately broken: Suspend/resume kills the video display and seems to stop the kernel if dri is active under xorg's server. Turning off dri in the X configuration makes this problem go away. I plan to retest this with XFree86 as I believe that this is an Xorg problem. My video Chipset is an ati rage Mobility 7500 and my drm module is /boot/kernel/radeon.ko. Second, what I haven't been able to completely research: The PC card bus dies when on the first suspend resume. There seems to be no way to restart it. The second issue may be a configuration problem. I'm interested in hearing from anyone who is running 5.3-STABLE on a laptop so I can gather a list of all the configuration places and write a webpage on it. Any help anyone can provide would be appreciated. Thanks Chris Hilton -- Chris Hilton chilton-at-vindaloo-dot-com ------------------------------------------------------------------------ "All I was doing was trying to get home from work!" -- Rosa Parks