From owner-freebsd-current Wed Oct 16 10: 2: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D583337B401; Wed, 16 Oct 2002 10:01:59 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D01B43EA9; Wed, 16 Oct 2002 10:01:55 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA29056; Wed, 16 Oct 2002 13:01:54 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g9GH1Oc57293; Wed, 16 Oct 2002 13:01:24 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15789.39780.590216.5727@grasshopper.cs.duke.edu> Date: Wed, 16 Oct 2002 13:01:24 -0400 (EDT) To: Mitsuru IWASAKI Cc: jhb@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: PCI problems with today's current In-Reply-To: <20021017.011142.23004863.iwasaki@jp.FreeBSD.org> References: <20021015130947.A86610@panzer.kdm.org> <20021016.045918.109976092.iwasaki@jp.FreeBSD.org> <20021015193547.A88774@panzer.kdm.org> <20021017.011142.23004863.iwasaki@jp.FreeBSD.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mitsuru IWASAKI writes: > > > > If still NG, please try the attached patch against SupermicroP3TDE6.asl. > > > > # _BBN is bridge bus number, my guess is 0x3. You can try to change it > > > > # if failed. > > > > > > Maybe 0x2 is correct. > > > > I tried 2, and it seems to work correctly now. > > > > Thanks! > > Congratulations! > > # Now we can start discussing ACPI PCI vs. legacy PCI :) > DSDT in ACPI BIOS on Supermicro P3TDE6 has obviously wrong _BBN value, Actually, I'd like to hijack this thread for just a second. I have a buggy supermicro board too: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 4, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 5, version: 0x000f0011, at 0xfec01000 Pentium Pro MTRR support enabled ACPI-0623: *** Warning: Type override - [DEB_] had invalid type (Integer) for Scope operator, changed to (Scope) <... 11 similar lines deleted> ACPI-0623: *** Warning: Type override - [CMOS] had invalid type (Integer) for Scope operator, changed to (Scope) It also misses the peer bus. Non ACPI: pcib1: on motherboard IOAPIC #1 intpin 8 -> irq 11 pci1: on pcib1 pci1: (vendor=0x14c1, dev=0x8043) at 1.0 irq 11 ACPI: pcib1: on acpi0 acpi0: couldn't attach pci busdevice_probe_and_attach: pcib1 attach returned 6 What's nearly as bad, each time I get an interrupt on the on-board fxp, my (serial) console is spammed like this: Doing initial network setup: hostname domain. ACPI-1047: *** Error: AcpiEvGpeDispatch: No handler or method for GPE[20], disabling event ACPI-1047: *** Error: AcpiEvGpeDispatch: No handler or method for GPE[21], disabling event <...> up to ACPI-1047: *** Error: AcpiEvGpeDispatch: No handler or method for GPE[3f], disabling event At which point it cycles back to GPE[20]. If missing the peer bus didn't make it useless, this console spammage certainly does. What can I do? Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message