public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: venkatesh.pallipadi@intel.com, suresh.b.siddha@intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: x86-PAT tree merge causes keyboard problems
Date: Tue, 15 Sep 2009 15:44:16 -0700	[thread overview]
Message-ID: <4AB018C0.30203@zytor.com> (raw)
In-Reply-To: <20090915205259.GA1910@phenom2.trippelsdorf.de>

On 09/15/2009 01:52 PM, Markus Trippelsdorf wrote:
> The merge of the PAT tree today breaks certain key combinations of my
> keyboard.  For example I switch my virtual desktops with
> ctrl-alt-left/right and this combination stops working. Basically all
> keyboard combinations involving the left alt key are broken on my
> machine as a result of this merge.

> I bisected this down to:
> 
> »
> 335ef896d4c6639849d79367f0fef9abc06d121b is the first bad commit
> commit 335ef896d4c6639849d79367f0fef9abc06d121b
> Author: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> Date:   Fri Jul 10 09:57:36 2009 -0700
> 
>     x86, pat: Add rbtree to do quick lookup in memtype tracking

I think we have a winner for the second bizarrest bug report I've ever
seen[1].  Not doubting you in any way, just that it is clearly a very
strange combination of things at play here.

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.

	-hpa


[1] The bizarrest one was a floating-point bug in the original Crusoe
CPU, which ended up having the effect that a pair of double doors on a
particular level in Quake 1 would only have one of the two half-doors
swing open when the player approached.

  reply	other threads:[~2009-09-15 22:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 20:52 x86-PAT tree merge causes keyboard problems Markus Trippelsdorf
2009-09-15 22:44 ` H. Peter Anvin [this message]
2009-09-16  2:07   ` Suresh Siddha
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=4AB018C0.30203@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=suresh.b.siddha@intel.com \
    --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