RE: 2.6.22.14 oops msg with commvault galaxy ?

[Fortier,Vincent [Montreal]]

> -----Message d'origine-----
> De : linux-kernel-owner@xxxxxxxxxxxxxxx 
> [mailto:linux-kernel-owner@xxxxxxxxxxxxxxx] De la part de Dhaval Giani
> 
> On Wed, Dec 12, 2007 at 07:57:33AM -0500, Fortier,Vincent 
> [Montreal] wrote:
> > > -----Message d'origine-----
> > > De : Dhaval Giani [mailto:dhaval@xxxxxxxxxxxxxxxxxx]
> > > 
> > > On Tue, Dec 11, 2007 at 10:06:53PM +0100, Ingo Molnar wrote:
> > > > 
> > > > * Fortier,Vincent [Montreal] <Vincent.Fortier1@xxxxxxxx> 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 ?
> > 
> > It got triggerred also using a 2.6.22.14:

Here are my preliminary test results:
       2.6.21.7: OK
   2.6.22.13/14: Failure
       2.6.23.9: OK
2.6.24-rc5-git2: OK

It seems to only hang using a 2.6.22 kernel.

> 
> No, not any more. Would it be possible for you to do a 
> git-bisect? I am not too well versed with sysfs, so it is not 
> apparent to me what is causing this oops. It seems to be 
> easily reproducible. I don't still have a reliable method to 
> reproduce it without the CFS patch. Could sysfs experts 
> please help debugging?
> 

I seriously doubt I have the time to do a git-bisect at the moment....

- vin
--
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/