From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Cc: Ingo Molnar <mingo@elte.hu>,
mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-git4+ regression
Date: Mon, 04 Feb 2008 12:36:36 +0100 [thread overview]
Message-ID: <1202124997.32654.78.camel@lappy> (raw)
In-Reply-To: <20080204111747.GB4450@ics.muni.cz>
On Mon, 2008-02-04 at 12:17 +0100, Lukas Hejtmanek wrote:
> Ingo,
>
> any progress here? I've tried to revert this patch:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=67e9fb2a39a1d454218d50383094940982be138f
>
> as it was marked as suspicious patch in this case
> (http://www.uwsg.indiana.edu/hypermail/linux/kernel/0801.3/1665.html)
>
> but in such a case, kernel 2.6.24-git13 does oops at startup in sched_slice.
>
> I think this is really *big* regression in 2.6.24 kernel.
I can't reproduce this with a pure cpu load. I started 10
while :; do :; done &
instances and aside from slowing down, nothing bad happened.
May I suggest you try latency top to see if there is something in your
build scenario that generates horrible latencies (some IO path or
whatnot).
next prev parent reply other threads:[~2008-02-04 11:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 13:56 2.6.24-git4+ regression Lukas Hejtmanek
2008-01-31 10:29 ` Ingo Molnar
2008-01-31 10:55 ` Lukas Hejtmanek
2008-02-04 11:17 ` Lukas Hejtmanek
2008-02-04 11:36 ` Peter Zijlstra [this message]
2008-02-04 14:36 ` Lukas Hejtmanek
2008-02-04 14:45 ` Peter Zijlstra
2008-02-04 17:00 ` Lukas Hejtmanek
2008-02-04 12:01 ` Ingo Molnar
2008-02-04 12:29 ` Lukas Hejtmanek
2008-02-04 13:04 ` Ingo Molnar
2008-02-04 13:49 ` Lukas Hejtmanek
2008-02-14 16:55 ` Srivatsa Vaddagiri
2008-02-17 20:26 ` Lukas Hejtmanek
2008-02-18 4:28 ` Ingo Molnar
2008-02-18 7:38 ` Mike Galbraith
2008-02-18 8:20 ` Srivatsa Vaddagiri
2008-02-18 8:36 ` Mike Galbraith
[not found] ` <1203325554.4889.2.camel@homer.simson.net>
[not found] ` <1203345102.5984.1.camel@homer.simson.net>
2008-02-19 8:15 ` Mike Galbraith
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=1202124997.32654.78.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=xhejtman@ics.muni.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.