From owner-freebsd-current@FreeBSD.ORG Fri Jan 16 14:33:18 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 22A8A16A4CF for ; Fri, 16 Jan 2004 14:33:18 -0800 (PST) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE74B43D5E for ; Fri, 16 Jan 2004 14:33:12 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: (qmail 18435 invoked from network); 16 Jan 2004 22:33:11 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 16 Jan 2004 22:33:11 -0000 Received: from 10.50.40.206 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.10/8.12.10) with ESMTP id i0GMX4M2089506; Fri, 16 Jan 2004 17:33:07 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: "Bjoern A. Zeeb" , current@freebsd.org Date: Fri, 16 Jan 2004 17:21:29 -0500 User-Agent: KMail/1.5.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401161721.29167.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) 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: Fri, 16 Jan 2004 22:33:18 -0000 On Friday 16 January 2004 03:25 pm, Bjoern A. Zeeb wrote: > Hi, > > back last year I had trouble with some PCI rerouting: > http://lists.freebsd.org/pipermail/freebsd-current/2003-July/thread.html#71 >55 > > Noriyoshi Kawano came up with the attached patch but it hadn't been > committed because it was unknown why a kernel panic happens at boot > time. > > Today I rebuilt a kernel from HEAD and still had trouble so the > tunable saved my weekend. > > Can we somehow get this debugged and sorted out ? 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. Have you tried enabling ACPI? The panic you are getting I think comes from not having a valid curpcb yet, but that seems odd. Ah, we never set it for proc0 during boot. Try this patch: Index: machdep.c =================================================================== RCS file: /usr/cvs/src/sys/i386/i386/machdep.c,v retrieving revision 1.585 diff -u -r1.585 machdep.c --- machdep.c 3 Jan 2004 02:02:24 -0000 1.585 +++ machdep.c 16 Jan 2004 22:19:25 -0000 @@ -2010,6 +2010,7 @@ pcpu_init(pc, 0, sizeof(struct pcpu)); PCPU_SET(prvspace, pc); PCPU_SET(curthread, &thread0); + PCPU_SET(curpcb, thread0.td_pcb); /* * Initialize mutexes. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org