From owner-freebsd-questions@FreeBSD.ORG Wed Aug 18 20:38:35 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD54E16A4CE for ; Wed, 18 Aug 2004 20:38:35 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id AACE943D31 for ; Wed, 18 Aug 2004 20:38:35 +0000 (GMT) (envelope-from pete@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1937) id A93C15C945; Wed, 18 Aug 2004 13:38:35 -0700 (PDT) Date: Wed, 18 Aug 2004 13:38:35 -0700 From: pete@mu.org To: freebsd-questions@freebsd.org Message-ID: <20040818203835.GC74014@mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-PGP-Key-Location: http://www.more.net/~pete/pubkey.asc X-PGP-Key-Fingerprint: 0429 BBF3 2FAC F428 0107 3523 8133 496D F164 407C Subject: processor eflags = interrupt enabled,vm86 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Aug 2004 20:38:35 -0000 Hi, I have a Gateway 920 server that I'm trying to load 4.10 on. I'm seeing an error that I've never come across before. It looks like it might in the processor flags, but I can't seem to find anyone with this issue---except a few guys with the same model server. No one seems to have the answer to the problem---maybe maybe most people wouldn't buy a Gateway 920 to put BSD on either...it's not my choice though. NOTE: I've tried 3 different CD images, serveral boot floppies, even some newer versions of 5.x, but they all get the same error. I've even tried it on several different 920s. They all have the same problem. I've looked through LINT and I can't find a reference to vm86. It looks like it's a cpu flag, but I don't see where to disable or change it. Any clues what's causing this or how to fix it? It happens right after the kernel get's loaded into memory. Here it is: Fatal trap 10: trace trap while in vm86 mode instruction pointer =0xf000:0xf842 stack pointer =0x0:0xff8 frame pointer =0x0:0x0 code segment =base 0x0, limit 0x0, type 0x0 =DPL 0, pres 0, def32 0, gran 0 processor eflags =interrupt enabled,vm86, IOPL = 0 current process = Idle interrupt mask = net tty bio cam trap number = 10 panic: trace trap Uptime 0s