From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 24 13:38:35 2003 Return-Path: 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 507E316A4B3 for ; Wed, 24 Sep 2003 13:38:35 -0700 (PDT) Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64DD644017 for ; Wed, 24 Sep 2003 13:38:33 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 13049 invoked from network); 24 Sep 2003 20:38:32 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 24 Sep 2003 20:38:32 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id h8OKcT6Y024339; Wed, 24 Sep 2003 16:38:29 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200309241926.h8OJQEl0029131@wattres.Watt.COM> Date: Wed, 24 Sep 2003 16:38:32 -0400 (EDT) From: John Baldwin To: Steve Watt X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: hackers@freebsd.org Subject: RE: PCI bridges & interrupts X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2003 20:38:35 -0000 On 24-Sep-2003 Steve Watt wrote: > [ Too advanced for -questions? Trying again. ] > > I'm having a strange problem with interrupts, PCI bridges, and > FreeBSD 4-STABLE (cvsupped from a few months ago). > > The motherboard is a Supermicro X5DL8-GG, dual-Xeon capable (only one is > populated). The BIOS is AMIBIOS 7.00.00. The BIOS settings have PnP OS > set to NO, ACPI OS is YES ('cause FreeBSD-CURRENT was once installed), > and power management is all disabled. Turn ACPI off, there's a slim chance it might help. > Everything on the board works when directly connected to the host, > except that we can't go 66MHz and we can't close the case. With > the riser card, *almost* everything works, except for interrupts. > I can see the interrupt line low *on the card edge connector on > the motherboard*, but it's not acknowledged, and our driver's ISR > doesn't run. We've throttled the riser card to 33MHz to eliminate > that possibility. > > What follows is the verbose dmesg from the boot up without the > riser (bridge), followed by diffs when booted with the riser. > > I'm looking for clues. It's about >< that far from working right, > and this almost looks like a FreeBSD issue. > > Buddy, can you spare a clue? Why isn't the ISR running? Have you tried 5.x? Basically, 4.x doesn't really have all the infrastructure to route interrupts, and if your BIOS screws it up, then you aren't going to get the right IRQ number hooked up. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/