From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: teresa@kvitka.net
Cc: "CK Mailinglist" <ck@vds.kolivas.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: Linux Kernel cfs scheduler and xorg kbd
Date: Tue, 31 Jul 2007 00:49:09 +0200 [thread overview]
Message-ID: <6bffcb0e0707301549t6be3cd97y27726f5421bb7680@mail.gmail.com> (raw)
In-Reply-To: <1185827130.26459.16.camel@xtower.fri>
Hi,
On 30/07/07, <::.. Teresa_II ..::> <teresa@kvitka.net> wrote:
> Hi all,
>
>
> first of all i am not sure if its scheduler issue. But i didn't found
> anything about that in google related to something else.
>
> So i tried 2.6.22.1 kernel with new cfs scheduler v19.1 from Ingo page.
> Previous i used 2.6.22-ck1.
>
> After 24 hours running i get strange behavior in Xorg. It act slower
> with my special keys, like SHIFT, or CTRL. So if i hold SHIFT and press
> ")" and than will press enter, i release SHIIFT and press ENTER it
> doesn't create new line. Even if i start write a Sentence or word with
> "SHIFTed" char it makes next char in high case also.
> Like this: "HAllo" even if i type "Hallo".
>
> It's extremely unusable.
>
> It doesn't happen if i am on other kernel.
>
> I am ready to provide any requested information to find issue.
> If its not kernel related thing - i am very sorry, i just don't know
> where to start to trace whats wrong.
>
> I am on gentoo and use latest xorg server. Keyboard driver is "KBD".
> Mouse use "evdev" driver.
Ingo, can you take a look at this?
>
> --
> Teresa Kalitowska
> jid: teresa@kvitka.net
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
next prev parent reply other threads:[~2007-07-30 22:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 20:25 <::.. Teresa_II ..::>
2007-07-30 22:49 ` Michal Piotrowski [this message]
2007-08-01 6:48 ` Ingo Molnar
2007-08-01 11:31 ` Andi Kleen
2007-08-01 11:01 ` Rene Herman
2007-08-01 12:34 ` Indan Zupancic
2007-08-01 12:50 ` Rene Herman
2007-08-01 13:07 ` Indan Zupancic
2007-08-01 13:26 ` Rene Herman
2007-08-01 13:33 ` <:::.. TeresaII ..:::>
2007-08-01 13:58 ` Rene Herman
2007-08-01 14:44 ` <::.. Teresa_II ..::>
2007-08-01 15:00 ` [ck] " Matthew Hawkins
2007-08-01 15:53 ` <::.. Teresa_II ..::>
2007-08-02 7:11 ` Sébastien Dugué
2007-08-02 12:22 ` Rene Herman
2007-08-02 13:18 ` Indan Zupancic
2007-08-01 15:06 ` Indan Zupancic
2007-08-01 15:09 ` Ingo Molnar
2007-08-01 15:13 ` Rene Herman
2007-08-01 15:20 ` Ingo Molnar
2007-08-01 15:19 ` Rene Herman
2007-08-01 15:26 ` Indan Zupancic
2007-08-06 7:12 ` Ingo Molnar
2007-08-06 13:10 ` Rene Herman
2007-08-06 15:19 ` Indan Zupancic
2007-08-06 17:46 ` Rene Herman
2007-08-06 18:26 ` OT: enabling Xcomposite [was: Linux Kernel cfs scheduler and xorg kbd] Indan Zupancic
2007-08-07 4:40 ` Linux Kernel cfs scheduler and xorg kbd Kyle Moffett
2007-08-07 6:05 ` Arjan van de Ven
2007-08-07 10:17 ` Indan Zupancic
2007-08-07 13:15 ` Rene Herman
2007-08-09 21:14 ` Mark Lord
2007-07-31 11:18 ` [ck] " <::.. Teresa_II ..::>
2007-07-31 11:42 ` <::.. Teresa_II ..::>
2007-07-31 14:27 ` Ingo Molnar
2007-07-31 16:39 ` <::.. Teresa_II ..::>
2007-07-31 15:06 ` Rene Herman
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=6bffcb0e0707301549t6be3cd97y27726f5421bb7680@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=ck@vds.kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=teresa@kvitka.net \
/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®