From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alessandro Suardi <alessandro.suardi@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: 2.6.24-git2: Oracle 11g VKTM process enters R state on startup and is unkillable [still broken in 2.6.25-rc1]
Date: Mon, 11 Feb 2008 20:56:17 +0100 [thread overview]
Message-ID: <200802112056.17839.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.1.00.0802111131310.2920@woody.linux-foundation.org>
On Monday, 11 of February 2008, Linus Torvalds wrote:
>
> On Mon, 11 Feb 2008, Rafael J. Wysocki wrote:
>
> > On Monday, 11 of February 2008, Alessandro Suardi wrote:
> > > >
> > > > 2.6.24-git1 is okay
> > > > 2.6.24-git2 is bad
>
> Ok, that's git ID's
>
> b47711bfbcd4eb77ca61ef0162487b20e023ae55 2.6.24-git1
> 9b73e76f3cf63379dcf45fcd4f112f5812418d0a 2.6.24-git2
>
> so if you get a git tree, you can do
>
> gitk b47711b..9b73e76
>
> to see what happened in there.
>
> However, the obvious candidates are the scheduler or the ocfs2 merge, and
> the latter is only relevant in case you use ocfs2, of course.
>
> The rest of it tends to be the DVB and SCSI updates.
>
> But it would be great if you could do a bisect and verify. Just do
>
> git bisect start
> git bisect good b47711bfbcd4eb77ca61ef0162487b20e023ae55
> git bisect bad 9b73e76f3cf63379dcf45fcd4f112f5812418d0a
>
> and off you go..
Well, I've already bisected that down to commit
6f505b16425a51270058e4a93441fe64de3dd435 "sched: rt group scheduling" and
provided a simple test case. Moreover, there are patches from Peter that fix
the problem, but they are lost somewhere in the way from him to you (please see
http://lkml.org/lkml/2008/2/5/535 and http://lkml.org/lkml/2008/2/6/320).
Thanks,
Rafael
next prev parent reply other threads:[~2008-02-11 19:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 16:20 Alessandro Suardi
2008-02-11 19:09 ` Rafael J. Wysocki
2008-02-11 19:38 ` Linus Torvalds
2008-02-11 19:56 ` Rafael J. Wysocki [this message]
2008-02-11 20:49 ` Ingo Molnar
2008-02-11 22:10 ` Ingo Molnar
2008-02-11 23:12 ` Rafael J. Wysocki
2008-02-11 23:31 ` Alessandro Suardi
2008-02-13 12:28 ` Ingo Molnar
2008-02-12 13:44 ` Peter Zijlstra
2008-02-12 14:35 ` Alessandro Suardi
2008-02-12 14:53 ` Peter Zijlstra
2008-02-12 19:28 ` Rafael J. Wysocki
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=200802112056.17839.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=alessandro.suardi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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®