From owner-freebsd-current@FreeBSD.ORG Sat Mar 20 17:01:14 2004 Return-Path: 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 D771B16A4CE for ; Sat, 20 Mar 2004 17:01:14 -0800 (PST) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id A6BD143D2F for ; Sat, 20 Mar 2004 17:01:14 -0800 (PST) (envelope-from nate@root.org) Received: (qmail 24995 invoked by uid 1000); 21 Mar 2004 01:01:16 -0000 Date: Sat, 20 Mar 2004 17:01:16 -0800 (PST) From: Nate Lawson To: Petri Helenius In-Reply-To: <405C5119.5000505@he.iki.fi> Message-ID: <20040320165935.D24978@root.org> References: <405C5119.5000505@he.iki.fi> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE cc: freebsd-current@freebsd.org cc: acpi-jp@jp.FreeBSD.org Subject: Re: [acpi-jp 3122] CSA gigabit ethernet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Mar 2004 01:01:14 -0000 On Sat, 20 Mar 2004, Petri Helenius wrote: > I have been trying to convince Supermicro support that the CSAB entry > would need _PRT Method to work properly and have not really got a "go > away" message but not "we=B4ll fix it" either. > > Obviously this causes problems with the CSA gigabit if device apic is > enabled and the APIC is enabled in the bios also. (watchdog timeouts, I > also saw a PR open on the symptom) > > Comments? I put the whole dump to http://helenius.fi/p4sctii.asl > > The board in question is P4SCT+II. I suspect the problem exists in all > Supermicro boards with CSA. > > Running on 5.2.1-RELEASE or 5.2-CURRENT behave similarly. > > Disabling APIC in the BIOS makes the system usable. > > Pete > > Device (CSAB) > { > Name (_ADR, 0x00030000) > Device (CSAD) > { > Name (_ADR, 0x00010000) > Method (_PRW, 0, NotSerialized) > { > Return (Package (0x02) > { > 0x0B, > 0x05 > }) > } > } > } Sorry, I can't quite understand what the problem is. What are CSAB and CSAD? Is CSAB another bus (PCI?) containing CSAD? A devinfo of this box would help me understand the hierarchy. You can always create your own _PRT entry under CSAB and compile a custom AML. See the acpi debugging section of the handbook for info. -Nate