> That's odd, since FreeBSD and Linux work fine on K6, even though
> they don't do special treatment with K6 (as for the PGE bit). So
> perhaps setting the bit is not the direct cause.
Hmm, perhaps you can take a look at how they use the PGE feature and see if
it differs from what I did in oski
From: Roland McGrath <[EMAIL PROTECTED]>
Subject: Re: Problems with oskit-mach
Date: Wed, 6 Sep 2000 14:49:55 -0400 (EDT)
> I'm pretty sure I already make exactly that check (using the oskit header
> files and functions). That is the official Intel way of checking for the
> feature. The problem
I'm pretty sure I already make exactly that check (using the oskit header
files and functions). That is the official Intel way of checking for the
feature. The problem people are reporting is with AMD K6 family
processors, which appear to report that feature bit in cpuid but not
actually support
From: Roland McGrath <[EMAIL PROTECTED]>
Subject: Re: Problems with oskit-mach
Date: Wed, 6 Sep 2000 13:30:55 -0400 (EDT)
> It is certainly harmless to disable the code that uses PGE. It is just an
> optimization. It would be helpful to figure out exactly when it is and
> isn't safe to use this
> On Tue, 05 Sep 2000, Igor Khavkine wrote:
>
> > The first problem was that my computer generated a general protection
> > fault in the i386/intel/pmap.c::pmap_boostrap() function where the code
> > was trying to modify the %cr4 register. I have a K6-III which pretends
> > to support the PGE ext
Hi Igor!
On Tue, 05 Sep 2000, Igor Khavkine wrote:
> The first problem was that my computer generated a general protection fault
> in the i386/intel/pmap.c::pmap_boostrap() function where the code was trying
> to modify the %cr4 register. I have a K6-III which pretends to support the
> PGE exten
