From: Suresh Siddha <suresh.b.siddha@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: x86-PAT tree merge causes keyboard problems
Date: Tue, 15 Sep 2009 19:07:39 -0700 [thread overview]
Message-ID: <1253066859.2667.1.camel@sbs-t61.sc.intel.com> (raw)
In-Reply-To: <4AB018C0.30203@zytor.com>
On Tue, 2009-09-15 at 15:44 -0700, H. Peter Anvin wrote:
> We need more information about your system, the lspci -vv and dmidecode
> output, as well as your entire dmesg, and a dump of
> /debug/x86/pat_memtype_list.
I am able to reproduce similar such mem type conflict messages on my
system. Will look more detailed into this tomorrow.
thanks,
suresh
next prev parent reply other threads:[~2009-09-16 2:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 20:52 Markus Trippelsdorf
2009-09-15 22:44 ` H. Peter Anvin
2009-09-16 2:07 ` Suresh Siddha [this message]
2009-09-16 5:26 ` Markus Trippelsdorf
2009-09-16 6:01 ` H. Peter Anvin
2009-09-16 21:28 ` Suresh Siddha
2009-09-17 3:40 ` Markus Trippelsdorf
2009-09-17 21:13 ` [tip:x86/pat] x86, pat: don't use rb-tree based lookup in reserve_memtype() tip-bot for Suresh Siddha
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=1253066859.2667.1.camel@sbs-t61.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®