From: Ingo Molnar <mingo@elte.hu>
To: "Alejandro Riveira Fernández" <ariveira@gmail.com>
Cc: 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: Sun, 30 Sep 2007 17:26:22 +0200 [thread overview]
Message-ID: <20070930152621.GB24077@elte.hu> (raw)
In-Reply-To: <20070928222631.25504d68@gmail.com>
* Alejandro Riveira Fernández <ariveira@gmail.com> wrote:
> > Even if CFS v20.5 worked well for you, please try this release too, with
> > a good focus on interactivity testing - because, unless some major
> > showstopper is found, this codebase is intended for a v2.6.24 upstream
> > merge.
> >
> > ( Even a quick, subjective report of: "checked this patch, it didnt
> > crash and it feels like v20.5" or "laggier than v20.5" or "feels
> > better than v20.5" is useful to us and enables us to judge the general
> > direction of interactivity. )
>
> 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). I run with the nvidia kernel
> module so I know my report is useless but just for the record... Here
> it is my config:
hm. There are no similar reports so far. Could you try to run the wine
program from a VGA text console (first do 'xhost +' in an xterm under X
and then 'export DISPLAY=:0' in the text console) and see whether
anything gets output to that console? Also enable nmi_watchdog=2 - which
could print a backtrace of the point of the hard lockup.
but in general there's nothing scheduler-specific about screensavers or
wine - but it could be related to 3D mode of the chip (hence related to
the nvidia module) - do you get a similar lockup if you try to run
'glxgears'?
Ingo
next prev parent reply other threads:[~2007-09-30 15:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 11:13 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
2007-09-30 15:26 ` Ingo Molnar [this message]
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]
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=20070930152621.GB24077@elte.hu \
--to=mingo@elte.hu \
--cc=ariveira@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®