From owner-freebsd-current Thu Oct 17 17:54:35 2002 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 EECC537B404 for ; Thu, 17 Oct 2002 17:54:33 -0700 (PDT) Received: from www.fastmail.fm (fastmail.fm [209.61.183.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D04943E6E for ; Thu, 17 Oct 2002 17:54:33 -0700 (PDT) (envelope-from freebsd@fastmail.fm) Received: from www.fastmail.fm (localhost [127.0.0.1]) by localhost.localdomain (Postfix) with ESMTP id D75466DBC1 for ; Thu, 17 Oct 2002 19:54:24 -0500 (CDT) Received: from server3.fastmail.fm (server3.internal [10.202.2.134]) by www.fastmail.fm (Postfix) with ESMTP id CF6886DBAA for ; Thu, 17 Oct 2002 19:54:24 -0500 (CDT) Received: by server3.fastmail.fm (Postfix, from userid 99) id 9C1D22FD34; Thu, 17 Oct 2002 19:54:23 -0500 (CDT) Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 X-Mailer: MIME::Lite 1.2 (F2.6; T1.001; A1.48; B2.12; Q2.03) Date: Fri, 18 Oct 2002 00:54:23 UT From: "Glenn Gombert" To: current@freebsd.org X-Epoch: 1034902464 X-Sasl-enc: pkBLu74KAJ+nRffV26l+sQ Subject: Remote GDB Trap 12 Fatal On Target Message-Id: <20021018005423.9C1D22FD34@server3.fastmail.fm> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am trying to get a remote gdb kernel debugging session and on the Target macine I get the following error: "Fatal trap 12: page fault while in kernel mode" .. fault vurtual address = 0x26 fault code = supervisor read, page not present" is anyone else getting this as well ?? There is a thread in -Current last June sometime, with the "fix" being to add the following line to the config file: ............ Turns out the workaround is to use DISABLE_PG_G. Two things made me try this. One: In his commit of pmap.c and locore.s on 7/12 7:56 Peter had this to say: +-- |- Try and fix some very bogus PG_G and PG_PS interactions that were bad | enough to cause vm86 bios calls to break. vm86 depended on our existing ... |New option: DISABLE_PG_G - In case I missed something. ---------------------\ This did not fix the problem thought, any other ideas appreaciated!! Thanks: -- Glenn Gombert freebsd@fastmail.fm "Never trust any operating system you don't have the source code for" -- http://fastmail.fm - The holy hand grenade of email services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message