From owner-freebsd-acpi@FreeBSD.ORG Tue Oct 5 17:38:51 2004 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 2CE9A16A4CE; Tue, 5 Oct 2004 17:38:51 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0982743D2D; Tue, 5 Oct 2004 17:38:51 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Tue, 05 Oct 2004 10:38:50 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 5D4185D04; Tue, 5 Oct 2004 10:38:50 -0700 (PDT) To: John Baldwin In-reply-to: Your message of "Tue, 05 Oct 2004 12:09:44 EDT." <200410051209.44530.jhb@FreeBSD.org> Date: Tue, 05 Oct 2004 10:38:50 -0700 From: "Kevin Oberman" Message-Id: <20041005173850.5D4185D04@ptavv.es.net> cc: acpi@FreeBSD.org cc: freebsd-acpi@FreeBSD.org Subject: Re: ASUS P5A broken by ACPI black-list 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, 05 Oct 2004 17:38:51 -0000 > From: John Baldwin > Date: Tue, 5 Oct 2004 12:09:44 -0400 > > On Tuesday 05 October 2004 11:54 am, Kevin Oberman wrote: > > > From: John Baldwin > > > Date: Mon, 4 Oct 2004 15:57:30 -0400 > > > > > > On Monday 04 October 2004 02:33 pm, Nate Lawson wrote: > > > > Kevin Oberman wrote: > > > > > It looks like interrupts from the Ethernet are not delivered without > > > > > ACPI, but that is hardly your problem. I have over-ridden the > > > > > black-list and things are back to normal. > > > > > > > > The reason this system works in Windows without ACPI is that irq > > > > routing in Windows uses multiple info sources including _PIR and $PIR. > > > > John Baldwin has patches to do this for us too. > > > > > > $PIR routing already works on FreeBSD and has worked for quite a while. > > > The patches I have are to make the acpi_pci_link code work more like the > > > $PIR code already does. It doesn't change the ACPI code to actually use > > > $PIR or the MPTable though. I can try to look at why the ethernet device > > > doesn't get interrupts correctly if you can provide verbose ACPI and > > > non-ACPI dmesgs to look at. > > > > I am attaching the files. I do see some oddities with the > > interrupts that I had not previously noted, but they seen to be linked to > > sound, not the Ethernet. And, for whatever it's worth, "vmstat -i" does > > not show my sound card, at all. dmesg indicates it should be on IRQ 6. > > interrupt total rate > > irq0: clk 4242251 99 > > irq1: atkbd0 3 0 > > irq7: ppc0 1 0 > > irq8: rtc 5430044 127 > > irq10: xl0 13699 0 > > irq13: npx0 1 0 > > irq14: ata0 166980 3 > > irq15: ata1 136 0 > > Total 9853115 232 > > First, do you have a floppy drive? IRQ 6 should be used for your > floppy drive if so. Note that $PIR says that IRQ 6 is not an option > for your link devices but ACPI does. In the non-APCI case we use IRQ > 10 for both xl0 and pcm0. Are you saying that in that case pcm0 works > but xl0 does not? I have a floppy controller, but I stole the drive a while ago for my Windows system which grew a requirement for one to support disaster recovery. I have not tried the pcm0 in either case. I have no idea whether it works right now. I'll be at the system at around noon (PDT) today and I can try it. I have not use the sound card on that system in quite a while. I seldom am physically close to it except when working on it. -- 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