From: Con Kolivas <kernel@kolivas.org>
To: Con Kolivas <kernel@kolivas.org>
Cc: Grzegorz Kulewski <kangur@polcom.net>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.7-ck1
Date: Sat, 19 Jun 2004 15:26:00 +1000 [thread overview]
Message-ID: <40D3CE68.2000403@kolivas.org> (raw)
In-Reply-To: <200406191406.45750.kernel@kolivas.org>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
Con Kolivas wrote:
> On Sat, 19 Jun 2004 04:35, Grzegorz Kulewski wrote:
>
>>Hi Con,
>>
>>I have two problems with 2.6.7-ck1. My distribution is Gentoo Linux
>>unstable with all latest updates. Oh, yes, both 2.6.7-ck1 and 2.6.7-rc3
>>I tested have vesafb-tng applied from http://dev.gentoo.org/~spock/, but
>>it should not cause any problems because it is very non-intrusive patch I
>>think. Maybe you should include this in your patchset?
>>
>>1. When booting init script freezes after starting input hotplugging (it
>>is udev system). The only way to make it run is to press Ctrl-Alt-SysRQ
>>and various keys to display kernel state several times. After that system
>>starts normally. I do not know if it is only -ck problem because I had
>>no time to test 2.6.7 vanilla, but 2.6.7-rc3 worked fine. (Log included.)
>
>
> Yes I have a sneaking suspicion it's related to the fact kernel threads are
> fixed priority at the moment in staircase (they dont descend priority like
> normal tasks so act like relatively low priority real time tasks). I'm
> addressing that for the next version so hopefully that will fix it.
Here's a diff for -ck1 which brings you up to staircase7.1
Can you try that?
Con
[-- Attachment #2: from-2.6.7-ck1_to_staircase7.1 --]
[-- Type: text/x-troff-man, Size: 426 bytes --]
--- linux-2.6.7-ck2pre/kernel/sched.c 2004-06-19 15:12:15.280924354 +1000
+++ linux-2.6.7-ck1/kernel/sched.c 2004-06-19 14:58:08.000000000 +1000
@@ -334,8 +334,7 @@ static int effective_prio(task_t *p)
if (used_slice < first_slice)
return prio;
- if (p->mm)
- prio += 1 + (used_slice - first_slice) / rr;
+ prio += 1 + (used_slice - first_slice) / rr;
if (prio > MAX_PRIO - 2)
prio = MAX_PRIO - 2;
return prio;
next prev parent reply other threads:[~2004-06-19 5:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 11:22 2.6.7-ck1 Con Kolivas
2004-06-18 16:28 ` 2.6.7-ck1 Felipe Alfaro Solana
2004-06-19 3:48 ` 2.6.7-ck1 Con Kolivas
2004-06-19 5:20 ` 2.6.7-ck1 Con Kolivas
2004-06-19 8:39 ` 2.6.7-ck1 Felipe Alfaro Solana
[not found] ` <Pine.LNX.4.58.0406182004370.32121@alpha.polcom.net>
2004-06-19 4:06 ` 2.6.7-ck1 Con Kolivas
2004-06-19 5:26 ` Con Kolivas [this message]
2004-06-19 16:25 ` 2.6.7-ck1 Grzegorz Kulewski
2004-06-19 16:38 ` 2.6.7-ck1 Con Kolivas
2004-06-28 22:46 ` 2.6.7-ck1 Pavel Machek
2004-06-28 20:52 ` 2.6.7-ck1 kernel
2004-06-29 8:19 ` 2.6.7-ck1 Felipe Alfaro Solana
2004-06-19 21:00 ` 2.6.7-ck1, cfq ionice? Prakash K. Cheemplavam
2004-06-19 21:05 ` Prakash K. Cheemplavam
2004-06-19 23:18 ` Con Kolivas
2004-06-20 7:40 ` Prakash K. Cheemplavam
2004-06-21 16:02 ` 2.6.7-ck1 Brian S. Stephan
-- strict thread matches above, loose matches on Subject: below --
2004-06-19 20:50 2.6.7-ck1 AshMilsted
2004-06-19 23:10 ` 2.6.7-ck1 Con Kolivas
2004-06-25 13:48 2.6.7-ck1 Con Kolivas
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=40D3CE68.2000403@kolivas.org \
--to=kernel@kolivas.org \
--cc=kangur@polcom.net \
--cc=linux-kernel@vger.kernel.org \
/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