From: Rene Herman <rene.herman@gmail.com>
To: "<:::.. TeresaII ..:::>" <teresa@kvitka.net>
Cc: Indan Zupancic <indan@nul.nu>, Andi Kleen <andi@firstfloor.org>,
Ingo Molnar <mingo@elte.hu>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
CK Mailinglist <ck@vds.kolivas.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux Kernel cfs scheduler and xorg kbd
Date: Wed, 01 Aug 2007 15:58:40 +0200 [thread overview]
Message-ID: <46B09190.1070201@gmail.com> (raw)
In-Reply-To: <46B08B95.2010405@kvitka.net>
On 08/01/2007 03:33 PM, <:::.. TeresaII ..:::> wrote:
> Problem is, that i can't reproduce it after last reboot.
> Can this be different on each reboot ? Any idea ?
>
> About another kernel: i only had -ck kernels since last year or more, i
> can remember i had same behavier atleast 6 month ago, or maybe more. But
> it wasn't that hard and it dissapiered self after some time.
Hmm.
> Now on first run of 2.6.22.1-cfs-v19.1 i got it again. And realy bad. It
> was even very hard to write report mail.
I notice by the way that you are also using Thunderbird 2.0 -- that was my
own suspect; I had just switched from Thunderbird 1.5.
> I did reboot, day after that it was back, but not that hard. And now
> rebooted yesterday and cant reproduce it at all.
I believe that at least for now we can safely remove this from any list of
possible CFS regresssions. I'll sit on it and see what I can find out
when/if my stuck delete happens again.
Indan -- under what circumstances/programs did you experience what?
Rene.
next prev parent reply other threads:[~2007-08-01 14:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 20:25 Linux Kernel cfs scheduler and xorg kbd <::.. Teresa_II ..::>
2007-07-30 22:49 ` Michal Piotrowski
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 [this message]
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=46B09190.1070201@gmail.com \
--to=rene.herman@gmail.com \
--cc=andi@firstfloor.org \
--cc=ck@vds.kolivas.org \
--cc=indan@nul.nu \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--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