From: Frans Pop <elendil@planet.nl>
To: linux-kernel@vger.kernel.org
Cc: Venki Pallipadi <venkatesh.pallipadi@intel.com>,
Ingo Molnar <mingo@elte.hu>
Subject: [git head] Should X86_PAT really default to yes?
Date: Fri, 2 May 2008 21:22:03 +0200 [thread overview]
Message-ID: <200805022122.03576.elendil@planet.nl> (raw)
With X86_PAT enabled, when X is started I get about 40 lines (with varying
addresses) like:
kernel: Xorg:3358 /dev/mem expected mapping type write-back for
807bf000-81000000, got uncached-minus
And when X exits I get a bunch of lines like:
kernel: Xorg:3349 freeing invalid memtype 80020000-8002a000
I also noticed artifacts (a band of about 2 cm high across the screen) after
X goes to black but before the switch to VT1.
When I unset X86_PAT all this disappeared.
Apparently this has been seen before:
http://lkml.org/lkml/2008/5/2/139
The author of that mail also points to:
http://marc.info/?l=linux-kernel&m=120612742217604&w=2
Is this a bug in PAT or not. If it is, should PAT really be recommended to
be enabled by default?
System: Intel desktop with D945GCZ mainboard
Intel(R) Pentium(R) D CPU 3.20GHz
x86_64 kernel; Debian unstable
Video: 00:02.0 VGA compatible controller [0300]:
Intel Corporation 82945G/GZ Integrated Graphics Controller
[8086:2772] (rev 02)
Cheers,
FJP
next reply other threads:[~2008-05-02 19:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 19:22 Frans Pop [this message]
2008-05-02 19:37 ` [git head] Should X86_PAT really default to yes? Pallipadi, Venkatesh
2008-05-02 20:40 ` Jesse Barnes
2008-05-02 21:55 ` Pallipadi, Venkatesh
2008-05-02 22:07 ` Jesse Barnes
2008-05-04 7:10 ` Frans Pop
2008-05-04 9:04 ` Ingo Molnar
2008-05-04 20:23 ` Yinghai Lu
2008-05-05 16:55 ` Frans Pop
2008-05-05 17:00 ` Pallipadi, Venkatesh
2008-05-05 17:42 ` Yinghai Lu
2008-05-05 18:56 ` Frans Pop
2008-05-05 15:57 ` Jesse Barnes
2008-05-05 17:32 ` Frans Pop
2008-05-05 17:45 ` Jesse Barnes
2008-05-05 17:59 ` Pallipadi, Venkatesh
2008-05-05 18:59 ` Frans Pop
2008-05-05 19:04 ` fb layer & ioremap_wc Jesse Barnes
2008-05-05 19:30 ` Frans Pop
2008-06-13 16:42 ` Frans Pop
2008-06-13 16:42 ` Frans Pop
2008-05-06 22:42 ` [git head] Should X86_PAT really default to yes? Venki Pallipadi
2008-05-07 7:02 ` [git head] X86_PAT & mprotect Ingo Molnar
2008-05-07 19:18 ` Hugh Dickins
2008-05-07 23:23 ` Venki Pallipadi
2008-05-09 10:08 ` Ingo Molnar
2008-05-09 20:05 ` Venki Pallipadi
2008-05-09 20:09 ` Venki Pallipadi
2008-05-09 20:48 ` Hugh Dickins
2008-05-09 22:11 ` Dave Airlie
2008-05-09 22:20 ` Pallipadi, Venkatesh
2008-05-10 6:19 ` Dave Airlie
2008-05-10 6:29 ` Keith Packard
2008-05-10 5:45 ` Keith Packard
2008-05-07 22:36 ` Venki Pallipadi
2008-05-25 15:08 ` [git head] Should X86_PAT really default to yes? Frans Pop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200805022122.03576.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=venkatesh.pallipadi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.