Date: Tue, 27 Mar 2001 14:10:06 -0800 (PST) From: natedac@kscable.com To: freebsd-ports@FreeBSD.org Subject: Re: ports/25958: Xfree86's savage and vesa drivers%2 Message-ID: <200103272210.f2RMA6G48020@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/25958; it has been noted by GNATS.
From: natedac@kscable.com
To: freebsd-gnats-submit@FreeBSD.org, natedac@kscable.com
Cc:
Subject: Re: ports/25958: Xfree86's savage and vesa drivers%2
Date: Tue, 27 Mar 2001 16:02:52 -0600 (CST)
Problem has been solved by a workaround in the kernel source. Thanks to
the help of some of the guys on #BSDcode on EFnet (hi BigSpoon!).
Apparently MTRR doesn't work on this paricular processor, an AMD 550 MHz
Athlon, or the kernel is somehow detecting it wrong. XFree86
4.4.x obviously is trying to use this feature somehow, and that was
causing a kernel panic.
Temporary Workaround:
At line 572 of /sys/i386/i386/i686_mem.c, comment out the commands that
attempt to detect the MTRR facility, like this:
---- snip ----
static void
i686_mem_drvinit(void *unused)
{
/* Try for i686 MTRRs */
/*
if ((cpu_feature & CPUID_MTRR) &&
((cpu_id & 0xf00) == 0x600) &&
((strcmp(cpu_vendor, "GenuineIntel") == 0) ||
(strcmp(cpu_vendor, "AuthenticAMD") == 0))) {
mem_range_softc.mr_op = &i686_mrops;
}
*/
}
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103272210.f2RMA6G48020>