From: "Alejandro Riveira Fernández" <ariveira@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8, v2.6.21.7, v2.6.20.20
Date: Sat, 29 Sep 2007 18:51:34 +0200 [thread overview]
Message-ID: <20070929185134.4a76c80d@gmail.com> (raw)
In-Reply-To: <20070929022013.GA24496@khazad-dum.debian.net>
El Fri, 28 Sep 2007 23:20:13 -0300
Henrique de Moraes Holschuh <hmh@hmh.eng.br> escribió:
> On Fri, 28 Sep 2007, Alejandro Riveira Fernández wrote:
> > I feel it better than 20.5 but the later is more stable. Let me explain.
> >
> > I patched a 2.6.22.9 kernel with both versions 22 and 20.5[1]. With the 22
> > version if i lock the screen (run screensaver) or i try to run a wine program
> > i experience a hard lock up no keyboard or mouse and i have to reboot the
> > machine (i can not try to access it via ssh because i do not have a second
> > machine).
>
Thanks for the response :D
> I have seen that twice with v20.5 under 2.6.22.7/.8. Didn't see it yet with
> v22. xterm would get pissed if I tried to "secure keyboard", so something
> stole the keyboard focus and wouldn't give it back to xorg. Maybe a locking
> bug in xorg somewhere?
>
> Anyway, my kernel is NOT tainted, so rest assured that at least this one is
> not nVidia's fault.
>
> BTW, v20.5 in 2.6.21.7 would sometimes cause dmcrypt to oops when first
> mounting a LUKS volume if there was some non-extra-light disk activity going
> on. Probably something missing in the backport to 2.6.21...
>
> Sorry, days down here have been very busy, so I didn't have time to send a
> proper bug report.
I can add another data point 2.6.23-rc8-cfs-v22-g1bef7dc0-dirty does not have
any problem with wine or xscreensaver is working fine. Again i use nvidia and
a 3 party gpl driver for my wifi rt2500 which have compiled fine with the new
kernel (surprise surprise!)
If you need any more info just ask.
Thanks
P.S: I use ubuntu feisty fwiw
--
Nunca discutas con un idiota. Al final te hacen rebajarte a su nivel y entonces
te acaban ganando debido a su mayor experiencia.
next prev parent reply other threads:[~2007-09-29 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 11:13 [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8, v2.6.21.7, v2.6.20.20 Ingo Molnar
2007-09-26 13:33 ` S.Çağlar Onur
2007-09-26 13:48 ` Ingo Molnar
2007-09-28 20:26 ` Alejandro Riveira Fernández
2007-09-29 2:20 ` Henrique de Moraes Holschuh
2007-09-29 16:51 ` Alejandro Riveira Fernández [this message]
2007-09-30 15:26 ` Ingo Molnar
2007-10-02 18:12 ` Alejandro Riveira Fernández
2007-10-26 18:56 ` [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8,v2.6.21.7, v2.6.20.20 Fortier,Vincent [Montreal]
-- strict thread matches above, loose matches on Subject: below --
2007-09-29 11:11 [patch/backport] CFS scheduler, -v22, for v2.6.23-rc8, v2.6.22.8, v2.6.21.7, v2.6.20.20 Matthew
2007-09-30 15:43 ` Ingo Molnar
[not found] ` <e85b9d30709300943rded9801xddc6ca0a4773ff53@mail.gmail.com>
2007-09-30 17:27 ` Ingo Molnar
2007-09-30 23:54 ` Bill Davidsen
2007-10-02 9:06 ` Matthew
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=20070929185134.4a76c80d@gmail.com \
--to=ariveira@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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