From owner-freebsd-current@FreeBSD.ORG Mon Jul 11 16:19:38 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 C175916A41C for ; Mon, 11 Jul 2005 16:19:38 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D23F43D46 for ; Mon, 11 Jul 2005 16:19:37 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ds0zd-0002bx-AT for freebsd-current@freebsd.org; Mon, 11 Jul 2005 18:18:53 +0200 Received: from mulder.f5.com ([205.229.151.150]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 11 Jul 2005 18:18:53 +0200 Received: from atkin901 by mulder.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 11 Jul 2005 18:18:53 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: othermark Date: Mon, 11 Jul 2005 09:17:37 -0700 Lines: 47 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: mulder.f5.com User-Agent: KNode/0.9.0 Sender: news Subject: is there a way not to believe the bios' IRQ prog and use the $PIR? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 11 Jul 2005 16:19:38 -0000 Hi, I believe since the following commit, I have had serious problems with interrupts on one class of machines (TYAN S1867 - thunder 2500): http://article.gmane.org/gmane.os.freebsd.devel.cvs.src/46247/ jhb 2005-04-14 18:25:09 UTC FreeBSD src repository Modified files: sys/i386/pci pci_pir.c Log: Trust the settings programmed by the BIOS over what the $PIR says. Specifically, if the BIOS has programmed an IRQ for a device that doesn't match the list of valid IRQs for the link, use it anyway as some BIOSes don't correctly list the valid IRQs in the $PIR. Also, allow the user to specify an IRQ that $PIR claims is invalid as an override, but emit a warning in that case. Revision Changes Path 1.117 +48 -18 src/sys/i386/pci/pci_pir.c Unfortunately, I'm quite sure that no more fixes for this older mboard will be forthcoming from the vendor. Under high to moderate load, the layer will simply 'miss' interrupts, leading to file/network traffic corruption and dropped characters on serial consoles. Here's the non -v boot showing the warning entries. pcib2: pcibus 2 on motherboard pir0: on motherboard $PIR: Using invalid BIOS IRQ 17 from 1.0.INTA is for link 0x12 $PIR: Using invalid BIOS IRQ 23 from 0.7.INTA is for link 0x18 $PIR: Using invalid BIOS IRQ 16 from 0.3.INTA is for link 0x11 $PIR: Using invalid BIOS IRQ 18 from 0.4.INTA is for link 0x13 $PIR: Using invalid BIOS IRQ 20 from 0.5.INTA is for link 0x15 $PIR: Using invalid BIOS IRQ 22 from 0.6.INTA is for link 0x17 Is there a tunable I'm not aware of that I could revert back to not believing the BIOS and use the $PIR entries? -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired);