On Thursday, 7 of February 2008, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>
> > > http://programming.kicks-ass.net/kernel-patches/sched-rt-group/
> > >
> > > on top of sched-devel.
> >
> > Indeed, with these patches applied the issue is not reproducible any
> >
On Thursday, 7 of February 2008, Ingo Molnar wrote:
* Rafael J. Wysocki [EMAIL PROTECTED] wrote:
http://programming.kicks-ass.net/kernel-patches/sched-rt-group/
on top of sched-devel.
Indeed, with these patches applied the issue is not reproducible any
more.
great! I've
On Thu, 2008-02-07 at 20:53 +0100, Rafael J. Wysocki wrote:
> On Thursday, 7 of February 2008, Ingo Molnar wrote:
> >
> > * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> >
> > > > http://programming.kicks-ass.net/kernel-patches/sched-rt-group/
> > > >
> > > > on top of sched-devel.
> > >
> >
On Thursday, 7 of February 2008, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
>
> > > http://programming.kicks-ass.net/kernel-patches/sched-rt-group/
> > >
> > > on top of sched-devel.
> >
> > Indeed, with these patches applied the issue is not reproducible any
> >
On Thursday, 7 of February 2008, Ingo Molnar wrote:
* Rafael J. Wysocki [EMAIL PROTECTED] wrote:
http://programming.kicks-ass.net/kernel-patches/sched-rt-group/
on top of sched-devel.
Indeed, with these patches applied the issue is not reproducible any
more.
great! I've
On Thu, 2008-02-07 at 20:53 +0100, Rafael J. Wysocki wrote:
On Thursday, 7 of February 2008, Ingo Molnar wrote:
* Rafael J. Wysocki [EMAIL PROTECTED] wrote:
http://programming.kicks-ass.net/kernel-patches/sched-rt-group/
on top of sched-devel.
Indeed, with these
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > http://programming.kicks-ass.net/kernel-patches/sched-rt-group/
> >
> > on top of sched-devel.
>
> Indeed, with these patches applied the issue is not reproducible any
> more.
great! I've queued Peter's fixes and enhancements up in
On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
>
> On Wed, 2008-02-06 at 23:18 +0100, Rafael J. Wysocki wrote:
> > On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
> > >
> > > On Wed, 2008-02-06 at 22:50 +0100, Rafael J. Wysocki wrote:
> > > > On Wednesday, 6 of February 2008,
On Wed, 2008-02-06 at 23:18 +0100, Rafael J. Wysocki wrote:
> On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
> >
> > On Wed, 2008-02-06 at 22:50 +0100, Rafael J. Wysocki wrote:
> > > On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
> >
> > > > Well, that whole queue.
> > >
> >
On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
>
> On Wed, 2008-02-06 at 22:50 +0100, Rafael J. Wysocki wrote:
> > On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
>
> > > Well, that whole queue.
> >
> > It doesn't compile for me.
>
> I did solve some compile issues since
On Wed, 2008-02-06 at 22:50 +0100, Rafael J. Wysocki wrote:
> On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
> > Well, that whole queue.
>
> It doesn't compile for me.
I did solve some compile issues since posting, Ingo should have the
compiling version in sched-devel soonish (don't
On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
>
> On Wed, 2008-02-06 at 19:25 +0100, Rafael J. Wysocki wrote:
> > On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
> > >
> > > On Wed, 2008-02-06 at 09:40 +0100, Dmitry Adamushko wrote:
> > > > On 06/02/2008, Rafael J. Wysocki
On Wed, 2008-02-06 at 19:25 +0100, Rafael J. Wysocki wrote:
> On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
> >
> > On Wed, 2008-02-06 at 09:40 +0100, Dmitry Adamushko wrote:
> > > On 06/02/2008, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote:
> > > > On Tuesday, 5 of February 2008,
On Wed, 2008-02-06 at 19:25 +0100, Rafael J. Wysocki wrote:
On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
On Wed, 2008-02-06 at 09:40 +0100, Dmitry Adamushko wrote:
On 06/02/2008, Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Tuesday, 5 of February 2008, Dmitry Adamushko
On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
On Wed, 2008-02-06 at 19:25 +0100, Rafael J. Wysocki wrote:
On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
On Wed, 2008-02-06 at 09:40 +0100, Dmitry Adamushko wrote:
On 06/02/2008, Rafael J. Wysocki [EMAIL PROTECTED]
On Wed, 2008-02-06 at 22:50 +0100, Rafael J. Wysocki wrote:
On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
Well, that whole queue.
It doesn't compile for me.
I did solve some compile issues since posting, Ingo should have the
compiling version in sched-devel soonish (don't know
On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
On Wed, 2008-02-06 at 22:50 +0100, Rafael J. Wysocki wrote:
On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
Well, that whole queue.
It doesn't compile for me.
I did solve some compile issues since posting, Ingo
On Wed, 2008-02-06 at 23:18 +0100, Rafael J. Wysocki wrote:
On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
On Wed, 2008-02-06 at 22:50 +0100, Rafael J. Wysocki wrote:
On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
Well, that whole queue.
It doesn't compile
On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
On Wed, 2008-02-06 at 23:18 +0100, Rafael J. Wysocki wrote:
On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
On Wed, 2008-02-06 at 22:50 +0100, Rafael J. Wysocki wrote:
On Wednesday, 6 of February 2008, Peter Zijlstra
* Rafael J. Wysocki [EMAIL PROTECTED] wrote:
http://programming.kicks-ass.net/kernel-patches/sched-rt-group/
on top of sched-devel.
Indeed, with these patches applied the issue is not reproducible any
more.
great! I've queued Peter's fixes and enhancements up in sched-devel.
(not
On Tuesday, 5 of February 2008, Dmitry Adamushko wrote:
> Rafael, any progress with this issue? (a few questions below).
>
> > >
> > > Does this artsmessage thing also run with RT priority?
> >
> > Well, it's in a strange state (after it's broken). From top:
> >
> > PR = -51
> > NI = 0
> > S = R
Rafael, any progress with this issue? (a few questions below).
> >
> > Does this artsmessage thing also run with RT priority?
>
> Well, it's in a strange state (after it's broken). From top:
>
> PR = -51
> NI = 0
> S = R
> %CPU = 0.0
> %MEM = 0.0
cat /proc/$PID/stat ; sleep 3; cat
Rafael, any progress with this issue? (a few questions below).
Does this artsmessage thing also run with RT priority?
Well, it's in a strange state (after it's broken). From top:
PR = -51
NI = 0
S = R
%CPU = 0.0
%MEM = 0.0
cat /proc/$PID/stat ; sleep 3; cat /proc/$PID/stat ?
cat
On Tuesday, 5 of February 2008, Dmitry Adamushko wrote:
Rafael, any progress with this issue? (a few questions below).
Does this artsmessage thing also run with RT priority?
Well, it's in a strange state (after it's broken). From top:
PR = -51
NI = 0
S = R
%CPU = 0.0
%MEM
On Friday, 1 of February 2008, Peter Zijlstra wrote:
>
> On Fri, 2008-02-01 at 12:50 +0100, Rafael J. Wysocki wrote:
> > On Friday, 1 of February 2008, Peter Zijlstra wrote:
>
> > > > It arts run as root, or does it use RLIMIT_RTPRIO to allow users to
> > > > execute realtime tasks?
> >
> >
On Fri, 2008-02-01 at 12:50 +0100, Rafael J. Wysocki wrote:
> On Friday, 1 of February 2008, Peter Zijlstra wrote:
> > > It arts run as root, or does it use RLIMIT_RTPRIO to allow users to
> > > execute realtime tasks?
>
> artswrapper is setuid root and RLIMIT_RTPRIO is apparently not used.
>
On Friday, 1 of February 2008, Peter Zijlstra wrote:
>
> On Fri, 2008-02-01 at 08:44 +0100, Peter Zijlstra wrote:
> > On Fri, 2008-02-01 at 03:04 +0100, Rafael J. Wysocki wrote:
> > > On Friday, 1 of February 2008, Rafael J. Wysocki wrote:
> > > > Hi,
> > > >
> > > > This is related to the
On Fri, 2008-02-01 at 08:44 +0100, Peter Zijlstra wrote:
> On Fri, 2008-02-01 at 03:04 +0100, Rafael J. Wysocki wrote:
> > On Friday, 1 of February 2008, Rafael J. Wysocki wrote:
> > > Hi,
> > >
> > > This is related to the problem I reported earlier this week:
> > >
On Fri, 2008-02-01 at 08:44 +0100, Peter Zijlstra wrote:
On Fri, 2008-02-01 at 03:04 +0100, Rafael J. Wysocki wrote:
On Friday, 1 of February 2008, Rafael J. Wysocki wrote:
Hi,
This is related to the problem I reported earlier this week:
http://lkml.org/lkml/2008/1/30/554
On Friday, 1 of February 2008, Peter Zijlstra wrote:
On Fri, 2008-02-01 at 08:44 +0100, Peter Zijlstra wrote:
On Fri, 2008-02-01 at 03:04 +0100, Rafael J. Wysocki wrote:
On Friday, 1 of February 2008, Rafael J. Wysocki wrote:
Hi,
This is related to the problem I reported
On Fri, 2008-02-01 at 12:50 +0100, Rafael J. Wysocki wrote:
On Friday, 1 of February 2008, Peter Zijlstra wrote:
It arts run as root, or does it use RLIMIT_RTPRIO to allow users to
execute realtime tasks?
artswrapper is setuid root and RLIMIT_RTPRIO is apparently not used.
Still,
On Friday, 1 of February 2008, Peter Zijlstra wrote:
On Fri, 2008-02-01 at 12:50 +0100, Rafael J. Wysocki wrote:
On Friday, 1 of February 2008, Peter Zijlstra wrote:
It arts run as root, or does it use RLIMIT_RTPRIO to allow users to
execute realtime tasks?
artswrapper is
On Fri, 2008-02-01 at 03:04 +0100, Rafael J. Wysocki wrote:
> On Friday, 1 of February 2008, Rafael J. Wysocki wrote:
> > Hi,
> >
> > This is related to the problem I reported earlier this week:
> > http://lkml.org/lkml/2008/1/30/554
> >
> > Apparently artswrapper, run by KDE in openSUSE 10.3
On Friday, 1 of February 2008, Rafael J. Wysocki wrote:
> Hi,
>
> This is related to the problem I reported earlier this week:
> http://lkml.org/lkml/2008/1/30/554
>
> Apparently artswrapper, run by KDE in openSUSE 10.3 with a real time priority,
> is mishandled by the scheduler. The problem is
Hi,
This is related to the problem I reported earlier this week:
http://lkml.org/lkml/2008/1/30/554
Apparently artswrapper, run by KDE in openSUSE 10.3 with a real time priority,
is mishandled by the scheduler. The problem is that after the user logs out,
artswrapper stays in TASK_RUNNING
On Fri, 2008-02-01 at 03:04 +0100, Rafael J. Wysocki wrote:
On Friday, 1 of February 2008, Rafael J. Wysocki wrote:
Hi,
This is related to the problem I reported earlier this week:
http://lkml.org/lkml/2008/1/30/554
Apparently artswrapper, run by KDE in openSUSE 10.3 with a real
36 matches
Mail list logo
