From owner-freebsd-current@FreeBSD.ORG Mon Jan 19 00:50:28 2004 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 2E18016A4CE; Mon, 19 Jan 2004 00:50:28 -0800 (PST) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C81343D53; Mon, 19 Jan 2004 00:50:11 -0800 (PST) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id C7DF11FF91D; Mon, 19 Jan 2004 09:50:09 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 24C9C1FF90C; Mon, 19 Jan 2004 09:50:08 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 267D5155AB; Mon, 19 Jan 2004 08:40:17 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 2407E155A7; Mon, 19 Jan 2004 08:40:18 +0000 (UTC) Date: Mon, 19 Jan 2004 08:40:18 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: John Baldwin In-Reply-To: <200401161721.29167.jhb@FreeBSD.org> Message-ID: References: <200401161721.29167.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: FreeBSD current mailing list Subject: Re: PCI rerouting 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, 19 Jan 2004 08:50:28 -0000 On Fri, 16 Jan 2004, John Baldwin wrote: > You need to do a gdb listing of the actual faulting IP address printed out in > the panic messages (part after colon of instruction pointer line). Ah, I > think I know what is happening perhaps. > Your BIOS might be broken when we try to route an interrupt. it's a compaq deskpro - BIOS obviously not the best. > Have you tried enabling ACPI? Yes have done this morning; works w/o panic. > The panic you are > getting I think comes from not having a valid curpcb yet, but that seems odd. here is the faulty instruction w/o acpi enabled and w/o your patch: (kgdb) l *0xc0708134 0xc0708134 is in trap (/usr/src/sys/i386/i386/trap.c:457). 452 break; 453 454 /* FALL THROUGH */ 455 456 case T_SEGNPFLT: /* segment not present fault */ 457 if (PCPU_GET(curpcb)->pcb_flags & PCB_VM86CALL) 458 break; 459 460 /* 461 * Invalid %fs's and %gs's can be created using It seems curpcb has been a good guess. > Ah, we never set it for proc0 during boot. Try this patch: will give me a Fatal trap 9: gen. protection fault while in km gdk -k says: no source file for address. even if moving the newly added PCPU_SET a bit further to the end of init386() after td_pcb {->pcb_flags} had been initialized it will give the same panic (fat. trap 9 with the same IP as before). Any more ideas ? -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT 56 69 73 69 74 http://www.zabbadoz.net/