From owner-freebsd-current@FreeBSD.ORG Mon Jan 31 12:01:23 2005 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 65A6616A4CE for ; Mon, 31 Jan 2005 12:01:23 +0000 (GMT) Received: from hetzner.co.za (lfw.hetzner.co.za [196.7.18.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97B5E43D2F for ; Mon, 31 Jan 2005 12:01:22 +0000 (GMT) (envelope-from ianf@hetzner.co.za) Received: from localhost ([127.0.0.1]) by hetzner.co.za with esmtp (Exim 3.36 #1) id 1CvaF6-000CXI-00 for current@freebsd.org; Mon, 31 Jan 2005 14:01:20 +0200 To: current@freebsd.org From: Ian FREISLICH X-Attribution: BOFH Date: Mon, 31 Jan 2005 14:01:20 +0200 Sender: ianf@hetzner.co.za Message-Id: Subject: sys/1386/i386/mptable.c rev 1.239 breaks boot. 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: Mon, 31 Jan 2005 12:01:23 -0000 Hi I have a dual pII machine that doesn't boot with 1.239 of sys/1386/i386/mptable.c. It boots with this patch backed out. Does anyone have any ideas beyond backing out this patch? revision 1.239 date: 2005/01/18 20:27:24; author: jhb; state: Exp; lines: +7 -1 If a valid ELCR was found, consult it for the trigger mode of ISA interrupts that have a trigger mode of conforming. This fixes problems on some older machines that still route PCI devices via ISA interrupts when using an I/O APIC. This seems to be a case of breaking, rather than fixing older machines. It's highly reproduceable. I mailed the author of this commit over a week ago, but have not had a response yet :(. This is definitely a show-stopper, for me at least. Ian -- Ian Freislich