Re: 2.6.24-git2: Oracle 11g VKTM process enters R state on startupand is unkillable [still broken in 2.6.25-rc1]

[Peter Zijlstra]

On Tue, 2008-02-12 at 15:35 +0100, Alessandro Suardi wrote:
> On Feb 12, 2008 2:44 PM, Peter Zijlstra <a.p.zijlstra@xxxxxxxxx> wrote:
> >
> > On Tue, 2008-02-12 at 00:12 +0100, Rafael J. Wysocki wrote:
> > > On Monday, 11 of February 2008, Ingo Molnar wrote:
> > > >
> > > > * Ingo Molnar <mingo@xxxxxxx> wrote:
> > > >
> > > > > no, they were not lost, they just didnt pass QA here (they crashed on
> > > > > a particularly hard to debug 8-way box i have) and Peter worked on
> > > > > that queue of fixes up until today to get it really correct. Could you
> > > > > check:
> > > > >
> > > > >    git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-sched.git
> > > > >
> > > > > combo patch below as well - whichever you prefer. The shortlog can be
> > > > > found below as well - but i dont yet consider this pullable, i'd like
> > > > > it to see pass a full night of randconfig tests on my test-systems.
> > > >
> > > > ok, we just found the reason for the 8-way crash, the delta fix from
> > > > Peter is below if any of you have tried the previous combo patch.
> > > > Updated sched.git as well, new HEAD is
> > > > fec13e45305d69fd0bd23b30bd05a0a42cf341f8.
> > >
> > > With the previous patch and this patch applied, the issue is not reproducible
> > > here.
> >
> > Did you enable CONFIG_RT_GROUP_SCHED (it defaults to n)?
> >
> > If you didn't, could you try with it set to y?
> 
> I just rebuilt 2.6.25-rc1-git2 with Ingo's patch and your patch on top,
>  and the Oracle VKTM issue is still gone even with
> 
> [asuardi@sandman ~]$ grep GROUP_SCHED
> /share/src/linux-2.6.25-rc1-git2-orafix/.config
> CONFIG_GROUP_SCHED=y
> CONFIG_FAIR_GROUP_SCHED=y
> CONFIG_RT_GROUP_SCHED=y
> # CONFIG_CGROUP_SCHED is not set
> 
>  so it's good for me.
> 
> Or is it necessary to also enable CONFIG_CGROUP_SCHED and retest ?

No that should be quite all-right. Thanks for testing!

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/