From owner-freebsd-bugs Fri Mar 1 4:52:39 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2A23A37B41A; Fri, 1 Mar 2002 04:52:36 -0800 (PST) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g21Co9U34849; Fri, 1 Mar 2002 04:50:09 -0800 (PST) (envelope-from dwmalone) Date: Fri, 1 Mar 2002 04:50:09 -0800 (PST) From: Message-Id: <200203011250.g21Co9U34849@freefall.freebsd.org> To: dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org, dwmalone@FreeBSD.org Subject: Re: kern/28418: XFree86 4.X panics FreeBSD 4.3-STABLE on Asus A7A266 motherboard Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: XFree86 4.X panics FreeBSD 4.3-STABLE on Asus A7A266 motherboard Responsible-Changed-From-To: freebsd-bugs->dwmalone Responsible-Changed-By: dwmalone Responsible-Changed-When: Fri Mar 1 04:44:46 PST 2002 Responsible-Changed-Why: I can reproduce this on the same motherboard at home when I install XF86-4. According to some intel documentation I have, if you get a GPF in protected mode then either the privilage level is not 0 (which it should be in the kernel) or the value in ECX isn't a valid MSR register number. I guess we must be looking at the latter. I wonder this is a problem specific to the A7A266 board, or if relates to all Athlon processors? Is anyone using FreeBSD-4 or FreeBSD-current with XFree86-4 with a video driver which would try to alter the MTRR settings? http://www.FreeBSD.org/cgi/query-pr.cgi?pr=28418 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message