From owner-freebsd-current@FreeBSD.ORG Tue Jul 22 11:44:57 2003 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 D9A8937B401 for ; Tue, 22 Jul 2003 11:44:57 -0700 (PDT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC66F43FAF for ; Tue, 22 Jul 2003 11:44:56 -0700 (PDT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 0685C1FFBD5; Tue, 22 Jul 2003 20:44:55 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id DCE771FFAE4; Tue, 22 Jul 2003 20:44:53 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 8BAF115540; Tue, 22 Jul 2003 18:44:41 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 7FEAC153D2; Tue, 22 Jul 2003 18:44:42 +0000 (UTC) Date: Tue, 22 Jul 2003 18:44:42 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: "M. Warner Losh" In-Reply-To: <20030722.113257.116353248.imp@bsdimp.com> Message-ID: References: <20030721103221.C95793@mbox.cksoft.de> <86n0f82r2c.wl@brain.nrik.jp> <20030722.113257.116353248.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS snapshot-20020300 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 18:44:58 -0000 On Tue, 22 Jul 2003, M. Warner Losh wrote: Hi, > In message: > "Bjoern A. Zeeb" 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? ${SUBJECT} the machine boots again and doesn't panic at boot time. for more information please se my initial post. @see http://lists.freebsd.org/pipermail/freebsd-current/2003-July/007155.html > 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. I never debugged why this started to happen between 5.1R and HEAD. The machine is a Compaq DeskPro or s.th. like this; ~ 2 years - so not that old but perhaps with a "strange" BIOS. It had run fine with 4.x and 5.0R and booted a 5.1R for building HEAD. Noriyoshi Kawano came up with the patch that made it boot again so I am happy but as this doesn't seem to happen for many people and the patch is not mainline I asked if there is any better solution to make it work on b0rken machines and mainline. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/