On Fri, 2013-01-11 at 06:22 +0100, Mike Galbraith wrote:
> On Thu, 2013-01-10 at 13:58 -0600, Shawn Bohrer wrote:
>
> > Here is the output:
> >
> > [ 81.278842] SysRq : Changing Loglevel
> > [ 81.279027] Loglevel set to 9
> > [ 83.285456] Initial want: 5000 rt_b->rt_runtime: 95000
On Thu, 2013-01-10 at 13:58 -0600, Shawn Bohrer wrote:
> Here is the output:
>
> [ 81.278842] SysRq : Changing Loglevel
> [ 81.279027] Loglevel set to 9
> [ 83.285456] Initial want: 5000 rt_b->rt_runtime: 95000
> rt_rq->rt_runtime: 9
> [ 85.286452] Initial want: 5000
On Thu, Jan 10, 2013 at 05:13:11AM +0100, Mike Galbraith wrote:
> On Tue, 2013-01-08 at 09:01 -0600, Shawn Bohrer wrote:
> > On Tue, Jan 08, 2013 at 09:36:05AM -0500, Steven Rostedt wrote:
> > > >
> > > > I've also managed to reproduce this on 3.8.0-rc2 so it appears the bug
> > > > is still
On Thu, Jan 10, 2013 at 05:13:11AM +0100, Mike Galbraith wrote:
On Tue, 2013-01-08 at 09:01 -0600, Shawn Bohrer wrote:
On Tue, Jan 08, 2013 at 09:36:05AM -0500, Steven Rostedt wrote:
I've also managed to reproduce this on 3.8.0-rc2 so it appears the bug
is still present in the
On Thu, 2013-01-10 at 13:58 -0600, Shawn Bohrer wrote:
Here is the output:
[ 81.278842] SysRq : Changing Loglevel
[ 81.279027] Loglevel set to 9
[ 83.285456] Initial want: 5000 rt_b-rt_runtime: 95000
rt_rq-rt_runtime: 9
[ 85.286452] Initial want: 5000
On Fri, 2013-01-11 at 06:22 +0100, Mike Galbraith wrote:
On Thu, 2013-01-10 at 13:58 -0600, Shawn Bohrer wrote:
Here is the output:
[ 81.278842] SysRq : Changing Loglevel
[ 81.279027] Loglevel set to 9
[ 83.285456] Initial want: 5000 rt_b-rt_runtime: 95000
On Tue, 2013-01-08 at 09:01 -0600, Shawn Bohrer wrote:
> On Tue, Jan 08, 2013 at 09:36:05AM -0500, Steven Rostedt wrote:
> > >
> > > I've also managed to reproduce this on 3.8.0-rc2 so it appears the bug
> > > is still present in the latest kernel.
> >
> > Shawn,
> >
> > Can you send me your
On Tue, 2013-01-08 at 09:01 -0600, Shawn Bohrer wrote:
On Tue, Jan 08, 2013 at 09:36:05AM -0500, Steven Rostedt wrote:
I've also managed to reproduce this on 3.8.0-rc2 so it appears the bug
is still present in the latest kernel.
Shawn,
Can you send me your .config file.
On Tue, Jan 08, 2013 at 09:36:05AM -0500, Steven Rostedt wrote:
> >
> > I've also managed to reproduce this on 3.8.0-rc2 so it appears the bug
> > is still present in the latest kernel.
>
> Shawn,
>
> Can you send me your .config file.
I've attached the 3.8.0-rc2 config that I used to
>
> I've also managed to reproduce this on 3.8.0-rc2 so it appears the bug
> is still present in the latest kernel.
Shawn,
Can you send me your .config file.
Thanks,
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Mon, 2013-01-07 at 17:02 -0600, Shawn Bohrer wrote:
> On Mon, Jan 07, 2013 at 11:58:18AM -0600, Shawn Bohrer wrote:
> > On Sat, Jan 05, 2013 at 11:46:32AM -0600, Shawn Bohrer wrote:
> > > I've tried reproducing the issue, but so far I've been unsuccessful
> > > but I believe that is because my
On Mon, 2013-01-07 at 17:02 -0600, Shawn Bohrer wrote:
On Mon, Jan 07, 2013 at 11:58:18AM -0600, Shawn Bohrer wrote:
On Sat, Jan 05, 2013 at 11:46:32AM -0600, Shawn Bohrer wrote:
I've tried reproducing the issue, but so far I've been unsuccessful
but I believe that is because my RT tasks
I've also managed to reproduce this on 3.8.0-rc2 so it appears the bug
is still present in the latest kernel.
Shawn,
Can you send me your .config file.
Thanks,
-- Steve
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On Tue, Jan 08, 2013 at 09:36:05AM -0500, Steven Rostedt wrote:
I've also managed to reproduce this on 3.8.0-rc2 so it appears the bug
is still present in the latest kernel.
Shawn,
Can you send me your .config file.
I've attached the 3.8.0-rc2 config that I used to reproduce this in
On Mon, Jan 07, 2013 at 11:58:18AM -0600, Shawn Bohrer wrote:
> On Sat, Jan 05, 2013 at 11:46:32AM -0600, Shawn Bohrer wrote:
> > I've tried reproducing the issue, but so far I've been unsuccessful
> > but I believe that is because my RT tasks aren't using enough CPU
> > cause borrowing from the
On Sat, Jan 05, 2013 at 11:46:32AM -0600, Shawn Bohrer wrote:
> I've tried reproducing the issue, but so far I've been unsuccessful
> but I believe that is because my RT tasks aren't using enough CPU
> cause borrowing from the other runqueues. Normally our RT tasks use
> very little CPU so I'm
On Sat, Jan 05, 2013 at 11:46:32AM -0600, Shawn Bohrer wrote:
I've tried reproducing the issue, but so far I've been unsuccessful
but I believe that is because my RT tasks aren't using enough CPU
cause borrowing from the other runqueues. Normally our RT tasks use
very little CPU so I'm not
On Mon, Jan 07, 2013 at 11:58:18AM -0600, Shawn Bohrer wrote:
On Sat, Jan 05, 2013 at 11:46:32AM -0600, Shawn Bohrer wrote:
I've tried reproducing the issue, but so far I've been unsuccessful
but I believe that is because my RT tasks aren't using enough CPU
cause borrowing from the other
We recently managed to crash 10 of our test machines at the same time.
Half of the machines were running a 3.1.9 kernel and half were running
3.4.9. I realize that these are both fairly old kernels but I've
skimmed the list of fixes in the 3.4.* stable series and didn't see
anything that appeared
We recently managed to crash 10 of our test machines at the same time.
Half of the machines were running a 3.1.9 kernel and half were running
3.4.9. I realize that these are both fairly old kernels but I've
skimmed the list of fixes in the 3.4.* stable series and didn't see
anything that appeared
20 matches
Mail list logo
