From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Fortier,Vincent [Montreal]" <Vincent.Fortier1@EC.GC.CA>,
Greg KH <gregkh@suse.de>, Randy Dunlap <randy.dunlap@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
kay.sievers@vrfy.org, Balbir Singh <balbir@in.ibm.com>
Subject: Re: 2.6.22.14 oops msg with commvault galaxy ?
Date: Wed, 12 Dec 2007 12:38:16 +0530 [thread overview]
Message-ID: <20071212070816.GA31455@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071211210653.GA6902@elte.hu>
On Tue, Dec 11, 2007 at 10:06:53PM +0100, Ingo Molnar wrote:
>
> * Fortier,Vincent [Montreal] <Vincent.Fortier1@EC.GC.CA> wrote:
>
> > > That has changed from /sys/kernel/uids/<uid>/cpu_share
> > >
> >
> > Here is my config.
> >
> > Maybie I should give it a shot without CFS at all and see what
> > happends ?
>
> and also with CFS but without CONFIG_FAIR_GROUP_SCHED.
>
Hi Ingo,
I am able to reproduce the oops here on my system with 2.6.22.14 +
CFS backport. I am not able to reproduce it with 2.6.22.13 + CFS
backport. I believe the CFS backport is just exposing the bug. Can't
find an obvious culprit and am looking into this issue.
Vincent, could you please confirm if you are able to reproduce this with
2.6.22.13 + CFS?
Thanks,
--
regards,
Dhaval
next prev parent reply other threads:[~2007-12-12 7:09 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 13:02 2.6.22.14 oops msg with commvault galaxy ? Vincent Fortier
2007-11-30 17:12 ` Randy Dunlap
2007-11-30 17:35 ` Fortier,Vincent [Montreal]
2007-12-04 13:47 ` Vincent Fortier
2007-12-07 22:15 ` Randy Dunlap
2007-12-07 23:11 ` Andrew Morton
2007-12-08 1:14 ` Randy Dunlap
2007-12-10 13:20 ` Fortier,Vincent [Montreal]
2007-12-10 14:03 ` Fortier,Vincent [Montreal]
2007-12-10 17:15 ` Randy Dunlap
2007-12-10 17:55 ` Fortier,Vincent [Montreal]
2007-12-11 14:54 ` Dhaval Giani
2007-12-11 16:43 ` Dhaval Giani
2007-12-11 17:04 ` Greg KH
2007-12-11 17:23 ` Dhaval Giani
2007-12-11 17:47 ` Fortier,Vincent [Montreal]
2007-12-11 18:20 ` Dhaval Giani
2007-12-11 18:25 ` Dhaval Giani
2007-12-11 19:08 ` Fortier,Vincent [Montreal]
2007-12-11 19:12 ` Randy Dunlap
2007-12-11 21:06 ` Ingo Molnar
2007-12-12 7:08 ` Dhaval Giani [this message]
2007-12-12 12:57 ` Fortier,Vincent [Montreal]
2007-12-12 13:05 ` Fortier,Vincent [Montreal]
2007-12-12 13:41 ` Dhaval Giani
2007-12-12 18:45 ` Fortier,Vincent [Montreal]
2007-12-13 11:43 ` Dhaval Giani
2007-12-13 12:55 ` Ingo Molnar
2007-12-13 13:02 ` Dhaval Giani
2007-12-13 13:12 ` Ingo Molnar
2007-12-13 13:43 ` Vincent Fortier
2007-12-13 13:24 ` Vincent Fortier
2007-12-13 14:41 ` Dhaval Giani
2007-12-13 13:59 ` Kay Sievers
2007-12-13 15:02 ` Vincent Fortier
2007-12-13 16:23 ` Kay Sievers
2007-12-13 16:50 ` Ingo Molnar
2007-12-13 17:10 ` Kay Sievers
2007-12-13 20:21 ` Ingo Molnar
2007-12-14 2:14 ` Dhaval Giani
2007-12-14 16:26 ` Greg KH
2007-12-14 17:07 ` Dhaval Giani
2007-12-14 17:28 ` Greg KH
2007-12-20 13:49 ` Vincent Fortier
2007-12-13 17:20 ` Dhaval Giani
2007-12-11 19:31 ` Greg KH
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=20071212070816.GA31455@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=Vincent.Fortier1@EC.GC.CA \
--cc=akpm@linux-foundation.org \
--cc=balbir@in.ibm.com \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=vatsa@linux.vnet.ibm.com \
/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