LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	"Ingo Molnar" <mingo@elte.hu>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [Regression] 2.6.24-git9: RT sched mishandles artswrapper (bisected)
Date: Tue, 5 Feb 2008 22:46:32 +0100	[thread overview]
Message-ID: <b647ffbd0802051346k563a44f7t42739515c130124b@mail.gmail.com> (raw)
In-Reply-To: <200802020040.05519.rjw@sisk.pl>

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 /proc/sched_debug; sleep 3 ; cat /proc/sched_debug

and also cat /proc/$PID/stat taken when this task still looks 'sane' :-/

Do you mean that only SCHED_NORMAL tasks can't run on this cpu or RT
tasks of high prio as well (so that maybe the scheduler is in
inconsistent state) ?
If the latter, the watchdog should have triggered after a while (if
enabled), I guess.

>
> Here's the corresponding trace from sysrq+t:
>
>  [<ffffffff8022fdb7>] ? try_to_wake_up+0x77/0x200
>  [<ffffffff8023573d>] __cond_resched+0x2d/0x60
>  [<ffffffff804ddce1>] _cond_resched+0x31/0x40
>  [<ffffffff804ddd24>] wait_for_common+0x34/0x170
>  [<ffffffff8022fdb7>] ? try_to_wake_up+0x77/0x200
>  [<ffffffff804ddec8>] wait_for_completion+0x18/0x20
> [ ... ]

does a stack trace always look like this?


-- 
Best regards,
Dmitry Adamushko

  reply	other threads:[~2008-02-05 21:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  1:37 Rafael J. Wysocki
2008-02-01  2:04 ` Rafael J. Wysocki
2008-02-01  7:44   ` Peter Zijlstra
2008-02-01  9:50     ` Peter Zijlstra
2008-02-01 11:50       ` Rafael J. Wysocki
2008-02-01 12:09         ` Peter Zijlstra
2008-02-01 23:39           ` Rafael J. Wysocki
2008-02-05 21:46             ` Dmitry Adamushko [this message]
2008-02-06  1:21               ` Rafael J. Wysocki
     [not found] ` <b647ffbd0802060040wbfe16afq4355e8f4f31ab06b@mail.gmail.com>
     [not found]   ` <1202288548.19243.47.camel@lappy>
2008-02-06 18:25     ` Rafael J. Wysocki
2008-02-06 21:43       ` Peter Zijlstra
2008-02-06 21:50         ` Rafael J. Wysocki
2008-02-06 22:01           ` Peter Zijlstra
2008-02-06 22:18             ` Rafael J. Wysocki
2008-02-06 22:34               ` Peter Zijlstra
2008-02-06 23:31                 ` Rafael J. Wysocki
2008-02-06 23:34                   ` Ingo Molnar
2008-02-07 19:53                     ` Rafael J. Wysocki
2008-02-07 21:20                       ` Peter Zijlstra
2008-02-10 12:30                     ` Rafael J. Wysocki

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=b647ffbd0802051346k563a44f7t42739515c130124b@mail.gmail.com \
    --to=dmitry.adamushko@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=rostedt@goodmis.org \
    --subject='Re: [Regression] 2.6.24-git9: RT sched mishandles artswrapper (bisected)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).