From owner-freebsd-current Thu Nov 29 5:36:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 4C9E137B420 for ; Thu, 29 Nov 2001 05:36:31 -0800 (PST) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id AAA09945; Fri, 30 Nov 2001 00:36:22 +1100 Date: Fri, 30 Nov 2001 00:36:26 +1100 (EST) From: Bruce Evans X-X-Sender: To: Peter Jeremy Cc: Subject: Re: Panic changing screen mode with vidcontrol In-Reply-To: <20011126173543.A7551@gsmx07.alcatel.com.au> Message-ID: <20011130003256.T1674-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Mon, 26 Nov 2001, Peter Jeremy wrote: > Having installed a new kernel and userland from sources about a day > old, my vidcontrol command now causes a panic: > > Fatal trap 12: page fault while in vm86 mode > fault virtual address = 0xc359b > ... > The backtrace shows nothing useful - gdb doesn't seem to handle > tracing through vm86 :-(. > > The command I used was "vidcontrol 132x60" after confirming that > this was listed in "vidcontrol -i mode". I have previously been > using VESA_132x60, but that also panics now. > > Any suggestions where to look? If it's a new bug, then it might be from not updating bios.c in the recent pmap changes. From error output: ./@/i386/i386/bios.c: In function `bios16': ./@/i386/i386/bios.c:379: warning: comparison between pointer and integer Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message