On Tue, Aug 14, 2018 at 9:54 PM Johannes Lundberg
wrote:
>
>
> On Tue, Aug 14, 2018 at 3:39 PM Konstantin Belousov
> wrote:
>
>> On Tue, Aug 14, 2018 at 08:55:36AM -0500, Eric van Gyzen wrote:
>> > On 8/14/18 4:12 AM, Johannes Lundberg wrote:
>> > > Hi
>> > >
>> > > Something that we have seen
On Tue, Aug 14, 2018 at 3:39 PM Konstantin Belousov
wrote:
> On Tue, Aug 14, 2018 at 08:55:36AM -0500, Eric van Gyzen wrote:
> > On 8/14/18 4:12 AM, Johannes Lundberg wrote:
> > > Hi
> > >
> > > Something that we have seen for a long time on FreeBSD is the boot
> message
> > >
> > > Failed to
On Tue, Aug 14, 2018 at 08:55:36AM -0500, Eric van Gyzen wrote:
> On 8/14/18 4:12 AM, Johannes Lundberg wrote:
> > Hi
> >
> > Something that we have seen for a long time on FreeBSD is the boot message
> >
> > Failed to add WC MTRR for [0xd000-0xdfff]: -22; performance may
> > suffer
> >
On 8/14/18 4:12 AM, Johannes Lundberg wrote:
Hi
Something that we have seen for a long time on FreeBSD is the boot message
Failed to add WC MTRR for [0xd000-0xdfff]: -22; performance may
suffer
Taking a closer look at this with memcontrol I can see that the 256 MB
region that DRM
Hi
Something that we have seen for a long time on FreeBSD is the boot message
Failed to add WC MTRR for [0xd000-0xdfff]: -22; performance may
suffer
Taking a closer look at this with memcontrol I can see that the 256 MB
region that DRM wants to set as WC is already covered by this entry
