From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 4 00:41:32 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCA3716A41F; Sun, 4 Dec 2005 00:41:32 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A60843D5F; Sun, 4 Dec 2005 00:41:32 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: by ion.gank.org (mail, from userid 1001) id 008EC2BBBE; Sat, 3 Dec 2005 18:41:31 -0600 (CST) Date: Sat, 3 Dec 2005 18:41:31 -0600 From: Craig Boston To: John Baldwin Message-ID: <20051204004131.GA7596@nowhere> References: <20051130020734.GA6577@nowhere> <200512020817.55769.jhb@freebsd.org> <20051203005104.GA22567@nowhere> <200512031630.59476.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512031630.59476.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, imp@freebsd.org Subject: Re: Weird PCI interrupt delivery problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 00:41:33 -0000 On Sat, Dec 03, 2005 at 04:30:58PM -0500, John Baldwin wrote: > That's becuase the dmesg prints out what their current setting was before the > pci_link driver attached to them. It's basically what the BIOS set them up > as. Ah, makes sense. > Grrr. I'm pretty much out of ideas at this point. Yeah, it's pretty frustrating... Then again I knew when I got this machine what I might be getting myself into. Thanks for taking the time to help work on this and provide some ideas. I'll keep hacking on it and follow up here if I figure anything out. > At least you have it working in -ACPI -APIC mode. :-/ Unfortunately it seems that it's actually still broken in this case. I just discovered that even with the hint, the cardbus controller / devices don't generate any interrupts at all. The only reason it seemed to be working is that when I have the radio enabled, ath0 generates about 1000 interrupts/second (which seems high, but that's another discussion). So effectively is was just running in polling mode. I didn't notice that until this morning when I booted into single user mode and was trying to use some cardbus cards before ath0 was configured. Random tangent, it's kind of sad that one of the co-authors of the ACPI spec (Toshiba) would sell a machine that has so many problems with it. Though I think ATI deserves at least part of the blame as this appears to use one of their "system-on-a-chip" designs. Craig