From owner-freebsd-acpi@FreeBSD.ORG Sat Oct 25 22:43:48 2008 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B82DE106567E for ; Sat, 25 Oct 2008 22:43:48 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 73A738FC14 for ; Sat, 25 Oct 2008 22:43:47 +0000 (UTC) (envelope-from mav@FreeBSD.org) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 226127437 for freebsd-acpi@FreeBSD.org; Sun, 26 Oct 2008 01:43:46 +0300 Message-ID: <4903A120.7040003@FreeBSD.org> Date: Sun, 26 Oct 2008 01:43:44 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.16 (X11/20080726) MIME-Version: 1.0 To: freebsd-acpi@FreeBSD.org Content-Type: multipart/mixed; boundary="------------080606050200070300070407" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: PCIe bridges resources disappearing with ACPI enabled. X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Oct 2008 22:43:48 -0000 This is a multi-part message in MIME format. --------------080606050200070300070407 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Hi. I have spent whole day trying to investigate strange problem of my Acer TM6292 laptop (965GM+ICH8M). When booted with ACPI enabled, all three of PCIe-to-PCIe bridges appearing completely without I/O resources: pcib1: irq 17 at device 28.0 on pci0 pcib1: domain 0 pcib1: secondary bus 2 pcib1: subordinate bus 3 pcib1: I/O decode 0x0-0x0 pcib1: no prefetched decode ... At the same time, with ACPI disabled, resources are present. There are some different problem with IRQ in that case, but it is another question, not so interesting to me. I have tried both IO and memory mapped PCIe configuration registers without success. I have made heavy digging trying to find where resources disappearing. I have even added debug printing inside pcireg_cfgwrite() and pciereg_cfgwrite() to trace if somebody erases it and found nothing. Nothing writes into that devices configuration registers. At this moment I am living with ugly hack found here: http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004905.html, and I would be grateful if somebody give me a hint what is going on here and why Windows and Linux (according reports) work fine. Here is my pciconf -l: hostb0@pci0:0:0:0: class=0x060000 card=0x011b1025 chip=0x2a008086 rev=0x03 hdr=0x00 vgapci0@pci0:0:2:0: class=0x030000 card=0x011b1025 chip=0x2a028086 rev=0x03 hdr=0x00 vgapci1@pci0:0:2:1: class=0x038000 card=0x011b1025 chip=0x2a038086 rev=0x03 hdr=0x00 uhci0@pci0:0:26:0: class=0x0c0300 card=0x011b1025 chip=0x28348086 rev=0x03 hdr=0x00 uhci1@pci0:0:26:1: class=0x0c0300 card=0x011b1025 chip=0x28358086 rev=0x03 hdr=0x00 ehci0@pci0:0:26:7: class=0x0c0320 card=0x011b1025 chip=0x283a8086 rev=0x03 hdr=0x00 hdac0@pci0:0:27:0: class=0x040300 card=0x011b1025 chip=0x284b8086 rev=0x03 hdr=0x00 pcib1@pci0:0:28:0: class=0x060400 card=0x011b1025 chip=0x283f8086 rev=0x03 hdr=0x01 pcib2@pci0:0:28:2: class=0x060400 card=0x011b1025 chip=0x28438086 rev=0x03 hdr=0x01 pcib3@pci0:0:28:3: class=0x060400 card=0x011b1025 chip=0x28458086 rev=0x03 hdr=0x01 uhci2@pci0:0:29:0: class=0x0c0300 card=0x011b1025 chip=0x28308086 rev=0x03 hdr=0x00 uhci3@pci0:0:29:1: class=0x0c0300 card=0x011b1025 chip=0x28318086 rev=0x03 hdr=0x00 uhci4@pci0:0:29:2: class=0x0c0300 card=0x011b1025 chip=0x28328086 rev=0x03 hdr=0x00 ehci1@pci0:0:29:7: class=0x0c0320 card=0x011b1025 chip=0x28368086 rev=0x03 hdr=0x00 pcib4@pci0:0:30:0: class=0x060401 card=0x00000000 chip=0x24488086 rev=0xf3 hdr=0x01 isab0@pci0:0:31:0: class=0x060100 card=0x011b1025 chip=0x28158086 rev=0x03 hdr=0x00 atapci0@pci0:0:31:1: class=0x01018a card=0x011b1025 chip=0x28508086 rev=0x03 hdr=0x00 atapci1@pci0:0:31:2: class=0x010601 card=0x011b1025 chip=0x28298086 rev=0x03 hdr=0x00 none0@pci0:0:31:3: class=0x0c0500 card=0x011b1025 chip=0x283e8086 rev=0x03 hdr=0x00 bge0@pci0:4:0:0: class=0x020000 card=0x011b1025 chip=0x169314e4 rev=0x02 hdr=0x00 iwn0@pci0:5:0:0: class=0x028000 card=0x11018086 chip=0x42298086 rev=0x61 hdr=0x00 cbb0@pci0:10:1:0: class=0x060700 card=0x011b1025 chip=0x14101524 rev=0x01 hdr=0x02 none1@pci0:10:2:0: class=0x050100 card=0x011b1025 chip=0x07301524 rev=0x00 hdr=0x00 sdhci0@pci0:10:2:1: class=0x080501 card=0x011b1025 chip=0x07501524 rev=0x00 hdr=0x00 none2@pci0:10:2:2: class=0x050100 card=0x011b1025 chip=0x07201524 rev=0x00 hdr=0x00 sdhci1@pci0:10:2:3: class=0x050100 card=0x011b1025 chip=0x07511524 rev=0x00 hdr=0x00 fwohci0@pci0:10:9:0: class=0x0c0010 card=0x011b1025 chip=0x8024104c rev=0x00 hdr=0x00 Problematic devices are 0:28:0, 0:28:2, 0:28:3. What is also strange is that PCIe-to-PCI bridge 0:30:0 working just fine. ASL attached. -- Alexander Motin --------------080606050200070300070407--