From owner-freebsd-current@FreeBSD.ORG  Tue Jul 22 10:33:20 2003
Return-Path: <owner-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 9B47937B401
	for <current@freebsd.org>; Tue, 22 Jul 2003 10:33:20 -0700 (PDT)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2F36943F93
	for <current@freebsd.org>; Tue, 22 Jul 2003 10:33:17 -0700 (PDT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.9/8.12.3) with ESMTP id h6MHX9FL050301;
	Tue, 22 Jul 2003 11:33:14 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Tue, 22 Jul 2003 11:32:57 -0600 (MDT)
Message-Id: <20030722.113257.116353248.imp@bsdimp.com>
To: bzeeb-lists@lists.zabbadoz.net
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <Pine.BSF.4.53.0307211602420.45284@e0-0.zab2.int.zabbadoz.net>
References: <20030721103221.C95793@mbox.cksoft.de>
	<86n0f82r2c.wl@brain.nrik.jp>
	<Pine.BSF.4.53.0307211602420.45284@e0-0.zab2.int.zabbadoz.net>
X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: bowie@nrik.jp
cc: current@freebsd.org
Subject: Re: Fatal trap 12: page fault while in kernel mode
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jul 2003 17:33:20 -0000

In message: <Pine.BSF.4.53.0307211602420.45284@e0-0.zab2.int.zabbadoz.net>
            "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> writes:
: On Mon, 21 Jul 2003, Noriyoshi Kawano wrote:
: 
: > I have similar problem.
: > disable re-route interrupts.
: > It's works fine.
: >
: > --- /sys/dev/pci/pci.c.orig	Tue Jul  1 23:08:32 2003
: > +++ /sys/dev/pci/pci.c	Mon Jul 21 11:04:55 2003
: > @@ -800,7 +800,7 @@
: >  	}
: >
: >  	if (cfg->intpin > 0 && PCI_INTERRUPT_VALID(cfg->intline)) {
: > -#if defined(__ia64__) || (defined(__i386__) && !defined(SMP))
: > +#if defined(__ia64__)
: >  		/*
: >  		 * Try to re-route interrupts. Sometimes the BIOS or
: >  		 * firmware may leave bogus values in these registers.
: 
: 
: Thanks. This works fine. Is there any "global" solution to the problem
: so that I won't need to patch again the time 5.2R comes out ?

I'm just catching the tail end of this problem report.  What problem
is solved by not rotuing interrupts?

I'm guessing it is the "we don't setup things correctly to call some
BIOSes" or "some older pci bioses lie to us so we shoot our selves
when we believe the lies" or something like that.

Warner