From: Brian Rogers <brian@xyzw.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mike Galbraith <efault@gmx.de>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [BUG] How to get real-time priority using idle priority
Date: Mon, 12 Jan 2009 17:05:58 -0800 [thread overview]
Message-ID: <496BE8F6.1040308@xyzw.org> (raw)
In-Reply-To: <20090112131406.GB670@elte.hu>
Ingo Molnar wrote:
> i've applied your fix to tip/sched/urgent and merged it into tip/master.
> Brian, you might want to test tip/master, as per:
>
> http://people.redhat.com/mingo/tip.git/README
>
> which now has this fix included. Can you make it break?
>
Yeah, I was able to trigger the same freeze again once on my desktop,
but it appears to be harder to trigger now. I couldn't get my program to
freeze the system, but one of the times I suspended then resumed BOINC,
it happened.
While experimenting on my laptop, things got into a funny state where
konsole froze, then gnome-terminal froze, so I just started launching
xterms. pgrep and pidof would freeze and never terminate. ps axl froze
after listing process 23681, which was a BOINC process. The next
process, 23682, was another BOINC process. Going into /proc/23682 and
running ls -l as root froze the shell. I figured out that ls -l exe was
enough to freeze it. I couldn't shut down BOINC because process 23682
wouldn't close, and kill -9 did nothing to it. top, which actually did
work, showed that process just continuing to run with around 100% CPU
time. I had to power cycle the system.
I'll try Mike's "more complete" patch on top of 2.6.29-rc1 and see what
that does.
next prev parent reply other threads:[~2009-01-13 1:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 10:58 [BUG] How to get real-time priority using idle priority Brian Rogers
2009-01-12 5:09 ` Mike Galbraith
2009-01-12 13:03 ` Mike Galbraith
2009-01-12 13:14 ` Ingo Molnar
2009-01-12 15:23 ` Mike Galbraith
2009-01-12 15:24 ` Ingo Molnar
2009-01-13 1:05 ` Brian Rogers [this message]
2009-01-13 2:58 ` Mike Galbraith
2009-01-14 5:13 ` Mike Galbraith
2009-01-14 5:31 ` Ingo Molnar
2009-01-14 6:02 ` Mike Galbraith
2009-01-14 7:35 ` Ingo Molnar
2009-01-15 9:28 ` Mike Galbraith
2009-01-15 10:14 ` Peter Zijlstra
2009-01-15 10:30 ` Mike Galbraith
2009-01-15 11:37 ` Mike Galbraith
2009-01-15 11:41 ` Peter Zijlstra
2009-01-15 12:54 ` Ingo Molnar
2009-01-15 13:05 ` Peter Zijlstra
2009-01-15 13:15 ` Ingo Molnar
2009-01-15 13:16 ` Peter Zijlstra
2009-01-15 12:07 ` Brian Rogers
2009-01-12 20:46 ` [patch take 2] " Mike Galbraith
2009-01-12 20:50 ` Mike Galbraith
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=496BE8F6.1040308@xyzw.org \
--to=brian@xyzw.org \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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